Main menu
You are here
automation editing prob
I seem to have encountered a prob with qtr's automation editing. I have a MIDI track and I'm trying to draw an automation curve for a softsynth parameter but qtr won't let me draw the line I want in both linear and spline modes. I'm just trying to draw a straight line (or a spline) that starts at -infiinity dB (silence) and goes a little way up a bar or two later. The problem is that as soon as I draw such a line, qtr's automation curve simplification code kicks in and deletes the first node which I positioned at -infinity dB (the very bottom left of the clip) and replaces it with a new starting value that is about 1/6th of the way up the MIDI tracks's automation display but without any node there that I can adjust.
Is there a way to make qtr less eager with simplifying automation curves so that I can do this? If my description isn't clear enough I can upload a video to demonstrate the problem later if you want Rui?
Thanks for your help!
Re. automation editing prob
not giving any guarantees, but have you tried the logarithmic mode flag? that might trump the linear auto-in-line-smoothing-simplify-optimization-thing :)
be warned that the "auto-simplify" feature is most welcome and convenient when dealing to recording automation, especially if the target subject is mapped to some live tweak-able MIDI knob/slider controller ;)
basically it tends to drop redundant automation data point nodes, ones that add nothing but cruft to the curve slope. it has its short-comings namely that it only does it by just linear regression.
the case on hand is about you visual editing the values via mouse click-n-drag, whatever--point is linear moves on the screen are directly proportional to scalar value changes, and that applies 1:1 to linear and spline modes while (sample&)hold mode is special, obviously.
now say, if your automation curve is set into so called "logarithmic" mode, as is found convenient for dB valued data series like gain etc. you'll be detaching the linearity predicate between actual data signal and the visual graphic where you move things around.
have i made it a too complicated excuse? :)
hth.
cheers
anyway
log mode
I've just tried both linear and spline again but with log mode enabled and I still have the same prob. The only real difference with log mode enabled is that when the first node disappears the curve defaults to starting in the middle of the automation / track display instead of ~1/6th of the track height from the bottom.
I think you understand my problem but I can still upload a video if required?
Thanks Rui
re. log mode
then you better go through the workaround of manually adding new points/nodes wherever fits your purpose and will.
remember that you can also edit each point/node numerically (double-click on it) when drag-n-move is not coping with your wishes.
hth.
cheers
auto tactics
It seems the workaround here is to first work out the value and position of the second automation node. Then create the first two nodes and make sure the second node is placed exactly where you want it before dragging the first node into position. Once the first node has been positioned, the second cannot be moved or it destroys the first and you also have to be careful with positioning subsequent nodes so they don't suffer a similar fate.
Add new comment