« Guven Oguz - A Short Groove | App News | haQ attaQ: Top 5 iOS AUv3 FX Plug-ins for 2018 »

Elastic FX Update

Elastic FX developer Oliver Greschke has been playing a lot of guitar lately. He got annoyed with the mess of pedals laying around so he packed all of their features into Elastic FX! Today's update includes a "preamp" section with a tuner, a new compressor, overdrive, and distortion. The update also includes a Big Reverb effect.

What's new in Elastic FX v1.2.0:

- Added Audioshare Export/Import
- "Open In" works from other apps now also
- Possibility to quickly record some audio in Audiofiles overlay
- Added Midi Bluetooth search
- New Big Reverb
- New Overdrive and Distortion effects especially made for guitar
- New preamp section (comes before other effects) consisting of:
- New Noise Gate / Compressor
- New Tuner
- Debugged Background Audio option
- Bugfixes and improvements

Reader Comments 9

No Auv3?

Future plans: No Auv3.
February 21, 2019  | person grammatonfeather
--> that makes no sense imho, even though every second is asking for it. Elastic FX is rather a "standalone app" than a "plugin" effect app and I don't know if the automation features, which is what makes Elastic FX different from other effect apps, would even work as AUv3! It would at least feel pretty differently.

Apart from the fact, that there are zillions of great AUv3 effects already. What makes Elastic FX different, is that it has 4 effect channels, and that you can route and automate these 4 effects and store all of this in the app itself. This would not be possible to do, if Elastic FX would be an AUv3 unit. Maybe I am wrong, but the idea of AUv3 is to store the apps data in the host app, therefore it would work completely different, if not to say it would not work at all !

Can you store automation data in AUM? I don't think so. Can you store automation data in Cubasis? Maybe, if an AUv3 fx unit gives out automation data as midi controller data to Cubasis. But then the automation data is stored to Cubasis and not in the effect app itself. The automations would be bound to that one Cubasis session and not available for other sessions, be it in Cubasis, other DAW's or in a standalone use case.
February 21, 2019  | touch_app O-G-SUS
AU can store information afaik. This app would be a great AU effect. And to be honest, I never use it BECAUSE it is not AUv3...so...And I think I am not the only one in this situation. Just to be clear with all devs of effects apps. No AU no buy, period.
February 22, 2019  | person_outline Hgoudha
you all have valid points.. i really like the independence of stand alone apps (from a studio perspective) . AUv3 is nice because one can add multiple instances in hosts (dependent though on other apps for functionality ).. but ... if you dont use it just because it is not an AUv3 - that doesn´t make sense...

maybe we will see a AUv4 which will allow apps to be simultaneously used as inserts(auv3 style) and as a standalone instances... ;)
February 22, 2019  | person_outline Spaced Invader
While I support the notion of making all apps AUv3, the practice of not using something useful because of its format seems like a classic case of "cutting off your nose to spite your face." There are dozens of excellent, unique, apps that will probably never get updated to AUv3, but do things that no other app does. Furthermore, these tend to be the apps (like Elastic FX) that really take advantage of the multi-touch-screen interface of iOS devices. So many of the AUs coming out are desktop ports with simple knob and button interfaces, which raises the question, "if you just want to use these desktop ports, why not use a desktop?" They're more powerful, more flexible, more stable, etc. What makes iOS interesting, IMO, are the weird apps that encourage interaction and really take advantage of the touch interface (Elastic FX, Samplr, Borderlands, Fugue Machine, Quantum, Patterning, Xynthesizr, Shoom, SpaceCraft; in that list only SpaceCraft is an AUv3). Would I prefer them to be AUs? Sure, but I'm not going to avoid them just because they're not! And forcing developer's hands with a "no AU, no buy" dictum will probably just result in more desktop ports and less innovation.

The advantages of AUs are:
1- multiple instances
2- state saving in the host
3- automation control

In Elastic FX's case, with Audiobus StateSaving and MIDI control, 2 and 3 are covered. And ElasticFX tends towards the extremes (as modulation is it's calling card), so putting multiple instances in a track would result in a very busy sonic field. Maybe that's what you need, but if you just want multiple instances of subtle modulation, there are plenty of other effects that cover that with less overhead.

