Locking native filters and tweaking automation curves?

[flanneljammies]

Is there a way to lock native Tracktion filters? If there is, I can't find it. I suppose it's because they aren't floating like a VST's GUI is. While working with automation curves last night, I found it frustrating that the T reverb filter disappeared whenever I tried tweaking the wet-level curve. Why would I need it, you say? Because the values on the curve points aren't in the same units as the filter parameter (the curve shows 0.06 for example, but the wet level value is -15.68 dB).

So, even though I've never done it before, I'm thinking about FRs.
- Locking navtive T plugins (and I suppose that involves floating the GUI).
- Matching automation point values and filter parameters.
- Also, now that I think about it, how about a display of an automation curve's value when hovering or at least when selecting a point? (Right now, the only way to get the point's value is to acutally move it and sometimes all I want to do is to check it.)

[Samb]

You can lock anything in the properties panel by clicking on the little padlock next to the title (ie next to "reverb filter" in your case) and an automation point's value will be shown if you hover your mouse over it

[flanneljammies]

You can lock anything in the properties panel by clicking on the little padlock next to the title

hmmm... must've missed that. I'll take a peak.

an automation point's value will be shown if you hover your mouse over it

Not true; only if you actually move a point. This annoyed me in T1 too!

[Samb]

It definitely is true in version 2.0.1.13. I was sure it was, but I checked before replying to make sure and yes, both the time and value of the automation point will be displayed in a little speech bubble when you hover the mouse over the point.

[flanneljammies]

Maybe I'm just not hovering long enough?
...or I'm a dumb-ass ...or both. I'll check it out.

[flanneljammies]

OK, so I'm a dumb-ass. Locking the context window is easy. yay! The automation points do indeed show the value when hovering! So... the only issue is the mismatch between the automation values and the actual parameter values. BTW: thanks Samb.