1: Subgroups will be better rather than buses with the channel sends being at a variable level. A subgroup is essentially a post-fader bus with the send level (relative to the ch>lr send level) locked at unity. This means each channel has a simple assign\un-assign, rather than needing to worry about send levels. To set a bus up as a subgroup, select the bus, go over to the config tab, use the 3rd encoder to set the tap point to subgroup, then push to confirm. Now if you select the bus and press the sends-on-faders button, you'll notice the mute buttons above the channel faders for all the channels illuminated. This indicates that those channels are *not* assigned to the selected subgroup. Press the mute buttons so they're not illuminated anymore to assign channels to the subgroup.   2: By default you only get the dry channel signals in LR.   3: You will need to un-assign the individual channels from LR by selecting the channel and pressing the "Main stereo" button in the "Main bus" section of the channel strip. That leaves you with nothing in LR, because by default the bus is also not assigned there. Select the bus, then press the "Main Stereo" button again to assign the selected bus to LR.   Edit: Don't forget to put the bus master fader up so you can actually hear it in LR.  Also, "View" in the "Monitor" section of the console (top left next to the TB section,) "Monitor" tab, and set "Mixbus Solo AFL" on so that you can hear the bus's eq\comp etc in the headphones. Read more

Yes to all quesions.  Either plug something in to them or mute them. Read more

I'm still here.  I've just been finding it difficult to navigate the new forums and find stuff that I can respond constructively to. Read more

