Zynewave.
xis23Hey, having a problem with parameter automation… Mainly, that is that my vsts aren’t always picking up the right data… ie I might have the paramater ‘filter bypass’ set to 100 so it’ll bypass, but then when i offline bounce it doesn’t always seem to pick up the correct values :(. On the other hand if I want something set to 0 then it’ll always pick up my 0 or abscense of data.
Actually, sometimes it does this when not offline bouncing anway…. for instance I might stop playback and find that some parameters have reset to 0, in the case of using a bypass parameter, then this starts overloading my cpu and I can’t use play to reactivate the bypass again.
xis23oh i think I know why my bounce tracks were coming out funny… i had split them from one big track to smaller ones and forgot to use ‘set duration’…. but i still dunno why params are resetting sometimes when i hit stop or when the end of a loop is reached…. also the bounce bug is still happening… on certian tracks it seems that it will always happen, and if i record normally it fixes it.
ZynewaveI’m a little lost in your description of the problem. Could you post a screenshot or give a more detailed explanation on how to reproduce the problem?
but then when i offline bounce it doesn’t always seem to pick up the correct values
It’s possible that some plugins have a problem with automation during offline bounce rendering. They may rely on real-time timers or idle notifications from the host for updating automation states. Idle notifications are skipped during bounce rendering.
xis23oh i see… this explains the problem i was having with a few plugins… does this also explain plugins wherin ‘100’ sets a bypass state rather than ‘0’ effecting a bypass state.. the 0 gets stuck on? Sometimes I have been using a sequence to set the area for 100 and then just ending the sequence and having a blank space to set the 0 until I need to reset to 100 again, and by merging the events inbetween and redrawing in the 0 have found this fixes the problem, but it doesn’t always work ie. where 100 is what I want rather than 0 sometimes it seems to revert to a zero on seuqnces.
acousmodI don’t know if it is related, and if I have well understood, but you have said that you have splitted a big sequence ?
There is a very old bug with automation curves, hard to reproduce, which happends some times with sequences that have been splitted + clone phantom + crop sequence correctly made.
Sometimes old values that are no more in the sequence are active even if you draw other values.
The only solution is to delete the sequence and draw a new fresh one.
Perhaps that some “old” 100 or 0 values interfer with the one that you see ?
(when sequences are merged, the sent values are also sometimes shifted in comparison to the ones that are seen)
ZynewaveIt would be nice if either of you could create and email me a simple project file with a problematic automation track. It’s difficult for me to reproduce the bug based on your descriptions.
xis23ok i’ll give it a go when i get home… the main vst that seems to do this is spectron, although I think I have some others that require 100 rather than 0 to set a bypass. The reason I have probably noticed this more than anyone else is that I have been using 15 or so of them in a chain so i can dump the audio and resample it en masse for different drum hits. Trouble is I only need 1 spectron active at any one time. For now I will try using sends to eradicate this problem. I could send you this arrangement if you like, although it’s not that simple but it just takes audio as an input so I’ll change the input to a static audio file rather than kontakt.
“There is a very old bug with automation curves, hard to reproduce, which happends some times with sequences that have been splitted + clone phantom + crop sequence correctly made.
Sometimes old values that are no more in the sequence are active even if you draw other values.
The only solution is to delete the sequence and draw a new fresh on” – that might be it yes.
xis23doh, have moved to a house with no internet so might be a while before i can get this back to you…
acousmodThis is a project with two arrangements :
http://mediasonie.free.fr/temp/test_envelopes.pod
“Wrong fade” shows a curve but you hear the previous editing (a constant fade out).
I don’t know how to reproduce it, it happends from time to time after editing.
The curve can be moved and edited, the new points are “mixed” with old invisible ones.
The only solution that I’ve found is to erase the event and draw another one.
“Shift” can be reproduced each time : when I merge two enveloppes events the new curve is “time stretched”.
It happends when the arrangement is set to Linear. When Musical the point curves are not shifted.
The test project has been made with 1.60 and I shows the same behaviour in 1.62.
For me, the problems have always been present.
acousmodDoes the file helps to find a solution ?