.Beta2 is up. Another revision of the UI, and a few bug fixes.
@Zynewave wrote:
I considered a solution where an empty “
” box would always be placed at the bottom of the chain. Select an effect here, and a new empty effect track is automatically inserted at the bottom. But that means that there will always be two unused tracks in the chain (one in the master chain), and I think that takes up too much space.
I changed my mind on this, and I have now added an “add effect” combobox at the bottom of the effect chain. Let me know if this is convenient or a nuisance.
I’ve incorporated some of the suggestions made in this topic, so hopefully the revised UI is now less caotical 😯
Tomorrow I’ll go through the posts in this topic and reply to questions.
I think the group panel selectors (highlighted) would look better recessed as there are too many floating elements, which doesn’t look great imo, particularly when the track is colourised.
Any chance of a user option on that?
Mart.
Okay. This it how it should looks like.
Seriously. Source FIRST. Then fx list. Last we need sends. Those sends should be “balloon”. Just like those X, R, E buttons. It take less space, and its looks 10 times better. It’s not only me who want’s those “Balloons”.
EDIT
I made it more clearly now.
That “M baloon” is simple MIDI IN. Now whole view is CLEAR and EASY / FAST to discern. Does anyone else agree?!?!?
@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.
@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.
