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.
Problem recording Ravenscroft as MIDI instrument in MultiTrackStudio
Anyone using Ravenscroft as MIDI imstrument in MTS? I get only crackling. Ravenscroft AU will playback a recorded MIDI a track fine in MTS, but I can’t seem to record new MIDI with it loaded. Anyone have similar problem or solution? I using latest versions of Ravenscroft and MTS. Don’t have the cracking problem with other MIDI instruments, just RavensCroft under MTS.
Comments
What hardware and OS are you running and what buffer size?
I’m using iPad 9th generation in iOS 16.6. Running Ravenscroft stand-alone shows sample rate 48000 Hz, buffer size 256 samples. I have no problems playing under stand-alone with those settings. Under MTS there doesn’t seem to be option to change those in the AU.
Edit: The Ravenscroft AU has a red border around it when I try to play, like there’s a conflict or something.
See what happens if you change the buffer size. Is Ravensctoft the only plugin running when this happens?
No change. Yes, this is the only plug-in running when it happens. I just tried under Cubasis and Ravenscroft AU loads and plays fine there, no crackling. Rebooted iPad. Other AU’s are playing fine (pure piano, pianoteq) under MTS. Only Ravenscroft AU isn’t working (which happens to by my favorite). I haven’t noticed this before because I previously always recorded Ravenscroft as audio track via Audiobus. I can still do it that way, was hoping to do some MIDI tracks with it to edit out my bad notes.
EDIT: thank you for you replies and suggestion btw.
in the meantime I will just record using another loaded Instrument, and switch it Ravenscroft AU when playing back midi track. Playback works, just not recording.
Just to be clear, you adjusted the buffer size in MTS, not in Ravenscroft Standalone, right?
(It doesn't really sound like buffers are the issue, but just to eliminate that as a possible cause...)
No I didn’t change the buffer size under MTS. I don’t see the option there in the AU. There is an Options menu, but has only few options in it, like global tuning, polyphony amount.
You change it in the host, not in the plugin. MTS should have a setting for the buffers it, and all the plugin instances in it, use. Be sure to force-quit the standalone Ravenscroft and all other standalone apps before trying to change the MTS buffer size.
Rebooting the iPad is always a good thing to try when strange things happen, if you haven't tried that already.
I am talking about MTS ‘ buffer not one in the AU
Oh! I don’t know. I have to leave right now for an appointment, but will continue off when getting back home. Thank you both for your input.
I’m now at the mechanics waiting on an auto repair. Playing with my iPad here with Ravenscroft + MTS I see this AU problem exists without my MIDI controller hooked up. Using the built-in MTS keyboard playing Ravenscroft fails too. That rules out my MIDI controller and interface I guess.
Here’s something else I’ve noticed - when MTS is open with the Ravenscroft AU loaded, all other apps using the AU (and the Ravenscroft stand-alone too) will also crackle until I close MTS, after that it clears up. There’s a conflict somewhere. I’ve played with every setting I can find in MTS.
It does sound like MTS is asserting a buffer size (or latency) that is too small. Once a buffer (and sample frequency) is set, everything on the device uses it; there can only be one buffer size for the entire audio system. Are you able to find the MTS buffer settings?
You could try loading AUM while MTS is loaded. Looking in the AUM Settings will show the current buffer size, etc.
Thanks @uncledave! That may be it. I found an ‘Audio Latency’ setting under devices in MTS. Changed it from the default setting of Medium to High and now the cracking is gone. Will trying to record when I get back home. Hope it works!
It's strange that an iPad 9th generation would need High buffer setting just to playback Ravenscroft. That sounds like an MTS incompatibility of some sort, unless you see it in other hosts as well.
You're not using Bluetooth headphones or anything are you?
Nope, no bluetooth. I’ve never had this problem before with any other instruments or hosts on this iPad.
That's something that either the Ravenscroft of MTS developer will have to sort out. It shouldn't be happening.
I had a problem with Ravenscroft controlled by LoopBud in Loopy Pro at 48 kHz/64 samples. Ravenscroft would occasionally crash. When I increased the buffer to 128, the problem disappeared. And like @Dav said I had no similar issue with other instruments, the Numa Player or PSP in my case.
I'd be surprised if MTS "medium" setting is 64 buffers though. More likely 128 or 256.
One way to find out would be to close all apps, start up MTS, then go to Ravenscroft standalone and see what the buffer setting is. It should be forced to the same as MTS. For good measure it would be best to cross check that by opening another app such as AUM. AUM should definitely be the same as whatever MTS has set. If there's any mismatch between AUM and and standalone Ravenscroft then it may point to Ravenscroft not being set properly by MTS.
Okay. Here are the results of doing that. Started MTS first, put latency on Medium. Ravenscroft stand-alone buffer showed 256, and so did AUM. Crackle city, Closed them all, did it over again with MTS latency set to High. Ravenscroft buffer then said 512, AUM showed 256 still. No crackle.
Those are weird results. I'm surprised AUM showed 256. However at least it shows that Ravenscroft seems to be getting its buffers set correctly. Something fishy is going on though.
I'm very surprised Ravenscroft needs 512 buffers to play in MTS on a 9th generation iPad. But it is what it is I guess.