Questions & Answers

Split console or multiple consoles

+22 votes
469 views
asked Dec 24, 2017 in Look and Feel by Scoox (16,880 points)

At the moment S1 has a single console window--like most DAWs. When working with high track count, it would save a lot of time to be able to see two parts of the console simultaneously.

For example, if all the bus channels are placed at the far right of the console and the user is tweaking a father on the far left, a crowded console will require regular scrolling left and right to access both.

A simple solution is to add a vertical draggable split, effectively splitting the console into two halves each with its own scroll bar. Users could then scroll to the bus channels in one half, whilst having access to other channels in the other half.

This is probably asking too much but it would be even better if each half of the mixer could display a different mix scene and channel width.

Cubase has taken a different approach where there is a main mixer and then two secondary mixers, which can be shown concurrently. I think is pretty cool, because users can have a mixer just showing bus channels and another showing everything else.

Cubase provides an additional two mixer windows, which you can tweak according to our needs. When working on large projects, you can create groups and assign a mixer for a group or assign a window for vocal related effects and plugins.

If Studio One could do this, the F3 keyboard shortcut would toggle the main console, while the secondary console(s) would have to be assigned to different keyboard shortcuts.

Mix scenes are very useful but IMO they solve a different problem.

1 Answer

+1 vote
answered Jan 17, 2018 by AlexTinsley (925,070 points)
 
Best answer

Thank you for the feature request. 

If anyone else agrees or disagrees, please VOTE!

The developers pay close attention to those that are voted on the most. 

You are allowed one vote. You can change your vote later if you choose.

(Here's some helpful info on how to use the voting system)

Please vote the original question / feature request. 

Please DO NOT Vote on THIS response!

...