Mixdown bug with Fabfilter Pro-Q

[TomSwitz]

Hi

First of all my compliments!
This is by far the greatest sounding app out there!
2 serious bugs with the fab filter q:
- when inserted in the master bus the master effects are bypassed, inserting it in a track instead is a workaround
- mixdown: any other setting than zero latency will produce bugs like freezing the app and buggy output file

Thanks for your support and keep up the great work!
Best,
Tom

iPad 3 iOS 5.1.1

[Rim]

Tom,

Thanks for the feedback on this. I've e-mailed Fabfilter to see if they can look into this.

Thanks,
Rim

[TomSwitz]

Thanks Rim

Also, I noticed in iTunes Auria produces project files with a size of over 400 mb. I know there is only 1 file for mastering in this project..
What is that?

Thanks, Tom

[Rim]

An Auria Project file is actually a "bundle". It's a special type of folder, and contains inside it the project file and all the audio files for your project. mixdown files are separate, and are found in Auria's main folder.

In the current version of Auria, if you delete a region, the associated audio file doesn't get deleted automatically, so it's possible that if you had audio files in your project before and deleted their regions, there's still some files in your project bundle.
The next update will automatically clean your project files each time it loads.

Rim

[TomSwitz]

Thanks Rim for your explanation, that makes sense.

Tom

[amonglights]

When is the next update scheduled to be released?

[Rim]

I can't tell you for sure, but I hope to have to sent to Apple by the end of the week. You can see the latest status by checking the Bug Status thread (look at the number of FIXED items).

Thanks,
Rim

[TomSwitz]

Hi

Unfortunately the bug is still there.
When FabFilter-Q is inserted in the master bus the Auria internal plugins are bypassed.
Since I'm using it for mastering, it makes the FabFilter-Q useless at this point!
Hope to see a fix soon!

Best,

Tom

[Rim]

We fixed this bug:

Doing a mixdown when Pro-Q is inserted on a track, and is set to a non zero-latency mode results in freezing


Is this still not working? I remember testing this, and it worked for me.

Rim

[TomSwitz]

Yes you fixed 1 bug.
But I described 2 of them and only one has been solved.

Try this:

Tweak the effects on the master channel.
Now put the Pro-Q as an insert in the chain.
Try bypassing the plugin and if you set it back on, you will hear what I mean.
Somehow it steals the audio away from the master channel.

Don't know what's going on, but it's definitely not right!
Let me know if you need anything else.

Tom

[Rim]

Tom,

Sorry, I must have forgotten to put that second bug on the list. I just tried what you said, and it's working for me here. Here's what I did:

1. Load the demo song (The Approach)
2. On the MasterStrip, press BYPASS in the upper left corner, then adjust the compressor to an extreme setting (Thresh to -30, Ratio to 10:1, Makeup to 16dB, Output control to +12)
3. Insert Pro-Q on the top slot. Draw a curve.
4. Press play. Pressing Bypass on the Pro-Q Bypass button works fine (I can still hear the compressor from the MasterStrip). Press it again, and I hear Pro-Q.

Rim

[TomSwitz]

Thank you Rim for taking the time to double check.
Hope this gets solved with the next update, since I'm using Auria mainly for mastering my app music.

Cheers,
Tom

[Rim]

But it's not doing it for me. Could you please look at my previous post and make sure I'm following the same steps as you are? It works perfectly fine for me.

Thanks,
Rim

[TomSwitz]

Sorry Rim

You were right.
After loading the Demo the bug disappeared.
Really really odd, no idea what that has been.
I've been always generating a new project with 2 tracks 44,1 khz, then pasting the audio into track 1, then tweaking eq, comp, lim. Nothing special, maybe it has to do with the licensing of the plugin.

Anyway, seems to work now. So I'm happy again!

Thanks for your patience.

Tom