Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterHi,
The zoom bar in the right pane of the window is a display scale zoom. It does not change the relative track heights, which you set by dragging each individual track. This makes it possible to quickly zoom out so that all tracks are at their minimum height, and zoom back in again without disrupting the relative heights of the tracks. In the first arrangement in your project file, it seems that you had set the zoom out to maximum, and then dragged the height of the tracks. Thus when restarting Podium (or by setting the track zoom to default by control clicking the zoom bar), all the tracks will be huge.
I’m going to revise this behaviour the coming days. The next release 1.35 will save the zoom settings of each arrangement in the project file.
ZynewaveKeymasterFor the end of 2006 perhaps ?
Sounds about right, if I’m going to process your other requests first 😉
ZynewaveKeymasterHi Podianer,
Welcome to the forum, and thanks for your comments.
ZynewaveKeymasterif I insert a RoomVerb M2 on a track in my laptop, the CPU indicator can show 10 or 20 % depending on the Preset, even if there is no sound played on this track
It should be the job of the plugin to bypass its internal processing if it receives silent input. Podium cannot make the assumption that a silent input to a plugin will produce silent output, so the plugin process function has to be called. Are you feeding the M2 absolute silence? If you e.g. are monitoring analog inputs through the M2, the noise floor of the AD converters may trigger the plugin processing.
ZynewaveKeymasterCould you please email me your project file.
ZynewaveKeymasterOk, I thought you meant the audio processing. Possibly the graphics optimizations in 1.35 will improve on this. I’ve managed to improve the responsiveness of plugin editors at high CPU load. Also appearing in 1.35 is an option to unload plugins from memory when the bounce track is activated.
ZynewaveKeymasterThe next release 1.35 will have speed optimizations of the graphics. I’ll look at speed-optimizing the disk streaming code in a later release. That includes adding a disk bandwidth indicator next to or combined with the CPU indicator.
ZynewaveKeymasterThe maximum zoom button should adjust according to the actual length of the arrangement. Are you sure you have erased all events at the end of the arrangement, including markers?
ZynewaveKeymasterSince the version 1.28 (if I remember well ?) the plugins can’t no more go to sleep when they are not used
😮 It works fine here. Please give me more details.
ZynewaveKeymasterI have increased the font size of the CPU indicator. Will be released in version 1.35. The alternative visual representation will have to wait for another time.
ZynewaveKeymasterI heard that the more of the meter you use the more bits you use and so the more resolution you have
This applies only to fixed point mixing. Podium uses floating point mixing. I recommend you try to avoid any ‘red’ meters. The red color is meant as a warning signal that overload may occur in the mix.
ZynewaveKeymasterI used to highlight items that I was currently working on for the next release. I dropped this, because I found it bothersome to maintain this. The development did not always turn out as the highlighted items indicated.
ZynewaveKeymasterWhat Martin said.
ZynewaveKeymasterJust a quick question, does it matter if any audio channle is in the red as long as the master is’nt
As long as the ‘red’ channels are routed straight to a higher mixing point, then they can be gain reduced there. If the overloaded audio is routed through plugins on its way to the master, then the plugin processing may suffer from the overloaded audio input.
ZynewaveKeymasterthe colours used in the audio editor in the sreenshot on the home page
That is the ‘Colors – Deep Blue.ini’ setup file.