What’s the difference between a multi-out track and a normal track?

jameslondon74

Let me elaborate my question, e.g. an 8 track project in Drambo running on separate per-track channels in AUM.

What’s the difference between:
1. AUM tracks 1-8 containing Drambo tracks 1-8 accordingly
2. AUM tracks 1-8 containing 1x Drambo project split across 8 multi-outs accordingly

Trying to get my head around exactly what multi-out offers...

Thanks!

Samu

With multi-out you've got one instance of Drambo running that can output to 8 different tracks if needed.

At least for me it's easier to keep check of one instance than 8 individual instances and with reduced CPU usage and less files to save it's a win-win situation.

[Deleted User]

With multiout you can apply effects to individual tracks

jameslondon74

@rms13 said:
With multiout you can apply effects to individual tracks

You can that with a standard project too.

Seems like the previous poster nailed it - more efficient and simpler. But there doesn’t seem to be any difference between
1. 8 x Separate Drambo tracks on separate AUM tracks
2. 1 x Drambo project split into 8 multi outs.

I think another difference would be taking say, Drambo track 1 across several different AUM tracks. Perhaps the difference lies in treating multi-outs as OUTPUTS rather than instances of the same track.

Like, I could have a wet and dry version of the same Drambo track, and perform it in the one channel.

royor

@jameslondon74 as @Samu already mentioned, with the 8 multi-outs version, you can control ALL 8 channels from ANY 1 of those.. they’re the same instance.. just split up..
Whereas 8 separate Drambos means each drambo channel needs to be controlled by that particular drambo.. they’re ALL individual.. so you end up juggling many windows instead of one.. does that make sense?

jeez.. how many times can I mention drambo in one comment..🤷🏻‍♂️ 🤪

jameslondon74

Got it! 1 project on 8 tracks, vs 8 projects on 8 tracks.

The end result could still be the same though, which is what was throwing me.

McD

It sounds like it boils down to having control of when different sound sources are "mixed".
One output implies that (potentially) multiple sound sources (bass, drums, pads, etc) are mixed in the app and multi-out can allow the mixing decisions (and knobs/sliders) be
adjusted in a later stage. Following the classic studio bussing models each track becomes
a potential bus that can be routed though FX, split or combined towards a final "stereo" dual channel mix down output.

Like most capabilities that shift the math from 2 to N the number of permutations goes up
exponentially.

Tradeoffs.

Sometimes we get "mixed" by the technology and have drop outs.

supadom

@jameslondon74 said:
Got it! 1 project on 8 tracks, vs 8 projects on 8 tracks.

The end result could still be the same though, which is what was throwing me.

Dude, at times one page of Drambo makes my head spin like a top. Can’t imagine what a project with several instances must be like to manage brrrrrrr. Multi out is a godsend but I still don’t trust it for live jamming. There’s been a lot of talk of cpu use when in development, I must have gotten emotionally scared 🤣

sigma79

I had a vast auv3 setup and switched to multiout.

I lost faders per track ( on a controller ) plus inputing midi whilst still tweaking another drambo track. You still can though with multiout. Although midi trigger also switches track. If you are already tweaking a filter or something on previous track, its still adjustable but invisible.

Gains from multiout are as described but also more intimate via screen switching.

I have multiout, plus auv3, plus samplers and controllers same as previous setup. For app and effect show plugin.

Hoping drambo can host effects and p-lock to sequencer?

AudioGus

Yah I really gotta give Drambo another try. I pretty much stopped last time when I was getting a headache imagining the export / mixing stage of the process. But now, multi out may do the trick fine.

Gravitas

@AudioGus said:
Yah I really gotta give Drambo another try. I pretty much stopped last time when I was getting a headache imagining the export / mixing stage of the process. But now, multi out may do the trick fine.

We can now export audio at 32bit as a single file.
also having the multi-out into AUM is very useful.

Until I've developed my own dRambo mastering tools
using AUM is perfect for mixing and using other apps
and with the addition of WebDAV we can also
move and export files with ease.

[Deleted User]

@jameslondon74 said:

@rms13 said:
With multiout you can apply effects to individual tracks

You can that with a standard project too.

Seems like the previous poster nailed it - more efficient and simpler. But there doesn’t seem to be any difference between
1. 8 x Separate Drambo tracks on separate AUM tracks
2. 1 x Drambo project split into 8 multi outs.

I think another difference would be taking say, Drambo track 1 across several different AUM tracks. Perhaps the difference lies in treating multi-outs as OUTPUTS rather than instances of the same track.

Like, I could have a wet and dry version of the same Drambo track, and perform it in the one channel.

Yeah, never mind me. I was confused as to what you were asking

aleyas

@jameslondon74 said:
The end result could still be the same though, which is what was throwing me.

I think you may be overlooking a major aspect of Drambo. Modulation between tracks.
In Drambo signals flow from left to right, but also from top to bottom. This means that track 8 could potentially receive modulation, midi, or audio from any of the preceding tracks 1-7.

So, 8x instances of Drambo ≠ 1 multi out instance.. that's because signals can not be routed between separate instances, whereas they can be routed in a single multi-out project.. this inter-track modulation IS reflected and preserved with multi-out.

For example - a kick drum from track 1 can be routed to a transient detector on track 2. This transient detector could send a gate signal to a CV sequencer on track 2 which steps through the pitch of a high-hat sample. The high-hat could then be routed to a waveguide on track 3 which has an amp envelope triggering from trigs from its own track sequencer. And so on and so forth, signals can cascade from track 1 to track 2, all the way down subsequent tracks till track 8. That would be simply impossible using 8x different instances.

I might upload a demo of this later.

@jameslondon74 said:

@rms13 said:
With multiout you can apply effects to individual tracks

You can that with a standard project too.

Seems like the previous poster nailed it - more efficient and simpler. But there doesn’t seem to be any difference between
1. 8 x Separate Drambo tracks on separate AUM tracks
2. 1 x Drambo project split into 8 multi outs.

supadom

@aleyas said:

@jameslondon74 said:
The end result could still be the same though, which is what was throwing me.

I think you may be overlooking a major aspect of Drambo. Modulation between tracks.
In Drambo signals flow from left to right, but also from top to bottom. This means that track 8 could potentially receive modulation, midi, or audio from any of the preceding tracks 1-7.

So, 8x instances of Drambo ≠ 1 multi out instance.. that's because signals can not be routed between separate instances, whereas they can be routed in a single multi-out project.. this inter-track modulation IS reflected and preserved with multi-out.

For example - a kick drum from track 1 can be routed to a transient detector on track 2. This transient detector could send a gate signal to a CV sequencer on track 2 which steps through the pitch of a high-hat sample. The high-hat could then be routed to a waveguide on track 3 which has an amp envelope triggering from trigs from its own track sequencer. And so on and so forth, signals can cascade from track 1 to track 2, all the way down subsequent tracks till track 8. That would be simply impossible using 8x different instances.

I might upload a demo of this later.

@jameslondon74 said:

@rms13 said:
With multiout you can apply effects to individual tracks

You can that with a standard project too.

Seems like the previous poster nailed it - more efficient and simpler. But there doesn’t seem to be any difference between
1. 8 x Separate Drambo tracks on separate AUM tracks
2. 1 x Drambo project split into 8 multi outs.

This might explain why it didn’t seem to make a difference to me as I don’t do any vertical audio routing, not even as much as sidechain compression.

It makes sense though. I wonder if routing a parallel signal in track settings vertically as well as to a separate channel might be possible? Might cause gain increase in some cases I guess but likely solvable via careful balancing?

Sorry more questions than answers, I haven’t tried it yet. 😇