FabFilter AUv3 On The Way

OscarSouth

@richardyot said:

@OscarSouth said:

@richardyot said:

@OscarSouth said:
Otherwise, it puts the Auria Pro versions in a bit of a weird place going forward (nice to have but not worth the cost in a million years, if you already have access to the AU — and the logical one of the two to buy is the AU).

It really depends on the performance of the AU versions. In Auria you can run 20-25 instances of these plugins live (it depends on the plugin and the latency settings of course, but Pro Q2 for example is easy to run many instances of, Pro MB or Pro L2 are more CPU intensive).

The CPU hit looks good, but it would be interesting to hear from those who've bought the AU version how many instances they can run at once.

Yeah that's what I mean. Being able to run natively in Auria Pro would most likely be a huge advantage in compatibility and performance, but I can't see it being a realistic proposition for most users. I think the prices are better than fair, but unrealistic to double buy. Means that only users who already own the Auria Pro versions on this date will realistically be able to use them.

Well for the time being I would still certainly continue to buy the Auria native versions if any new plugins are released, and I have zero regrets about any of the purchases I made in Auria, including the recent Pro L2. But then I admittedly am a die-hard Auria fanboy.

The only thing that could muddy the waters would be if something like Logic for iOS was to drop tomorrow, then I might have to re-assess things.

Yeah, I would actually also be in the same boat (massively love Auria Pro in my workflow) but I never actually bought the plugins in the first place -- mainly use Auria pro for tracking/editing/arranging and the PSP channel/master strips have been more than good enough for those purposes. I can definitely see more use for them personally in a 'live host' like AUM or BM3 (still to this day I haven't settled on a reverb or delay plugin as my 'go to' for example).

stemshade

Au still has the 512 max buffer though right? A big plus is being able to crank the buffer up super high for big sessions. I routinely stick pro-q and a compressor and either fabfilter timeless or saturn on each track (8-10) plus pro r as a buss fx plus a limiter on the master.

obijohn

@vpich said:
Au still has the 512 max buffer though right? A big plus is being able to crank the buffer up super high for big sessions. I routinely stick pro-q and a compressor and either fabfilter timeless or saturn on each track (8-10) plus pro r as a buss fx plus a limiter on the master.

The 512 max buffet applies to MIDI, not audio. Now, there is a wrinkle here in that all (I think, haven’t confirmed that it is indeed “all”) the FF plugins have some type of MIDI functionality, like sidechaining on MIDI triggers or MIDI automation of parameters. So I’m not sure if that would mean the AU versions of these are limited to 512. I do know that is NOT the case in the Auria plugins. To actually use the MIDI functionality you’d probably need a MIDI track too so then you’d hit that limit. But just using them as an audio FX no.

stemshade

@obijohn said:

@vpich said:
Au still has the 512 max buffer though right? A big plus is being able to crank the buffer up super high for big sessions. I routinely stick pro-q and a compressor and either fabfilter timeless or saturn on each track (8-10) plus pro r as a buss fx plus a limiter on the master.

The 512 max buffet applies to MIDI, not audio. Now, there is a wrinkle here in that all (I think, haven’t confirmed that it is indeed “all”) the FF plugins have some type of MIDI functionality, like sidechaining on MIDI triggers or MIDI automation of parameters. So I’m not sure if that would mean the AU versions of these are limited to 512. I do know that is NOT the case in the Auria plugins. To actually use the MIDI functionality you’d probably need a MIDI track too so then you’d hit that limit. But just using them as an audio FX no.

The au limitation used to be on audio in auria pro too. So they lifted that?

richardyot

@vpich said:
The au limitation used to be on audio in auria pro too. So they lifted that?

I think it's in comparison to the native plugins, which can all run at 4096 frames. AUs are still limited for the most part, although apparently it's up to the individual plugin devs to allow for higher latencies.

Carnbot

I think it's time to give Apple feedback about crossgrade possibilities being good for the iOS consumer, which will also entice more desktop pro users who have already bought the entire desktop versions.

obijohn

@richardyot said:

@vpich said:
The au limitation used to be on audio in auria pro too. So they lifted that?

I think it's in comparison to the native plugins, which can all run at 4096 frames. AUs are still limited for the most part, although apparently it's up to the individual plugin devs to allow for higher latencies.

Maybe @WaveMachineLabs can chime in with clarification on this, but IIRC audio AUv3 FX plugins are not limited to the 512 max buffer size -- unless you've got MIDI tracks already in Auria, since the 512 max buffer is a CoreMIDI limitation (so if you've got even one MIDI track you are limited to 512 globally). The thing is, most of us are using AU instruments too, which implies at least one MIDI track is going to be present. But if it's a pure audio project with no MIDI, you can use an audio AUv3 FX plugin at higher buffer sizes, assuming of course that the plugin itself supports the higher buffer setting. I'm not a home right now but I can do a couple of tests later to confirm whether or not I'm just spouting nonsense here.

