Zynewave's Forum Page

@estwing wrote:

so i’m not sure about your idea to change the inspector as mentioned in page 3 of this thread; and the compact mode in 195 gives fast access to busses,effect routings etc but you still need the inspector for the input mappings; midi and audio.

If this is the post you refer to:
@Zynewave wrote:

Since I first designed the track inspector years ago as a panel inside the tracks region, the inspector has grown in size with the addition of embedded plugin editors and the group panel. I’m considering moving the inspector out of the tracks region and instead embed it as a panel at the left edge of the browser window, similar to the “List” panel at the right edge. Imagine there is an “Inspector” tab at the top left corner, just before the project tab. This has the advantage that the inspector can be the full height of the window, and showing the mixer will not reduce the height.

What I suggest here does not change the functionality of the track inspector. It’s just an idea for moving the placement of the inspector from inside the tracks region to the left edge of the editor window. It will allow the inspector to use the full height of the screen.

@Phoenix wrote:

You can create effect tracks in compact…

But if you switch to expanded, you can not create them. But if you click on the child of the fx track, you can delete it.

Is this intentional?

The “New Effect Track” is a menu I created for the compact mode. The expanded mode is still unmodified compared to previous Podium releases. When I’ve completed the compact mode, I’ll probably modify the expanded track menu commands so they match the compact mode menus.

Beta 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).

@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 basis

mart.

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.

@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?