Let's learn/re-learn Drambo 2.0 together

wim

@jollyDodger said:

@wim said:

@jollyDodger said:

@wim said:
It's really simple. Just place DrumComputer on a track. Send notes to it to sequence it. Different notes trigger different pads, so only one sequencer track is needed. To split the signal by multi-out, you just tap the audio icon on the destination and you'll see the choice of outputs on DrumComputer. You can use layers, a mixer, or other tracks for your separate channel processing. Anything that is to the "right" of DrumComputer can accept any one of its outputs.

If you haven't set up multi-output in DC before, the quickest way to do so is to go to the gear icon, then tap the Quick Setup icon at the bottom-right of the Channel Assignment section.

Thanks Wim, that’s how I have it now, but it limits me to a drum sequencer where steps with more than two kit parts played at the same time are shown in the UI as a chord due to Drambo not have a special drum type track. I know ‘comp’ in the bar graph allows some separation of notes for adjusting, but I really like having separate rows in the step seq for each different part of the kit, it makes programming and editing a bit easier when jamming live. So that’s why I was wondering if I can route midi (or audio) backwards through Drambo, as a workaround.

You can have multiple "sequencing" tracks. You don't need to route them backward. Just make sure that DC is on the track after your sequencing tracks. Then add a Midi Mixer module before DC and add the other tracks' Midi outputs to it. Lastly, set DC's Midi input to the Midi Mixer output.

(I haven't tested this and don't have time now, but that should work.)

Using midi mixer works, and that’s another great workaround, thanks.. but I can’t add fx on each channel in Drambo this way. I will try the midi feedback module next… in lieu of a Drambo step ‘drum track’ i.e. DrumTrack(midi only)>DrumComputer>AudioTracks

Yes you can add FX on each DC channel. You just need to learn how to use a Layer Mixer. There are other ways to do it, but that's the most compact and straightforward IMO.

I'm really not sure why you think you need the Midi feedback for this. I can't even think of how that would help you in the first place. And it will add latency.

wim

@jollyDodger - here's a nice, compact way to do it using Drambo inside itself as the MIDI sequencer.

• The Drambo AUv3 is where you can do your sequencing. There are 10 tracks, one for each DC pad. Each track has a single Midi Out module. You can also do without the Midi Out module and just set each track to output to Midi Out in its settings.
• Drum Computer Midi Input is set to the Midi Output of the Drambo AU.
• Each layer of the Layers Mixer is set to receive audio from the corresponding DC pad. You can put whatever FX you want in each layer.

Grandbear

@wim said:
@jollyDodger - here's nice, compact way to do it using Drambo inside itself as the MIDI sequencer.

• The Drambo AUv3 is where you can do your sequencing. There are 10 tracks, one for each DC pad. Each track has a single Midi Out module. You can also do without the Midi Out module and just set each track to output to Midi Out in its settings.
• Drum Computer Midi Input is set to the Midi Output of the Drambo AU.
• Each layer of the Layers Mixer is set to receive audio from the corresponding DC pad. You can put whatever FX you want in each layer.

I just want to add that for future convenience you can save all of this as a track preset or, if you add the modules to a rack, as a rack preset, which is an often overlooked Drambo feature. No other host has something like this, only at most FX chain presets.

mistercharlie

You could also use Polybeat or Octachron in place of the Drambo AU here, for the sequencing. I find that if I host Drambo inside Drambo it gets very confusing.

jollyDodger

@wim said:
I'm really not sure why you think you need the Midi feedback for this. I can't even think of how that would help you in the first place. And it will add latency.

Tracks need imo to be easily accessible for both for midi and audio. So I’m not separating midi and audio tracks, duplicating them or hiding them in layers. I like that grooveBox/octatrack jamming UI, that Drambo has, and going into sub-groups, is for me only geeking out with sound-design or tech-setup. Having the audio and midi in the same track keeps it simple when performing.

In the non-working example bellow, the feedback module does not work with midi?

Part of the issue here is that Drum computer is too heavy to put on each track separately for individual hits, or that my modular sound design skills can’t match the accessibility and acoustics of DC (I.e. I could do it all in Drambo)