richardyot

@obijohn said:

@richardyot said:

@vpich said:
The au limitation used to be on audio in auria pro too. So they lifted that?

I think it's in comparison to the native plugins, which can all run at 4096 frames. AUs are still limited for the most part, although apparently it's up to the individual plugin devs to allow for higher latencies.

Maybe @WaveMachineLabs can chime in with clarification on this, but IIRC audio AUv3 FX plugins are not limited to the 512 max buffer size -- unless you've got MIDI tracks already in Auria, since the 512 max buffer is a CoreMIDI limitation (so if you've got even one MIDI track you are limited to 512 globally). The thing is, most of us are using AU instruments too, which implies at least one MIDI track is going to be present. But if it's a pure audio project with no MIDI, you can use an audio AUv3 FX plugin at higher buffer sizes, assuming of course that the plugin itself supports the higher buffer setting. I'm not a home right now but I can do a couple of tests later to confirm whether or not I'm just spouting nonsense here.

AFAIK that's exactly right. But most plugin devs have implemented 512 as the limit.

brambos

@richardyot said:

@obijohn said:

@richardyot said:

@vpich said:
The au limitation used to be on audio in auria pro too. So they lifted that?

I think it's in comparison to the native plugins, which can all run at 4096 frames. AUs are still limited for the most part, although apparently it's up to the individual plugin devs to allow for higher latencies.

Maybe @WaveMachineLabs can chime in with clarification on this, but IIRC audio AUv3 FX plugins are not limited to the 512 max buffer size -- unless you've got MIDI tracks already in Auria, since the 512 max buffer is a CoreMIDI limitation (so if you've got even one MIDI track you are limited to 512 globally). The thing is, most of us are using AU instruments too, which implies at least one MIDI track is going to be present. But if it's a pure audio project with no MIDI, you can use an audio AUv3 FX plugin at higher buffer sizes, assuming of course that the plugin itself supports the higher buffer setting. I'm not a home right now but I can do a couple of tests later to confirm whether or not I'm just spouting nonsense here.

AFAIK that's exactly right. But most plugin devs have implemented 512 as the limit.

That's probably because it's the default setting in Apple's AUv3 sample code. You have to manually change it as a dev

richardyot

@brambos said:

@richardyot said:

@obijohn said:

@richardyot said:

@vpich said:
The au limitation used to be on audio in auria pro too. So they lifted that?

I think it's in comparison to the native plugins, which can all run at 4096 frames. AUs are still limited for the most part, although apparently it's up to the individual plugin devs to allow for higher latencies.

Maybe @WaveMachineLabs can chime in with clarification on this, but IIRC audio AUv3 FX plugins are not limited to the 512 max buffer size -- unless you've got MIDI tracks already in Auria, since the 512 max buffer is a CoreMIDI limitation (so if you've got even one MIDI track you are limited to 512 globally). The thing is, most of us are using AU instruments too, which implies at least one MIDI track is going to be present. But if it's a pure audio project with no MIDI, you can use an audio AUv3 FX plugin at higher buffer sizes, assuming of course that the plugin itself supports the higher buffer setting. I'm not a home right now but I can do a couple of tests later to confirm whether or not I'm just spouting nonsense here.

AFAIK that's exactly right. But most plugin devs have implemented 512 as the limit.

That's probably because it's the default setting in Apple's AUv3 sample code. You have to manually change it as a dev

Yes I remember you saying that previously Would be good if word got out.

stemshade

@brambos said:

@richardyot said:

@obijohn said:

@richardyot said:

