So... drambo... is MIDI mapping releasing update soon?

jameslondon74

This is all amazing. It’s what I’ve been waiting for the most.

reasOne

@echoopera said:

@dreamsaremaps said:
I have a feeling being able to control the scene crossfader via midi will be the single most consequential addition for me in the history of music software. Now, I just wish there were reasonable quality midi crossfader style cadets available. I’m pretty sure I’m slowing fucking up the cadets on my LCXL by treating them like a dj fader...

Make one yourself
https://www.synthanatomy.com/2020/05/yaeltex-lets-you-design-your-dream-midi-controller-will-buit-it-for-you.html

that’s awesome

rs2000

@no1normal said:
Endless encoders are OK but can be pretty limiting still.
If you want to map multiple instruments on the same midi controller I would recommend a Faderfox PC4.
16 pages of 24 pots with a very rare feature... Pots can be set to snap instead of jump. No more parameter jumps. That ability alone is worth the price 100%

From the PC4 manual:

In pot mode ’jump’ the pots send immediately whereas in pot mode ’snap’ you must search and catch the old value with the pot before it sends data.

So you have to turn the knob until you've hit the "old value"?
This is nothing like rotary encoders and slower to use than simple jumpy pots.

You're certainly better off with a Faderfox EC4 with true incremental controls.

wim

"snap", more commonly known as "pickup mode" is better implemented in the target app or hardware. I don't think I'd ever use it in a controller.

wim

@Gavinski said:
I have the Bluetooth nanokontrol but the problem for me with this is exactly the lack of sync between knob start position on hardware and the iPad instruments it is controlling. That faderfox looks good, but I definitely prefer Bluetooth

This will always be true for any controller that doesn't have two-way midi communication and either motorized knobs or endless knobs with Led position indicators. And even then it's dependent on whether the target app or hardware has two-way communication as well. Very few iOS apps have two-way communication.

Gavinski

Ah, that's very useful to know, if apps aren't capable then there is no point anyway, thanks a lot.

rs2000

@Gavinski said:

@rs2000 said:

@no1normal said:
...
Midi mapping is here! Control type options show toggle, momentary, absolute, incremental. I don’t quite understand the incremental... is that what you were asking for? (relative midi)

Simply said: There are two types of MIDI control knobs:

• Potentiometers with defined start and end point (like on most cheap controllers): When you turn a knob after loading a new preset or project, the mapped destination knob will inevitably jump to the knob value as soon as you turn it, so you "lose" the initial setting. You can avoid that by enabling "CC takeover" in settings but then you will have to turn the knob to the very left or right if you want to control the full range because the hardware knob position is wrong until "corrected" this way.
• Rotary encoders, the"endless knobs" like on many Arturia or DAW controllers, don't have that problem, you turn the knob and the knob in Drambo will follow, no jump and no range limitation.

Also, DJ controllers with jog dials that send small increments instead of numbers can be used e.g. to scratch through a loop inside Drambo's Flexi sampler 😎

I didn't know the names for this distinction. Useful info, thanks. I think I need rotary encoded knobs in my life definitely. Any particular recommendations?

That's very much a matter of taste.

• The Arturia Beatstep has 16 pads and 16 encoders and price-wise it's most likely the best option. The encoders are not of the best durability but for the price it's acceptable.
• Arturia MiniLab Mk2
• Arturia KeyLab Essential 49
• Faderfox UC4
• Faderfox EC4 might be interesting if you want to control lots of parameters from hardware knobs.

Not tested by me but these should work too:

• Icon Platform Nano
• Icon Platform M+
• M-Audio Code 25 Black
• Native Instruments Traktor Kontrol F1
• Native Instruments Komplete Kontrol A25
• Midiplus SmartPad (I have seen mixed reviews about the quality but the price is very low)

Some controllers that are not produced anymore but work well:

• Got an old Behringer BCR2000? It has endless controllers too and they work with Drambo.
• IBK 10-Control and 4-Control

