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.
Way Behind on MIDI Control of AUV3’s :-(
I am C&P’ing this from the Tera Pro thread. Didn't want to derail it.
Apologies if this is too clueless to bother with - but any help to save on the learning curve would be appreciated.
@Pynchon said:
Having 5 instances in Cubasis is of not much relief, because Cubasis is unusable for live performing, given that you can't MIDI map the AUv3 parameters. So you can't modulate parameters with external apps such as miRack, Rozeta Sequencer Suite or Drambo. And you can't use the knobs in your MIDI keyboard. Completely denying the potential for sound design of this synth.Until AUM supports multi core processing or it becomes a Universal app compatible with MacOS, I will treat Tera Pro as an external hardware synthesizer connected with a single instance to Bitwig in my Mac.
And I'm ok with this, this is one of the best sounding synths released in desktop or iOS, which is on par with the sound of a Waldorf hardware synthesizer, that costs much more.
This is off topic but I’m new to iOS music and I just read this and Im in shock. It didnt even occur to me to check to see if I can map hardware controls to synth parameters inside DAWs :-0
I just assumed.
I saw midi learn in passing on a couple of apps like Zeeon right off the bat and didnt give it another thought.
As a newb to the platform I have mostly been researching what instruments are available and checking them out in standalone - on my couch away from controllers and fiddling using the ipad screen - I havent even gotten into actual production mode..
I have 2 or 3 DAWs based on their ubiquity in the community and I have a high-level understanding of their comparative strengths and weakness
Now all these comments I have seen about “exposed parameters” are starting to hit me.
So from what I gather just from what I have picked up in my peripheral vision, ApeMatrix and Aum allow this somewhat, but what about actual DAWs?
Cubasis apparently doesnt (!) - what about NS2?
Can anyone save me a little pain before I do a deep dive into this and point me to some of the best resources to get up to speed on this?
(Update: now Im looking around in different synths in standalone and some dont even have MIDI learn that I can easily see - like Bleass Omega. Holy S—- I feel stupid. Never ASSume as they say. Damn…).
Comments
Do I understand correctly that Cubasis is the DAW you prefer and you want to map MIDI from external controllers to your AUv3's inside Cubasis?
Background:
AUv3 tends to downplay direct MIDI control, offering a more flexible API in its place consisting of those exposed parameters, which have names.
If there is to be a mapping from external MIDI to AUv3, it is economical for the host, like AUM or apeMatrix, to do this right once, rather than for each AUv3 to implement their own version.
Hosts like AUM have midi learn built in. So you can virtually control any parameter you want with a controller. As long as that parameter is exposed by the app. Most apps these days have most, if not all parameters, exposed. However if that’s a main feature your looking for, you can always do a little research here in the forum, on the AB Wiki, the apps manual, or YouTube, to make sure the app your looking at has its various knobs, faders, etc.. exposed, before you purchase.
Yeah, when you're using the AU version of an app, you can often attach MIDI messages to its "AU parameters". It's similar to using an app's built-in MIDI learn function, but it uses the DAW's interface instead of a unique interface for each app, and more apps support it, including Bleass Omega.
In AUM, you can tap the menu button in the top right of the screen, then tap "MIDI Ctrl", and where it says "No MIDI Source!" in the top right of the screen, select your MIDI controller. Then tap the back arrow, the one shaped like "<", and scroll down to the category labeled "Channels". You'll see a list of the AUs you have loaded. You can probably figure out the rest from there. Every AU window also has a shortcut to its list of parameters in its title bar. The icon with the faders, third one from the top left.
Is Cubasis 3.3's MIDI Learn and Extended MIDI routing not getting it done?
Thanks folks
Not sure tbh. I am going mostly by the post I quoted from Pynchon in the OP and then seeing no obvious way to do what I have always done on desktop.
Basically, I just want to be able to tap on a knob or fader on an AUV3 synth, such as the filter cutoff and assign it to a knob or fader on my keyboard (and then record that as a MIDI performance).
I am basically assuming I would want to use Cubasis, but I would just as happily use NS2 if it allowed this.
Thanks gents.
Now I understand why everyone likes AUM so much.
Of course now I have to figure out a workflow for a getting a midi timeline to be able to record and edit MIDI tracks and controller gestures (like live filter sweeps, panning or whatever…).
I understand 4Pockets has a few modules that offer such solutions.
Found this for NS2. Blip community member Dendy outlines how to do it with the macros feature and the mixer details view.
https://www.blipinteractive.co.uk/community/discussion/900/is-it-possible-to-cc-map-midi-learn-auv3s-model-d
It may be this easy in Cubasis as well, I just havent found it yet.
Have gotten some good advice about 4pockets and AUM.
Any other thoughts would be appreciated.
I suggest advocating for this in the Cubasis section of https://forums.steinberg.net/
Maybe it's coming soon.