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.
Comments
I just tried Flowtones on my (other iPad) 6th Gen 2018 base/iPadOS13.7.... and have the same flashing keyboard issue.
So it's apparently an issue on both the 5th & 6th Generation base ipads (..as well as any other models reported by others).
I don't know if it's common knowledge, but I just realized that different instances can use different color schemes. It's all saved and recalled in AUM. Very cool, makes it easier to differentiate instances.
BTW I see the same problem with the flashing keyboard, (base iPad 2020, iPadOS 14.7.1) but only if I force it by playing some speedy nonsense, not in real usage
Right, the image refresh seems to be hampered most with rapid playing, especially multiple notes at one time.
A fix for the visual keyboard glitch is on its way through appstore review.....
It took me some time to figure out that I have to first tap to select... then tap again and hold on the patch... then drag it exactly to the side, and it becomes movable.
I started by dragging diagonally, and it did not work. Also, I'm finding I have to start with an unselected patch.
That was quick.. Thank you!
That works - thanks! (FROM a GUI perspective anyway)
Unfortunately, patches are not assigned to the new category.
I'm moving patches from "bass" to "Bass" using the above method, but when reopening Flowtones, they are still assigned to "bass".
Also, when "bass" category has no patches left after reassigning them all via drag\drop, the "bass" category does not disappear. This is strange, since "bass" and "Bass" are treated as two separate categories in the Category list, so I would have thought the internal reassignment operation was case sensitive too?
Just discovered that changes to category are not working either with the older method, of selecting patch, Clicking "Category" and changing manually from "bass" to Bass.
To get this to work, I have to drag to a temporary category, and then to the final category i.e.
I cannot drag & drop or rename category from "bass" to "Bass" in one step, but have to go from "bass" to "temp" to "Bass".
Great update though @DJB!
Is anyone able to confirm this behaviour with moving patches between two categories which only differ by case?
Fantastic!
And... it's fixed.
How can I initialize the patch ?
In the randomizer window, there is a reset button.
Fastest way I’ve found is to use the dice and tap ‘reset’ or load a template preset.
I have made my own init preset as I’m not too fond of the default 10db velocity > level setting per oscillator setting.
So yeah, fastest way is to make your own default preset and load it.
Is the batch import of entire user preset banks (a'la Richard, for example) not yet implemented, or have I been reading the update descriptions not carefully enough?
Click 'Load' and then 'Import set'. Choose the zip file to import. That's it.
On my way to the store then.
Thank you!
@DJB there's one thing I'm curious about, but keep forgetting to ask - why is the Cutoff knob bipolar? It's quite unusual and the manual doesn't mention anything special about it.
I've wondered this myself as well...
...the only logic I can find is that it starts at a 'center frequency' to cater for different filter types (LP/BP/HP etc.) so nothing is 'silent' when selecting a filter type. If for example the filter started at 0 and LP was selected everything would be silent as the cutoff frequency would be close to 0.
Maybe there's an even more rational explanation to this?
Could it be that it starts at the note? So it accounts for keyboard tracking at 100%?
@DJB my apologies if this has already been answered. Is there a way to hide the app keyboard when using as an AU?
Yeah, that's an other very reasonable explanation.
Exactly. It's an offset to the current MIDI note (assuming key tracking is set to 100%). Hence +12 means that the cut-off frequency would be 12 semitones above the MIDI note that is used for the voice. Similarly, -12 would an octave below the MIDI note.
Yes the keyboard will disappear automatically if you change the aspect ratio to be wider. This only works on iPad though.
The issue here is that the iOS file system is not case sensitive while trying to read a file. Hence you can create a patch called 'Name', but if you try to read a non-existent file called 'name', it will load 'Name' instead. To resolve this, we currently don't allow 'Name' and 'name' to be present simultaneously. There may be better solutions for this that we are looking into but it's unfortunately a hard problem to crack without running the risk of users accidentally overwriting files that only differ by case in the path name.
Thanks for your reply.
Not sure if I’m understanding here ... I had both “bass” and “Bass” in the Category list (and both “pad” and Pad” etc) which is why I started renaming all the “bass” ones, which is when I discovered the issue.
Are we describing the same phenomenon?
Yes. You can have 'bass' and 'Bass' as category if they are in different libraries (e.g. different parent folders) but they cannot co-exist in the same folder (library). As an example, on your mac, try to make two folders called 'Bass' and 'bass' in the same parent folder. You'll see that macOS doesn't allow you do this if you've installed a case-insensitive version of macOS (which is the default), and hence our app can't do this either.
Any plans to fix this for the iPhone? It makes the app pretty unpleasant to use as an AU because it makes the rest of the controls smaller than necessary
Would be possible to have routing options for the sequencer?
Like having a Part A and Part B switch in the sequencer page
Got it - thanks again for your responsiveness
No worries :-) Just wondering if auto capitalization would solve this (if you would enter 'bass' as new category, library or patch name it would auto capitalize to 'Bass').
That would be a quick solution