acousmod.
acousmodHi,
I don’t know if it’s me or if it’s a problem inside Podium :
when I automate plugins values within their interface, the value “resets” to 0 from time to time, more or less fast according to the plugin. It happends with mine but also with other ones.
There is no problem when controlling the values with an external MIDI cc or with the track slider.
But, even with the track slider, when I release it while continuing to record the value jumps also to 0.
This behavior doesn’t occur with other hosts and I’ve tried in previous version of Podium which gives the same result 🙁
I don’t think that something has changed in my config, but…?
Am I the only one with this problem ?
Thanks.
acousmod2nd part :
When there is no track automation, the parameters of the plugins have a “normal behavior”, BUT when I put some parameter on a track its value turns to 0 each time Podium starts playing.
The only way to keep the actual value of a knob is to mute the automation track…
The same thing happends at the end of an automation sequence : the last value is not hold, instead it returns to 0 😥
Is this normal doctor ?
Zynewavewhen I automate plugins values within their interface, the value “resets” to 0 from time to time
Are you recording into/over an existing curve sequence that already has events?
When you e.g. loop while recording and grab a control to change the automation, then the behaviour depends on whether the plugin supports the effBeginEdit/effEndEdit calls. If the plugin supports these, then Podium will be notified that a parameter is being held (and thus automated) and Podium will then not play back any existing automation while the control is held. If the plugin does not support the BeginEdit/EndEdit calls, then Podium has no way of knowing whether a received parameter change is the last in an ongoing automation, and will thus play back existing curve automation.
Zynewavewhen I put some parameter on a track its value turns to 0 each time Podium starts playing
It will be set to whatever default value is defined in the parameter object properties. Whenever there is a blank interval on the track without a curve sequence, then the parameter is set to the default value. If I were to change this behaviour, so that parameters were never set if there wasn’t a curve sequence, it would have other potentially confusing implications. You would have ‘holes’ in your arrangement where a given parameter could have a random value, depending on whether you have manually moved the play cursor or changed the parameter in the plugin or synth. Thus playback would sound different, depending on where you started. If you e.g. automate a pitch-bend parameter, then the pitch-bend would be left in whatever position was last played. As it works now, Podium is in control of the parameter value at any position in the arrangement.
acousmodAre you recording into/over an existing curve sequence that already has events?
no, start allways with a blank one.
Whenever there is a blank interval on the track without a curve sequence, then the parameter is set to the default value.
oh, very annoying !
You would have ‘holes’ in your arrangement where a given parameter could have a random value, depending on whether you have manually moved the play cursor or changed the parameter in the plugin or synth. Thus playback would sound different, depending on where you started. If you e.g. automate a pitch-bend parameter, then the pitch-bend would be left in whatever position was last played.
ok, but what about the function that we find in Cubase (for MIDI since the ATARI version !) and others that simply consists to play the last previous value that is found on the track ?
I founded this simple and practical…
As it works now, Podium is in control of the parameter value at any position in the arrangement.
Podium, but not me !!!
So the only way is to put a continuous automation value for the entire length of the project, even for places where there is no change…
snif
If there a chance for an update ?
acousmodConcerning my first question, perhaps the jumps to 0 during the movements with the objects are due to the fact that they are not very regular ?
So, each time that my hand makes a little stop Podium thinks that the automation has finished and puts the default value ?
An alternative solution for the values during the recording of the automation could be “keep the last value” instead of “insert the default value” ?
acousmodAn alternative solution for the values during the recording of the automation could be “keep the last value” instead of “insert the default value” ?
Hi !
I have changed the values in the Parameter Properties (I’ve put 0 to 127 and default to 64, is there any standard better values ?).
Result : the last value when I stop moving is held !
So no more jumps.
I will update all my Devices Mapings with this values.
Cheers,
ZynewaveConcerning my first question, perhaps the jumps to 0 during the movements with the objects are due to the fact that they are not very regular ?
So, each time that my hand makes a little stop Podium thinks that the automation has finished and puts the default value ?
No that should not be an issue. Note that even if a plugin does not support the BeginEdit/EndEdit calls, Podium still remembers the last recorded parameter change, so that when the next change is received, it will erase any old events that is recorded over. Only problem is that the plugin can behave odd, because it receives parameter changes for a control that you may be editing by mouse dragging.
ZynewaveI have changed the values in the Parameter Properties (I’ve put 0 to 127 and default to 64, is there any standard better values ?).
Depends on the parameter. I assume it is VST plugin parameters you are referring to. If a VST parameter on the UI is e.g. a value from 0..100, you would enter these values as min/max in the parameter object.
Result : the last value when I stop moving is held !
Hmm, are you sure it is not set to the default value you entered (i.e. 64 ~ 0.5)?
acousmodHmm, are you sure it is not set to the default value you entered (i.e. 64 ~ 0.5)?
Yes.. it is OK.
I just need after to redraw with the pencil in the curve editor to obtain smooth curves.
acousmodBad analyzis from my part : the problem that I have discribed at the begining is due in fact to the default length of the sequence that Podium creates when we start the automation recording, which is different according to the playing position and what we do on other tracks.
And sometimes the sequence constructs itself whiloe recording and causes the jumps to the default values.
There is no problem when starting from the begining of the “song” with a fix length, only the first second of each new automation sequence is jerky during the time which Podium creates the fix length sequence.
It is a little bit disturbing for me since I have the habit of more freedom and I have some difficulty to perceive where and which are the constraints in Podium.
It’s learning curve is rather “special” and I must recognize that it’s the first time that a software gives me so much trouble : so logical and at the same time filled with a lot of little traps ! (it’s not a complain, it’s an observation)
But I will insist ! 😉
so :
I don’t know if it’s me or if it’s a problem inside Podium
it was me, because I haven’t yet understood all the special features of Podium…
To ending, I maintain nevertheless my request/suggestion for something simpler that seems to me less disturbing (and also for guys who work in a similar manner) :
– sequence of the length of what is recorded (the length is automaticaly adjusted while recording, like the future audio and MIDI recording way, if I have well understood ?)
– automatic playing of the last value in the previous sequence (can be set on or off !)
If you have some time in a year or two !!!
Cheers,