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
Epic Dev achievement unlocked.
You're a far better man then me etc...and actually one could do a PhD thesis on the sociology of gender and social change as per a timieline from Lois Maxwell to Naomie Harris but I fear I have already threatened to derail this thread too far...Apologies EG, but wouldn't have happened (surely?) if the damn thingie was already here and out
Cheers @Samu for the info. Should be OK with that.
Noob type question but will the pads always be mapped to the same keys so I can map them to a 4x4 setup easily?
Yepp, you can set the start note for the first pad for the pads in the preferences.
The start note is global for all loaded kits as it's not saved with the preset...
Meaning if you set the start key in the preferences all loaded kits will use it
Awesome! So in NS2, I would be able to:
Load up Segments on a channel and receive midi from a different channel with Slate on it and play/sequence from there if I want to live drum it 4x4 style.
Route audio to a channel with Segment on it so I could sample whatever I wanted to it?
It kinda depends how the host handles audio-routing...
In AUM you can load sEGments in the effects slot and record anything.
In AUM though I prefer to record using AUMs built-in recording functions and import the perfectly looped clips into sEGments.
(In sEGments it's just a matter of loading the init preset and then load the file from the AUM folder in AudioShare).
Same procedure works in Cubasis too, save to MediaBay and use the document picker to load the file from the Cubasis folder.
This could work in NS2 as well, but the only way to record audio in that app is the Slate or Obsidian, this might change if/when NS2 gets audio-tracks...
Thanks @ElliottGarage I'm totally okay with devs making sure all the i's & t's are dotted and crossed before releasing an app. Too many have like these v.1 through v.2 defacto beta testing releases. I'm just impatient; the video's so far & the layout...just looks so cool.
Good luck brother, got mine pre-ordered & hopefully all of us iOS music production true believers will support the devs, especially class acts like Elliot.
You can create an empty track in NS2, put Segments FX on that empty track as the first effect, now you can create a MIDI item and send MIDI to that Segment FX, just as if it were an instrument AU, this includes sending MIDI from other tracks yes, you can now route any audio you want in to Segments FX via an audio send in the mixer too.
Note here that Segments record feature is extremely basic, turn it on, turn it off, no level setting, no threshold etc, these are things that hopefully get worked on.
Also note that Segments passes audio through, so when you route audio to Segments, if it is already playing on another track it will be doubled (Just messaged EG about this now, definitely should be an option for this use case)
Also note that there is no sample editing in Segments either, so you wont be trimming/normalising etc etc, the record feature is more of a bonus than a real feature right now, personally I would prefer to see an "open in" feature ala desktop apps, than EG wasting time on adding a full audio editor, Segments uses files.app, so in combination with a 3rd party audio editor, this would be very powerful.
Also note that you have to live within the bounds of NS2 limited AU FX support too, so no automation at all.
Sending files using 'Open In...' works for the stand-alone app but to import audio into the AUv3 one has to use either the Files.app pop-over and use Drag'n'Drop a file to the Plug-In window or use the -init- patch and tap the folder icon and use the document picker to choose a file or record when loaded as an Stand-Alone or AUv3 FX.
Worth to note though is that presets created in the stand-alone are directly available in the AUv3 as well and vice versa.
Yet there is nothing quite like that waiting room feeling. Once it is out it’s like pouring marbles out of the bag.
You kind of missed my point, I suggested that "Open in" would be better than adding in an audio editor, so from Segments the ability to "Open in" in external 3rd party audio editors, much like desktop software does, this negates the need for sample editing in Segments because going down that rabbit hole is never ending.
I would be happy to open in Auditor.
Ok, as iOS is now that would require one to save the edited sample to another location and the re-import it to sEGments and in that case it's better to record the audio in the other app which is what I do already.
iOS Sandboxing doesn't allow two apps to have access to the same file at the same time which can be done on the desktop.
This might work for linked files stored in iCloud but not files stored in an apps own container.
The 'Record' function in sEGments is a rabbit hole...
...and when sEGments gets one feature EG Pulse users want it too and that will increase the development time even further to keep both apps in sync.
In short the 'record' function could be removed without causing too much damage...
Another way to edit the recording would be sEGments had a folder in Files.app.
This way one could use Auditor to open the file from the sEGments folder for editing and then over write the file.
What sEGments then would have to do is to check if the file has been changed and update all the slice-marker locations of the preset to match the edited file.
The problem with this would be that the seamless sharing of presets between stand-alone and AUv3 would suffer since the files would no longer be in the shared container which is needed for the file sharing between the AUv3 and Standalone app.
Storing the presets on iCloud could be another solution for shared resources.
This way they can be accessed from Files.app, StandAlone.app and the AUv3.
The more I think about it I lean towards doing the actual recording in another app and keeping sEGments as clean slicer...
pls ppl -
make a small clear timestretch/pitchshift video for moi...:)
I guess that will sell it for many other ppl.
thanks!
@waka_x a quick video featuring timestretch is gonna be publish later today
What are you talking about ?
Record in Segments, "Open in" xyz app, edit, save file, reopen in Segments, this isn't rocket science or complicated.
You aren't getting two files in storage because Segments only stores files when saved as a part of host project or saved as a preset.
>
Problem appears when you do 'Open In...' from the AUv3. For the stand-alone app it works...
You can not use an sEGments AUv3 as the destination for 'Open In...' from the audio editor so you need to save it to a temporary location first.
That's great, thanks! Time stretching quality when slowing down vocal and percussive slices to about -30% is the major factor for me.
Three more questions if you don't mind, since i have thousands of loops that would take too much space uncompressed:
1. "Apple Loops" also includes compressed m4a/aac audio files with slice information embedded. Just to make sure: They're supported too?
2. Does your app support local folders so I can use categories and sub-categories like e.g. GuitarLoops/Blues/096bpm ?
3. What options are available for import and export of loops without internet, only local WiFi access?
as @Samu said to share presets and samples between AU3 and standalone version of the app I need to save files in a special app location that cannot be accessed by ios FILE app. I'm still studying to see if there's a solution.
@rs200 can you please send me some Apple loops in compressed format to [email protected] so that I can support them.
About local folders you can access from the app all the documents in your FILE app.
Also I want to remember that you can import files also via AIRDROP from any MAC or other iOS devices on the same WIFI....that's pretty fast and easy too!
Just a quickie: where do I actually find or have apple loops? Are these stored somewhere accessible (even if it’s from Apple?! 😳)
Basic record function is my number one use for the app, not just a bonus feature. I don’t need to trim or normalise, I just want to slice. If it were removed I would certainly feel the damage.
OK, Let me try and explain better.
1 You record a sample in Segments.
2 You use the "Open in" option (That does not currently exist in Segments) to open said sample in an external editor, for arguments sake Auditor
3 You trim and Normalise said sample in Auditor and then save as a new file to your chosen sample folder.
4 You load said sample back in to Segments via the load button.
No shared files, no bother, sample stored where you want it stored, and if the sample already exists on your iPad, then Segments shouldn't be saving it as part of the preset or project (It currently does, but that needs to be changed or be optional)
The above approach removes any need for any built in audio editor, which you need whenever you are recording obviously.
This simply does not work as iOS is today. It is not possible to 'live link' to a file outside the apps own 'container'.
A copy be it real or virtual is always made...
OK, so you are saying that an app cant send a file to another app using "Open in" ?
That's strange because I just did it in Audioshare.
Or are you talking about semantics that have little to nothing to do with what I suggested ?
(Segments creating a temp file in the background is of no interest whatsoever to the end user, and is near enough invisible to anybody as long as it is not permanently stored and inaccessible and never used, but I am fairly sure that the developer is a bit cleverer than that)
Another APP yes, but not to an AUv3 instance...
When did I ever mention an AU instance ?
Quoting to try and clarify, again.
Sure, here you are: See info@...