@Grandbear yes Drambo is great like that, saving modularised solutions, you can recall.

wim

@jollyDodger - OK, the AUv3 method isn't the best for you, but I still maintain that you do not need the midi feedback at all to achieve what you want to do. If I have time tonight I'll put together a working example.

That said, quickly looking at your example, it looks like you have DC's midi input connected to the track. It needs to be connected to the Feedback Rcv 1 module.

cokomairena

@Angie said:
Does Drambo have a handy dandy MIDI panic button? Um…asking for a friend. 🤣

undo+play should do it if I remember correctly, but it seems to not always work

everything involving the u button is dangerous and finicky, I'm scared even naming it twice xD

cokomairena

@jollyDodger said:

@wim said:
I'm really not sure why you think you need the Midi feedback for this. I can't even think of how that would help you in the first place. And it will add latency.

Tracks need imo to be easily accessible for both for midi and audio. So I’m not separating midi and audio tracks, duplicating them or hiding them in layers. I like that grooveBox/octatrack jamming UI, that Drambo has, and going into sub-groups, is for me only geeking out with sound-design or tech-setup. Having the audio and midi in the same track keeps it simple when performing.

In the non-working example bellow, the feedback module does not work with midi?

Part of the issue here is that Drum computer is too heavy to put on each track separately for individual hits, or that my modular sound design skills can’t match the accessibility and acoustics of DC (I.e. I could do it all in Drambo)

@Grandbear yes Drambo is great like that, saving modularised solutions, you can recall.

I use sitala and have the first three tracks dedicated to sequence the same instance, just add sitala on the third track and use a midi mixer there, I'm not sure if that's what you want to do or not.

rs2000

@cokomairena said:

@jollyDodger said:

@wim said:
I'm really not sure why you think you need the Midi feedback for this. I can't even think of how that would help you in the first place. And it will add latency.

Tracks need imo to be easily accessible for both for midi and audio. So I’m not separating midi and audio tracks, duplicating them or hiding them in layers. I like that grooveBox/octatrack jamming UI, that Drambo has, and going into sub-groups, is for me only geeking out with sound-design or tech-setup. Having the audio and midi in the same track keeps it simple when performing.

In the non-working example bellow, the feedback module does not work with midi?

Part of the issue here is that Drum computer is too heavy to put on each track separately for individual hits, or that my modular sound design skills can’t match the accessibility and acoustics of DC (I.e. I could do it all in Drambo)

@Grandbear yes Drambo is great like that, saving modularised solutions, you can recall.

I use sitala and have the first three tracks dedicated to sequence the same instance, just add sitala on the third track and use a midi mixer there, I'm not sure if that's what you want to do or not.

Audio feedback is done via Feedback Send and Receive modules.
MIDI feedback can be done using a MIDI Out module sending to Drambo's "MIDI feedback" port and setting the track input to the same feedback port.

You have the choice:
Either place DrumComputer first, route its audio outputs to tracks and use the MIDI feedback port to sequence the DC instruments from the tracks behind it,
or place DC last and merge (mix) all MIDI tracks to sequence it.

In order to have one dedicated track for each DC instrument, I find the MIDI feedback option more elegant and likely more efficient.

rs2000

@rs2000 said:

@cokomairena said:

@jollyDodger said:

@wim said:
I'm really not sure why you think you need the Midi feedback for this. I can't even think of how that would help you in the first place. And it will add latency.

Tracks need imo to be easily accessible for both for midi and audio. So I’m not separating midi and audio tracks, duplicating them or hiding them in layers. I like that grooveBox/octatrack jamming UI, that Drambo has, and going into sub-groups, is for me only geeking out with sound-design or tech-setup. Having the audio and midi in the same track keeps it simple when performing.

In the non-working example bellow, the feedback module does not work with midi?

Part of the issue here is that Drum computer is too heavy to put on each track separately for individual hits, or that my modular sound design skills can’t match the accessibility and acoustics of DC (I.e. I could do it all in Drambo)

@Grandbear yes Drambo is great like that, saving modularised solutions, you can recall.

