Update Limit When Sending Control Parameters to Cascade
Hello,
I'm morphing between two different equalizer curves using the raw output of a Live dial and some Scale objects. It works fine at first but then after a few minutes it goes nuts - I hear all this zipper noise and distortion which gets progressively worse, then silence. I changed the Update Limit of the Live Dial to 40ms and the problem subsided. My question is have I just side-stepped a larger problem or should I minimize data controlling the Cascade filter? If so, what is the best practice for this sort of thing and does this apply to controlling other objects as well?
Darren
Can you show the device?
I believe I figured out what the problem was. I had cascade, filtergraph, plugin and plugout towards the bottom right and it was sorta messy in general. I was ignoring the order of things. So I did some organization on it and the problem went way - I was able to remove the update limit. It works perfectly now. At least I haven't experienced that same problem.
So, I'm guessing that if I just align things in a way that looks right I'm halfway towards making it work efficiently. As this is my first M4L project, I'm still a bit fuzzy on what the best practice is for optimizing signal flow.
Using the trigger object is a good means to knowing what is going where, and in what order. The right-most output will always be sent with first.
instead of _shorter update times i would try to interpolate the modulation data by making it a signal.
I'm not sure I would know how to do that [See attached if you like]. I'm actually using the exponential response setting in the live dials to get equal power curves (it's a 5 channel surround panner). I started this from a very simple quad panner someone had posted on the live forum some time ago because his idea with the dials seemed like an easy way to get the curves. It's kinda wonky in that the dials have a stepped response when the curve is steep but I don't hear it int the end result. I'm sure it's a pretty novice design but it seems to be doing the job ok. Any advice on making it more efficient and smoother would be appreciated.
Hello, i had some problem last nigth with live.gui object max update 5.1.5. I think the problem could be in the Update limit settings 1 for default.
1) live.gui objects with Update limit > 0 does not initialize correctly own value, i think the init value is delayed of Update setup time (1) the problem it's easly solvable putting Update limit = 0, anyway the gui.object they should emit init value at time 0.
2) strange behavior when sending data through "set $1" message, see example for more details:
i'm waiting news, thanks regards :-)