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
@JohnnyGoodyear Wohoo, that's the 'root' folder of the iOS-Device. Is your device by any chance 'Jail-Broken'?
I've been able to 'import' complete folders from AudioShare using 'Cloud/iOS-FIlepicker.'
@BastienCo The 'path' to 'samples' recorded in BeatHawk is definitely broken as a newly recorded samples need to be 'loaded' from the 'Records' folder before they are playable and show up in the 'Sample' tab...
Also sometimes the 'User Library' is not 'refreshed' after import (need to select another 'Library' and return to 'User Library' for it to show)
Hope these issues get sorted out ASAP.
@Samu Nope. Not broken over. Not my style or my skill-set....but I did have a moment of 'the Emperor, no clothes, behind the curtain.....'
Yes syncing with Cubasis is only with IAA, it is not a midi clock, I just receive host state so I know its position in time.
With audiobus I did not find the possibility of syncing as I would with IAA..
In collections you cannot remove only certain samples, the collection cannot be modified.
I added a popup on startup that ask if you want your session restored (so you can discard your sessions if it is too heavy, If you decide to load it anyway it wont kick you out anymore, because Apple don't allow you to stay too long in the loading screen).
Also, I added the autosaved file in the documents so it can be retrieve easily in case>
@RustiK said:
I'll have a look at this, thanks
Thanks for your suggestions!
The bug of the pad not working after recording is fixed (will be in 1.1.1), I'll have a look at the refresh..
mmmh, I though I fixed that already, I'll have another look.. It was after importing with audiocopy right ?
@BastienCo Just a quick question that popped-up...
There seems to be no way to apply 'groove' or 'quantize' to already recorded material as both 'groove' and 'quantize' are 'baked-in' during pad-recording. Is this 'by-design' or something that will be an option in the future?
Alternative approach for this would be to keep the recording 'as is' and apply the 'groove' and 'quantize' in real-time, this would make it easy to experiment with different 'groove' and 'quantise' values for each pad (1/4 for kicks, 1/8 for snares, 1/16t for hi-hats as an example) without having to re-record everything. Optionally it should be possible to 'burn-in' the 'groove' and 'quantize' values to the pattern.
Another idea for the 'Pads' would be to be able to trigger multiple notes (chords for instruments) at once.
This could be done by selecting multiple notes in 'Pitch-Mode'. This could also be used to set the 'default pitch' for the pad.
Nice to see that recording location will be fixed in the next version
If on the top left of the browser it does say "Refresh" or any message, just wait, beathawk is indexing the packages. If there is no message at all try to go to Beathawk documents from iTunes on your PC/MAC and delete beathawk.db, then restart the app. Tell me if this changes something.
It works perfect now
Exceedingly good news. Thank you, Bastien!