Zynewave's Forum Page

@pj geerlings wrote:

@Zynewave wrote:

I’ll spend a couple of days on the Podium Guide, and then release 2.22 later this week.

I noticed this:
guide/getting_started.txt · Last modified: 2009/09/30

How many sections did you have a chance to work on in total?

thanks
pj

I aim to revise all the sections and screenshots in the getting started chapter.

@thcilnnahoj wrote:

Another one to report. I followed the multiple monitor outputs tutorial, and there seems to be a problem resulting in a crash. Probably came with the compact track layout?

It happens when you try to delete the very last track inside a hierachy that’s placed above another hierachy in the tracklist.

Thanks. Fixed and uploaded beta 6.

I also changed the creation of the secondary master track so that it is set up as a group track capable of inserting effect tracks, similar to the normal master track.

@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.

@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.

@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.