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
Is this reproducible for you? I have tried what you say and changing the buffer in Ableton to 64 or 32 has no impact on the latency on my system (MacOs High Sierra and iOS 14.7.1) bit ot does impact the crackles.
I haven't seen any recent reports on the Studiomux Forum of small buffers causing high latency. Some weeks ago someone (perhaps you?) reported 200+ ms latency and then reported that it was solved by deleting and reinstalling.
Please report to the devs if you are continuing to see small buffers causing high latency as I don't think that is on Pascal's radar.
I'll try and reproduce it at some stage. Yes, I did respond to somebody at the ZeroDebug forum who was having the same issue. And the process to rectify it was as you described (me describing it).
As I said, it works well enough at 128 so I don't consider it "broken" but it's very weird. I have less time and patience these days than when ZeroDebug opened it up for beta testing -- more than a year ago?
And I'm not going to uninstall and reinstall it every time I want to use it.
(replied here as I was worried I might derail the original thread https://forum.audiob.us/discussion/47134/stay-on-ipad-or-go-back-to-pc)
I would make more use of Studiomux but at the moment I find there is too much state that needs to be manually restored both when opening a Studiomux session and in the DAW to get it to reconnect.
It could be specific to Logic but I need to manually reconnect every SM instance when reopening a project, even if SM remains running on the iPad between closing and reopening the Logic project. On the SM side, reloading a saved session also throws away AU instrument/FX state. The solution here would be to host the instruments/FX in AB or AUM but that adds another dependency and at the moment AUM does not route correctly to SM and I can't reliably get AB talking to SM.
If I could save an SM session with all of the AUs and FXs presets intact and the DAW plugin automatically reconnected if the session was up and listening on the iPad then that would be ideal. I am looking forward to the AU hosting code making its way back to ModStep (2) as it has been pretty solid in my use so far.
The charge + utilise thing is a great bonus!
I agree, SM does open up a massive range of cheap and capable apps to the desktop which is worth jumping through a few hoops for. I have not got into the desktop plugin market but I'm sure if you did the sums on a fairly recent iThing then there may be cases where it is cheaper to buy the hardware + iOS plugin than the desktop equivalent plugin and no software/hardware piracy locks to bother about either.
It is a good point you make about being able to store project notes with the project and we can do the same on the iPad with the Session Notes AU, if only SM saved its state
I forgot about apeMatrix so did a quick test there. It had the same problem as AUM when added into the input slot as apeMatrix (Bus) or apeMatrix (Instr) BUT on a whim I tried adding apeMatrix (Fx) into the FX slot and whaddya know it works!
Not as flexible as AUM as you can only use one instance of it but means I could in theory host a number of apps with their presets set up how I want them inside apeMatrix and then manually route audio/MIDI as needed. Tried as an instrument host and as an effect provider and both work. I might be imagining it but there does feel like there is slightly more latency when using apeMatrix as an IAA FX, but still nothing to complain about.
Edit: odd, after playing with this I tried adding AUM as an input again and it started working. Sigh.
@MisplacedDevelopment
Good idea to continue the discussion here. My workflow is to create 'channel strips' in AUM and feed those to StudioMux and for the most part, it's friction-free. Another benefit here is that I use those same 'channel strips' in Cubasis. The biggest fly in the ointment seems to be iOS/iPadOS itself. When things start to become flaky, a quick cold reboot always seems to get things back on track.
One thing with this workflow that we need to be cognisant of, is that IAA is dead in Apple's eyes, and bug fixes are increasingly unlikely to happen. It's a pity that StudioMux isn't an IAP within AUM, that's an approach that would really streamline things...
It's great that StudioMux is back to being reliable, but I agree, ModStep 2 (if and when it finally arrives) would streamline things a great deal. Back in time, I was a devoted ModStep user but times change and ModStep got left behind. As an Ableton user, ModStep is far closer to the musical wiring in my brain, than Cubasis 3 (which I see as a necessary evil, simply because its multicore capabilities work well with the M1 iPad Pro).
All in all, I agree that things a far from perfect. But thinking back to the days when moving from project to project entailed at least 30 minutes of setup, I'm hardened to a little bit of legwork!
Please make sure to report any StudioMux issues to the developer…and re-report any outstanding issues that may have been reported more than a version ago.
^ This is my takeaway from today's experiments! I had not rebooted for a while so just assumed IAA routing was broken.
I have set up AUM like you suggested, with labelled SM channels and a template AUM session with each lane listening on a different MIDI channel. This works very well, thanks!
I will see if I can work out what steps led to the problem. Do you know if they have a preferred route for reporting bugs?
Despite its deprecation, Apple has kept IAA solid. I suspect partly because a lot of important music apps from the large developers are still IAA.
While they might pull it from some future iOS version, it seems like they are keeping it solid in iOS 15.
A daily hard reset seems beneficial on any of my devices on which I do music…even if I don’t use IAA apps but especially if I do.
Spent some time setting up 8/16 channel Logic templates and the equivalents in NS2/Gadget/AUM. Strange to be playing Obsidian using Live Loops but very cool! @jonmoore I take it back, there is a lot of worth to be had in using Studiomux for pulling in iPad instruments. Once you have some basic templates set up then everything becomes a lot easier.
I agree, it works great! Latency free for me if I use a cable also. But currently I treat them as "external instruments" so I'll record audio into my DAW. But that works really well, so I have the whole arsenal of my iPad available
Hi everyone!
I've got to set Studiomux in Reaper, using the iPad as an fx unit. But, I'm getting some weird results when rendering/freezing the track.
Has anyone tried to render/freeze tracks on any desktop DAW?
I would think you would need to do a real-time playback/capture. At least that is what I do in Live.
Does Reaper normally successfully freeze audio tracks that use outboard gear in an effects loop?
I also do real-time render in Logic and it works fine. What happens to the audio when you do the render in Reaper?
I think the problem here is that it doesn't "know" that it has to treat this like external gear. In Studio One, when I freeze my hardware Synth it renders it in real time, but for Studiomux it treats it like a plugin and that can't work.
Yes, I'll try setting rendering to real-time.. and no, this is the first time I use outboard gear as fx.
However, I've never experienced any issues like this before rendering in Reaper.
The freezed take is like gated, and the overall signal level gets super low.
I'm using it connected with the lightning/usb cable, not bluetooth/wifi.
I've just spent a good week away with AUM / Studiomux on iPad Pro and Ableton on a MacBook Pro. Things mostly worked, but a couple of times I went down a wormhole of tech despair.
The big thing I finally learned and thought worth sharing was:
Always have Studiomux on iPad in the foreground when setting up the plugins in desktop DAW.
Hope that helps people avoid my painful lost hours.
Sage advice, it does tend to disappear from view in the desktop if you leave it in the background for too long.
I think apple has annoying rules for a lot of this stuff when connecting to windows. Apps like Duet and teamviewer crap out when minimized too.
To clarify, I mean the SMUX app needs to be full screen on the iPad during DAW plug-in setup, not in the background behind AUM. Once the DAW plug-ins are setup they can be closed in the DAW (and AUM brought to the foreground on iPad).
Yup, i got you meant that.
Just making sure for any poor lost iDamned souls that may follow
Thanks for this tidbit
I have some issues on Win10 and latest app (shouldn't update it)
1. Can't delete a custom midi port from within the app , it always re-appear both in the app and on my pc
2. custom midi ports created from the App work and can send midi from iOS to PC but not from PC to iOS , only way is to send midi is within the channel where the AU is hosted on StudioMux app . (I'd like to use different app)
3. Not working anymore inside AB3
Air2 ios13
Does anyone have any info on what's happening with Zerodebug and Studiomux?
The Studiomux beta expired a couple of months ago, which is a shame because it was working sending desktop (Mac) audio back to AUM, something the App Store version (5.123) isn't doing well for me, with lots of digital distortion. Audio from iPad to desktop is working, as is a roundtrip via AUV3 effects hosted in Studiomux, but my use case has always relied on getting the audio out from Studiomux to AUM and back again.
The Zerodebug forum (for Touchable as well) is active, but the developers appear to have been absent since late last year 2021.
Clearly something is up, I hope it's nothing bad and they're just taking a break, but desktop audio back and forth to Loopy Pro in AUM is a tantalising holy grail... Studiomux is unique and has so much potential, I hope it can be resuscitated, even if by just reactivating the last beta version.
Was hyped when the beta was launched
Was told to uninstall anything old on pc
Tried to use the beta version, wouldn’t work properly with my version of ableton
Then tried to just use my old version of software and old app, never really got it to work properly again
So gave up
Back in the day, they were never helpful and got it working from other random people on YouTube
Shame really
But will just get an interface sometime this year, can’t be bothered with studiomux, spent more time trying to get it to work than making music
Oh well
But like you mentioned, I hope they are all healthy, don’t wish anything bad on anyone, but I haven’t got the time for studiomux
If bram or someone else took on this task then they would receive my full support and money
I hear you, but I think we should do everything we can to encourage them to keep going. It’s clearly quite a challenge, no one else has developed a successful alternative - it must be very tempting to give up in the face of criticism. C’mon Zerodebug, one more push…
@steve99
Go zero debug
But until it works on my version of ableton 10
I am not that bothered
Is there anything like this for IPad to IPad (Mainly Midi). Bluetooth is not up to par..
iPad Air 4 USB-C to Lightening.. Someone needs to make a simple cable for this.. Or maybe there’s already such a thing?
It seems like two of these, or similar, hooked together would work, but I haven't tried it. I only have one. It would also require two Apple CCK's.
https://www.amazon.com/gp/product/B077X7R74Y/