ZynewaveZynewaveBeta 6 is uploaded. New is the pan dial and gain fader at the bottom of audio enabled track headers. On my todo list is implementing mouse-over highlighting of all the controls in the lane headers (like it is done inside the chain panel).
ZynewaveZynewaveZynewaveZynewave@estwing wrote:
Hi Frits
say i have seven active group tracks with thirteen lanes containing audio events etc, i may also have an extra four unused group tracks present since the project is worked from a template so i could have 20 tracks to hide and i have to do this on a per track basismart.
ok i’ve just tried my most recent project in 194 and when i have the “empty” tracks hidden, provided i keep the inspector open i can follow the routings for each group easily.I suppose in the past i have tended to keep the inspector closed to keep a bigger full screen.
Ok, so since you have not been using the inspector, you’ve shown the lanes for your effect tracks to get access to the plugins on these tracks. The good news is that with the new compact mode you can hide these tracks and access the effect plugins in the new chain panel, still without having to use the inspector. I may even decide to force hide effect tracks in compact mode, and thereby remove the “hide track lane” option, to further reduce UI complexity.
ZynewaveZynewave@estwing wrote:
when I only need to see audio midi and controller events, I could switch between this macro view and a micro view of track groups as i wished.
I’m trying to understand what kinds of tracks you want to hide, if they are not used for audio, midi or automation. Assuming you have hidden the tracks with effect plugins, the only remaining tracks are group tracks? How many group tracks do you have in one of your arrangements?
ZynewaveBut at least for now please do not so quickly and easily dismiss the idea of db values behind those new track sliders. I have always admired the way the db values on the glass mixer buttons update and correctly reflect what is underneath them in the mixer.
To clear up any possible misunderstandings: The fader knob shows the current gain dB value, just like the mixer knobs. It’s the 0, -3, -6 etc. labels underneath that I have decided not to show to avoid cluttering the lane headers with too much text. This may change in the future, if I decide to provide an option for precision metering on the lane headers. The faders on the lane headers are meant for a quick way to adjust the gain. If you want to do precision mixing, then use the mixer.
ZynewaveZynewave@estwing wrote:
give the option to “hide tracks in group with empty lanes” and I will be even happier
When you say “empty lanes”, do you mean tracks with no events on the timeline? If these are tracks you use only to route effect plugins, why not hide them with the “hide track lane” menu option?
Zynewave🙂 No vacation time here. I’ve been hanging out in this topic:
http://www.zynewave.com/forum/viewtopic.php?t=1452
This is a major feature, and an important one too, which is taking a long time to get right.
Zynewave@darcyb62 wrote:
Actually I think the Compact Track Layout does a decent job of simplifying things but I find the list of sends/plugins redundant with the improvements that have been made to the track inspector. All I would like to see there is the pan/gain and assortment of mute/solo/bounce/e buttons.
The problem with the list in the compact track layout is that you lose visibility once you add a couple of sends/plugins. Maybe not so important but why duplicate functionality that is handled so well in the inspector. Maybe all that is needed is the meter and buttons…
I can understand why you’d like a clean track header, if you prefer to work with the inspector and mixer. But there are others who have said they don’t like the inspector, and would prefer a way to work without it. The benefit with showing the sends and plugins on the headers is that you can see the assignments on all visible tracks. With the inspector you need to select a track before you can see the effects chain. Maybe I’ll add an option to hide the chain panels.
One thing I noticed is that if I create a new group track I cannot copy other tracks onto the group.
The track menus are not fully implemented yet. I’ll keep this one in mind.
ZynewaveI see this is partially achieved with the new pan and level controls staying at the bottom of the track header!
Yes. The pan and gain fader are the most important controls, so removing them from the bottom of the chain panel and embedding them on the header ensures they are still shown on tracks with a partly obscured chain panel.
3- Is it me or is impossible to view the input mapping on track headers in compact mode?
This is coming later.
I think what Podianer meant to ask is why the fader doesn’t move on the middle of the line, as on a real mixing board.
Yes, I misunderstood him when first reading his comment. I have since moved the line down to the middle of the knob. The reason the slide was at the top of the knob was to allow text to be written on the area where the knob moves, like it’s done in the mixer. I have since decided not to write dB labels on the fader background.
Thanks for the feedback.
Zynewave@estwing wrote:
I’m not sure if the compact view in the inspector is useful to me,the commands to move tracks are precise but I generally drag them around the main screen (and use “undo” when i drop them in the wrong place)
That’s cool. You can just hide the group panel in the inspector view menu. But what about the new compact track headers, with the list of sends/plugins and the pan dial and gain slider. Is this useful to you?
Thanks for the feedback.