Also, with regards to performance, I find that when I'm loading my iPad with lots of apps, opening the UI of an AUv3 will result in crackles and dropped audio. Switching to a standalone version of the app seems to have less of a performance hit - I'm assuming the simultaneous drawing of host and AU UIs pushes things over the limit. Note, use Audiobus app switching, not the iOS native switcher as that has a lot of animations that will cause a hiccup during the switch.
February 22, 2019  | favorite_border ajp
True but I really mean « effects » should be AUv3, not all apps. In your list, Elastic is the only effect. The other apps are generators. I am a bit more tolerant for this...at the moment
February 22, 2019  | person_outline HGoudha
😎
February 22, 2019  | person_outline Spaced invader
On February 22, 2019 - @ajp said:
While I support the notion of making all apps AUv3, the practice of not using something useful because of its format seems like a classic case of "cutting off your nose to spite your face." There are dozens of excellent, unique, apps that will probably never get updated to AUv3, but do things that no other app does. Furthermore, these tend to be the apps (like Elastic FX) that really take advantage of the multi-touch-screen interface of iOS devices. So many of the AUs coming out are desktop ports with simple knob and button interfaces, which raises the question, "if you just want to use these desktop ports, why not use a desktop?" They're more powerful, more flexible, more stable, etc. What makes iOS interesting, IMO, are the weird apps that encourage interaction and really take advantage of the touch interface (Elastic FX, Samplr, Borderlands, Fugue Machine, Quantum, Patterning, Xynthesizr, Shoom, SpaceCraft; in that list only SpaceCraft is an AUv3). Would I prefer them to be AUs? Sure, but I'm not going to avoid them just because they're not!
Very well said! :)
To be honest, as much I have to agree, that AUv3 is superior to IAA in a technical way, I don't like, where the journey goes at the moment. Many AUv3 plugins feel similar to desktop plugins indeed, with fiddly small knobs and buttons and it doesn't help fun to feed your host app with several instances of the same app, with a non inspiring interface. Why should I use an iPad when it looks the same as on my laptop? I want bold fullscreen apps and a user interface that creates some benefit of a touch screen. (even I praise the use of Midi controllers in that video, haha, well, but that's for poor guitar players, that need their hands for playing)

Even I am an iOS developer, I use a computer with a gigantic monitor as recording central most of the time, because I don't want to limit myself to one device (except on holidays). And I use iPad(s) and other hardware as my creative tool(s). I rarely use more than 2 apps at the same time on one device, because I want it to be simple, intuitive and creative! I rather use several iPads, each with a few fullscreen apps, than one iPad with lots of apps going on the same time. Of course this is very personal and luxury, because I own several devices for testing purposes, and it has the disadvantage of not being able to store it altogether, but I just find it more intuitive and inspiring this way. Again, my very personal choice, of course you might think the total opposite way.


In Elastic FX's case, with Audiobus StateSaving and MIDI control, 2 and 3 are covered. And ElasticFX tends towards the extremes (as modulation is it's calling card), so putting multiple instances in a track would result in a very busy sonic field. Maybe that's what you need, but if you just want multiple instances of subtle modulation, there are plenty of other effects that cover that with less overhead.

Also, with regards to performance, I find that when I'm loading my iPad with lots of apps, opening the UI of an AUv3 will result in crackles and dropped audio. Switching to a standalone version of the app seems to have less of a performance hit - I'm assuming the simultaneous drawing of host and AU UIs pushes things over the limit. Note, use Audiobus app switching, not the iOS native switcher as that has a lot of animations that will cause a hiccup during the switch.
Very well said again! :) It would not make sense to use several instances of Elastic FX, because you would end up in sonic mayhem, if you use all 4 effect slots. AND you would surely end up with crackles and audio dropouts, because 4 effect channels is heavy processing and several instances of that is even more heavy processing!

An AUv3 version of Elastic FX would work and would make sense, with one effect channel and then you could add several instances of it without crackling. BUT, then it would be a totally different app: The sound of Elastic FX is like it is, because you are able to use 4 fx processors at the same time and you have different routing options also that effect the sound.
So I can only say at the moment, use it as it is, or not. There are lots of videos about the app, that should give a good idea, what you can do with the app. If AUv3 is a main criteria for you - because that suits your workflow best - Elastic FX might not be your app indeed.
February 24, 2019  | touch_app O-G-SUS
On February 22, 2019 - @HGoudha said:
True but I really mean « effects » should be AUv3, not all apps. In your list, Elastic is the only effect. The other apps are generators. I am a bit more tolerant for this...at the moment

Understood. And to be clear, I’m not against AUv3 at all! But, given the choice between innovative app that takes advantage iOS’s strengths but isn’t an AU, or desktop port AU, I would vastly prefer the innovative app.

Of course, something like SpaceCraft that’s both is the ideal!

BTW, there are a several other non-AU effects apps that are unique and still fantastic:
Borderlands - I personally use it more to granulate real-time audio than as a source of audio. The motion recording here can create wonderful, rhythmic bursts of grain clouds.
Jasuto - node-based modular synth that can do some impressive processing of real-time audio (FFT/IFFT). It has a paradigm where the distance between nodes affects the level / value of signals between the nodes. With motion recording you can get very cool results.
Holderness effects - the XY pads in the iPad versions allow very nice morphing of parameters (I do wish there was motion recording)
Then there are effect apps that, while maybe not fully leveraging iOS’s touchscreen strengths, are still unique and IAA/Audiobus-only, like Moebius Lab or Fieldscaper.

On February 24, 2019 - @O-G-SUS said:
To be honest, as much I have to agree, that AUv3 is superior to IAA in a technical way, I don't like, where the journey goes at the moment. Many AUv3 plugins feel similar to desktop plugins indeed, with fiddly small knobs and buttons and it doesn't help fun to feed your host app with several instances of the same app, with a non inspiring interface. Why should I use an iPad when it looks the same as on my laptop? I want bold fullscreen apps and a user interface that creates some benefit of a touch screen.

This is ultimately what I’m concerned about. While there are more and better music apps than ever before, i find myself buying fewer and fewer. More are covering similar sonic territory and fewer are using the strengths of the platform.
February 24, 2019  | favorite_border ajp
comment

  Post a New Comment

You are not currently logged in. Would you like to login or register?
Enter your information below to add a new comment anonymously.

I'm not a racist, but...
Usernames need to be at least 2 characters!
I'm not a racist, but...
Please don't use weird characters in usernames!
{[ Ctrl.useravailable[Ctrl.userselector] ]}
{[ Ctrl.useravailabletext[Ctrl.userselector] ]}
Wow, that's a short email address!

Comment:

Do not use HTML in your comments. Tags: [b] Bold Text [/b] [i] Italic Text [/i]
Links will be generated if you include http:// or https:// at the beginning of a URL.
Submit