Topic: Preview 2.23: Redesigned group panel

Viewing 15 posts - 196 through 210 (of 256 total)
  • #16804
    Zynewave
    Keymaster

    Beta 11:

    Lots of bug-fixes, but this beta is not yet stable. I’m aiming to have a stable beta ready within a couple of days.

    Added a “small size” rack option to the inspector options menu.

    The mixer strips are now split so that sends are aligned to the top, and effects to the bottom. There’s also a small space between the effects and the input/source selectors.

    I’ve started a reorganization of the track menu. When you right-click a selector, you will get a track menu with only the choices relevant for the device. If you right-click the background of a track lane header or a mixer strip, you will get a track menu without any device specific commands. Previously when you right-clicked the source selector, you would get one big track menu with both source device options and general track options. Splitting the menu up into two, helps keeping the track menu cleaner. Let me know what you think of this.

    #16805
    LiquidProj3ct
    Participant

    Why do you think it is important; Is it only because you want to minimize the vertical space used by the current slider?

    Well, I liked the idea of have a send in any place of the chain keeping the chain tidy. I saw this in the initial screenshot of reaper homepage. I thought that was important in that moment, although now I see that there is more important things to do 🙂

    Splitting the menu up into two, helps keeping the track menu cleaner. Let me know what you think of this.

    I think this is a good idea, I hate infinite menus

    edit: just found a piano roll bug, when you want I notify you let me know

    #16806
    thcilnnahoj
    Participant

    When you say you’re done, I hope that means the track header changes are postponed, not scrapped. 🙂
    If you keep the selection frames, I think you “must” use the new proposed layout. The frame doesn’t color the “group level strips”, and it would look strange if the frame extended downwards to encompass tracks inside the group or associated parameter tracks.

    About the menu redesign:

    It’s generally a good idea, but there’s one thing that strikes me as strange, as it has many drawbacks.
    For one, it’s impossible to create mixer parameter automation lanes if you disable source selectors on track headers. It’s also awkward that you’d have to set up level automation from the source menu on a track only processing audio files.
    There are other situations too, where this would force the user to take a few extra steps. For example, you’re on the editor page, want to create an automation lane for a track and edit it right away – simple. But you won’t be able to do this in the arrangement view, since the tracks are naturally sized so small that they don’t show the selector buttons. You have to switch profiles, zoom in, or open the right inspector panel to get access to the parameter menu.

    For these reasons, I’d say it’s better to keep the most important options (source, input and automation) in the track header menu, always quickly available in every situation.

    Other things:

    – Why does the source selector right-click menu contain settings for inputs? If it’s for when you have the input selector hidden, then I think it’d be placed in the general track menu (see above point).

    – What’s the topmost greyed-out menu entry that says “Track: “? Isn’t it pretty obvious on which track you opened the menu?

    – If you set the mixer options for ‘gain/pan fader: show value in separate field’ and ‘control type: slider with value on knob’ then the pan value won’t be displayed at all.

    – If there’s no instrument assigned, selecting ‘automate parameter’ from the source right-click menu brings up the parameter list of the first effect in the chain.

    – I think the ‘default track color’ setting is ready to be retired. With the default opacity settings, it messes everything up if you select anything but shades of grey.

    – Gain/pan faders could probably be removed from the track panel in the inspector. You can enable faders in the rack panel instead, providing far better use. Most of the time the track panel faders would be unavailable anyway, as the track panel (by nature) only displays things relevant to the selected track, thus rightfully not following the fader position in the chain.

    – Are you happy with how the selection frame looks in the mixer – I mean the SMR buttons & mixing grid being over/underlapped? I know it’s nice to have them glued to the edge, but this just doesn’t look very good, in my opinion…

    Edit:
    – The bypass buttons on the new selectors do not update to a newly selected mute color until the UI is refreshed (like closing and reopening the inspector.

    – 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.
    Also, this is unrelated to 2.23 however, if you select a phantom copy item in the arrangement and set keyboard focus to the mixer, for example, the + icon next to the event name still uses the active selection font color.

    #16807
    Zynewave
    Keymaster

    Beta12:

    Bug fixes and further changes to the track menu layout.

    There is a new “Track” menu button inserted between the “File” and “Edit” buttons in the edit toolbar. This will show the track menu for the focus track. The redundant track clipboard commands have been removed from the edit menu.

    #16808
    Zynewave
    Keymaster

    @thcilnnahoj wrote:

    When you say you’re done, I hope that means the track header changes are postponed, not scrapped. 🙂

    Sure. Probably coming in 2.24.

    About the menu redesign:

    It’s generally a good idea, but there’s one thing that strikes me as strange, as it has many drawbacks.
    For one, it’s impossible to create mixer parameter automation lanes if you disable source selectors on track headers. It’s also awkward that you’d have to set up level automation from the source menu on a track only processing audio files.

    Good point. The “source”, “input” and “automate parameter” menus are now again available on the track header/mixer strip menu.

    – Why does the source selector right-click menu contain settings for inputs? If it’s for when you have the input selector hidden, then I think it’d be placed in the general track menu (see above point).

    That was a mistake. Now removed.

    – What’s the topmost greyed-out menu entry that says “Track: “? Isn’t it pretty obvious on which track you opened the menu?

    My intention is perhaps clearer in beta12, where there is a new “Track” menu button in the edit toolbar. I think showing the track name as a greyed out title helps as verification that you are editing the correct track. Try out beta12 and let me know if it still is strange. If it makes sense, I would similarly add a title line to the edit menu, listing details about the current event selection.

    – I think the ‘default track color’ setting is ready to be retired. With the default opacity settings, it messes everything up if you select anything but shades of grey.

    Can you clarify?

    – Are you happy with how the selection frame looks in the mixer – I mean the SMR buttons & mixing grid being over/underlapped? I know it’s nice to have them glued to the edge, but this just doesn’t look very good, in my opinion…

    The grid is now not shown in the default setup. I think it tries to do too much. I may trim it down to only indicate meter position. Anyone have opinions on the usefulness of the fader/meter grid?

    I tried moving the BSMR buttons away from the edge, so that the focus frame is not overlapped, but it just didn’t look good. The BSMR buttons are aligned to the right edge, because they will then join the BSMR indicators on collapsed child tracks. Also the BSMR buttons overlap the focus frame on track headers, so at least the appearance is similar for both the track headers and mixer strips.

    #16809
    thcilnnahoj
    Participant

    About beta 12:

    – What’s up with the ‘apply track height’ command – is it supposed to replace ‘set default track height’? The help text says it only works on parameter tracks however (and it does), so shouldn’t the menu entry itself say so if that’s the intention? Also, I think it’s strange that you get this option in any track menu, regardless if it’s a parameter track or not. I hope it’s just a mixup. 🙂

    – If you moved the contents of the track region menu over to the top of the track menu (they don’t have to be in the track header context menu), and modified them to enable creation of multiple tracks at once, I think it would be a much better solution than the menu button below the tracklist. Unless you have something else in mind with regards to the mystic “track toolbar.”

    – “Show send controls” help only reads “shows send dials”, whereas the options for gain and pan read “faders/dials.”
    – “Show source selectors” help reads “shows parameter selectors.” (?)
    – Track headers don’t always show the same elements even if they’re supposedly the same height after using the ‘set default track height’ option. This was in beta 11 – can’t test it in 12.

    The mixing grid is a very nice tool to have, in my opinion. Setting the fader position most definitely has its uses, and since it doesn’t get in the way if you don’t want to use it, I wouldn’t say it’s necessary to disarm it further. I don’t really have a problem with the track name menu entry at the top either.

    If 2.23 is finished, it’d be great if you could take a look at the real-time bounce issue mentioned here: http://www.zynewave.com/forum/viewtopic.php?p=15899#15899. With beta 12 and the new signal chain layout it seems Ctrl-H is gone, and so it’s become impossible to unhide effect tracks so you can insert an empty event to record in manually. 🙁

    #16810
    thcilnnahoj
    Participant

    @Zynewave wrote:

    Sure. Probably coming in 2.24.

    Otherwise known as Podium 4.0! =P~

    @Zynewave wrote:

    – I think the ‘default track color’ setting is ready to be retired. With the default opacity settings, it messes everything up if you select anything but shades of grey.

    Can you clarify?

    Um, I’ll try, but I can’t guarantee that my explanation will make sense to you! 😆
    For reference, example 1 has 2.23’s default color settings: overall color opacity 100%, track background opacity 20%, some random track colors and no default track color assigned.

    Before 2.23, you could select a default color and still override it when you set per-track colors, provided you set opacity to 100%.
    Now, the strips are always colored, even if you set rack/header/strip opacity to 0. Even on higher opacity levels you don’t override the default track color but can only add various track colors to it instead. So you have a choice between all track backgrounds being pretty much shades of the same color (ex. 2, low opacity) or getting a real color mix (ex. 3, high opacity), like in previous versions, but coloring the whole strip this time. All in all very bright compared to the default settings. (Edit: It can of course be dark as well – I meant to say it’s quite intense.)
    Setting the default color to a shade of grey is a little more useful, as you can make tracks appear generally brighter or darker, if moderately applied. (Edit: Sorry, this is of course not correct. It can be achieved by setting a lighter or darker shade of the panel background color! It’s just that I always use grey…) 😉

    #16811
    thcilnnahoj
    Participant

    A rare bug… sometimes, the group expand/collapse button will ignore the track color and be colored with the panel background color instead.
    This is the best way I could find to reproduce it: Open an arrangement that has a group track (I think child tracks have to be collapsed) -> move it so it is the last track in the mixer (apart from docked tracks) -> delete the group track and its child tracks (it’s quicker with DEL) -> undo. It doesn’t happen every time… try restarting Podium if it doesn’t happen at all.

    #16812
    H-man
    Participant

    Hey there, it’s late here but I thought I might just contribute a just a couple of notes:

    The state of the track headers no longer changes with the tabs (I liked this behavior a lot).

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

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

    Adding output gain and output panning to and effect in the rack sets the fader at two locations on the mixer strip (two active squares) and shows additional Pan & Fade controls in the mixer

    Also,

    Would it be possible for the new track menu to stay rolled out and change focus as you click on different tracks in the mixer? As it is now I still prefer to right-click the track. Clicking anywhere else would close it of course.

    I like the grid as is thanks

    #16813
    MelodyMan
    Participant

    Just wanted to say that, as a “normal” user i am in awe of the great suggestions made in this topic. Way out of my league but great and above all constructive! =D>

    #16816
    LiquidProj3ct
    Participant

    @Zynewave wrote:

    My intention is perhaps clearer in beta12, where there is a new “Track” menu button in the edit toolbar. I think showing the track name as a greyed out title helps as verification that you are editing the correct track. Try out beta12 and let me know if it still is strange. If it makes sense, I would similarly add a title line to the edit menu, listing details about the current event selection.

    I don’t like too much that thing, because I would never use “Track” menu and I don’t think that it would be a problem have a mistake: we have undo function and it’s difficult fail selecting the track. I would say that it clutters the menu.

    I imagine you want release asap 2.23 so I’ll avoid make request 🙂

    Cheers!

    #16823
    Zynewave
    Keymaster

    Beta13:

    I couldn’t resist the temptation, so in beta13 the track headers now use the same hierarchy visualization as the mixer strips. 8)

    There are still bugs in this, but if you try beta13, I would like to hear your opinion on the new hierarchy layout.

    I’ll get back to the other bug reports later today.

    #16824
    LiquidProj3ct
    Participant

    Hello Frits. I’m a little confused with new hierarchy, specially when you select a group track. It seems that it’s a “children track” instead a group track. Maybe you could do something to fix this as allow that selection frames take more space to the left.

    #16826
    thcilnnahoj
    Participant

    @thcilnnahoj wrote:

    – Track headers don’t always show the same elements even if they’re supposedly the same height after using the ‘set default track height’ option.

    It seems this happens because there’s a larger space between selector buttons and the faders when there’s an effect added to the chain.

    Here are two tracks – only the second one has effects on it.
    On the top row, they’re both at the smallest possible size where you can still see everything except the effect chain. On the bottom row, the additional space is easily visible after setting track size so that you get to see the controls on the second track too.

    There’s also a little extra space on the right side of the track headers, even when you disable vertical meters and the color bar. It’s more apparent now with the selection frame – it looks a bit strange that it doesn’t cover the whole header.

    Can’t say much about beta 13 other than it looks great! 🙂

    #16832
    LiquidProj3ct
    Participant

    This is the little piano roll bug I said before:

    Best regards 🙂

    edit: I’m also getting tons of freezes exiting podium, when the system ask if I want to save the project and I say ‘no’, around 1 each 3 times. I don’t know how to replicate.

Viewing 15 posts - 196 through 210 (of 256 total)
  • You must be logged in to reply to this topic.
© 2021 Zynewave