Zynewave's Forum Page

does each vocal track need to be wrapped in two tracks for each FX?

If you want to apply different Comp and EQ to each vocal track, then yes. Enabling the use of multiple plugins on a single track is high on my list, but it will require some careful design and so will take a while before it is implemented.

I create a group track for the vocal track, which has a compression plug on it which flows upwards towards another second group track which has an EQ plug in it…correct?

Yes.

Is there any other way to create track FX in Podium without having to create a group track for the FX? For instance, dragging an insert FX directly to the track without having to create a group track?

You can drag mappings onto the bottom blank area of the tracks region to add a new track with the plugin. Dragging a mapping to insert between tracks is not possible yet, but I will be working on that later on.

So are FX only added to a track by wrapping an instance of the FX around a track?

Yes, but it is only necessary if you have mappings further down the hierarchy that is feeding the effect. Tracks with audio events can have the effect mapping assigned directly on the track.

Also is there a limit to the number of FX a single track (wrapped around another) can have?

The engine can handle any number of cascaded effects. The UI limits the maximum track group level to 9.

I just tried installing Podium on my D: drive, and I get the same error. I’ll get this fixed for 1.32. The guide files are still installed to the correct place, so you can open the guide with the ‘Podium Guide’ item under the Zynewave group in the Windows start menu.

Thanks.

I actually had planned to start experimenting with docking the note/drum/curve/sound editors inside an arrangement editor. I don’t know if it will be ready for release 1.32.

I think I will put an ‘enable note transpose’ check-box option in the track properties along with a numeric input. On tracks where this is enabled will then appear a text and dial for the transpose value, similar to the gain and pan dials. I don’t plan to show the note transpose in the mixer strips though. How far should the transpose range be allowed, -127..127, -48..48?

The ‘transpose notes on input’ only works on notes received on a MIDI input interface. If you have a recorded note sequence, then the only way currently is to transpose the notes with the keyboard editor. Recently there was a forum discussion about adding a transpose setting to the track properties. I’ll try to implement that for the next release.

And what about using the control key (or using the right button) for controling the vertical zoom / amplitude zoom ?

I think there would still need to be the two sliders to illustrate the two different zoom levels.

change the height of a channel when the cursor is on the bar that separate the channels

I’ll put that on the list.

Concerning the vertical zoom button, it will be more logical (in my opinion) if its behaviour will be the same as for the other windows : zoom of the channels instead of zoom of the amplitude

That was my initial intention, but the problem is that to allow both an amplitude zoom and a channel height zoom similar to the tracks in the arrangement editor, then there would have to be two vertical sliders. I could not find a good way to implement this, so I decided on the restriction that all channels are always visible in the sound editor. That way I could get rid of the channel zoom slider. I then implemented the ‘relative’ zoom of each channel to allow that a single channel could be zoomed out for detail editing.