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
So I haven’t used ToneStack in a while.
Edit: never mind!
@Edward_Alexander working for me, iPadOS 15.1. You're adding it to an effects insert, right?
I'm also on iPadOS 15.1 and everything works as expected here :
TS Go IAA in both instrument and FX slots, and TS Pro works in the FX slot 👍🏻
Yes, of course I am!
looks around to make sure nobody saw me trying to load it in the input node
Does this thing still crash all the time?
While I haven't used it a ton, I've never had it crash on me. Under what circumstances has it been crashy for you?
I've never had a single crash. Ever. I've used it probably 50 hours or so.
@ambrosiajam - are you referring to the current ToneStack Pro that includes AUv3, or the older ToneStack standalone only product?
Tonestack pro.
Crashes in AUM under severely basic use. Do not have that issue with other apps, iPad is in good shape, etc... Haven’t used it in months, as that is completely unacceptable for a guitar amp sim. I used tonestack ‘1.0?’ Exclusively as my bass amp rig for years, no issues.
I just use nembrini’s blackice for my bass amp now and other stuff for guitar.
No crashes here.
No crashes here, I use Tonestack Pro AUv3 in AUM every day.
I just discovered that for CC mappings to be saved and recalled one has to turn on the setting for Load CC Maps. Doing that will result in CC maps saved with a preset to be recalled. There is also a mechanism to set a cc mapping to because the default for that effect...if you double-tap a midi learned control, there is a dialog that lets you make that the default for that effect.
No crashes here, and very light on cpu
Has this been fixed so that the AU can "see" midi coming in from AUM sources? Last I knew you could not midi sync or control params via AUParams... Reviews in the store mention it as well...
On my iPhone 15 pro and iPad Pro 4-th under Drambo, even single instance ToneStack Pro crash during long session (I didn’t test it under other hosts) … where other auv3s still worked ok… so my question:
Is ToneStack PRO stable?
EDIT; I see some updates was released last months, I will test it again.
I just tested this with TouchOSC on iPad controlling Tonestack Pro AUv3 in AUM on iPhone via BT MIDI and the assignments work fine. You just have to make the assignments via the Tonestack AUv3 GUI rather than via parameters exposed to the host. MIDI PC messages also work as expected.
I think it would be fair to say the MIDI implementation is aimed at live or realtime use rather than host automation.
I can’t speak to its enduring reliability as I don’t use it on a daily basis but I wouldn’t write it off as it’s never crashed on me.
Thank you, I also just finished session without any crash, so it’s promising!
In my environment, the following steps reproduce a crash.
EDIT: The below works, but even though it is not obvious (actually hidden) only receives hardware midi. To get Mosaic or other midi into Tonestack, you must connect Mosaic to "AUM Source (virtual) and then open TS, click on the top left "mixer icon" for control settings and under MIDI controls, choose AUM destination.
I posted this in another thread, but perhaps this will help others who are having trouble with Tonestack Pro's midi connections and getting midi working inside AUM or as a plugin in general.
In AUM, the midi port will only show up if you start the standalone TS as well. Then in my preset (inside TS) I setup the midi CC's and saved it as the default midi mapping for the unit. I also had to turn on the "Load CC Map from Patch" and the "Load Unit Default Map on Add". (not sure if the later was necessary, but I did and it works.) I made sure the same settings were inside the plugin. After that I was able to reboot my laptop, NOT start TS standalone. Midi connection in AUM shows a broken icon for TS, BUT (!!!!) it still works! CC's are getting inside TS and wah pedal (in my case) and moving!
I've just been informed that Tonestack Pro now has MIDI functionality.
I can’t seem to get midi to work in my quick test in AUM and LoopyPro-as midi au. Doesn’t seem to recall saved CCs either..
"Works for me", but there's a trick. Using AUM, I mapped the default reverb Size to CC10, routed KB-1 Knobs to ToneStack, and was able to control the Size value with the knob. Saved the session and the mapping was lost. But, when I turned on "Load CC Map from Patch" and rebuilt the mapping, it was restored with the session. So, you need to anticipate that you want the mapping saved before saving the session, or the mapping will be set back to defaults. I find it odd that you would ever want to reload the session with the mapping erased, but that's the default.
Thanks for the reply @uncledave 👍. The tip re saving cc maps is v.kool. I still can’t get ToneStack to learn midi via LoopyPro, but it works via KB-1. I tested another Yonac app, Kauldron, & that can learn midi via LoopyPro, but for some reason Tonstack can’t..😾
Have you routed midi to it? Tonestack Pro’s midi learn is working for me in Loopy Pro.
Can you post screenshots of your setup? Are you sending midi to it from widgets or midi controllers? Both work for me.
Still not available as an AU for macOS, but I’m hopeful.
Thanks for the reply @espiegel123 👍 I’m actually trying to get it to work inside AUM, not LoopyPro - I’m trying to use the midi au version of LoopyPro to control ToneStackPro. In the pics below, I use AUM destination (which the green fader I made in LP is set to) to both Kauldron & TSP - Kauldron learns the midi, TSP doesn’t..
You don’t have the output of the Loopy Pro AU routed to ToneStack. What is the destination of the fader you have in Loopy Pro? It should be set to MIDI Out
Thanks @espiegel123 I’ve always used AUM as the destination, I remember that being the only option that worked. So I tried your suggestion to set the Fader to Midi Out instead - Same result Kauldron maps, ToneStack doesn’t..
Change the CC number. Tonestack doesn't midi learn CCO and a few others.
Here is a demonstration of one of the setups I tried.
That worked! Both AUM + Midi Out can be used as destinations in LoopyPro in the examples above, just NOT with midiCC-0. I had no idea cc0 was a no-go for midi mapping & will be mindful of that ballbaggery in the future. Thanks again @espiegel123 ! 👍😺
Use MIDI Out rather than AUM. Best practices for sending MIDI from AU is to use the AU's output where possible unless there is a compelling reason not to. Before the update, Tonestack didn't have a MIDI input port...the hacky workaround was to route midi via AUM's output port because Tonestack listened to that.