On 12/23/2015 12:52 PM, Philip Yassin wrote:
> Hi! Just a quick one on automation
>
> Ever since TYOQA, when I use it, it's usually because I played with a
> plugin control, and decided I wanted its value to go from A to, say B.
> Sometimes there are more than 2 values.
> So I set said control to value A, and keep value B in my head. Then I
> create an automation curve for this control.
> Now what I'm expecting at that point, is an infinite curve with one
> point on it, set at value A.
> Even better for this point would be to be created not at the start to
> the song, but at the playhead's position. That would make 3 points. I
> hope I'm making sense.
> Now depending on the plugin use, I get the curve, but with no actual
> point on it, and it is "set" at either minimum 0 value, or (seemingly)
> max value. The control's (current) A position is lost, oh well.
>
> But hey, I can work too, I can still retrieve my values and set them.
>
> But wait, that will be hard, because there is no indication of the value
> of the point, neither as tooltip, nor in the messages window, not even
> stderr.
>
> None of this is blocking. Furthermore, I suspect that 1-getting &
> setting those values at those precise times may be impossible on
> Qtractor's end, depending of the plugins - please note that I (and my
> friends) tend to use exclusively LV2 plugins for those reasons - I'm
> just saying. Now I got to retrieve my values, and it can (probably will,
> it depends) be long and tedious, specially if the variations are small
> in between A and B (And C and X) and I spent a lot of time within the
> plugin setting them up. I had this PB many times and forgot to mention
> it. It can be a nightmare, what I do is I loop the part, then open the
> plugin, then watch the control move, then close the plugin, pause
> everything, adjust the curve points, rinse and repeat :) reminds me a
> bit of my tracker times when each value had to be manually entered as
> (hexa) text values :)
>
> Phil
>
> PS - My life in Qtractor is no longer the same since I know the
> shift-click trick. You know what would be cool? A continuous contextual
> status bar keyboard help (what, you don't have a CCSBKH? Sheesh ;)) like
> the one in Inkscape. If you decide to do it, I can help with filling in
> all the messages slots
>
wow! that was so quick and overwhelming that i've missed the whole
question :)
just a hunch: have you ever tried double-click on an automation node? ;)
hth.
cheers
--
rncbc aka. Rui Nuno Capela
|
