Zynewave's Forum Page

@LiquidProj3ct wrote:

About CPU usage. Podium, at least with one track, only use one core in my PC. Take a look to this screenshot, where I use Nithonat, Toraverb and Redoptor with maximun quality settings:

(click on picture until you see it at real size)

edit: I’m on Xp home, 32bits

It’s impossible for the host to split up the processing of a single plugin, or even a chain of serially connected plugins. The host asks a plugin to process a buffer of samples. It’s not possible for the host to split this up into smaller buffers, and then ask the plugin to process these simultaneously, because almost all plugins requires that samples are processed serially. Even a simple EQ plugin requires the processed result of the previous sample in its computation of the next sample.

If a single plugin should utilize multiple CPUs, it needs to be implemented in the plugin, which knows what parts of its internal processing can be performed in parallel. One example is the latest version of the NI Kontakt sampler. I remember reading that it now supports multiprocessing internally. It makes sense for a multitimbral instrument/sampler, because each voice could be processed separately.

@Malcolm Jacobson wrote:

I agree with others comments that the “Add new effect” button should be above the existing FX, and that the new effect should be added at the top, so the behaviour in the Group Panel matches the order of the Mixer.

By popular request, the “add new effect” (or “+”) button is now placed at the end of the chain.

I don’t understand the need for the Tick button. I like the information about the effect to be shown in the Inspector as soon as I click on the effect name. I don’t like having to click the “Tick” button as well. Can we add an option to hide this button and have the information automatically displayed?

I can’t see how I can avoid the tick/select button. There need to be an indication in the group panel of which effect track is selected, and thus which track is being edited with the object lists at the bottom of the inspector. I can’t see how I can combine this into the selector buttons. The selectors already use colors to indicate plugin open/close state. Clicking selectors are used to open menus or open/close editors, and you don’t always want the track to be automatically selected when you just want to open a plugin editor.

2. I can’t help but to think those shadows look a little exaggerated on brightly colored backgrounds, like the default blue for selections on Vista. I don’t know about your UI rendering engine, of course, but is there any way you could try something similar to rendering shadows with a different blend mode? You know, Like in image editors – multiply, screen, overlay… A “simple matter of programming”, surely. 😉

I agree that the shadows are a bit too agressive. I’ve toned down the button shadows in the new beta6.

In beta6 the effect record buttons are finally gone. The track lane record button will also record enable all plugin effect tracks.

Beta4:

Another button bites the dust. The select and menu buttons are now combined into one. Clicking the button will select the track. Clicking the button when the track is selected will open the menu.

The “add effect” selector is now a simple “+” button. It can be hidden with the “show new effect buttons” option in the inspector options menu.

Clicking a selector with a send assigned will toggle the display of send controls.

Still to do:

Right-click on buttons.
Drag-reordering.
And I’m still thinking of ways to get rid of the record buttons.

@Markus wrote:

@Zynewave wrote:

@Markus wrote:

How about coding just simple compressor / duck / gate fx? It doesnt have to be good. Just that good so we can use it for sidechain.

How long it will take to code something like this? Simple duck fx? Thanks for your time.

Based on my experience with zPEQ, zReverb and zPitch, I estimate that it will take me at least a month to make a zComp. I tend to be thorough when I start on a new plugin. At present time my time is better spent on Podium, but I’m looking forward to when I get time to expand on the zPlugins suite.

No, i mean SIMPLE. Very simple. We can use third part compressors. But i’m asking very very simple ducking fx. Something what you can code like in couple days or one week. Or then you may add support to some free compressors. Or something.. Like i said, it doesnt have to be good.

I really want to change Podium to my main DAW:n. But as an electornic music producer, lack of this kinda feature is deal breaker for me (and many others)..

Anyway, thanks.

The ducking effect is achieved using a compressor and the compressor needs to support sidechain input. If you are talking about the sidechain track routing within Podium, then that is already supported. I’m sorry that it doesn’t work the way you prefer.

@Markus wrote:

How about coding just simple compressor / duck / gate fx? It doesnt have to be good. Just that good so we can use it for sidechain.

How long it will take to code something like this? Simple duck fx? Thanks for your time.

Based on my experience with zPEQ, zReverb and zPitch, I estimate that it will take me at least a month to make a zComp. I tend to be thorough when I start on a new plugin. At present time my time is better spent on Podium, but I’m looking forward to when I get time to expand on the zPlugins suite.