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
Sound Test Room video would be nice right about now. Just sayin'.
This thing does amazing things to drum loops..
is it easy to create seamless loops even though the waveform display does not have zooming, and are there any pops/clicks with the loops that you make?
also can you audition music from your iTunes library before importing into the editor?
Yes, you can grab the waveform with two fingers and slide along until you are happy then 'lock' that portion to loop. Please someone tell me how to switch on the damn FX though. I have a file playing and I am altering various settings but it's not effecting the signal. HELP it must be so obvious.
Sorted, thanks.
trueyorky can you browse and audition your iTunes library before importing into the editor?
It looks like you should be able to. A box pops up saying preview but nothing happens when I press it although that could be down to the file types in my library. The manual gives the following message...
NOTE'that'only'WAV'or'AIF'files'in'the'iTunes'library'are'loaded'into'the'app
okay, that's exactly what I wanted to know,so it won't convert the files allowing you to use your mp3 library but any wave files in your library they'll use. I want to use it with impc pro anyway, so I suppose I could sample with that then copy paste into css and then resample back into the impc pro through the iaa slot
this app is still a bit pricey, i wish they would lower the price at least until they get the audio bugs worked out
Oh, this is so good. I feel like I've had my money's worth already. Love it.
No audio bugs found here. I think the errors I experienced were just me being too eager and trying to load files while another was playing. Well worth the asking price imo.
How does this thing compare to Turnado? What's the deal with the vocoder? It's a pitch effect?
Anyone having issues with connecting to Dropbox? I've had a few crashes and also error messages. Still glad I took the plunge,
@thinds said:
Hmmmm, not showing up at all in AB for me...
Works in AB for me but my ipad3 can't hack it running when other apps are running too. Dropbox issues but Dropbox>audioshare>audiocopy>csSpectral is working.
Hopefully a reset sorts out the Dropbox issue because that would be a great workflow from Reason 7 and Reaktor to this and back to the PC.
Really loving this app, just playing round with some bell samples and I fell asleep
must of hit some hypnotic frequency 
@Buska said:
Thanks for responding. Have deleted and reinstalled but still no AB. Very strange.
@papertiger said:
>
Im guessing youve already tried opening it before opening audiobus? Thats the only way it would work for me.
Yep. Tried that too. Interestingly, AB database says csSpectral does not support AB.
Also throwing up errors when I try to use it as IAA in Audioshare.
What iOS are you on? I am still on 7.1.2
Me too. This is nuts. IAA errors in Auria and Cubasis. I've even powered down the ipad, then powered back up.
That is very strange. I used it on-and-off for a couple of hours last night, in various configurations, and it didn't miss a beat.
Edit: what buffer size are you running in AB and CS? I ran it at 256 and 512 no probs.
Switched both to 256 and nothing. Restarted ipad, nothing.
Anyone want to save an AB preset, share it, and see if that works? I'm baffled. Maybe it's the combo of apps i have on my ipad? No idea what could explain this...
Audiobus preset 'Spectral Echopad': http://preset.audiob.us/P9rU229sWE5nkQZ
Try this
@thinds said:
You're the best for uploading the preset. I tested it out and the input slot for csSpectral just sits there sleeping. It says tap to launch, but nothing happens when I tap. The icon for csSpectral is also not visible.
This is totally weird. I have no idea what the issue is, but csSpectral does not work in AB or as IAA on my ipad (ipad 4).
You obviously tried starting Spectral before loading the preset? Must be some weird iPad4 thing. I'm out of ideas anyway.
Yes, I did. Going to restart one more time and give it a try. Guess I'll have to email Boulanger labs tomorrow... Maybe someone else will have the same issue (not that I want anyone to!)
Here is the email that I sent to Boulanger Labs this morning. In case anyone else is having issues with Audiobus, there appears to be a "fix" for it. I've bolded and italicized it below.
First, congrats on the release of CsSpectral. Functionality and sound-wise it's totally worth the wait! I can't wait to dig into it, which is why I'm writing to bring some issues I've been having with the app to your attention. I'm using an iPad 4, with the latest version of iOS 7 (7.1.2), and the latest version of Audiobus 2 (2.1.5).
After downloading CsSpectral and using it for the first time I used it with an Apogee Duet. I'm not sure if that's relevant for bug hunting purposes, but I want to be as detailed as possible. To get a feel for the program, I used the default preset, the one with the acoustic guitar riff. Everything worked really well.
After a little while I changed locations, unplugged the Duet and set out to test CsSpectral with other apps. I wasn't using headphones -- I was just using the built-in iPad speaker. When I went to load CsSpectral into Audiobus, it wasn't showing up in the list of Inputs, Effects, or Outputs. It just wasn't there. At all. I then tried to load CsSpectral as an IAA in Audioshare. I received the error that an IAA node could not be created.
I deleted CsSpectral from my iPad and installed it again,with no change in behavior. It was neither listed in Audiobus, nor did it work in Audioshare as IAA. I then tried to use CsSpectral in Auria as IAA -- again it wasn't listed, although I did notice that there was a new entry in the list of available IAA: "filter." I tried it, and I received an error. I then downloaded Cubasis to try things out, and also got an error when trying to load CsSpectral as an IAA insert effect. (Please note that I followed the workaround when an IAA crashes, i.e. to start the app that crashed from the home screen, shut it down, and then try it again. This workaround did not fix the problem).
Someone on the Audiobus forum was kind enough to post a preset using CsSpectral in Audiobus, so I tried to load that. Although the other two apps loaded just fine, the Input slot, where CsSpectral was supposed to be loaded, was sleeping, and the icon was blank. Nothing. I also tried to make sure that both apps were using the same buffer setting (256), but that didn't help either.
Finally, I went to the Discchord forum, where someone had posted a "fix" for people having Audiobus issues with CsSpectral. The workaround was to start CsSpectral with an "Init" preset, switch to Live Input mode, and unmute. To my surprise, this worked. I closed all of the apps, and started Audiobus, which finally showed up on the Audiobus list.
This morning CsSpectral is showing up in the Audiobus lists as expected, but IAA is still not working.
Please let me know if you have any questions about any of the above. Hopefully it will help you figure out what's wrong with IAA for CsSpectral.
Thanks.
Lol, the [email protected] email address has thrown an error at me too. yay!
This is stunning. Such fun to play around with even a simple audio loop.
It definitely needs patching a bit to make it more stable, but I understand that's already happening. I had some issues with using it in the FX slot, but following the init advice above, AND making sure that the audio buffer settings in the app match those in Audiobus itself, sorted it. If the buffer settings don't match, no live input will be processed. It took a while to figure out why I had to load the app before Audiobus for live input to work (cos then it controls the buffer setting), but after matching the buffer setting, I don't have to do that. The default is 512, and for live input you really want 256. Simply change it in the settings menu and you're good to go whenever you want to introduce the app into the signal chain.
What about on its own with loaded files?