I use sitala and have the first three tracks dedicated to sequence the same instance, just add sitala on the third track and use a midi mixer there, I'm not sure if that's what you want to do or not.

Audio feedback is done via Feedback Send and Receive modules.
MIDI feedback can be done using a MIDI Out module sending to Drambo's "MIDI feedback" port and setting the track input to the same feedback port.

You have the choice:
Either place DrumComputer first, route its audio outputs to tracks and use the MIDI feedback port to sequence the DC instruments from the tracks behind it,
or place DC last and merge (mix) all MIDI tracks to sequence it.

In order to have one dedicated track for each DC instrument, I find the MIDI feedback option more elegant and likely more efficient.

In @jollyDodger's example above, there's no need for the FB Send and Receive modules.
Just place a MIDI Out module behind the MIDI Mixer, set its output port to "MIDI feedback" and let the track that holds DC receive MIDI notes from the MIDI feedback port.

jollyDodger

@rs2000 said:

@rs2000 said:

@cokomairena said:

@jollyDodger said:

@wim said:
I'm really not sure why you think you need the Midi feedback for this. I can't even think of how that would help you in the first place. And it will add latency.

Tracks need imo to be easily accessible for both for midi and audio. So I’m not separating midi and audio tracks, duplicating them or hiding them in layers. I like that grooveBox/octatrack jamming UI, that Drambo has, and going into sub-groups, is for me only geeking out with sound-design or tech-setup. Having the audio and midi in the same track keeps it simple when performing.

In the non-working example bellow, the feedback module does not work with midi?

Part of the issue here is that Drum computer is too heavy to put on each track separately for individual hits, or that my modular sound design skills can’t match the accessibility and acoustics of DC (I.e. I could do it all in Drambo)

@Grandbear yes Drambo is great like that, saving modularised solutions, you can recall.

I use sitala and have the first three tracks dedicated to sequence the same instance, just add sitala on the third track and use a midi mixer there, I'm not sure if that's what you want to do or not.

Audio feedback is done via Feedback Send and Receive modules.
MIDI feedback can be done using a MIDI Out module sending to Drambo's "MIDI feedback" port and setting the track input to the same feedback port.

You have the choice:
Either place DrumComputer first, route its audio outputs to tracks and use the MIDI feedback port to sequence the DC instruments from the tracks behind it,
or place DC last and merge (mix) all MIDI tracks to sequence it.

In order to have one dedicated track for each DC instrument, I find the MIDI feedback option more elegant and likely more efficient.

In @jollyDodger's example above, there's no need for the FB Send and Receive modules.
Just place a MIDI Out module behind the MIDI Mixer, set its output port to "MIDI feedback" and let the track that holds DC receive MIDI notes from the MIDI feedback port.

Thanks @rs2000 works a treat! Had to set midi input to none on the drum channel tracks to stop the midi feedback endlessly looping.

sigma79

I messaged beepstreet lol.

Asked for a module that works like beat scholar.

Not sure how it would work and is based around mukti track anyway or an instance per track.

Ideally just a way of implementing Drambo size knobs ( instead of pies ) which would gain sub divisions and be auto like Euclidean but ideally ( perhaps ) able to be written to the main sequencers tracks ( maybe to gain additional sequencer functions and obviously pattern arrangment )

Based around multi track.

Might mean the user can resize a few modules to work on without switching tracks. Modules I dont think can be removed from a rack though and resized like AUs.

but if so.

Manually resize but then a midi trigger command that overides all resizing and made so by beepstreet.

The maximum amount of tracks ( knob modules ) currently of Drambo ( 12 ) and resized for ipad screens.

So multi per instance modules would looks like a single instance module.

sigma79

@jollyDodger said:

@rs2000 said:

@rs2000 said:

@cokomairena said:

@jollyDodger said:

@wim said:
I'm really not sure why you think you need the Midi feedback for this. I can't even think of how that would help you in the first place. And it will add latency.

Tracks need imo to be easily accessible for both for midi and audio. So I’m not separating midi and audio tracks, duplicating them or hiding them in layers. I like that grooveBox/octatrack jamming UI, that Drambo has, and going into sub-groups, is for me only geeking out with sound-design or tech-setup. Having the audio and midi in the same track keeps it simple when performing.

