Quote:
Fine by me, I've been posting about cabling anyway so it's topical to that.
Quote:
i wanna ask bernie if he's okay with that - after all, it's a bit off-topic and better belongs in the live sound forum...
Quote:
Originally Posted by
sirjuxtable
➡️
Could you elaborate a little more on this?
Quote:
the exceptions to the rule are of course festivals/live events, specifically in case bands don't bring their own cabling: correctly repatching signals from various subsnakes between bands is one of the most important tasks! - strangely enough, many younger techs no longer seem to be familiar with this process anymore and end up doing weird crosspatches between subsnakes, rather than getting things right in the patch/splitter world...?!
alright then...
i assume you are familiar with the concept of the '
festival patch'*? for me, there is zero reason why not to stick to it - anytime/anywhere! and personally, i don't get why folks use all different channel orders** for various bands (but then, we all have different taste).
anyway, in live sound (and when broadcasting), you absolutely must get things up and running fast - and reliably/correctly: you don't get a second chance! if you mess up a patch, foh, monitor world, recording and broadcasting simply cannot work and you'll quickly get behind schedule...
...which may have terrible consequences on live broadcast of large shows where advertisers book advertising slots for insane amounts of money or simply for logistical reasons on festivals where truck space/manpower is limited and all resources need to get allocated in the right spot at the right time.
___
the way i proceed is this: submulticores (mostly using lk 37's) go to the patchbay inputs, the patchbay outputs (on xlr's) go to the split input (passive or active), the split outputs (on lk150's, harting and whatnot with xlr fan outs) go to the stageboxes of the various departments (foh, monitors, broadcast).
on a festival, you assign one person to do nothing else than patching the outputs from the various subsnakes to the correct inputs of the splitter so that
all department get the channels in the exact same order - the idea is that if someone is having an issue (say: "i'm not getting any signal on 27"), you can easily track it down and don't have to guess who's getting which signal on what channel...?!
the same person is in charge when patching signals for bands which carry their own stage sub-multicores and for bands which are using the festival's gear (provided by a rental company), the latter of which probably gets used for the majority of band which don't carry their own stage cabling.
each department then may then use their preferred channel layout on their desk which imo would be by far the most easy, most reliable and fastet way to proceed! - of course you need to advance this information and have a capable stage manager who is prepared to enforce even unpopular decisions...
however, the sad reality today is that unexperienced folks can't seem to wrap their head around the fact that what may work well for them when travelling on their own mostly doesn't work (fast enough) when interfacing with larger setups on festivals - the result is that you have separate people doing the patching for each department which imo is not only a misallocation of resources but leaves you in the limbo if something goes wrong: who's in charge then? how quickly can someone fix things without derailing the rest of the production?
___
even though i personally may use a 'weird' layout based to my personal taste when touring with a band for a long time, i adapt my setup for festivals so if get struck down by a lightening or hurt/killed in a car accident, someone else can walk up to my desk and take over without getting lost deep down in the submenues of the desk - and the signals will show up in the channels and in an order that most anyone else is going to expect.
my channel order has been (more or less) the same for decades: for rock/blues/americana, it's: drums, percussion, basses, guitars, keys, horns, vocals, efx...
...and or for classical: 1st violins, 2nd violins, violas, celli, basses, woodwinds, brass, percussion, soloists, etc.
[i admit that since i have been using very capable desks (which i can configure to have quasi endless amounts of inputs, subgroups, stems, auxes, masters, matrices), my desks' structure has expanded:
for instance, on a very large drum kit or a percussion orchestra, i can have a shell group, a metall group, a crunch group etc. without running out of subgroups - or with an orchestra, i can have dca's of close, section, mains, ambis in addition to dca's of the various sections. and of course subgroups and dca's can get assigned to completely different (or mostly similar) groups/sections of instruments!]
___
* for those not familiar with the term: a festival patch essentially means that based on the riders of all bands performing on the same stage on a festival (or at least on the same day), you define a maximum patch/input list that covers all inputs of all bands; on smaller bands, you then just mute/leave the unused channels alone - pretty neat, innit?
** there was a reason in terms of using a specific
track order on some tracks back in the analog days/with tape but we're now definitely off-topic...