Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Ferrite shortcoming and workarounds
I’ve just started using Ferrite Recording Studio and am enjoying the time-saving features but have also found issues that cost time as well. I haven’t found a dedicated Ferrite forum or discord, so I’m posting this here and in other podcasting groups and other forums in hopes that others have found quick workarounds.
Each track has a volume control but it’s not like a typical mixer fader where the volume defaults to 0db and you and increase or decrease from there. In Ferrite, the track defaults to 0db, but that’s also “100%” so you can’t increase the volume any higher. This means volume automation can only go down. This has already cost me quite a bit of time as one of the tracks has very quiet passages in the source material where the podcaster completed voiceovers with the mic in a different position. I had to work around this by cutting out and moving these passages to a new track and apply an effect to get some extra gain, like an EQ or compressor.
No looping. When I’m setting eq, performing fine edits, or mixing volume against another track, I want to loop a section of audio. There doesn’t seem to be a way to do this. This results in me manually moving the playhead back for each pass.
Ducking. I’ve never had issues with ducking in any other app. Ferrite has only one attack/release parameter labeled “speed”. The volume of music underlying the spoken word was bouncing around jaggedly until I set “speed” to maximum which is the only way to slow down the release. Now, the first word is not really ducked fast enough. There needs to be separate attack and release controls. Also, ducking settings are global. That means my intro music has to use the same ducking settings as other musical segues which is not ideal. Volume automation is actually a better option than ducking, but is obviously much more time consuming.
Audio Units don’t have a bypass option. For example, I set up Brusfi and wanted to hear the difference it was making. Brusfi has a mix parameter so I used that to go from dry to wet because there is no bypass setting in Ferrite. If a plugin doesn’t have a mix parameter, you’ll have to remove the plugin from the track and add it back to hear the difference.
Comments
Ah, this was helpful as this setting was not elaborated to this degree in the user guide:
“ There’s an option in the Ferrite Settings to allow the volume to go over the maximum. This is off by default, so that no single track can clip. But if you switch it on, the scale of the track volume dials is changed so that they can amplify the audio above the clipping point. ”
It sounds like changing that setting would allow me to automate upwards.
Well, that setting does allow for a few more dbs of volume, but not nearly enough for my example. Automating the volume upwards to the new maximum for those phrases didn’t get them anywhere near the volume needed.
On one of the tracks, a very loud part has caused the rest of the track to be very quiet.
Can this but cut out and re-normalized in Ferrite or am I going to have to be tied to another audio editor for pre-editing-editing?
Here’s what I had to do with the track that had the quiet passages. It wasn’t just one loud spot that pushed everything else down in the normalization. The quiet parts are the exception, not the rule. I had to move those parts to a new track and use a compressor with significant amount of make-up gain to come anywhere close to the volume level needed.
These are both normal and expected scenarios considering how bad raw material from a client can actually be. This raw material is far better than what I’ve seen in the past, actually.
Of course, these volume-discrepancy issues render other Ferrite features less useful. Ducking and “strip silence” operate based on volume thresholds. I can’t even use strip silence without first fixing all of the above issues or whole phrases will be stripped.
Re-normalization is not an option that I can find. So, unless you can tell me another way to bring everything up past the limited volume fader, I have no choice but to use a plugin to raise up the gain.
I’m also now realizing you can’t overdub. Recording must be done outside of the project and then imported. I’m really wondering how this app is so popular when it has so many basic shortcomings.
Lumafusion is definitely slower for editing mainly because it’s a pain to move all following regions in sync……., but the ducking is actually usable, it has overdub with count-in, looping, ripple-editing, per-region volume control, etc. But in the end, it may be faster than Ferrite because it’s not self-crippled.
Ferrite excels at three things as far as I can tell, and that’s quick swipe deleting, scrubbing and the triple-tap to move all following regions in sync. Everything else seems to be a time-sucking headache. I’ve had to undo “strip silence” multiple times because of the volume issues I’ve described above so that’s another thing that I was hoping for that is a disappointment.
It looks like I’ll have to pre-edit in Cubasis or Auria, then use Ferrite for what it’s good at, then move everything back to Cubasis/Auria (or probably Lumafusion for ducking ease) to mix.
I did just that and provided a link to this thread.
Using a Compressor is the best way to go to adapt to loud clicks… unless you edit them out
After you normalize the audio.
Be sure to contact the developer with any big issues you find. He is fairly receptive to bug reports and suggestions to improve the app (based on prior comments of podcaster Jason Snell).
@Sabicas I used Ferrite to arrange snippets from Audioshare, which it did fairly well.
It doesn‘t loop, but the fast forward/backward buttons could partially compensate this by inserting one or two cuts (tap track, move playhead to loop start, snip, move playhead to end, snip). Not great, but did the job.
I liked the way the playhead reacts and it‘s precision and the screen action in general.
Automation points can be dragged by finger, but I preferred playhead positioning and dialing the control on the left side. It‘s got some distance awareness, so an existing point doesn‘t need to be hit precisely.
Imho this might serve for manual ducking (one dial up, one down), but takes a bit to get used to the scaling... as it takes to get used to the fake shift-tapping (multiple selections by holding one and tapping another) without dragging the 1st from it‘s position.
This may read humble, but Auria would simply drive me mad on the same task.
Ferrite could really be a great audio editor, if some features would be added or more elaborated.
Of course I stick with SAW Studio, which is at least 5-10 times more efficient or even Pro Tools 5 TDM (which I made mimic SAW by USB Overdrive mouse programming), but IF I had to cut/edit in IOS, I‘d pick Ferrite.
Yeah, he sent me the same. Solid response.
Good answers.