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.
Sequencing CCs in Drambo
I feel like a complete idiot. I'm trying to step sequence CV values, but I want to use the piano roll or step sequencer to do it. I can not, for the life of me, figure out how to go from Drambo to AUM. I've tried a plethora of different modules and routings. I can easily do LFOs and such, but converting the CV to MIDI CC has been beyond me. I feel like it should be so simple and I'm probably just being dense.
Comments
This is what I do in drambo loaded as an Auv3 midi in AUM
Then I step sequence the slider using step parameter locks or so
Make sure the channel and cc numbers are correct and AUM connections are correct as well
I would probably try something like this...
CC1 - allows you to use keyboard (and the main seq) as mod source *
CC2 - to use CV seq module as mod source
CC3 - other modulators
*you may also want to filter out the notes the main sequencer sends and keep CC only
@slicetwo - I'm not clear if where it's going wrong for you. Do you need help with getting notes in the sequencer converted to CC's? Or is the problem with getting the cc values out into AUM?
Using the sequencer to create CC values is straightforward. You just need a Midi CC Generator with the signal input set to the note output of a Midi to CV module, and the trigger input set to the trigger output of the CV module. Be sure to set the CC Generator to Bipolar Input. After that a midi out module is the clearest way visually to set the output. (You can set the track output to the CC generator if you like, but I prefer the midi out module for quick visual reference).
Thank you @hghon, @0tolerance4silence, and @wim. My issue was mostly user error and stupidity. Though I am now noticing that the keyboard in Drambo doesn’t go low or high enough to span all 128 range values. Haha.
The piano roll does though 😉
Keyboard covers range C-2 - C6 only, but if you switch to pads it’ll give you range C-2 - C8.
With the above example set ‘CC1’ knob to 0.4 and ‘Key’ mod amount to 0.8
Or you know... play around with it to see what custom range suits you the most
Odd. My piano roll and pads both start and stop at the same points and don't get down to 0 or up to 128.
OK I'll take this into the beta team, the key ranges should all span the full MIDI note range indeed.
Have you actually checked the note number? I am getting note 0 and note 127 in the piano roll and from the pads. Some apps name the octaves differently, so while Drambo shows note 0 as C-2, other apps may show that same note as C-1 or C-3 or something else.
(Note: there is no note 128 in MIDI.)
[edit] I get the full range from Drambo's keyboard too.
Yes. Drambo calls middle C (MIDI note 60) C3. That makes note 0 C-2 (C minus 2). The keyboard and pads both extend down to C-2. However, for me, the keyboard ends at B6, note 107. And the pads end at C8, note 120. Neither extends all the way up to G8, which would be 127.
(I tested this loading StreamByter as a MIDI effect in Drambo, and using StreamByter's monitor which displays the exact MIDI data.)
Sure?
Here, the pads go from MIDI note $00..$79, the keyboard from $00..$6B and only the piano roll covers the full range from $00..$7F.
You're right. I checked the lower end but didn't check the top end carefully. Anyway, the piano roll does cover the full range.
My piano roll only goes up to 105, not 127. What am I missing?
The lowest note in piano roll is C-2 and the highest one is G8, that covers 128 notes. At least that's what I see here.
G8 only sends up to midi cc 105.
Could you try an AUv3 MIDI monitor that would show the actual MIDI note message from the piano roll? For G8, it should be 127, or 7F in hex. I suspect your processing may be affecting the value in the CC message.
Can you post a screenshot or screenshots showing where/how you are entering the note?
how are you translating note to cc?
@espiegel123 @uncledave
@slicetwo : there must be a bug in your note number to cc value conversion. if you feed your midi monitor directly with the not G8, you will see that the note number is 7F (127)
@slicetwo On the piano roll, you're placing notes. If you get CC numbers instead then there's something wrong.
A few facts:
In the setup I posted above, I get C-2 = CC value 32 and G8 = CC value 116. So apparently there's not a 1-1 correspondence between note number and CC value. I did verify with MidiSpy that C-2 is note 0 and G8 is note 127
@rs2000 @wim @espiegel123 thanks for all the info! So what's my best way to sequence CC values as specific as possible over time? Just recording/writing automation?
A Streambyter or Mozaic script convert note value to CC value, assuming you're using Drambo standalone.
Natively, I don't know.
You can convert the notes to CC messages of course by using the CC generator. All you need to add is a Scale+Offset module:
Set Amount to 0.755 and Scale to 0.38 by double-tapping on each knob and entering the numbers by keyboard.
What's the science behind those numbers @rs2000?
None. I had a busy week, no head for maths so I just mangled the knobs until lower and upper limits worked 😅
😂👍🏼
i am a bit of a drambo ignoramus. Is there a way to see the numeric output of the cv-based modules?
Sure, either add an Oscilloscope (numbers are smoothed here) and connect it or long-tap on a CV port to see the better scope, including tools for monitoring polyphony.