Forums
I've added this mini "How to" that solves a recurring problem.
https://sourceforge.net/p/qtractor/wiki/How%20To%20-%2015%20Use%20Multi…
I've added this mini "How to" that solves a recurring problem.
https://sourceforge.net/p/qtractor/wiki/How%20To%20-%2015%20Use%20Multi…
Creative!
Creative!
I'm preparing a "How to" that will interest you
Maybe you already do it this way.
It's easy to handle the audio of multiple drum instruments separately.
The trick is to send auxiliary sends to MIDI buses instead of auxiliary audio.
Each instrument bus starts with a MIDI filter that only lets the instrument's note pass through.
This allows you to create a stable flow regardless of the plugin you use. It doesn't require multi-channel plugins, but it will work with them too.
It's also possible to use different plugins for each instrument.
Therefore, it's not only simpler than multi-channel audio, but also more versatile.
re. How to - 15 Use Multiple SoftSynths on a Track...
jfyi. it is now live:
timestamp: 2025-06-20 09:00+0100
cheers
Thanks
Thanks
Interesting. I'll have to…
Interesting. I'll have to give that a read. I'm pretty happy when my existing strategy of sending my drums (generated from a multi-out plugin) to a multi-in audio bus which is then split (by channel) to individual bus' (and then back into a single stereo). It takes a bit longer to setup but it's an obvious pattern (which means I'll understand it if I don't look at the material for months) and more importantly, I have access to several key areas. If I want to get into the snare drum, there's a place for it. If I want to get at the whole kit, there's a place for it... etc, etc...
I tend to think managing things at the MIDI note level (the mappings needed for the filter) wouldn't scale well for 2 reasons:
That said, I can see the MIDI filtering approach being MORE efficient for certain scenarios where drum performances are more simplistic and subject to less ongoing interaction during the writing phase.
Add new comment