Gavinski

Oh wow, you're a serious expert on Midi controllers I see. Thanks a lot for taking the time to put this list here.

rs2000

@Gavinski said:
Oh wow, you're a serious expert on Midi controllers I see. Thanks a lot for taking the time to put this list here.

Thanks! I've done a lot of testing and some incremental protocol specifications for Drambo.

sigma79

I got 3 controllers. Nanokontrol studio. Nanokey studio. Microkey air 60 something. Nanokontrol for drambo volumes in auv3 mode.

Nanokey studio for sequenced synths.

Korg microkey, well. Maybe for adding some notes somewhere.

and just tweak drambo on screen.

How would you use these in your set up?

Is auv3 drambo at 1024 buffer with sequenced synths better than another setup?

no1normal

@rs2000 said:

@no1normal said:
Endless encoders are OK but can be pretty limiting still.
If you want to map multiple instruments on the same midi controller I would recommend a Faderfox PC4.
16 pages of 24 pots with a very rare feature... Pots can be set to snap instead of jump. No more parameter jumps. That ability alone is worth the price 100%

From the PC4 manual:

In pot mode ’jump’ the pots send immediately whereas in pot mode ’snap’ you must search and catch the old value with the pot before it sends data.

So you have to turn the knob until you've hit the "old value"?
This is nothing like rotary encoders and slower to use than simple jumpy pots.

You're certainly better off with a Faderfox EC4 with true incremental controls.

Yeah it’s a bit slower but still pretty good.. I’ve never found a controller with that many endless encoders... will check out the EC4 maybe

echoopera

So far I am loving the latest @giku_beepstreet update and using it with the LaunchKey Mini mk3:

echoopera

Spent some time getting the following mapped:
. Scene Selections + CrossFader
. Audio Channels 1-8 Mixer Volume
. Patterns 1-8 Selector
. 2 octave Chromatic Keyboard
. Play
. Record
. Undo
. Steps Mode

Used up 2 Custom Modes to make it work so we’ll see how it goes. So awesome to have up to 4 Custom Modes on the X and it should be the perfect Drambo midi controller.

auxmux

@Gavinski said:
Oh wow, you're a serious expert on Midi controllers I see. Thanks a lot for taking the time to put this list here.

Another two to consider: Novation Launch Control XL and DJTechTools Midi Fighter Twister.

sigma79

Setup controllers. Everything is good.

Dont think I can map record button with drambo as a midi sequencer. As a drum machine with internal sound engine etc. You can set all auv3s to the same midi channel and cc.

As a midi sequencer and a single drambo. I think you have to set a midi channel for each track midi out and with a nanokey you set a midi channel per scene-to a synth. Unless AUM can route midi from multi channels whilst using scenes on the nanokey. Then the record button would need a selectable midi channel, like the midi channels for the midi out tracks in Drambo.

Thanks.

no1normal

@echoopera said:
Spent some time getting the following mapped:
. Scene Selections + CrossFader
. Audio Channels 1-8 Mixer Volume
. Patterns 1-8 Selector
. 2 octave Chromatic Keyboard
. Play
. Record
. Undo
. Steps Mode

Used up 2 Custom Modes to make it work so we’ll see how it goes. So awesome to have up to 4 Custom Modes on the X and it should be the perfect Drambo midi controller.

Works nicely on the mini also. I did find the faders a little redundant as you can only use half the height of the launchpad fader before you start peaking channels in drambo. Unless there is a way to restrict fader distance like when mapping controls directly to AUM?

sigma79

I will map tomoz.

Think it will need to map to the midi channel you select on midi sequencer page and the nanokey.

This means Id need to select scene on nanokey, then press record and un-record for each synth recording.

Think it might be better if the record could be an independent midi channel.

echoopera

Here's a better image with appropriate call outs:

Vlad11

@echoopera said:
Here's a better image with appropriate call outs:

F brilliant! Thanks

oceansinspace

sick lil rig man! hails