Zynewave's Forum Page

Hi Chris,

Welcome to the forum, and sorry for the delay with the license. Good thing you posted about this. I normally receive an email from share-it when an order has been placed. It turns out that my website host provider has turned off automatic email forwarding due to excessive spam emails (without notifying me) which means I didn’t receive any emails from my accounts at share-it and paypal. This is now fixed.

Frits

Click the pin button at the top of the preset panel.

It’s deliberate that is omitted from the track context menu. However, if you left-click on the map row in the mixer, you will get a device menu. I’m probably going to extend this to the group panel in the inspector, and maybe also to the mapping box in the track lane header.

Ok, I misunderstood your first post. The problem you pictured is probably related to the beginEdit/endEdit support of the plugin. We’ve discussed this before:
http://www.zynewave.com/forum/viewtopic.php?t=345

With plugins which have no GUI or when it is very simple, it is less annoying, because we get only the first jump from the default value to the current value (like at the begining of the first curve).

The Podium generic plugin editor implements the beginEdit/endEdit calls, so clicking and dragging a plugin control in the Podium editor does not result in erratic value jumps as long as the mouse is held down.

So I take it you are in favour of solution A. My problem with this, is that when you start playback at any position before the first recorded curve point event, the value of the parameter is undefined. The parameter will have the value that you either edited in the plugin editor, or the automated value it was set to when last playback was stopped. By forcing the parameter to the defined default value at any point on the timeline where there are no curve sequences, playback will be consistent no matter where it is started.

This is not a bug. If the current behaviour is a nuisance I’ll consider changing it.

The problem: If Podium does not set a value for the parameter at playback start, then until the playback cursor reaches the first point on the curve the parameter will have a random value, depending on what the parameter was set to when playback was last stopped.

So is the best solution to:

A/ Ignore updates of the parameter on the timeline until the first encountered curve sequence. (i.e. possible random parameter settings at playback start)

B/ When the first curve sequence is created on a new automation track, a curve point is placed at the start of the sequence with the value of the first recorded automation value.