In the non-working example bellow, the feedback module does not work with midi?

Part of the issue here is that Drum computer is too heavy to put on each track separately for individual hits, or that my modular sound design skills can’t match the accessibility and acoustics of DC (I.e. I could do it all in Drambo)

@Grandbear yes Drambo is great like that, saving modularised solutions, you can recall.

I use sitala and have the first three tracks dedicated to sequence the same instance, just add sitala on the third track and use a midi mixer there, I'm not sure if that's what you want to do or not.

Audio feedback is done via Feedback Send and Receive modules.
MIDI feedback can be done using a MIDI Out module sending to Drambo's "MIDI feedback" port and setting the track input to the same feedback port.

You have the choice:
Either place DrumComputer first, route its audio outputs to tracks and use the MIDI feedback port to sequence the DC instruments from the tracks behind it,
or place DC last and merge (mix) all MIDI tracks to sequence it.

In order to have one dedicated track for each DC instrument, I find the MIDI feedback option more elegant and likely more efficient.

In @jollyDodger's example above, there's no need for the FB Send and Receive modules.
Just place a MIDI Out module behind the MIDI Mixer, set its output port to "MIDI feedback" and let the track that holds DC receive MIDI notes from the MIDI feedback port.

Thanks @rs2000 works a treat! Had to set midi input to none on the drum channel tracks to stop the midi feedback endlessly looping.

Thats mad.

Using an ipad just for drums.

Per instance AUs.

lol.

The Drambo veterans give good advice.

sigma79

@sigma79 said:
I messaged beepstreet lol.

Asked for a module that works like beat scholar.

Not sure how it would work and is based around mukti track anyway or an instance per track.

Ideally just a way of implementing Drambo size knobs ( instead of pies ) which would gain sub divisions and be auto like Euclidean but ideally ( perhaps ) able to be written to the main sequencers tracks ( maybe to gain additional sequencer functions and obviously pattern arrangment )

Based around multi track.

Might mean the user can resize a few modules to work on without switching tracks. Modules I dont think can be removed from a rack though and resized like AUs.

but if so.

Manually resize but then a midi trigger command that overides all resizing and made so by beepstreet.

The maximum amount of tracks ( knob modules ) currently of Drambo ( 12 ) and resized for ipad screens.

So multi per instance modules would looks like a single instance module.

In theory though.

If every drum track has access to drambos tempo per track.

It might be similar anyway?

sigma79

Not the official Drambo thread.

tyslothrop1

I have a question concerning the CV quantizer. I'd like to feed it A minor and get A harmonic minor so I activate all the white keys except G and add G#. Now when I play a G I would need it to quantize up to G#... Unfortunately it quantizes down to F, I think. Is there a way to change that?

rs2000

@tyslothrop1 said:
I have a question concerning the CV quantizer. I'd like to feed it A minor and get A harmonic minor so I activate all the white keys except G and add G#. Now when I play a G I would need it to quantize up to G#... Unfortunately it quantizes down to F, I think. Is there a way to change that?

The CV quantizer always quantizes to the closest next enabled note which isn't always what you want.
Simple solution: You can add an Offset or a Scale+Offset module before the input of CV quantizer and give the input just that little lift it needs to be mapped to G#.
If the other notes end up wrong now then a slightly more advanced solution is to add a Math => Function module and use the "A=B" function to detect the pitch that needs to be corrected.
One octave equals * 0.125 in Drambo's "analog signal world", in case you need to calculate the correct numbers, and a semitone consequently is 0.125 / 12.
The Function module will output 1 when the formula is true for its two input signals and you can scale it down to just one semtone (Using Math => Scale or Scale&Offset) for adding to the CV signal than enters your CV quantizer.

Here's an example that allows you to shift only the G note to be mapped to whatever note you like by turning the Amount knob in the Scale module (you can also enter a negative number in the Scale module btw):

tyslothrop1

