Topic: Preview 2.23: Redesigned group panel

@H-man wrote:

@Zynewave wrote:

@H-man wrote:

As mentioned I’d like the state of the inspector and browser to be stored/recalled across tabs as well.

Please clarify.

A feature request really. At present the Inspector/Browser is independent of the Editor Profiles. I just though that if one was working on the Editor page with the Browser open, switching to the Mixer might have it hidden and on the Tracks page (profile) it could be shown but the inspector (for presets) rather than the browser.

Ok, understood. That’s a FR for a later release.

@Zynewave wrote:

@H-man wrote:

Clicking on a track in the rack doesn’t highlight the corresponding track in the mixer or track headers (ie. Group track).

If the track is shown in the rack, then it is already the focus track, and so should already be highlighted in the tracks and mixer regions?

I guess all I was saying was that clicking on a track in the rack, group, parameter or otherwise doesn’t update the focus on the Mixer or Track Header. If that’s the desired behavior then …okay.

I’m still not sure what you mean. Are you referring to effect tracks? They were previously highlighted individually on the track headers/strips, but this was something I never liked. With the new chain panels, all key shortcuts will influence the source track, and so the selection of an effect track is now only relevant for the inspector list panels.

One final thing, is intended that “Insert new effect track” is now gone from the Track Menu?

Yes. I’m trying to trim down the track header/strip menu to a minimum. I’m thinking that if you want to insert effects, you would want to do that using the new chain panel, where you visually can verify the result of the insert command. If it was available in the track menu, you could keep inserting effects without any visual indication of the action.

@Mike G wrote:

When selecting a track in arrangement it slides the track into view in the mixer, which is great.
However when selecting a track in the mixer it doesn’t slide the track into view in the arrangement… please can it, (Is there some config I need to set, I thought it used to do this… but I could be mistaken)

Good suggestion. Not going to make it into this release though.

@thcilnnahoj wrote:

@Zynewave wrote:

Btw. I’ve modified the default track coloring slightly in the new beta14, and specified a new default track color. Let me know if the new default colors present problems.

I only did a quick test – is it correct that default track color is not applied to colorless tracks anymore when you save a project? That’s the reason I never used it in the first place, as it quickly became a mess, but it looks like it has been fixed already somewhere along the way…?

Correct. I changed this very early in the 2.23 development.

From what I can tell, these are the problems I’ve found that made it as far as beta 14:
– Slider value pop-ups become stuck when changing profiles or closing the inspector with shortcut keys.
– The bypass buttons on the selectors do not update to a newly selected mute color until the UI is refreshed.
– If you open the mixer and then select a track in the arrangement view, the mixer strip uses the active selection font color instead of the inactive one.
– Sometimes, the group expand/collapse button will ignore the track color and be colored with the panel background color instead.
– When you’re dragging a device to a track, the selector button’s pop-up help gets a little in the way as it blocks the view of the chain.
– When you drag-and-drop an instrument to a track in a particular way, the “drop here” box overlay on the track becomes stuck. You can even ride it up and down using the scroll-wheel. Yee-ha! 😆
Here’s a GIF animation:

Thanks for the summary. Beta15 fixed these issues, except:

– If you open the mixer and then select a track in the arrangement view, the mixer strip uses the active selection font color instead of the inactive one.
– When you’re dragging a device to a track, the selector button’s pop-up help gets a little in the way as it blocks the view of the chain.

These are now fixed.

@thcilnnahoj wrote:

Also forgot to include this one in the summarized buglist:
– Something goes wrong when you create a second master group – input/source selectors appear on the master tracks.
You could assign these things before, even, but I don’t think that’s the point of multiple master groups, is it?

When you add multiple master tracks, Podium skips the search for a master section, and the master tracks becomes like group tracks. That’s the technical explanation. I may in the future change this, so that each topmost output track is treated like a master track.

Beta16 is up. This is hopefully the last beta. I’ll spend the rest of the evening testing it, and if nothing comes up, I’ll make a release later tonight.

Record-enabled audio tracks are now playing, if there is no audio input assigned on the track. That allows for automation recording of effects on the audio track.