Was trying to set up some input/output stuff today for a Drambo template that sort of mimic the OT’s Cue output. I wanted it a little different though, I wanted it so I could toggle between Track output, Cue output and Both (I have an iConnectivity Audio 4 so my ‘cue output’ is a separate virtual stereo USB output that I route to the headphone out on the iCA4)
This is where I got to but it seems a bit clunky. Can anyone improve it?
Just reaslied that looks confusing as fuck! The OUT goes straight to the module output via the Mixer. CUE goes to the first Audio Output (3/4). BOTH goes to the second Audio Output and the second input on the Mixer. The CV Sequencer is just an idea to be able to cycle through the 3 modes.
Hi does anyone know if I can have Drambo on 2 devices? Bought for iPhone and working as expected. Just added from App Store to new MacBook Pro running Monterey and I’m struggling…save me some time if anyone knows if its just a simple thing like a licensing issue…
(Just so you know, an oscillator will sound, but the ADSR doesn’t function. And the keys have no effect on the osc pitch)
I just tested mine on my MBPro M1 with Monterey and it is working when I load an OSC. But I barely use it and can’t find the ADSR to try and mimic your issue. Ive been too busy with other stuff to learn the software yet, so even just connecting the output of the OSC to something else is beyond me at the moment. Sorry but I suspect you are ok with the licensing part though.
Thank you @BassesAndPads that’s really kind. I thiiiiiink there is some disconnect between the MBP keyboard and the sound generation. I press a key, the right pad lights up and there is no sound.
Oh well. I’ll keep trying but, like you, I’ve had it ages and didn’t use it on my phone (too small), and don’t have or want to buy an iPad…Not sure what I’m doing wrong but maybe I’ll work it out
Getting there. Needed a MIDI to CV module in 1st position to get keyboard to trigger, then worked out routing to MBP speakers…Thanks for the encouragement
Oh! Yeah you definitely need that. Doesn’t the template "8 Tracks (MIDI to CV) load by default for you?
Good perseverence though! My advice would be to get used to the signal flow. The schema is that all signals flow out of the right side of a device and in through the left of the next one in the rack. This means that, for example, audio signals coming out of a device will automatically be routed to the next device on the right of it that can accept audio signals. The same principal though works with CV and modulation. So if you want to apply an LFO to the pitch of a VCO you have to have the LFO to the left of the VCO as the CV signal flows out of the LFO->VCO. If you have, say, an AD envelope to add into the path, this must go to the right of the VCO as the output of the VCO flow into the AD envelope. It’s something to get your head around as this will save you a lot of head scratching
Yes, with what I did and what you say above it has suddenly clicked…well, making a sound that I can turn on and off with my keyboard. It’s a start and I’m sure my DT and M:C cycles knowledge will help. Thanks for taking your time to write that
One thing that’s been bothering me: why does the step view vanish when enlarging the audio unit window? This makes no sense as the sequence navigation bar is still visible. Anyone know if this will be changed or if the clip launcher view will at least be made downward resizable?
Greets Drambophiles, I’ve tried to set up a track to control/automate xfader and scene switches, but no success. The track was spitting out midi as intended but when the fader was mapped to the corresponding Channel and CC, no movement. Am I missing something?
The solution I’ve found is to load an instance of Drambo in Audiobus as a Midi FX and then load Drambo as an AU instrument. I’m revisiting ways to remap midi from the OT scene switches and x fader to Drambo’s x-fader and scenes buttons. The amp module works as a CC value multiplier, so with a couple of them and careful level setting, an OT to Drambo scene mapper rack should be possible.
Screenshots taken on my iPhone but same thing happens on the iPad. The problem on the iPad is that the clip view is either taking up half the screen or the full screen - there‘s no option to slide it downwards like with the navigation bar/keyboard.
Ok, one more time then with screenshots from my iPad (now that I’m home and have access)!
Not all AUv3 plugins resize correctly such as TAL-U-NO-LX. When that happens there’s no way to view the complete plugin as well as the sequencer steps (I use an external MIDI keyboard so don’t need the internal one).
Here’s the normal view - tracks/clips plus sequencer steps and navigation bar are visible but not the whole plugin is accessible:
The obvious remedy would be - like stated above - to make the clip launcher view downwards resizable (currently it takes up either the lower half of the screen or the full screen).
Does anyone know if it’s possible to map MIDI controls to Drambo controls but have them respond to the active track instead of targetting specific tracks? As in the way MIDI keyboard responds to active track (if you set it to).
I believe if you set the Midi Channel for your Tracks to “OMNI” and set all the Tracks to “Receives MIDI” to Active Track, it should only receive Midi when you select the Track in Drambo.
Hmmm. There is no omni mode as far as I can see, only ‘Any’ for the channel selection. I tried ‘Any’ and ‘Active Track’ but the MIDI mapping is tied to the output channel of the MIDI device that you map the control to.
