<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><div style="direction: ltr;">Hello</div><div style="direction: ltr;">i think reaAccess is getting sleepy and wouldn't be used a lot in the few month</div><div style="direction: ltr;">lot of People is switching to OSARA, writen by NVAccess the company responcible for the NVDA screen reader</div><div style="direction: ltr;">would you mind trying it out?</div><div style="direction: ltr;">please note that OSARA plugin would require the SWS reaper extention</div><div style="direction: ltr;">thanks</div><div style="direction: ltr;"><br></div><br>Envoyé de mon iPad</div><div><br>Le 22 janv. 2016 à 12:57, Fiore Martin <<a href="mailto:mister.bloom@gmail.com">mister.bloom@gmail.com</a>> a écrit :<br><br></div><blockquote type="cite"><div><div dir="ltr">Hi all, <div><br></div><div>Does anybody know where I can get a copy of ReaAccess for windows ? The domain of the website seems to be expired.</div><div><br></div><div>By the way, the reason I need it is to test a plug-in I am working on at Queen Mary University of London called Accessible Spectrum Analyser, which sonifies frequency spectra</div><div>in order to make them accessible. </div><div><br></div><div>more info and link to the first prototype below and if you'd like to give some feedback, I am all ears</div><div><br></div><div>thank you </div><div>Fiore </div><div><br></div><div><br></div><div><br></div><div>Links for plug-in download:</div><div><br></div><div><div><a href="http://depic.eecs.qmul.ac.uk/sites/depic.eecs.qmul.ac.uk/files/AccessibleSpectrumAnalyser_draft1_32bit.dll">VST plugin 32 bit for Windows</a></div><div><br></div><div><a href="http://depic.eecs.qmul.ac.uk/sites/depic.eecs.qmul.ac.uk/files/AccessibleSpectrumAnalyser_draft1_64bit.dll">VST plugin 64 bit for Windows </a></div><div><br></div><div><a href="http://depic.eecs.qmul.ac.uk/?q=system/files/AccessibleSpectrumAnalyser.component.zip">AU plugin for Mac</a>, drop it in /Library/Audio/Plug-ins/Components</div><div><br></div><div>Usage:</div><div><br></div><div>You can select the range of frequencies you want to monitor by setting selection-start and selection-size parameters. </div><div>For example if you'd like to monitor the frequencies from 20Hz to 1Khz, you want to set selection start to 20Hz and selection size to 1880Hz </div><div>So once the selection size is set, by moving the selection start parameter, you can scan the whole spectrum from low frequencies to high frequencies. </div><div><br></div><div>Then to activate the sonification, you want to tweak the threshold parameter: when any of the frequencies in the selection goes above the threshold, the plug-in will beep at 440Hz plus one semitone per db of difference between the frequency component and the threshold. </div><div>For instance if your audio has one frequency component whose magnitude is -3db and you set your threshold at -2db you will hear an A#, which is given by 440Hz (A) plus one semitone for the 1 db difference.</div><div><br></div><div>at the moment only the frequency component with the biggest magnitude in the selection is taken into account for the sonification </div><div><br></div><div>dry and wet parameters are for volumes of the original audio and the sonification respectively. </div><div><br></div><div><br></div><div>And now some questions if you'd like to answer any of them : </div><div><br></div><div>1) would you find this plug-in useful ? </div><div><br></div><div>2) would you prefer to have some indication in the sonification of where the selection is in the total spectral range. For example I could use panning </div><div>to indicate if the selection and hence the sonified frequency components are towards the low end of the spectrum or the high end. </div><div>However this information might be redundant since you set the selection yourselves and you know already where it is? </div><div>Another option could be to use panning to give information about the location of the peaking frequency components within the selection. </div><div><br></div><div>3) would you prefer to have the sound of all the frequency components passing the threshold in the selection rather than the biggest ? </div><div>In this case the sound would be made out of a lot of sine waves with different pitch (one per component) and obviously the pitch would no longer be linked to the difference with the threshold. I am afraid this would turn out to be quite noisy though.</div><div><br></div><div>4) how easy/hard is it for you to handle parameters which such a big range like the selection start going from 20 to 20.000 ? </div><div><br></div><div>5) Would you prefer to have a selection-end parameter rather than selection-size or doesn't really matter ?</div><div><br></div><div>Thanks</div><div>Fiore</div></div><div><br></div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>RWP mailing list</span><br><span><a href="mailto:RWP@bluegrasspals.com">RWP@bluegrasspals.com</a></span><br><span><a href="http://bluegrasspals.com/mailman/listinfo/rwp">http://bluegrasspals.com/mailman/listinfo/rwp</a></span><br></div></blockquote></body></html>