acousmod.
druidHello everyone (mostly Frits),
I am having a slight issue with Podium and automation tracks. It may or may not be a bug, but I think it probably isn’t, but I can’t work out the logic behind what it’s doing.
Sometimes I prefer a track-wide automation track. In this instance it is fine. But sometimes I like to attach automation clips with the matching note clips, because they belong together.
I have a guitar synth in a track, and have three settings that I have created “init” clips for, which basically allows me to set them for most of the song (so if I play from the start of the track, it will set those options to how they should be before other automation clips change them).
However, oddly… As an example, one is “sustain”. When on, the note will continue playing until it dies or is stopped, when off, it stops when the MIDI note stops. On initialisation at the start, it is ON (1.00). The clip lasts for one beat, with one point at 0 time and set to bar mode. I watch it set it on the synth to ON. Then once the play cursor passes the end of the clip, it resets to OFF.
…. what? I never told it to go to 0.00. In fact, I tried even to save the .fxp file so that it was ON in it, to see if it was jumping to the original preset loaded, but it still does it.
So I thought, well, the first automation clip AFTER the initialisation sets it to 0.00, maybe Podium is reading the next point and jumping to it after clips stop. So I create an automation clip BEFORE the 0.00 one, and set THAT to 1.00, and play the initialisation clip to see what happens… Nope! It still jumps to 0.00!
Frits, can you tell me what the logic of this is, or if it’s something I’m missing, what’s wrong? To my logic, once a parameter is set, it would stay that way unless something else comes along to change it later, yes?
acousmodYes, it is a weird behavior which has been discussed…
http://www.zynewave.com/forum/viewtopic.php?p=9429
I have already asked for an option in the preferences to switch between the current mode – reset value when there is no automation clip – and keeping the last previous value, like for MIDI events.
ZynewaveThere’s also been some discussion in this topic:
http://www.zynewave.com/forum/viewtopic.php?t=1379
Druid, let me know if this answers your question.
acousmodDruid : do you use parameter automation clip or CC 64 MIDI clip ?
Normally, the sustain pedal value must not been reseted on clip end.
druid@acousmod wrote:
Yes, it is a weird behavior which has been discussed…
http://www.zynewave.com/forum/viewtopic.php?p=9429
Ah yes, that’s what I mean.
Frits, can you explain the logic of setting a parameter to 0 when a clip is not present? To my way of thinking, it should be one of two things:
– Last set value plays until new automation is reached
Or preferably;
– On playback (when pressing space or PLAY with a MIDI keyboard) find the previous clip in the timeline for a given track, take its last value, and apply it.
I suppose that last one is a bit like having a track-wide automation lane, which I don’t really approve of, I like having short clips, but I can’t really understand why a parameter would change when it runs past a clip boundary?
ZynewaveFrits, can you explain the logic of setting a parameter to 0 when a clip is not present?
The parameter is not set to 0 but to the default value defined in the parameter properties.
To my way of thinking, it should be one of two things:
– Last set value plays until new automation is reached
Or preferably;
– On playback (when pressing space or PLAY with a MIDI keyboard) find the previous clip in the timeline for a given track, take its last value, and apply it.
– Last set value plays until new automation is reached
What I don’t like about this approach: The parameter value will be random when you start playback at a position where there are no curve sequences on a parameter track. The parameter value will depend on where you stopped playback last.
When the parameter snaps back to the default value whenever there is no curve sequence present, you are guarenteed that parameter automation is determinate no matter where you start playback.
– On playback (when pressing space or PLAY with a MIDI keyboard) find the previous clip in the timeline for a given track, take its last value, and apply it.
I may add an option for this behaviour in a future update.
druidYes, I understand the first way could result in that, and indeed sometimes I have found it a problem, so fair point…
But I do like the second option I suggested.
Thanks for telling me about the default parameter thing. I am still very much a compact mode user and getting behind the scenes and editing all those things thoroughly for many plugins just isn’t something I want to do really. However, you have now explained what it does; I really couldn’t figure out the logic before. Thanks. 🙂
acousmodI may add an option for this behaviour in a future update.
Thank you A LOT Frits ! 😛