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.
Midiot Chronicles: What's, uh, a CC again?
First of all, thanks to everyone on this board for their infinite patience and help getting me up to speed in such a short time. I don't want to name all those who have helped for fear that I'll forget some (Kaikoo, Matt Fletcher, Samu, GoneKrazy, MSchenkel, InfoCheck, Wim...).
I can confidently load apps into modstep (via AUM and AB, as needed!). Cubasis is a second home. I understand the difference between midi in and out...if I think about it.
Midi CC's are the next hurdle. To my outsider eyes, midi mapping looks crazily time-consuming. I have tried to set up DM2 using a template in modstep. I kind of got it to work once, but now I can't remember how to do it. Can anyone point me in the direction of a good tutorial of midi CC? (I don't even think I'm using the syntax correctly here....)
I mean, iSem has midi out. So I can play the iSem keyboard into modstep or Cubasis. The notes will be read. But if I use the mod wheel or the pitcbend wheel, modstep doesn't read that, correct? How can I make that work? Also, I'm not using an external keyboard at the moment.
Thanks again.
Comments
Continuous controllers. Very handy.
I thought it was Control Change.
I prefer to use the keyboards that Modstep and Cubasis have.
Basically it is nothing more than a pair of an identifyer number and a value. The identifyer is linked to a specific parameter - some are assigned to standard functions like cc7 to volume, others are freely assignable to a function / are assigned by an app developer and you need to know this to be able to use them properly. And the value, in 128 steps, is used to control the parameter. So the pair of identifyer and value are used to control a specific parameter with the value you give it, and by sending many of these pairs in a short period of time you have real time control of the parameter. Clear as mud?
Ha! Got it!
Let me rephrase my question.
How do I modify the sound of Animoog while recording midi? How do I play that expressive keyboard AND gradually increase the delay or adjust the filter? Modstep and Cubasis understand the notes, but not the modulations.
Not sure on that one as I have not purchased the midi out option in Animoog.
I did remember that I made a little app to app midi demo a little over a year ago.
Normally you would set the midi OUT of the synth to your midi recording app IN to record its CC knob movements . Animoog , unfortunately , has an In App Purchase (IAP) requiring extra payment for the privilege of sending out its midi . If you're willing to pay that then the knob twiddling in Animoog ( & its Polyphonic aftertouch of Notes ) can be recorded into your midi recorder .
Alternatively , more generally & forgetting Animoog special keyboard , you could play notes & knob twiddles from an external keyboard into Modstep/Cubasis to record data ,whilst thruing to the synth . in this scenario you set the CC of the knobs on the keyboard to correspond to synth CC knobs .
OR... you could program either notes &/or CC in Modstep /Cubasis clips directly.
I did a little reading of the animoog manual, and tried a little test sending midi to Cubasis... It seems that once the midi add on IAP is purchased, animoog only transmits notes, velocity, and aftertouch. Twidling knobs in animoog is not transmitted via CCs or anything else.
It would require some sort of other controller, be it hardware or some app like lemur, mapped to animoog and midi thrued to your recording app.
@ExAsperis99 it seems Animoog doesn't transmit ccs....
In animoog in the Setup, there is a Option to map Midi cc .
He's talking about sending out midi cc. Pretty sure that option is for incoming cc.
Maybe be you have to set CC per knob for both Midilearn Input AND midisend output .
I don't have the IAP , but it definitely says It sends Midi CC out :
"Transforms Animoog into a MIDI controller as innovative and richly expressive as the Animoog sound engine itself. Use Animoog's unique keyboard to control other MIDI instruments, and send MIDI CCs from the XY pad and other on-screen controls."
It is control change (not continuous controller). The midi spec refers to such control change parameters. Since then, a vast population of incorrect people have somehow got it from someone else that it stands for continuous controller. It doesn’t and never did, the majority of the public are incorrect. An easy way to remember this is that a lot of CC (control change) messages are not continuous — switches, for example, which are either on or off.
It is
From the manual -
SENDS - CH. PRESSURE, POLY PRESSURE AND VELOCITY Touch to enable/disable the associated MIDI messages.
NOTE: Only available as part of the MIDI Expansion Pack.
I tested by recording into Cubasis and randomly turning every knob - the only CC beyond what's listed was 84; which is listed as Portamento in the spec....
Did you set any of the knobs to a CC before testing ? As I suggested above , maybe the knob needs a CC set before it sends .
If not , Moog are mis advertising the Midi Expansion Pack , as I quoted above ,
"Use Animoog's unique keyboard to control other MIDI instruments, and send MIDI CCs from the XY pad and other on-screen controls."
It's convoluted....
You need to midi learn CCs to each of the buttons you want to record and for Cubasis not to be using those values.
So for the sake of testing it I put one knob into TB midi stuff which I set to be CC20
Went into animoog
Setup map CCs pressed the res button
Switched to TB midi stuff.
Twiddled my one knob
Switched back to Animoog - there was now a number 20 in the square around the res knob
Pressed the map CCs button again
Loaded cubasis
Made a new midi track with no instrument. Routed the midi in /out to Animoog
Set a long count in, and pressed record
Switched back to Animoog
Played a few notes and twiddled the res knob a bit
Switched back to cubasis.
Stopped recording
Double taped on the recording
Pressed where is says velocity
Scrolled down to CC20
Lo and behold it had recorded the twiddling of the res knob
Pressed play and switched back to Animoog to watch the knob happily replaying the random twiddling And the notes being played.
And not forgetting, not all CC's are created equal, some 14bit 2x7bit CC's are sent odd and even, this creates a less stepped modulation. The Novation Bass Station 2 is an example.
Wow, thanks for this. I'm at work, so I can't really do a hands-on investigation. Will look later!
Wow indeed. Just tried this with Lemur and it worked! Even without Lemur running after mapping a knob - the Animoog knob transmitted the mapped CC to Cubasis. Very cool.