<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 28/07/2015 2:36 AM, Patrick Perdue via RWP wrote:<br>
<blockquote cite="mid:55B65E25.4050902@pdaudio.net" type="cite">Yes,
although I still prefer ReaAccess's metering, as you get a very
discrete VU and peak,</blockquote>
I assume you mean you want peak holding reported separately from
just the current level? I guess I didn't implement this originally
because by the time you hear the level, that time in the audio has
well and truly past; it will never be realtime due to the linear
nature of speech. <br>
<blockquote cite="mid:55B65E25.4050902@pdaudio.net" type="cite">and
you can also see more than just channels 1/2 if needed.</blockquote>
Adding support for more channels should be relatively trivial. I
just don't have a good test case for this. IIRC, ReaAccess only
supported 4 channels, but if I'm not mistaken, you're suggesting
there may actually be a need for more. The question is how many.<br>
<br>
As always, if you want stuff done, <a
href="https://github.com/nvaccess/osara/issues">file an issue on
GitHub</a><a href="https://github.com/nvaccess/osara/issues">,
including use cases, etc.</a><br>
<br>
Jamie<br>
<br>
<pre class="moz-signature" cols="72">--
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
<a class="moz-txt-link-abbreviated" href="http://www.nvaccess.org">www.nvaccess.org</a>
Facebook: <a class="moz-txt-link-freetext" href="http://www.facebook.com/NVAccess">http://www.facebook.com/NVAccess</a>
Twitter: @NVAccess
SIP: <a class="moz-txt-link-abbreviated" href="mailto:jamie@nvaccess.org">jamie@nvaccess.org</a>
</pre>
</body>
</html>