Zynewave's Forum Page

@thcilnnahoj wrote:

Was there something changed in regards to resizing the start of automation events?
Because it does seem to work now with events already present in projects I created/saved with 2.14, but not on events added with the beta, nor with any events in a newly created project. I believe you couldn’t do it at all up until now (?).

The 2.15 changes should not have an impact on how you resize curve sequence events. Could it be that the curve sequence events in your older project was originally created on an earlier start time?

@LiquidProj3ct wrote:

@Zynewave wrote:

Try the new beta3. Grabbing/releasing a Podium mixer parameter fader or a plugin editor control will now be recorded properly with start and end points. Note that some plugins do not report when a control is grabbed/released, so for these plugins you won’t get a final recorded end point on the curve when you release the control.

However there are problems yet. Try to record any knob movement (i record it tweaking the vsti knob instead podium mixer fader) when there is a curve sequence created:

1. When you move a knob and keep it in the same value the curve isn’t modified [in order to show the horizontal line] until you move the knob a little. I’ve tried with Firebird and Sylenth1, I don’t knob if these plugins have the report problem.

As soon as you release the mouse the curve should be overwritten ok I hope. Podium will only delete any existing curve being overwritten when it receives a new value from the plugin or when the control is released. That is for performance reasons.

edit: feature request while arm tracks: when you arm a track for record automaticaly arm all its plugin chain. I think this is a good idea because would be more easy for newbies record knobs tweaks without too much Podium understanding. Finding that Ctrl+click on a plugin arm their respective layer for record is a hard job.

I have now added support for Ctrl+Clicking on the track record button or pressing Ctrl+R key shortcut to toggle record mode of all tracks in the chain (source track and all effect tracks in the chain).

@pavouk100 wrote:

1. When automating VST parameter, would it be possible to see units of the current VST parameter (as e.g. in Podium’s generic VST effect ui), instead of number between 0 to 1?

It would be possible, but the problem is that the majority of parameter value texts supplied by plugins will not fit on e.g. the Podium fader buttons. It could be written in the value popup shown for a single selected point event in the curve editor. Maybe I’ll add that in a future update.

2. When automating Level, would it be possible to have values from -Inf to +12dB (as mixer faders have) instead of -Inf..0 (in other words, allow also amplification, not only attenuation).

That would require implementation of a new parameter type. The current “audio level” parameter uses a linear level scaling up to 0 dBFS. Changing this would break backwards compatibility with older projects. In a future update I could introduce a new “audio level (+12dB)” parameter type, which would use a level scaling similar to the gain faders.

@pernst wrote:

Is there a way to have the automation curve maintain the last value set in the clip if the clip window is expanded or contracted? This occurs if you have two clips for an automation track. If you set a point in the first clip, say at 50%. The line after the this point stays at a 50% level to the end to of clip and outside the clip. If you insert a second clip, the curve, from the 50% point in the first clip, linearly changes, to the default value for the parameter at the beginning of the second clip. A work around is to set a second point in the first clip at the final value one wants for parameter within the first clip, but it would be helpful the value of the parameter at the border of the clip is the value of the last point set in the clip.

If I have understood what you want: Select the last point in the first curve sequence and use the “convert to bar point” edit menu command.

@LiquidProj3ct wrote:

Visual bug: Open a piano roll editor (not embedded) and close it, then double click in any curve sequence and instead curve editor you will see another piano roll editor (if you double click in the curve sequence again you’ll see the usual curve editor).

Thanks. Now fixed in beta2. This bug was also present in previous Podium versions.

Beta2 also has a fix for a crash bug in the new automation code.