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
@satoshiszk I played with it for 10 minutes and bought it! Man this is awesome. It is the glue between my ipad and desktop I was waiting for. Thank you.
It is just unreal to setup an instrument in a DAW and add SideRack filled up with ipad effects and do some freaky stuff and sample it in the DAW.
@satoshiszk Ok I took the plunge and brought Siderack. As I like to mainly use my effect iOS apps with desktop plugins and enjoy combining iPad a Mac.
I Enjoy the flexibility this setup brings over IDAM had one crash which I think was due to having IDAM running at the same time which initially thought was needed. Actually having both running means you can either use the desktop VST and or the app to change settings with a mouse which is interesting.
I am getting one or 2 connection problems at times and there is a bit of a delay whilst the server VST connects.
Are there any plans to make the app a AU for sending midi in out into iPad hosts from midi generators scripts , apps on desktop ? Also maybe audio. I know Studiomux was IAA compatible.
In Ableton I’m not seeing the midi Siderack listed where would I find that? The midi VST, component shows up in Bitwig and Logic.
Also sometimes the apps symbol picture is shown other times it’s just the apps name in the server and Duo app is there a reason for that ?
Would be great if instruments, audio effects, midi effects could be split up into there groups rather than showing in every list at least on the instrument side but hey ho that’s probably down to individual developers of all the apps.
Hope you can keep the app and ecosystem supporting as it’s not the cheapest thing for what it does but it does it pretty well.
Is it possible to connect two iPads ?
No.
I have 3 ipads (pro, 9th & 7th) loaded in Bitwig in 3 instances of SideRack on 3 seperate tracks.
Initial I had some bad distortion, I had to change sample buffer size and sample rate in Bitwig.
When adding new plugins from the vst there is some slow down while playing, otherwise it works.
Adding a plugin on the ipad self will not cause slowdowns.
In the SideRack vst I can choose any of the 3 ipads.
good to know!!
thanks
I assumed @veitz was asking if you could connect two iPads directly to each other. I didn't realize that they could be asking if it was possible to connect two iPads to one Mac. Thanks for that answer.
-
Well now I am in doubt
I love how our brains are wired differently.
This is great. I often start things in loopy pro or the circuit tracks and then move over to logic on the Mac to put things together. This should really speed the up and add lots more options.
I’m playing with the trial at the moment and have seen the midi recording to be a little off e.g recording midi from Riffer or ChordJan into a midi track on Logic puts the notes after the beats. It could be cleaned up easily with a manual quantize but has any one else seen this and managed to rectify?
Currently, "SideRack MIDI Effect" transmits both audio and MIDI to the Duo app. We plan to enable MIDI transmission through "SideRack AudioEffect" to control effect parameters via MIDI Learn. Updates are forthcoming.
Technically speaking, the SideRack Plugin is the client side, while Duo is the server side.
Thanks. We are so glad to hear about your positive experience🙂
Could you provide more details about your issues? We'd like to fix problems users are facing.
Currently, we have no plans to make the Duo app AUv3 or IAA compatible. In what scenario would you love to use the app within such standards?
We apologize for the inconvenience with the AU component not appearing in Ableton's browser. This issue is under investigation. Meanwhile, the VST MIDI effect can be used as an alternative.
The SideRack plugin cannot directly access the icon images of AUv3 plugins on iOS devices. While we could implement image data transfer, it would consume additional bandwidth and potentially impact audio processing quality.
Currently, the list offers text search only, but we are considering adding filters to sort AUv3 plugins by type (MIDI Effect, Audio Effect, Instrument).
Wow! 78$ and that's the sale price, nonono nocando. Guess I'll keep connecting from interface to interface, not as cool but completely "free".
Interesting plugin, but I prefer to use IDAM because with IDAM I also have the possibility to send Midi CC to the iPad.
In addition, I can hardly use SideRack with my iPad Pro 2015 under 1024 samples without risking a high CPU utilization in Ableton 12. 128 samples is no problem with IDAM and my iPad Pro 2015.
-
@satoshiszk Thanks for getting back. All fair responses. Once I had a bit more time using Side Rack our update you on any issues. It’s mainly the server plugin on my Mac drops out randomly now and again but could be user error as still getting use to using it in different DAWs.
How would I send audio from a synth app on my iMac Mini from a DAW and receive the audio inside AUM or Cubasis 3 on my iPad? That’s what my thinking was around making DUO app a AUv3 maybe it’s not possible yet or maybe there is another way. I need to experiment more. Do you plan on putting out any videos for different user cases ?
Did the plunge today and bought a license. Works good, latency is still very high, but useable. Minor drawback: Buttersynth lets the app crash after few minutes. I hope this app gets continuously improved, stability and latency wise. Very nice and keep up the good work mr developer.
Thank you for the detailed explanation.
Currently, receiving audio from Mac's synth plugins on an iOS DAW is not supported. The goal of this product is not to simply provide a method for sending and receiving audio, but to offer a higher-level, comprehensive solution to use iOS plugins within a Mac-based DAW. The use of Mac plugins within an iOS DAW might diverge from this goal, considering the significant difference in the roles of each device. This issue cannot be resolved merely by making the Duo app compatible with AUv3 or IAA standards and might be better developed as a separate product. Regardless, your request will be seriously considered. Thank you for your request.
@satoshiszk I'd like to thank you for developing this tool, once set up and working it's going to be the glue that holds my rather chunky old plugins together with my Mac!
I want to ask for some advice/confirmation about functionality though - I'm running Duo on my iPad Pro 12.9 3rd gen (also tried on my iPhone Pro Max 15) and SideRack Midi Effect on my MacBook Air M2 as a plugin in Bitwig.
I'm able to connect to Duo and get audio from my plugins with no issues after tweaking the buffer a little, and I'm quite happy with the latency.
However, I seem to be unable to send Midi over to any plugins (I've tried a few different plugins) - using the "Midi effect" Sidetrack plugin - if I send any midi down to the Duo app then both the plugin and the Duo app immediately crash and must be restarted.
Is this a current limitation of the software, or am I doing something obviously wrong?
It's an interesting concept and the comparisons with Studiomux are fair though it's much more cleanly executed.
Very useful for using your iOS/iPadOS device as a non realtime processor for sure but not gonna cut it for realtime performance.
One interesting thing, as an experiment, I tried to send a MIDI PC to the SideRack AU plugin in Ableton Live 12. It triggers a shutdown of the app on the iOS side -- this is repeatable. When you reopen the app it remembers where you were, or the plugin is calling the previous state up. Anyway, FWIW, MIDI PC does not get passed through to the iOS/iPadOS device.
That's what I thought as well, it's really much more cleanly executed.
I think it's a bit like Overbridge from Elektron, but for all your iPad Synth's.
Which brings me to a feature idea: In the VST it should be possible to get the parameters from the auv3 to knobs inside the VST. Would be easier for handling automation and for quick parameter access through the VST.
Thank you for all the feedback.
@Vaultnaemsae @SquidgyB
The crash issue with the MIDI effect is believed to be a bug. I would like to prioritize fixing this issue, but I cannot reproduce the crash in my environment. It seems to be a troublesome problem that occurs only in specific combinations of versions of iOS, macOS, DAW, etc. If you are willing to cooperate with us to fix this problem, could you please send us the information through the feedback form? We have listed the questions necessary for our investigation in that form.
Thanks in advance.
Yeah, that would be nice a nice addition.. I was so surprised when I realized that you can select the iOS AUv3 from the macOS plugin. I’m gonna play around with the trial a bit more…I’m on the fence as my interface + AUM allow me to use iOS in real time with macOS already.
Will do - thank you.
As an aside, I think it might be related to Midi CC being transmitted; The devices I've been using are a Joue Play and Seaboard Block, which transmit several Midi CC's along with note data whenever a note is pressed, as per MPE specifications, which I think may not be handled by SideRack/Duo, in the same way @Vaultnaemsae was having issues with Midi Program Change causing what appears to be the same issue.
Sure, Will do
Thanks for your cooperation, @SquidgyB and @Vaultnaemsae.
We have successfully identified the code error and released the update. This time, the fixing was so smooth thanks to the information you two have provided.
The new version is already on the App Store, please update and give it a try.
Cool, thank you...it responds to MIDI CC and PC really smoothly now. Excellent fix!
One thing I'd like to ask...are the internal buffer (4096) and overall plugin latency likely to one day be refined for real-time performance use? Or is that a limitation of the technology at hand?
Thanks. It was good to hear that it's working in your environment.
As for the internal buffer size, we're planning to make it possible to set that value in the user preference page. Once that feature comes, the limitation will only be a matter of your machine's power.
a question before purchasing, does the MIDI only work for AUV3s with built in CC charts?
or can you expose parameters to be assigned on either host/receivers end?
No problem whatsoever, glad to have been able to help!
Excited to give it a try later once I get home from travelling