Topic: Preview 2.22: UI improvements

Viewing 15 posts - 31 through 45 (of 56 total)
1 2 3 4
  • September 18, 2009 at 10:21 #16415
    MelodyMan
    Participant

    @Malcolm Jacobson wrote:

    @Zynewave wrote:

    How about if I add “Export Sound Event To Sound File…” to the sound editor file menu. This will do an export limited to the range of the clicked event.

    Sounds great! 🙂

    Yes, cool 8) .

    September 22, 2009 at 14:57 #16427
    Markus
    Participant

    Hi guys

    I’m back! Like it or not 😮

    Podium has take some rly nice steps while i’m was away. I read that Frits is now focusing on inspector. So here is one idea to develop it to even better!

    Pls let me know what you guys think 8)

    September 23, 2009 at 02:00 #16430
    Zynewave
    Keymaster

    @Markus wrote:

    Hi guys

    I’m back! Like it or not 😮

    Podium has take some rly nice steps while i’m was away. I read that Frits is now focusing on inspector. So here is one idea to develop it to even better!

    Pls let me know what you guys think 8)

    I’m planning to do some more work on the inspector in the coming releases. This will include a redesigned group panel which may be a solution for your “FX slot” in the screenshot. Hopefully I’ll complete the inspector changes before the end of 2009.

    September 23, 2009 at 02:05 #16431
    Zynewave
    Keymaster

    Beta 3:

    • Added marker region to all the sound editor profiles in the default setup.

    • The sound editor now supports the Alt+M shortcut for inserting a marker at the cursor. The Q/W shortcuts will step between markers in the sound, in addition to the markers in the arrangement. When a marker is selected the cursor left/right keys can be used to select the previous or next marker.

    • Updated the edit menu in the sound editor. The “select all” and “select all from cursor” commands will now select an audio segment instead of markers.

    • Added “fade-in” and “fade-out” edit commands to the sound editor.

    • Renamed the “clone phantom sequence” and “crop unique sequence” edit commands to “clone” and “crop”. Added “clone and crop” command which will do both actions in one step.

    • VST effects are no longer reset with “all notes off” MIDI messages. This avoids crashes occurring with IK Multimedia effect plugins.

    September 23, 2009 at 02:11 #16432
    Zynewave
    Keymaster

    @Malcolm Jacobson wrote:

    @Zynewave wrote:

    How about if I add “Export Sound Event To Sound File…” to the sound editor file menu. This will do an export limited to the range of the clicked event.

    Sounds great! 🙂

    After some consideration and experimentation, I did not like my suggestion with the specific export option. Instead I added the “Clone And Crop” command to the event edit menu. Upon using this command you can then use the normal “export to sound file” in the sound editor.

    September 23, 2009 at 04:52 #16437
    thcilnnahoj
    Participant

    A recently conducted investigation (:wink:) yielded two crashes and one bug. Tested with Podium 221 and 222 beta 2.

    1- Crash when horizontally resizing the floating note editor too far. Grab the right hand window border and drag it all the way to the left. The sound and curve editor seem to be immune, since you can’t downsize them this much.

    2- Some(!) audio files seem to confuse the sound editor. The editor doesn’t update the waveform display when you select a different event, but shows the correct wave again if you make a selection or zoom. The files were all 32-bit float, 48 KHz WAV. I also let Podium create new .mini files a few times, to no change.

    I’ve made a quick video of these two: http://www.youtube.com/watch?v=l0vdmfJOVL4 (Note the ‘bass’ wave is always displayed correctly.)

    3- The other crash seems to be related to the scalpel tool in the sound editor, but I can’t reproduce it well enough yet. It randomly happened three times very soon after I made random ‘cuts’ in an audio segment, and then just moved the mouse over various other interface elements.
    By the way, does the scalpel have a real use in the sound editor, besides drawing saw and square waves? 😉

    I also have to say that since you added the ‘stretch’ element, the joined edit toolbar buttons look very nice!

    September 23, 2009 at 05:12 #16438
    thcilnnahoj
    Participant

    @Zynewave wrote:

    Beta 3: […]

    Awesome! 8)

    Two questions: Will the sound markers be stored somewhere outside the arrangement, like in the accompanying mini file?
    And can you tell us what type of curve the fade commands use? It looks a bit steeper than equal power.

    September 23, 2009 at 15:47 #16443
    kingtubby
    Participant

    @Zynewave wrote:

    Beta 3:

    • VST effects are no longer reset with “all notes off” MIDI messages. This avoids crashes occurring with IK Multimedia effect plugins.

    Seems to have done the trick. 🙂

    Mart.

    September 23, 2009 at 17:19 #16444
    Zynewave
    Keymaster

    @thcilnnahoj wrote:

    Will the sound markers be stored somewhere outside the arrangement, like in the accompanying mini file?

    They are stored in the wav file using the standard cue list chunk. This has always been supported in Podium, but up till now it was only the sound editor profile with the transport toolbar that had the marker region.

    And can you tell us what type of curve the fade commands use? It looks a bit steeper than equal power.

    It’s equal power, meaning ~-3dB midway in the faded segment. You can verify this by using the pencil tool to draw a line at the top of the wave editor, and then apply the fade on this waveform. Don’t play this waveform though!

    September 23, 2009 at 20:17 #16446
    Malcolm Jacobson
    Participant

    @Zynewave wrote:

    After some consideration and experimentation, I did not like my suggestion with the specific export option. Instead I added the “Clone And Crop” command to the event edit menu. Upon using this command you can then use the normal “export to sound file” in the sound editor.

    Thanks Frits, this works well and is a great improvement to my workflow. 8)

    I noticed that the exported sound file does not include fades that are on the event – i.e. the event had a fade in, but the exported sound did not. Are event fades meant to be included in the exported file?

    Cheers,

    Malcolm.

    September 24, 2009 at 01:27 #16448
    Zynewave
    Keymaster

    @thcilnnahoj wrote:

    1- Crash when horizontally resizing the floating note editor too far. Grab the right hand window border and drag it all the way to the left. The sound and curve editor seem to be immune, since you can’t downsize them this much.

    2- Some(!) audio files seem to confuse the sound editor. The editor doesn’t update the waveform display when you select a different event, but shows the correct wave again if you make a selection or zoom. The files were all 32-bit float, 48 KHz WAV. I also let Podium create new .mini files a few times, to no change.

    I’ve made a quick video of these two: http://www.youtube.com/watch?v=l0vdmfJOVL4 (Note the ‘bass’ wave is always displayed correctly.)

    Thanks. Beta 4 is uploaded with fixes for these two bugs.

    3- The other crash seems to be related to the scalpel tool in the sound editor, but I can’t reproduce it well enough yet. It randomly happened three times very soon after I made random ‘cuts’ in an audio segment, and then just moved the mouse over various other interface elements.

    No crash from random testing here. Let me know if you find a method to reproduce the crash.

    By the way, does the scalpel have a real use in the sound editor, besides drawing saw and square waves? 😉

    You could use it to remove clicks, if you feel you can’t draw accurately with the pencil tool.

    September 24, 2009 at 01:35 #16449
    Zynewave
    Keymaster

    @Malcolm Jacobson wrote:

    I noticed that the exported sound file does not include fades that are on the event – i.e. the event had a fade in, but the exported sound did not. Are event fades meant to be included in the exported file?

    No. The export is done on the “raw” samples in the sound editor. There could be multiple events referencing the same sound but with different fade-in/out. If you want the fades included in your export, you can either bounce and export, or destructively apply fades in the sound editor with the new fade edit commands.

    September 24, 2009 at 05:27 #16451
    thcilnnahoj
    Participant

    @Zynewave wrote:

    @thcilnnahoj wrote:

    Will the sound markers be stored somewhere outside the arrangement, like in the accompanying mini file?

    They are stored in the wav file using the standard cue list chunk. This has always been supported in Podium, but up till now it was only the sound editor profile with the transport toolbar that had the marker region.

    That’s good to know. It was well hidden before. 😉

    @Zynewave wrote:

    @thcilnnahoj wrote:

    And can you tell us what type of curve the fade commands use? It looks a bit steeper than equal power.

    It’s equal power, meaning ~-3dB midway in the faded segment. You can verify this by using the pencil tool to draw a line at the top of the wave editor, and then apply the fade on this waveform. Don’t play this waveform though!

    I’m relieved to know that I was mistaken, as I believe equal power would be the best choice in this case.

    I think this has led me to another bug (beta 4): If I try to draw a line at the very top, it snaps to the bottom instead, and it seems this only becomes visible at some zoom ranges. Drawing lines at the bottom works fine. http://www.youtube.com/watch?v=byP1O8HWLCs
    I can’t (rather don’t want to :shock:) verify if it’s only a visual flaw.

    Also, the undo for adding a marker just reads “new event.” If it’s not too much work, I think it should be renamed for clarity.

    Edit: Oh, and I always wonder why the navigator only displays the top half of a waveform.
    It’s good for stereo files, but I think the remaining space could be better utilized for mono.

    September 24, 2009 at 16:57 #16455
    Zynewave
    Keymaster

    @thcilnnahoj wrote:

    I think this has led me to another bug (beta 4): If I try to draw a line at the very top, it snaps to the bottom instead, and it seems this only becomes visible at some zoom ranges. Drawing lines at the bottom works fine. http://www.youtube.com/watch?v=byP1O8HWLCs
    I can’t (rather don’t want to :shock:) verify if it’s only a visual flaw.

    Well then, try the new beta5 🙂 . This only happened with 32-bit floating point sounds.

    Also, the undo for adding a marker just reads “new event.” If it’s not too much work, I think it should be renamed for clarity.

    Done in beta5.

    Edit: Oh, and I always wonder why the navigator only displays the top half of a waveform.
    It’s good for stereo files, but I think the remaining space could be better utilized for mono.

    I assume your mono file is about -10 dB from full scale. If the mono file is normalized, then the waveform should use the full height of the navigator.

    The reason I only show half of the waveform (actually it’s the full min/max range wrapped around the baseline), is because the waveform usually is symmetrical around the baseline when you look at it zoomed out. So by cutting away the redundant half you get twice the resolution for showing peaks.

    September 25, 2009 at 05:44 #16456
    thcilnnahoj
    Participant

    @Zynewave wrote:

    Well then, try the new beta5 🙂 . This only happened with 32-bit floating point sounds.

    Will do! 🙂 I’m always astounded by how short-lived bugs are in Podium, once spotted.

    @Zynewave wrote:

    I assume your mono file is about -10 dB from full scale. If the mono file is normalized, then the waveform should use the full height of the navigator.

    The reason I only show half of the waveform (actually it’s the full min/max range wrapped around the baseline), is because the waveform usually is symmetrical around the baseline when you look at it zoomed out. So by cutting away the redundant half you get twice the resolution for showing peaks.

    I think you wouldn’t get many files recorded hot enough to use the full resolution during ‘normal’ production, assuming you don’t work with Apple loops exclusively! 😳
    Still, you’ve convinced me – the additional display resolution is definitely preferrable.

    Incidentally, would changing the scale from percentage to dB be only a matter of renaming the labels, or would this require some more tedious work?

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