It’s a live Desk but because of its recording and daw controller functions it must have a complete Studio monitor management functions for the studio enviroment With Mono Dim & Volume button via touchscreen and all you need to work well in the studio
Yes yes yes.
Absolutamente…
This could be implemented entirely as soft functions, in my opinion.
Those that wanted monitor control would dedicate some soft keys and knobs to the functions of switch monitors (probably a key to iterate through previously defined set ups) and of course control room level. Physical outputs would be designated as monitor outs, and it’s essentially just some very lightweight channel functionality on a summing bus just past whatever hit Mix-L/R.
Take a look at how Nuendo/Cubase does this and I think you would see some very good ideas for this functionality.
This.
+1
+1
There’s a few flavors of this thread in here now. Might be useful to consolidate into a “using the SQ-6 in the studio and for recording” thread.
A solo in place function please!!!
+1
Everything the OP has requested is available in either the Dante or Waves card option. Please remember the SQ line’s designed limitations and price point are pointed to specifically delivering a small footprint, world class, FOH and performer monitoring. The fact remains that all possible needed optional recording opportunities beyond the SQ’s limited internal USB protocol are available via a Dante or Waves card. Loading up the SQ with any of these attractive studio features adds little or nothing to the primary operational FOH protocol the SQ was designed for.
Hugh
Put your +1 on the stereo width control thread. If that control which a lot of people want implemented had a midi address attached to it then a softkey or external midi button could be used to toggle mixes between mono and stereo.
Dim button is already possible using midi on the SQ.
again… I will warn about the way of implementing this…
I would like to see some features for studio use as well
but don’t like the idea that these functions are available all the time…
just to avoid operating errors
instead I would prefer to have it implemented as a different role like the monitor role
where the role defines the master fader function (could be the control room level in the studio setup)
it can additionally define the availability of the control room functionality mentioned before
if that is possible…
and a broadcast role…!?
maybe @keithjah can say something about it…
What’s the problem about stereo width control on Mix Busses like it’s available on Stereo Inputs?
Do you think there are operating errors, because of the stereo width control on the inputs?
On the GUI is at Mixes and Groups Tab exact the space empty, where this controls sit on the inputs.
So in my opinion it would be absolut LOGICAL to have there the same feature…
When I decide to use this bus in stereo, then i decide to have the same control as it is at the inputs…
The SQ is really a powerful consol - operating errors can occur everywhere…
So why this “Warning” of this feature?
greetings,
dd
What’s the problem about stereo width control on Mix Busses like it’s available on Stereo Inputs?Do you think there are operating errors, because of the stereo width control on the inputs?
I didn’t mentioned the stereo width control at all… talking about the whole studio setup thing…
changing the master fader, Solo in place, control room features and so on…
+1 for the Studio set up(control room, solo in place,etc.)I’m missing that features
While most of the studio requirements can be fixed with an external studio controller, the SIP mode of the PAFL system have to be implemented in the console itself, with the possibility to define busses and channels from being muted while some other channel is soloed.
For me I do not see any problems when the console will be more versatile and covers more use cases in future. I do nit think that live engineers will be completely confused and will make a lot of mistakes when there is a SIP mode possible with the PAFL system. Also switchable MONO and DIM on the listen bus, via soft buttons, is not a big deal when the operator do not expose that functions via soft buttons to the surface.
Simply in the Role section Activate or not the studio features would be a great implementation