template advice

[szaszhareen]

i've recently been inspired to attempt a "master template" which gathers the generators, effects and settings i tend to use and routes them through mixio, in the hopes of saving myself some time on adding machines and tweaking params. I have a couple of questions.



the "thru" at the bottom is jeskola gain. i'm using it since the mixio thru channels aren't accessible when you right click the channel number on the input wire. how can you assign inputs to the thru channels?

in this lovely picture from buzzmachines.com, a few auxsends are shown.



i've tried using this setup, but when i add auxreturn and attempt to get the signal routed properly, most of the channel pairs are silent. sometimes i'll get a signal, but there will be a distorted screeching laid over it. i thought that if (for example) auxsend1 is set to channel L(1) and channel R(2) and auxreturn1 is set to the same channels, the signal will be sent and returned as expected. however, the channel pairs seem almost random. how can i address this problem?

finally, i'm curious to see if anyone else has attempted to make a template like this and how it turned out, and if you have any tips on how i could improve mine.

[UNZ]

mixio thru channels aren't accessible when you right click the channel number on the input wire. how can you assign inputs to the thru channels?

just select "thru" on the OUTPUT channel.
input 1 always goes to THRU 1
input 2 always goes to THRU 2
etc.

for aux send: you also need aux return machines (not shown in the picture), mixio doesn't use aux itself at all. i suggest you use ld auxsend/return.

(and yes, you can have multiple connections from mixio to something else, just insert a dummy machine until the buzz GUI allows this finally).

if you want to build something like a send/return (wet only) effects rack i suggest you use two mixio (or more) connecting the returns to a different mixio instance.

[szaszhareen]

thanks for the advice! I hadn't considered using more than one instance of mixio, guess i was stuck in my mindset of "one mixer to rule them all". I'm using ld auxsend with ld auxreturn, but I'm having trouble getting them to work correctly.

if i add one auxsend and one auxreturn to my project, i can hear the signal from a generator with the default settings on each, but as soon as i add another auxsend/return to machine view, the first set goes silent. after this point, i'm unable to get a signal through the first set of auxsend/return machines no matter which channels they're set to. changing the channel settings will sometimes result in the audio coming through one stereo channel in a distorted manner, and usually results in the machines crashing.

is there a more reliable way to use these machines? I find myself needing sends/returns on a regular basis, and have developed workarounds, but it would be sweet to simplify things and just send/return things wherever and whenever i need to.

[UNZ]

hm, i have heard of problems with aux send/return, but i was under the impression that ld's machines work right. I don't use auxsend myself, maybe someone else can comment here (can't test it right now). What you can try is maybe switching off multithreading. Using latest buzz ?

[thOke]

yes ... if you add more instances of ldaux (send and return), the first two channels freak out, just go silent or crash the machine -
but if you save the bmx with the settings you want and reload it, everything is fine here.

solution: just make a template with as many aux connections you need - don't forget to set up all channels right before you save the template.

here is an example (bmx included in case the template has problems with cases )

LDAux 08 Channels.zip

(2.67 KiB) Downloaded 284 times

imo the aux connections are almost redundant except for those few machines that still depend on them.
you can route anything everywhere without aux machines.

[szaszhareen]

@unz: still using 1480. tried to update today but my computer is being a bugger and telling me "access is denied" to random things and being unreasonably slow at times. i had high hopes that with win7 i wouldnt have to do a yearly clean install, but whatever.

@thoke: thanks! I'll give that a shot. you're probably right about send/return being sort of redundant since we can route stuff anywhere anyway, once again i just need to shift my way of thinking about things.

[UNZ]

imo the aux connections are almost redundant except for those few machines that still depend on them.

not quite true, you can't create feedback connections without aux send/return. if you don't need that, then yes, avoid auxbus imho.

[thOke]

imo the aux connections are almost redundant except for those few machines that still depend on them.

not quite true, you can't create feedback connections without aux send/return. if you don't need that, then yes, avoid auxbus imho.

true