Topic: Preview 2.22: UI improvements

Viewing 15 posts - 1 through 15 (of 56 total)
1 2 3 4
  • September 5, 2009 at 03:35 #2041
    Zynewave
    Keymaster

    2.22 continues the UI improvements, but took a detour around the track inspector. That means development of the “track toolbar” is pushed back a bit.

    Beta1:

    • Added “adjust tempo and stretch to align bar at cursor” command to the tempo lane right-click menu. This is useful if you have recorded a midi performance that has dynamic tempo changes. You can then use this command to edit tempo events and align the grid to your performance while keeping the original timing of the performance. The command complements the old “adjust tempo to align bar at cursor” command which is used for aligning the grid to an audio recording with dynamic tempo changes.

    • Updated the button layout in the piano roll, velocity and curve regions, to match the recent updates to the toolbar layout.

    • Speed optimized the UI switching of editor profiles.

    • Pressing the 1-9 numeric keys switches between arrangement editor profiles.

    • Pressing F6 toggles the browser page.

    • Pressing F7/F8 restores/minimizes the first and second resizable region in the editor. This currently includes the embedded editor and the mixer.

    • The browser page can be activated by pressing the Tab key to rotate key focus between open panels.

    • Moved the color picker from the track panel to the top of the inspector. Right-clicking the color picker shows a menu with “enable track color”, “copy color” and “paste color”. Added popup-help to the color picker.

    • Removed the now redundant “enable track color” command from the track menu. Also removed the color option from the effect and parameter track dialogs.

    • Improved robustness of MIDI file import.

    September 5, 2009 at 11:20 #16360
    thcilnnahoj
    Participant

    Mmm… With such tasty appetizers, the time waiting for the main course will fly by. 😛

    With the color picker, you could go one step further and add 10 or so little boxes under it, to store and recall the user’s favorite colors.

    I also like the key focus framing on the project page, that you didn’t mention.

    September 7, 2009 at 14:39 #16362
    Conquistador
    Participant

    Hi Frits,

    Nice new changes. Small but they do add more consistency to the UI. I guess this stuff does take time. 😉

    You would clearly get a better response to this thread if the topic was covering MIDI or Audio features as that is clearly where most of us have our interests just going by the FR’s alone.

    But hang in there Frits. =D> Make the UI changes you need. So far the last two or three Podium releases have had changes that make it look and feel very modern and navigating it a pleasure (for the most part)…which brings me to…that track toolbar and changes to track headers..e.t.c But when you are ready of course. 😉

    Drums 🙁
    I would say (yes I have said it before) that the Midi drum presentation and set up is now just so far behind other parts of Podium (as of 2.22 especially) it really does stand out.

    How about a one click set up?
    I would ask if possible to consider adding a “Drum kit” button to the Presets panel for loaded VSTi’s. Currently the “Use Preset as drum kit” is hidden well out of view. Clicking on that new button should also automatically delete all notes that do not have drum note names as well. Those changes would at least get drum presentation and set up to a far more pleasurable level. More is needed but these two changes IMO are really basic, critical needs for that area of Podium at this point.

    What about this…? 🙂

    Zoom Presets

    Studio One has a rather nice little feature which i dismissed the first time I saw it but find it quite slick in terms of its simplification of UI navigation. Its effectively a set of Zoom presets for the Arranger. Any chance of that kind of feature making it into 2.22?

    If you want to really stir up your user base and get more responses to preview threads…just give us some new MIDI and AUDIO features… :D/ once the UI stuff (track toolbar e.t.c ) is finished of course 😉

    September 9, 2009 at 01:53 #16366
    Zynewave
    Keymaster

    @Conquistador wrote:

    Drums 🙁
    I would say (yes I have said it before) that the Midi drum presentation and set up is now just so far behind other parts of Podium (as of 2.22 especially) it really does stand out.

    How about a one click set up?
    I would ask if possible to consider adding a “Drum kit” button to the Presets panel for loaded VSTi’s. Currently the “Use Preset as drum kit” is hidden well out of view. Clicking on that new button should also automatically delete all notes that do not have drum note names as well. Those changes would at least get drum presentation and set up to a far more pleasurable level. More is needed but these two changes IMO are really basic, critical needs for that area of Podium at this point.

    What about this…? 🙂

    Your “critical” priorities are changing almost as frequently as mine :). That updating the drum editor is critical was not on your mind when we had the most recent VIP discussion of what I should spend my time on. The drum editor is scheduled for an update, but I would like to keep that out of the current series of overall UI revisions.

    Zoom Presets

    Studio One has a rather nice little feature which i dismissed the first time I saw it but find it quite slick in terms of its simplification of UI navigation. Its effectively a set of Zoom presets for the Arranger. Any chance of that kind of feature making it into 2.22?

    Not in 2.22. I think it was in the preview topic for the navigator that I mentioned I plan to add a zoom snapshot feature. The blank space to the left of the navigator will hold the controls for the snapshots.

    September 9, 2009 at 17:54 #16370
    Conquistador
    Participant

    @Zynewave wrote:

    Your “critical” priorities are changing almost as frequently as mine :). That updating the drum editor is critical was not on your mind when we had the most recent VIP discussion of what I should spend my time on. The drum editor is scheduled for an update, but I would like to keep that out of the current series of overall UI revisions.

    Yeah… 🙂 I guess I should have put it another way…maybe “one of the areas that would benefit from a revision a bit sooner possibly” instead of “critical”. More than one area is in need of attention but you cannot address everything at the same time. In any case I guess every suggestion from everyone has already been posted so you are aware of any issues or suggestions anyway. Consider my Drum kit /Editor revision suggestion a gentle reminder then. 🙂

    Not in 2.22. I think it was in the preview topic for the navigator that I mentioned I plan to add a zoom snapshot feature. The blank space to the left of the navigator will hold the controls for the snapshots.

    Ok cool. 8) I must have missed those details in the other thread.

    September 16, 2009 at 02:13 #16376
    Zynewave
    Keymaster

    Beta 2:

    • Added “export to sound file” to the arrangement editor and sound editor file menus. The commands show a dialog with bit resolution and normalize settings. The arrangement export uses the bounced audio of the master track. An “export bounced audio to sound file” command is also available in the bounce submenu of each individual track.

    • Removed the MIDI and bounce settings from the effect track properties dialog. The bounce settings are now exclusively managed with the track bounce submenu. The MIDI settings are still available in the source track properties dialog.

    • Reorganized the layout of the fader, meter and bounce track submenus.

    • Added “move bounced audio to new track” command to the bounce menu. Removed the now redundant “hide bounce track lane” option.

    The “export to sound file” dialog will in the future be extended with settings for sample rate, dither and encoding to mp3, ogg, flac etc.

    September 16, 2009 at 07:17 #16380
    pavouk100
    Participant

    Absolutely awesome. The new bouncing scheme is perfect, and IMHO solves nicely and very elegantly all bounce-related issues raised here in forums. =D>

    September 16, 2009 at 07:40 #16381
    swindus
    Participant

    Yes, works great. Thanks!

    Little bug: When using the command ‘crop unique sequence’ the view of an opened sound event editor is not updated correctly. The position of the sound event is wrong (navigator zoom?). After unselecting and selecting the sequence again the display is right.

    September 16, 2009 at 10:28 #16382
    Malcolm Jacobson
    Participant

    Hi Frits,

    Very nice improvements! Pity it means my “How to bounce” video is now out of date. 😀

    The only additional bounce feature I would like to request is a change to the way the “Render within punch range” works. When I edit a clip and select “Render within punch range” I get a new audio file that is the duration of the total arrangement, which is not what I want. To get it to match the duration of the punch range I then have to move/export the bounced audio and trim it in the editor, and then save it again.

    Is it possible to change the way “Render within punch range” works so the audio file matches the duration of the punch range?

    Cheers,

    Malcolm.

    September 16, 2009 at 11:51 #16383
    swindus
    Participant

    @Malcolm Jacobson wrote:

    Is it possible to change the way “Render within punch range” works so the audio file matches the duration of the punch range?

    Good one.

    September 16, 2009 at 13:41 #16384
    z_sfyr
    Participant

    Yes. I find that if I have, say, a couple of hours of material – music, or dialogue for example – arranged sequentially on the track page, that if I only want to render a few minutes starting at the 1 hour point, the render process seems to start from the very beginning of the timeline. I once had to edit 3 hours of a forum into individual speeches – you can imagine how long this process took. Is it possible to specify where the render begins and ends… or have I missed something?

    September 16, 2009 at 16:02 #16386
    Zynewave
    Keymaster

    @swindus wrote:

    Little bug: When using the command ‘crop unique sequence’ the view of an opened sound event editor is not updated correctly. The position of the sound event is wrong (navigator zoom?). After unselecting and selecting the sequence again the display is right.

    The editor is not really linked to the sound event, but is only initialized with the sound object and zoom range once the sound event is clicked. Eventually I’ll change this so that the editor keeps a link to the sound event, and thus will react to changes to the event.

    September 16, 2009 at 16:07 #16387
    Zynewave
    Keymaster

    @psychesonic wrote:

    Yes. I find that if I have, say, a couple of hours of material – music, or dialogue for example – arranged sequentially on the track page, that if I only want to render a few minutes starting at the 1 hour point, the render process seems to start from the very beginning of the timeline. I once had to edit 3 hours of a forum into individual speeches – you can imagine how long this process took. Is it possible to specify where the render begins and ends… or have I missed something?

    Are you using the “render within punch range” command? The render should start where you set your punch-in position.

    September 16, 2009 at 17:26 #16388
    thcilnnahoj
    Participant

    It’s definitely an improvement. The only inconvenience is that you’ll have to go through the same menus a few times, whereas you could set everything up in one go in a ‘bounce dialog’ like CQSD suggested in another thread.

    Two other things:
    – You may want to adjust the default size of the editor window (if not related to screen size) or horizontal size of the piano keys, as the new linked velocity buttons don’t fit anymore.

    – A minor inconsistency concerning the MIDI/note editor. The EE (embedded editor) will in some rare cases copy the velocity region height from the SWE (separate window editor), though they’re fine with having different region heights most of the time. Here’s one way to reproduce this:

    Switch to the ‘Editor’ profile > select a MIDI sequence > in the EE, set height of velocity region with the drag-handle > double-click a MIDI sequence to bring up the SWE and leave it there (it should have a different velocity region height) > click on a sound or curve sequence, so the EE switches to a different editor > select a MIDI sequence again > the EE should have assumed the velocity region height from the SWE.
    …That’s a mouthful! :-#

    September 17, 2009 at 04:20 #16392
    Zynewave
    Keymaster

    @thcilnnahoj wrote:

    – You may want to adjust the default size of the editor window (if not related to screen size) or horizontal size of the piano keys, as the new linked velocity buttons don’t fit anymore.

    Done.

    – A minor inconsistency concerning the MIDI/note editor. The EE (embedded editor) will in some rare cases copy the velocity region height from the SWE (separate window editor), though they’re fine with having different region heights most of the time. Here’s one way to reproduce this:

    Switch to the ‘Editor’ profile > select a MIDI sequence > in the EE, set height of velocity region with the drag-handle > double-click a MIDI sequence to bring up the SWE and leave it there (it should have a different velocity region height) > click on a sound or curve sequence, so the EE switches to a different editor > select a MIDI sequence again > the EE should have assumed the velocity region height from the SWE.
    …That’s a mouthful! :-#

    That’s because they are using the same editor profile. Besides the settings you find in the region dialogs, the profile also logs the “last used” size of resizable panels. So if you have two editors open showing the same profile, the last resize action will determine the size used the next time the editor is opened.

Viewing 15 posts - 1 through 15 (of 56 total)
1 2 3 4
  • You must be logged in to reply to this topic.
© 2021 Zynewave