ScottChesworth
ScottChesworth
I seem to remember @jscholes rustled up a working implementation of this a while back. Think he wanted to clean up the code before submitting. Did you ever get around...
Thanks for the code @jscholes. Most of that goes over my head, but from what I remember it seemed to be working well when I tried your test build here....
I turn track numbers off here, but hearing numbers being included with a range report wouldn't be a problem. If anything, I'd say it adds useful context, gives you a...
Confusing how, @jcsteh? I don't use Peak Watcher much here, so weight my input accordingly. My initial hunch is that global settings would likely be the first thing to get...
> I think some really solid thought needs to be put into the actual user experience with all of these ideas. > When you lay it out like that, agreed....
I like your proposed UX, but given that it sounds like implementing per project settings will be a lot of work as things stand, what about just introducing the "Save...
Hey @mespotine, good to see you showing up here! We've chatted a bit on the forum, I'm scottsdale over there. @jcsteh, I've labeled this P1 because other scripters have also...
we've not had a milestone version yet. Talked about it a few times, but I'm always worried about it discouraging adoption.
Should think we can get this situation improved in Reaper itself. I'll ask Cockos what changed as a starting point.
> I think we're going to need an alternative way to access this. > Maybe Cockos could include it for each effect in the window title? Easy to read when...