<div dir="ltr">Hi everybody,<div><br></div><div>Chris: </div><div>it is exactly as you said: <span style="font-size:12.8px"> </span><span style="font-size:12.8px">the higher the frequency the further to the right it is, and lower the frequency it goes to the left.</span></div><span style="font-size:12.8px">Where did you spot the mistake ? In the webpage of the analyser I am saying that :</span><div><span style="color:rgb(0,0,0);font-family:Verdana,serif;font-size:12px;line-height:19.2px;text-align:justify">the sonification is </span><b style="color:rgb(0,0,0);font-family:Verdana,serif;font-size:12px;line-height:19.2px;text-align:justify">panned from left to right</b><span style="color:rgb(0,0,0);font-family:Verdana,serif;font-size:12px;line-height:19.2px;text-align:justify"> and the panning represents </span><b style="color:rgb(0,0,0);font-family:Verdana,serif;font-size:12px;line-height:19.2px;text-align:justify">the position of the peaking frequency</b><span style="color:rgb(0,0,0);font-family:Verdana,serif;font-size:12px;line-height:19.2px;text-align:justify"> in the whole spectrum, ranging from 20 Hz on the very left, to 20050 Hz on the very right. For example, if the selected spectrum peaks at 50 Hz then you'll hear the beep towards the left, whereas if the peak is at 20 kHz the beep will occur towards the left.</span><span style="font-size:12.8px"><br></span><div><span style="font-size:12.8px">Maybe not the clearest way to put it but I think here we were on the same page. </span><br></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Also : it's not possible to have the sonification going through a different sound card than the sound being analysed. However you might find useful to play with the separate wet and dry parameters to go some way into that. </span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Hopes this is helpful. </span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Thank you for your feedback. </span></div><div><span style="font-size:12.8px">This project is now terminated so I am officially no longer working on this any more. </span></div><div><span style="font-size:12.8px">I know that for those of you who are not programmers it doesn't make much difference but we released the source code as well.</span></div><div><span style="font-size:12.8px">It's </span><span style="font-size:12.8px">linked from the web page of the plug-in </span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">all the best </span></div><div><span style="font-size:12.8px">Fiore </span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px"><br></span></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-03-03 8:08 GMT+00:00 Chris Belle <span dir="ltr"><<a href="mailto:cb1963@sbcglobal.net" target="_blank">cb1963@sbcglobal.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Well, the last point could be done by a time selection in your daw,<br>
and the table set to generate till the daw stops or something like that.<br>
Like a timed run of a specific portion.<br>
leave it to your brilliant mind to analyze and break all this down<br>
I like that table thing,<br>
and being able to change the resolution of what is analyzed would be great.<br>
I'm going to persevere with the current implementation and see what I can do with it.<br>
This is the first tool of it's kind I believe,<br>
we've had audio meters in hardware before, but it's nice now that the software ones are finally coming around to reality instead of just concept.<br>
I'm not a programmer, but in theory it shouldn't be hard to generate<br>
some kind of values which can be tied to text out-put,<br>
we'll never have it s good as being able to look at a graph, but it<br>
should be possible to link up something useful can you imagine as a programming guy how this might be done?<br>
YOu and this fellow would make a formidable programming team I bet.<br>
'grin'.<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
On 3/2/2016 2:20 PM, Snowman wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Well, here are my thoughts about this, for what it's worth.<br>
I find myself less able to make use of a real-time, dynamic audible output like this, especially while I'm also hearing the audio itself. But, also in general.<br>
To be honest, I wish this tool could generate a spectrum report, which would be a table of numbers describing a curve, showing how much peak, and average energy is in each frequency band, so you could study it, and learn where the peaks really reside.<br>
A constantly changing tone output has time delays associated with it, as you are aanalyzing the selection in real time. So, yeah, it takes a bit of concentration, especially for a partially tone deaf person, like me. I know, Not a musician any more. But, I still do audio production.<br>
If the tool would let me specify a bin size, maybe in hertz, or in octives, and the start and end frequencies of the spectrum I want to check out, much as it does now, except for the addition of the bin size. And then, produce a table of amplitudes, which generally show how much energy is in each bin, then I could understand what is actually going on.<br>
As it is, you have to violate the threshold before you get any indication that some coloration still exists.<br>
So, for example, I would specify start frequency, then width, or end frequency, and then bin size.<br>
So, Maybe I watch the area between 1k and 11khz, for a 10K total span, and I specify 100 hz bin size. so we divide the 10k span by the 0.1khz bin size, and then we generate 100 values. The first value represents the amount of energy in the span from 1k to 1.1khz. By inspecting that table, manually, or witt computerized aid, I can find out which bin has the most energy, even if it did not violate any threshold. From that, I can rather precisely tell where I am sharp.<br>
<br>
The last thin is to somehow identify the portion of a track, or file, that should be analyzed.<br>
<br>
Anyway, that is what I hope for. More of a static analysis tool, instead of a real-time dynamic tool.<br>
<br>
I don't claim that the current implementation doesn't have value. I think it does. I just wish for this additional static data output.<br>
<br>
----- Original Message ----- From: "Chris Belle" <<a href="mailto:cb1963@sbcglobal.net" target="_blank">cb1963@sbcglobal.net</a>><br>
To: "Reapers Without Peepers" <<a href="mailto:rwp@bluegrasspals.com" target="_blank">rwp@bluegrasspals.com</a>><br>
Sent: Wednesday, March 02, 2016 7:28 AM<br>
Subject: Re: [Rwp] Accessible spectrum analyser<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think there's some slight errors in the documentation,<br>
you said left when you meant right,<br>
or maybe I don't understand correctly, but<br>
the way I grasp it is that the tone goes up in pitch as the volume of the peak goes up, and the position of the sound in the<br>
pan field changes with frequency, the higher the frequency the further to the right it is, and lower the frequency it goes to the left.<br>
Is that right?<br>
<br>
And you can select the starting point, and the band width of the frequency range that is being tested.<br>
I'm curious,<br>
can the beeps be separated from the sound of the audio your testing?<br>
Right now the audio jumps around in the pan field as well, and that is rather disconcerting if you are trying to listen to it,<br>
and find a hot frequency spot as well as hearing the beeps.<br>
So if it's possible to unlink the audio and the beeps it might be easier to work with.<br>
Just a thought, it may not bother others.<br>
Thanks for working so hard on this.<br>
<br>
<br>
On 3/2/2016 6:40 AM, Fiore Martin wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
2016-03-02 10:49 GMT+00:00 Chris Belle <<a href="mailto:cb1963@sbcglobal.net" target="_blank">cb1963@sbcglobal.net</a> <mailto:<a href="mailto:cb1963@sbcglobal.net" target="_blank">cb1963@sbcglobal.net</a>>>:<br>
<br>
Hey this is wonderful.<br>
<br>
<br>
Thanks!<br>
<br>
You're the guy who also developed the accessible peak meter thing<br>
too right?<br>
<br>
<br>
That's right. In fact the spectrum analyser came from the idea of using the accessible peak meter's very sonification into the frequency domain.<br>
<br>
<br>
If you guys haven't gotten that tool, it's really useful as well.<br>
<br>
<br>
On 3/1/2016 9:44 AM, Fiore Martin wrote:<br>
<br>
Hi all,<br>
just to let you know the Accessible Spectrum Analyser VST/AU<br>
plug-in is now available online for free at<br>
<a href="http://depic.eecs.qmul.ac.uk/apm/spectrum.html" rel="noreferrer" target="_blank">http://depic.eecs.qmul.ac.uk/apm/spectrum.html</a><br>
<br>
Accessible Spectrum Analyser makes spectrograms accessible<br>
using non speech sound to supports core activities in audio<br>
production.<br>
The plug-in was developed as part of our research on<br>
accessibility and cross modal collaboration at Centre for<br>
Digital Music, Queen Mary University of London.<br>
<br>
More info on the web page linked above<br>
<br>
thank you<br>
all the best<br>
Fiore Martin<br>
<br>
<br>
_______________________________________________<br>
RWP mailing list<br>
<a href="mailto:RWP@bluegrasspals.com" target="_blank">RWP@bluegrasspals.com</a> <mailto:<a href="mailto:RWP@bluegrasspals.com" target="_blank">RWP@bluegrasspals.com</a>><br>
<a href="http://bluegrasspals.com/mailman/listinfo/rwp" rel="noreferrer" target="_blank">http://bluegrasspals.com/mailman/listinfo/rwp</a><br>
<br>
<br>
_______________________________________________<br>
RWP mailing list<br>
<a href="mailto:RWP@bluegrasspals.com" target="_blank">RWP@bluegrasspals.com</a> <mailto:<a href="mailto:RWP@bluegrasspals.com" target="_blank">RWP@bluegrasspals.com</a>><br>
<a href="http://bluegrasspals.com/mailman/listinfo/rwp" rel="noreferrer" target="_blank">http://bluegrasspals.com/mailman/listinfo/rwp</a><br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
RWP mailing list<br>
<a href="mailto:RWP@bluegrasspals.com" target="_blank">RWP@bluegrasspals.com</a><br>
<a href="http://bluegrasspals.com/mailman/listinfo/rwp" rel="noreferrer" target="_blank">http://bluegrasspals.com/mailman/listinfo/rwp</a><br>
</blockquote>
<br>
_______________________________________________<br>
RWP mailing list<br>
<a href="mailto:RWP@bluegrasspals.com" target="_blank">RWP@bluegrasspals.com</a><br>
<a href="http://bluegrasspals.com/mailman/listinfo/rwp" rel="noreferrer" target="_blank">http://bluegrasspals.com/mailman/listinfo/rwp</a><br>
<br>
</blockquote>
<br>
<br>
_______________________________________________<br>
RWP mailing list<br>
<a href="mailto:RWP@bluegrasspals.com" target="_blank">RWP@bluegrasspals.com</a><br>
<a href="http://bluegrasspals.com/mailman/listinfo/rwp" rel="noreferrer" target="_blank">http://bluegrasspals.com/mailman/listinfo/rwp</a><br>
<br>
</blockquote>
<br>
_______________________________________________<br>
RWP mailing list<br>
<a href="mailto:RWP@bluegrasspals.com" target="_blank">RWP@bluegrasspals.com</a><br>
<a href="http://bluegrasspals.com/mailman/listinfo/rwp" rel="noreferrer" target="_blank">http://bluegrasspals.com/mailman/listinfo/rwp</a><br>
</div></div></blockquote></div><br></div>