Yes, that would work.  Just keep in mind that there are no line delays available on the aux outs (though you'd unlikely be using them for monitors anyway,) and that the aux out sockets on the X32 series (though not the M32 series) have 5dB less headroom before distortion than their XLR counterparts (16dBu for TRS vs 21dBu for XLR.)  A super hot mix might be fine if it comes out of an XLR socket, but that same mix may distort if you try outputting it on a TRS socket, so you'd need to adjust your gain structure accordingly.  Depending on how hot your mixes are, this may or may not be a problem. Read more

There's something incongruous here: "Mix-Bus 9-12 from the X32R shall be routed to S16 XLR Out 9-12" and "I want to assign Mix-Bus 9-12 from the X32 Rack to XLR-Out 1-4 on the S16" You could route bus9-12 to both lots of sockets and essentially duplicate the outputs, but that leaves no room for the signals from FOH.   The XLR outs on the stageboxes work in blocks-of-8 (unlike the XLR outs on the back of the consoles which can work in blocks-of-4.)  Getting signals from 2 consoles (FOH+Monitors) onto the 1 block-of-8 of XLR outs on a stagebox requires staging them together in the one block-of-8 on one of the consoles.  As the "staging" tabs in the routing tables (out1-16, aux out, ultranet) can only deal with signals generated internally by the console itself (DOs from channels, buses etc, it can't be used for passthrough,) this means you need to "import" the FOH signals from FOH onto actual spare channels on the monitor console, then stage DOs from those spare channels in the out1-16 tab in the same block as bus9-12, so then you have 1 block-of-8 signals containing DOs of channels contianing FOH signals + bus9-12, then you can route that whole block-of-8 to the S16's XLR outs using the AES50B tab.  The other way of doing it is routing bus9-12 to spare channels on the FOH console, staging them in a block-of-8 with FOH signals, then sending that block-of-8 back down to the S16 using the X32Rack as passthrough.  As it's already a block-of-8, you don't need to worry about spare channels on the X32Rack.   The "spare channels" can be the Aux channels, so you can route signals to them using the console's AuxIn Remap option.  However the AuxIn Remap can only see the first 6 signals in the AES50 stream, so the signals you're wanting to get onto those aux channels need to be first in the AES50 stream, so some things need re-organizing.   (Assuming you're not sending bus9-12 from the X32Rack to FOH, but rather you're sending FOH to the X32Rack, and you're happy to have bus9-12 appear on XLR sockets 1-4 of the S16, and FOH on XLR sockets 5-8 of the S16.)   On the FOH console: Routing>Out-16 Outputs 1-4: Mtx1-4 (FOH signals) Outputs 5-8: Bus1-4 (Monitors if coming from FOH) Outputs 9-12: Mtx 1-4 Outputs 13-16: Bus1-4   Notice that this is reversed from the way you had it so that the FOH signals are in the first part of the block (and will therefore be in the first part of the AES50 stream) so they can be accessed by the X32Rack's AuxIn Remap.   You might need to swap around the delay settings in the delay tab from 1-4 to 5-8 and vice versa (and 9-12 and 13-16) if you've been using the FOH console to dial in line delays to the FOH speakers.   You can also swap around the signals in the XLR-out tab, or re-patch cables coming out of the console's XLR outs, as now FOH will be on XLR1-4 and 9-12 and bus1-4 on XLR 5-8 and 9-16.   Anyway, now that the FOH signals are coming out in the first part of the AES50 stream from the FOH console, it's time to get them onto spare channels on the X32Rack.  This is what the AuxIn Remap is for.   On the X32Rack: Routing>Home (or "Inputs" if you're using Edit.) AuxIn Reamp: AES50A 1-4. This gets the first 4 signals coming into the X32Rack on its AES50A socket onto Aux Channels 1-4.  Aux channels 5-6 are still fed by the TRS\RCA sockets on the rear of the console, but not the TRS aux in sockets on the rear of the console no go nowhere.  Now you've got FOH Mtx1 on Aux1, FOH Mtx2 on Aux2, FOH Mtx3 on Aux3, and FOH Mtx4 on Aux4.   Now you need to stage some DOs from those aux channels in the same block as the outputs from bus9-12. Still on the X32Rack: Routing>Out1-16 Output9-12: Bus9-12, Post Fader Output13: DirOut Aux1, In\LC Output14: DirOut Aux2, In\LC Output15: DirOut Aux3, In\LC Output16: DirOut Aux4, In\LC The In\LC tap point is used because the Rack shouldn't need to add processing to the FOH signal, and it means that if you inadvertantly add processing to\mute the aux channels on the Rack, it won't affect the FOH signal.   Now you've got a group of 8 signals (out9-16) containing bus9-12 and the FOH signals.  All you need to do is send that block of 8 to the S16 so it can appear on the S16's XLR outs.   If the S16 is in mode1, Routing>AES50A\B, set AES50B 1-8 (7th row if using Edit, 1st row if using the AES50B tab on the actual console interface) as out9-16. If the S16 is in mode2, Routing>AES50A\B, set AES50B 9-16 (8th row if using Edit, 2nd row if using the AES50B tab on the actual console interface) as out9-16. If the S16 is in mode3, Routing>AES50A\B, set AES50B 17-24 (9th row if using Edit, 3rd row if using the AES50B tab on the actual console interface) as out9-16. Alternatively, you can set all those rows to out1-16 then it won't matter whether the S16 is in mode1, mode2, or mode3.   That should leave you with: Bus1-8 being output on the X32Rack's own local XLR outputs. Bus9-12 being output on the S16's first 4x XLR out sockets. FOH mtx1-4 being output on the S16's last 4x XLR out sockets. FOH mtx1-4 and FOH bus1-4 (if doing monitors from FOH) being output on the FOH console's own local XLR out sockets.   HTH   Read more

In someone famous's words: "And another thing..." When seeing the recently updated threads\topics, it would be useful if the last post time of a particular topic\thread  was displayed somewhere.  It works well enough when there is only one post in the thread, or when there is only one reply, because the time displayed is accurate.   However when there is more than 2 posts in a thread, the time the OP was posted is displayed, and the time that the 2nd post was posted is displayed (which eg could be 1 week ago, and 6 days ago respectively,) but there could be another 20 posts in that thread, and you don't know when the most recent one was.  It might be 2 minutes ago, and you propbably haven't read it, so opening the thread is a good thing.  Alternatively, that thread's most recent post might be 5 days ago, in which case you probably have read it, and if you've just opened it to check if there was something knew, you've just wasted your time (assuming you had read it in the last 5 days.) Read more

Briefly glanced at the scenes.  There are only 2 there.  The third file is a channel preset. The problem with using multiple monitor consoles for the same inputs (assuming you want monitor channel processing different to FOH channel processing) is keeping the channel processing consistent between the two monitor consoles.  You don't want a lead vocalist eq'd one way in one bunch of monitors, and eq'd differently in a different bunch of monitors; someone will end up off pitch. If alternatively you're happy with having the same channel processing in monitors as is in FOH, and you're just using multiple monitor consoles purely for the extra buses, this becomes a lot easier. Assuming you *do* want different channel processing in monitors compared with FOH, I think I have a routing solution (though it has some caveats) which can work, but need to confirm a few details first. In one post you write that you have 2 DL16s, in another you write that you have 3.  How many do you actually have? (Assuming 3 DL16s and 32 mics) are all the mics connected to the first 2x DL16s? (ie the 3rd DL16 is purely for output; its preamps are unused.) Do FOH outputs need to come out of the DL16s, or do they need to come out of the FOH console's own XLR outputs? It looks like you've got some other outputs from the FOH console (some wedges, a HA etc.)  Do these need to come out of the DL16s, or the FOH console's own local XLR outs?  Keep in mind if you've got 3x DL16s and want 20x monitor mixes (10 per Core,) that only leaves 4x outputs available on the DL16s to fit the rest of the FOH mixes. I can understand each musician using their own tablet\phone to control their own monitor mix, but how (who) controls the actual channel processing for individual channels in those monitor mixes? Do any signals connected directly to the FOH console (eg the card in (click) other aux ins, talkback) need to make it to the monitor consoles?  I presume the click + TB would, but are there any others? Is the computer you're using for the Click running Windows?  If so, there's an app that can keep processing between 2 consoles the same, which would help. Are you using the AuxIO for any inserts?  I notice there is CR+HA outputs staged there.  Do they have to be on TRS or can they move to XLR? You mention have 10 people on each Core, but the one Core scene you did upload shows 14 buses (7 stereo) in use.  A single Core can't accommodate 10x stereo mixes.  At most you could have 9x (if you don't use FX and you use the Core's LR bus.)  How do you plan to fit 20x stereo mixes across 2 Cores, and fit 40 outputs onto 3 DL16s.  I'm not meaning to be facetious there, I just need the right info to help find the right solution, and ensure you're not misled and don't feel disappointed afterward when you find out the gear isn't equipped to do what you thought it would do. Read more

+1 to Kevin.  I also miss the different subforums for the X32 vs XAir series (if the distinction still exists I haven't found it.)  At least when threads were separated into these subforums and someone just mentioned their new "mixer" and didn't specify which one, you had some clue whether they were talking about an X32 or an XAir. Read more

What Spence said.   Think carefully before you get the Producer.  48 channels + 8 DCAs + 16 buses + 6x MTXs + M\C + sends-on-faders + geq on faders + DAW control sounds wonderful, but keep in mind that all this functionality is spread across only 16 faders.  There is no custom fader layout, no DCA spill\pop groups, no digital scribblestrips, and there's not a huge amount of space for tape... It's not really ideal...   Unless you need something to fit in a 19" Rack space, get the Compact.  If you do need something to be racked, look at the M32R.  Same functionality, but is 19" rackable, has digital scribblestrips, and you get the better Midas preamps, better ADC\DACs, better analogue output stages, the TRS outputs are in line with the XLR outs (instead of having -5dB less headroom,) better faders, better encoders, and the screen is at a far more ergonomic angle. Read more