[Rwp] Using envelope points with ReaAccess

[James Teh]

On 24/12/2015 4:57 AM, Scott Chesworth wrote:
> It does, thanks man. Metering is definitely something I need to talk
> with Jamie about.
Sorry to be grumpy about this, but honestly, people have been saying 
stuff like "OSARA needs better metering" or "I need to get around to 
filing an issuea bout metering" for months now and not one person has 
provided any useful information. I can just copy ReaAccess, but IMO, 
it's not entirely intuitive, nor can you configure holding of peaks 
which can be really useful. I need use cases. What do you need and why 
do you need it? How would you expect it to work?

This is kind of true across the board. I see comments like "OSARA 
doesn't quite do what I need yet" without a scrap of useful info. 
There's also not much time left as far as funding is concerned. I have 
to start being fairly picky about what I implement now; I've already 
done significantly more work than we budgeted for. (It seems I 
underestimated the work required.)

I've said this before and I'll say it again: if you want something, file 
it on GitHub. If you don't file it, it will not get implemented.

> In theory, OSARA can do multi presses, it's already
> being used to read position information, but I can't honestly say that
> I'm a huge fan of the concept personally.
While multi-press does certainly save keys, there are a few downsides:
1. If you make it entirely customisable, there is always a small delay 
before every press, as it has to wait for a possible subsequent press. 
This makes things feel sluggish. Sluggishness makes the user experience 
less pleasant. It can be rather subconscious; for some users, it will 
just feel "crappy" without them being able to pinpoint why.
2. When abused, it is ridiculously counter-intuitive. We want to make 
things efficient for users, but I also don't think everything should be 
geared towards the power user who is willing to spend hours figuring 
everything out.
3. If you want full customisation, it also can't be integrated nicely 
into REAPER's own action configuration. That means users have to deal 
with two ways to configure bindings.
4. It's not necessarily more efficient. Pressing 1 three times to go to 
marker 21 and waiting the small delay noted above is not much more 
efficient than control+j, m21, enter... and the latter is a hell of a 
lot more intuitive and less error prone.
5. Once you get past two or three presses, there is a high potential for 
error.

I'm happy to use it for specific actions where we don't have to wait for 
the second press. To do that, earlier presses cannot do something which 
will adversely affect later presses; e.g. first press might report, 
second press might select, third press might delete, but we could never 
have the first press delete.

Jamie

-- 
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: jamie at nvaccess.org