It’s interesting someone mentioned starting with drums. That’s how I was taught, and I know most pro-level guys do it that way too, but I agree drums are usually set and forget. Lately, I’ve been thinking it makes more sense to start with the things I have to adjust more often, like vocals, guitar, and keys. Really I can work with whatever so it doesn't really matter.
With the usual way layers are these days, what does it matter that the kit is at 1… flip to layer 2 on the console, and usually your first vocal is on the first fader ch(17)… but what really matters is when someone rolls up and wants kick in ch 1… as a national act and such… it;s always been that way, it should stay that way.
I believe your mute all wasn’t working because you have hard muted turned on. I believe with that the mute all won’t override a channel mute that has been turned on manually. That is why when you turned off the channel mute it started flashing because the mute all was on.
It works when connected to the mixer. So it’s never been a problem before when set like that. But it may work that way when it’s not connected. It also never flashes like that when connected to the mixer. It def responses differently when in stand alone mode.
The metering on the apps for the X32/M32 are super distorted as it's a linear scale, so licking -18dbFS (0dbu) is really more like licking -15~-12. If I need to see two things together (on the full size X32/M32) I'd just add them to a DCA which on the X32 act like pop groups/custom layers (assuming you leave them at unity). I'm mixing on busses anyway so the DCA's are typically un-used unless there's things I need to get at quickly. You many not see paired faders move in the app due to how the OSC works under the hood. The console will from memory do the up/down of the other fader automatically which sends back change values to any connected clients.
![Cody Johnson - I'm Gonna Love You (with Carrie Underwood) [Official Music Video]](http://i.ytimg.com/vi/yy9PuYMU29g/mqdefault.jpg)
Super nice info....... Thank you....
can you do a video on Transportation of sound equipment. it’s hard to find answers on what needs to be DOT, box trucks vs trailers etc
Sure I’ll get on that later this week.
@@thegrumpysoundguy thanks loving the videos!
Awesome video bud. Appreciate it
Watching from on the road brother.
It’s interesting someone mentioned starting with drums. That’s how I was taught, and I know most pro-level guys do it that way too, but I agree drums are usually set and forget.
Lately, I’ve been thinking it makes more sense to start with the things I have to adjust more often, like vocals, guitar, and keys. Really I can work with whatever so it doesn't really matter.
With the usual way layers are these days, what does it matter that the kit is at 1… flip to layer 2 on the console, and usually your first vocal is on the first fader ch(17)… but what really matters is when someone rolls up and wants kick in ch 1… as a national act and such… it;s always been that way, it should stay that way.
I believe your mute all wasn’t working because you have hard muted turned on. I believe with that the mute all won’t override a channel mute that has been turned on manually. That is why when you turned off the channel mute it started flashing because the mute all was on.
It works when connected to the mixer. So it’s never been a problem before when set like that. But it may work that way when it’s not connected. It also never flashes like that when connected to the mixer. It def responses differently when in stand alone mode.
Do you ever use the re-gaining feature on MixingStation its very helpful
Yes
The metering on the apps for the X32/M32 are super distorted as it's a linear scale, so licking -18dbFS (0dbu) is really more like licking -15~-12.
If I need to see two things together (on the full size X32/M32) I'd just add them to a DCA which on the X32 act like pop groups/custom layers (assuming you leave them at unity). I'm mixing on busses anyway so the DCA's are typically un-used unless there's things I need to get at quickly.
You many not see paired faders move in the app due to how the OSC works under the hood. The console will from memory do the up/down of the other fader automatically which sends back change values to any connected clients.