@vpich said:
The au limitation used to be on audio in auria pro too. So they lifted that?

I think it's in comparison to the native plugins, which can all run at 4096 frames. AUs are still limited for the most part, although apparently it's up to the individual plugin devs to allow for higher latencies.

Maybe @WaveMachineLabs can chime in with clarification on this, but IIRC audio AUv3 FX plugins are not limited to the 512 max buffer size -- unless you've got MIDI tracks already in Auria, since the 512 max buffer is a CoreMIDI limitation (so if you've got even one MIDI track you are limited to 512 globally). The thing is, most of us are using AU instruments too, which implies at least one MIDI track is going to be present. But if it's a pure audio project with no MIDI, you can use an audio AUv3 FX plugin at higher buffer sizes, assuming of course that the plugin itself supports the higher buffer setting. I'm not a home right now but I can do a couple of tests later to confirm whether or not I'm just spouting nonsense here.

AFAIK that's exactly right. But most plugin devs have implemented 512 as the limit.

That's probably because it's the default setting in Apple's AUv3 sample code. You have to manually change it as a dev

Ahh that’s it. I remember not getting audio using au plugins and set aum at 512, which is where i us au plugins. Since then i have only used fabfilters and native psp etc in auria since i only use it to mix and have the buffer at max.

lovadamusic

@AppleHorizon said:

@lovadamusic said:
iOS DAW-makers seem pretty maxed-out already. Auria Pro is one guy just trying to get and keep the app running well. I think Cubasis is a relatively small operation, and features appear regularly but slowly. I don’t know NanoStudio, but I hear a lot of talk… Do enough iOS users want to pay for much deeper features? And how many FabFilter AUs will people buy at full price? I guess it remains to be seen.

What would the pressure be for DAW makers? I’m not following the line of reasoning.

$$$ mainly. Having something of the stature of FabFilter as an iOS AU will entice desktop users to replicate their setups for mobile to do as much work as they can outside their desktop studio, which they'll return to when they need the more powerful cpu and ram on offer.

There will also be a push for cross compatibility in AUs so that a project can move from iOS to Desktop without issues if you also own the desktop AU, with full automation.

iOS has gotten by with some boutique DAWs up to this point, but desktop users buying into iOS AUs, especially if Pro-L 2 comes sooner than later, are going to want at least the limited intro level versions of their favorite desktop DAWs on offer for cross-compatibility, looking for a few steps up in UI and UX from the current iOS DAWs.

So, I am basically saying that the individual boutique devs are going to have intense competitive pressure from the major DAW companies having to expand their iOS divisions to respond to this demand which will start happening if this snowballs off of fabfilters lead, as I expect it will.

That's not a bad thing at all for me as a musician.

Some of the major DAW companies have some cross-compatibility at the moment, but their offerings are barebones compared to even intro versions of their desktop counterparts.

I often use GarageBand iOS whose files can open into Logic. For example, I own Sunrizer on both iOS and Mac. Now I'm in a situation where I can use Sunrizer as AU in GarageBand iOS, but if I try to open that file in Logic, it will say I don't have the AU for Sunrizer installed, even though I do have the desktop Sunrizer AU.

So, I need to ask for cross-compatibility for Sunrizer to make it a complete solution for me.

I have to believe a similar issue would arise from bringing Cubasis files into Cubase.

So I have to hope FabFilter have kept this in mind as they developed their iOS AUv3 implementation.

I'm all of a sudden very optimistic about what could happen within the next two years if things continue to develop this way.

I'm fairly certain that more desktop devs are going to realize they are leaving money on the floor if they don't also have iOS versions.

It also might put pressure on iOS AU devs to create desktop versions, too.

I think that makes sense, but it really depends on whether these $$$ actually exist for iOS music-making. I don't know why major DAW companies haven't been exploiting this presumed market -- I have ideas, but no inside info. It seems to me, the pro DAWs would come first, and then the pro plug-ins would follow rather than the other way around. If iOS AU FabFilters sell big at full prices, then companies should take notice. I kind of expect it won't be that dramatic, but I'd like to be wrong.

Longer term, I don't think it matters much. The technology is going to advance, and at some point there should be mobile solutions strong enough to attract the professional music production industry and with pricing that can support the big DAW makers.