@rs2000 cool, thanks. There are quite a couple utility- and math-modules, that I don't understand yet and maybe building what you did in the screenshot may help me with that a little. Coming back to your description might after that clear things up for me, as I didn't get that yet. That will probably solve my problem.

Just one little thing though: you (and the in-app-help) state that the cv-quantizer quantizes to the closest activated note, but that's not, what's happening here. If I play a G the closest is one semitone up to G#, but it actually goes down two semitones to F.

sigma79

Does the quantization switch in settings save in off mode?

Think Iv saved in off mode but it dosent generally save in off mode, so I assume it dosent save.

Wonder why Drambo is programmed to save with quantiztion on?

Theres also a descrepency in tempo around 83 and 84 bpm. Via abe link. An ipad will say 82. The other 83. Thought it might just be a UI thing but aum will tell you its something like 82.95 bpm.

So I dont use this bpm. In case theres bpm drift over time.

tyslothrop1

@rs2000 said:

@tyslothrop1 said:
I have a question concerning the CV quantizer. I'd like to feed it A minor and get A harmonic minor so I activate all the white keys except G and add G#. Now when I play a G I would need it to quantize up to G#... Unfortunately it quantizes down to F, I think. Is there a way to change that?

The CV quantizer always quantizes to the closest next enabled note which isn't always what you want.
Simple solution: You can add an Offset or a Scale+Offset module before the input of CV quantizer and give the input just that little lift it needs to be mapped to G#.
If the other notes end up wrong now then a slightly more advanced solution is to add a Math => Function module and use the "A=B" function to detect the pitch that needs to be corrected.
One octave equals * 0.125 in Drambo's "analog signal world", in case you need to calculate the correct numbers, and a semitone consequently is 0.125 / 12.
The Function module will output 1 when the formula is true for its two input signals and you can scale it down to just one semtone (Using Math => Scale or Scale&Offset) for adding to the CV signal than enters your CV quantizer.

Here's an example that allows you to shift only the G note to be mapped to whatever note you like by turning the Amount knob in the Scale module (you can also enter a negative number in the Scale module btw):

Ah, I think I get it:

If unquantized note and quantized note equals G, then use the scaler after that add the two together and run them through the second quantizer. Brilliant, thanks. I guess I'm a step closer to getting to grips with the math-modules.

tyslothrop1

@sigma79 said:
Does the quantization switch in settings save in off mode?

Think Iv saved in off mode but it dosent generally save in off mode, so I assume it dosent save.

I would like an option in the settings, to decide, if quantize is on or off by default. I tend to forget to turn it off before recording and would rather turn it on, when I want it.

Gravitas

@tyslothrop1 said:

@sigma79 said:
Does the quantization switch in settings save in off mode?

Think Iv saved in off mode but it dosent generally save in off mode, so I assume it dosent save.

I would like an option in the settings, to decide, if quantize is on or off by default. I tend to forget to turn it off before recording and would rather turn it on, when I want it.

It should default to last used settings.
I’ve reported it to the dev.

tyslothrop1

@Gravitas cool, thanks.

Gravitas

@tyslothrop1 said:
@Gravitas cool, thanks.

No probs.

Gravitas

@Gravitas said:

@tyslothrop1 said:
@Gravitas cool, thanks.

No probs.

It’ll be sorted for the next update.

tyslothrop1

@Gravitas awesome!

cam

I have 4 Pattern in Drambo with 5 instances of Sampler and Instruments. Any Chance to mute the track automaticaly? E.G.:So if pattern 2 is playing my Pad is muted.
Any chance to record the mute Session? So I have a Gated sequence?

Thanks in advance

sigma79

Does Drambo enable switch. Conserve cpu when switched off?

Grandbear

@sigma79 said:
Does Drambo enable switch. Conserve cpu when switched off?

Conserve CPU like Loopy Pro does with idle plugins? Nope

sigma79

@Grandbear said:

@sigma79 said:
Does Drambo enable switch. Conserve cpu when switched off?

Conserve CPU like Loopy Pro does with idle plugins? Nope

Shame.

Maybe it can be implemented.

Feel like I need another ipad. Just because I make a template.

So idle would be good.

Is the switch just to bypass?