Welcome to %s forums

BrainModular Users Forum

Login Register

32x32+ stereo routing matrix built using busses

Discussions about add-ons, announcements
Post Reply
gurulogic
Member
Posts: 1019
Contact:

Unread post by gurulogic » 20 Feb 2009, 08:50

I have deleted this one to clear out add-ons section clutter as I have uploaded a smaller example that should be easier to understand and also includes delay compensation for bus delays. I can upload again if anyone wants it for some reason

Add ons > Others

my intended use for this patch is to be able to use the preset manager to recall and manage vst plugin parameters and routings.
There are 32 "cells" which could each contain a plugin or other native Usine effect, although I have given eight cells
the option of being able to be mixed down to a single destination and then returned if desired to the matrix as there is no other way to tell any one cell to get the audio stream from more than one source.

Also, if so inclined, further fx could be placed on the input channels and output channel assignments which are also recallable with the preset manager.
In the event that you have no use for this many cells, inputs or outputs, simply delete the unwanted parts and update the listboxes via the Comma Text Left and Comma Text Right Textfields.

For using this, my approach would be to insert Usine vst onto every channel in my host as needed,open the interface, insert a vst plugin within a cell, connect the GetBus's and the Audio Outs/VU meters.
It is now possible to route audio from the input, through the cell and out again by clicking on the cell name button (ie:cell 1) to activate the cell and use the two list boxes in the interface container for the particual cell to choose the audio input source for either left or right channels, then activating an output channel and making a selection of the source audio cell.
Keep in mind that all routing selections are "get from" and not "send to" as the busses can make really bad noises if the send bus were manipulated while a realtime audio stream was passing through it.
One thing to watch out for is telling a cell to get audio from itself...not so good!

There is one unconnected Button and one Switch in each cell which I have put to the interface for easy access to bypassing the plugin and opening the plugin. X is bypass, > opens the plugin. Keep in mind that disabling the cell also bypasses the plugin.

On the outputs, M mutes the output and D (when lit green) feeds the signal to a continuously rolling 2 bar buffer on Output 16 (initially inactive) that is linked to the fader that controls presets so that every time a preset is selected,whatever outputs also assigned to the buffer will fade out smoothly over 2 bars as the next routing/vst configuration is activated.This allows the possibility of an FX tail on what would otherwise be an abrupt cutoff.

I spent a good many hours fiddling with a way to have each cell have a smooth fade out of several milliseconds or so in order to prevent any chance of a "pop" sound from audio being cut off abruptly but I:
A: could not even get a fade that would at all completely prevent a pop when fading out Bassliner on init settings (my benchmark)
B: Could not find a way to have the cells fade intelligently so that they only faded when I wanted them to.If anyone has any ideas on how to avoid any chance of a "pop" sound when changing presets....?

I haven't extensively tested this in regular daily use yet so there may be some blunders in the design and of course I would love to hear any ideas of how the design could be improved.

This might not fit on your monitor, I built it on 1600 x 1200 but it should work on 1600 x 1050-ish.Otherwise you may have to rearrange the interface yourself in order to access the lower section,the output channels lisboxes.

My usage will require lots more preset managers, however I did not do this as it may be personal preference as to how to control preset selection..

And if this is completely useless to anyone except myself, I perfectly understand :)

User avatar
senso
Site Admin
Posts: 4425
Location: France
Contact:

Unread post by senso » 20 Feb 2009, 09:40

what huge job!
you took an intelligent option, dealing with aux buses names instead audio routing; so this patch takes only 1.5% CPU on my two years old machine...
cool++

gurulogic
Member
Posts: 1019
Contact:

Unread post by gurulogic » 20 Feb 2009, 09:52

Cpu usage will definately climb as you activate "cell" patches and outputs.

Post Reply

Who is online

Users browsing this forum: No registered users and 23 guests