Zynewave's Forum Page

Does the full special edition of Podium feature in that one or the next edition, maybe due out around the end of Nov / early DEC ?

The next one coming out early December (issue 1|2007).

@acousmod wrote:

Another hack solution would be to always restrict channel heights to an odd pixel count, which on the other hand would result in less fluent zooming.

For me it would be a perfect solution.

As part of the ongoing work on the fade-in/out feature, I’ve now changed this so that each channel is always set to an unequal pixel height. Thus you won’t get the alternating thin/fat center line when you zoom vertically. Coming up in 1.73.

Ok, I did not find anything unexpected in your project. It works as intended.

Even though your audio file playing into the reverb is shorter than the bounce event, there is no way for Podium to know that the plugin will be silent after the audio file has stopped playing. In the case of zReverb you have the tail that slowly dies out. Other effect plugins may produce audio continuously. So Podium will process the entire length of the bounce event (even if only feeding the plugin silence), because it assumes that the bounce event is set to that length for a reason. In the case of zReverb you’ll notice that once the progress bar goes past the section where the audio file is playing, the bounce render speeds up significantly because the zReverb is optimized to consume less CPU when input is silent and the reverb has died out.

Btw. The bounce render even for your long bounce event took less than a second on my machine, so it was difficult to notice any difference between a short and long bounce event. How long does your render take with the long bounce event?

Program change and Volume MUST exist by default for each VSTi, but also the more common Controller numbers like Pan (10), Pedal (4), Sustain (64) etc.
I don’t see any problem to have more, do you ?

I can easily add more default MIDI parameters.

The only reason that I have not added more default MIDI parameters is because many synth plugins only support pitch bend and possibly modulation (CC1).

I have now added “Program Change” and “Volume” (CC7) as default parameters. ppw72: are there any more CC parameters that you use in your MIDI files?

I have seen slow bounces before but on closer inspection it appears the longer the sound event on a New Group bounce Track the longer an offline render or bounce takes to complete. When a New Group Bounce Track is created it is created with a very long sound event. Far too long.

If the effect plugin CPU usage is constant no matter the input (even silence) then the bounce render time is proportional with the length of the bounce event.

When a new bounce track is created the sound event is set to the length of the arrangement. If you want it to be shorter just resize the bounce event. You can also press undo once after creating the bounce track. This will undo the bounce event creation. A second undo command will undo the bounce track creation.

Even if each arrangement uses a similar or identical file, all Podium would need to do is simply replace any instance of that file wherever it is missing in each arrangement in a Project.

That’s not what I meant. Say you have two different sound files: arrangement1/beat.wav and arrangement2/beat.wav. If you now rename both arrangement folders and want to relink the files in your project, Podium wouldn’t know which beat.wav belonged to which arrangement. Thus you need to do the search for one arrangement at the time.

The “Search in File Folder” menu command was added in Podium 1.68, and in the latest 1.72 it was added to the guide:

http://www.zynewave.com/wiki/doku.php?id=guide:project_start_page#arrangements_sounds_panel

Your next question may be; “Why is there no “Search For Missing Sound Files” menu in the Arrangements & Sounds panel menu?”. Because each arrangement in a project may have similarly named sound files placed in different arrangement subfolders. So you need to select the broken sound files for one arrangement at the time, and direct the search to the proper subfolder for the arrangement.