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

Select the bus, config tab, 3rd encoder, turn to select subgroup, push to confirm if you want to change the tap points for all channels feeding the bus. Read more

You can set it up pretty much any way you like, as long as: Only one console is clock master. The other consoles are set to slave correctly. You set up the routing correctly. How are you getting signals out of the core(s) to feed monitors? If you have other stageboxes there you haven't mentioned, that could change things. Read more

Any chance the first-5-posts-hidden-and-directly-moderated-for-spam requirement could be reduced to 3? Read more

You could just un-assign all channels (except your house music) from LR while you build your monitor mixes, then assign them back later. Alternatively, a DCA mute would also work. Read more

The only workaround I can think of is to set up your monitor as stereo (ie it uses 2 buses.) That way the LGtr channel will automatically go to the odd numbered bus, and the RGtr channel will automatically go to the even numbered bus; no summation, so no phasing issues. Then you just feed your actual monitor from only one of the buses (eg the odd numbered bus, which only has the LGtr signal, not a sum. The even numbered bus doesn't get routed anywhere.) All other channels for your monitor mix can be panned centrally or to the left in your stereo monitor bus and you'll still hear them along with the guitar. For any other stereo channel in your monitor mix that you *do* want summed, you just manually pan both sides of that stereo channel to the odd numbered bus (or centre.) Read more