Zynewave's Forum Page

@thcilnnahoj wrote:

Edit: Hmm, as I like to use bright track colors, I find the GP looking a bit strange now. Applying the track color to the controls (like on track headers) would make them more immedeately readable and would also make the shadows look less unnatural, too. Track colors might of course clash with selection/record/bypass colors, but shouldn’t that be the user’s responsibility? 😉

Hmm :-k , my current standpoint is that it can become too difficult to discern button select states, if the unselected buttons should assume the background color. If the source/input comboboxes are shown on a selected track header (in a future update), the color of the selector buttons would be the same selected as unselected.

@LiquidProj3ct wrote:

On the slot:
Left click in a empty slot for a instrument/effects menu
Left click in a busy slot for select it
Double left click show/hide the instrument/effect and select it
Right click menu with options/parameters

Thanks for the suggestion/reminder.

Beta3:

The selector buttons now turn into editor buttons once a plugin is assigned. That gets rid of the separate editor buttons. Good riddance, I say. When you alt+click the selector button, the effect is removed, and the effect selector menu reappears.

Also in beta3:

The default position of plugin editor windows are offset so that they don’t cover the track inspector.

Perhaps this screenshot also illustrates why sends cannot simply be presented on a row outside the signal chain:

Sends in Podium are not placed at fixed positions in the signal chain, like they are in the mixers of some other hosts. The screenshot shows a sidechain input placed in the chain, and this also works as a send. If you took out the send controls from the chain and presented them on a row, then it would be difficult to know what the sends controlled.

The same thing applies to the gain/pan controls. They are also displayed at the position in the signal chain where the gain/pan is applied. If you enable gain/pan on more than one effect track, you’ll see multiple gain/pan controls in the chain.

All this follows the simple rule that all controls/buttons/sliders are placed in the chain in the order that the signal flows. From the bottom input to the topmost master output. Even though some users would prefer the instrument plugin to appear at the top, this would mean that the signal routing can no longer be seen as going in a straight line from bottom to top.

@Zynewave wrote:

A final remark: you’re stepping away from the integrated gui of the z plugins with the inspector then? Your current design doesn’t really leave room for these.

In a later release I’ll remove the embedded plugin editor from the track panel, and instead insert it into the group panel, just below the combobox where the effect is selected. That will allow a zPEQ editor to be open when the source track is selected, and it also allows multiple embedded editors to be open at the same time. For this purpose, there will be a new button next to the current ‘E’ button, which will open/close the embedded editor.

Which reminds me:

With plugin editors embedded in the group panel, would it not make sense to rename the “group panel” to “rack”?

I also plan to extend the current group panel options into perhaps 3 separate configs. That way you can quickly switch between different layouts, without having to toggle each individual option in the inspector menu. Instead of the “Group Panel” button at the top of the inspector, there would be buttons for “Rack 1”, “Rack 2” and “Rack 3”. Good idea, or overkill?

Preview 2.23: Redesigned group panel

@ronin wrote:

I’ve integrated the switch-buttons into the transport-toolbar to preserve more space for the arrangement-editor. Since you can switch with the number key now, I think there is no real need for a large profile-bar(because you don’t have to click the buttons)…maybe this integration should be standard but on the other hand this integration may not very useful for small resolutions. I’m working with 1680×1050 and have enough space left in the transport-bar.

The new screenshots in the getting started chapter is made at 1280×800 resolution (common resolution in laptops of today). As you can see, when the inspector is open, the edit and transport toolbars are almost maxed out. No room for the profile bar.

• Export to sound file.
• Various improvements and bug fixes.

Topic: 2.22