Web-based Real Time Tuning Analysis (RTTA) Tuner

Whistle
1

Having my Chromatic Tuner now working nicely, I realized it was a simple and obvious task to leverage the same code base to do this:

This tool can be used to check the pitch of an instrument across its entire range, as well as for checking how well you play in tune.

It should also work on phones and tablets as well as desktops but it can be a lot of data to show on a small screen.

This tool was inspired by Terry McGee’s original Tartini-R Polygraph RTTA tool at:

My simple web-based chromatic tuner is available here:

or can be launched from the bottom of the ☰ menu in my ABC Transcription Tools.

Demo video:

2

Wow ! Totally impressive + useful.

Question: where are the tone-extraction calcs done ? Locally (browser-daughter) ? Remotely ?

thanks very much,

trill

3

Wow, that is stunning Michael! I’ve not spent long with it, but it seems pretty straightforward to use.

The only thought I have at this stage is how can I save a graph once I have created it? For example, I’ve just graphed the RTTA of a Killarney whistle, and I’d like to be able to give it a name and save it as say: Killarney Whistle RTTA. How do I best do that, preferably on my phone, as it’s great to be able to do this on a portable device!

(P.S. please excuse us 78 Year Olds trying to keep up with you young folk!)

4

I’ve updated the Chromatic Tuner and Real Time Tuning Analysis (RTTA) tool to now support both Equal Temperament and Just Intonation (with selectable root note).

The Chromatic Tuner is at:

https://michaeleskin.com/abctools/tuner.html

The Real Time Tuning Analysis (RTTA) tool is at:

https://michaeleskin.com/abctools/rtta.html

If you use the ABC Transcription Tools, both of these utilities are part of the offline cache, so to pick up the new versions, you’ll need to update to the latest version of the tool:

3152_012126_1800

The version number is displayed at the bottom left of the “Settings” dialog in the standard editor.

If your version starts with a number less than 3152, click the version number to do a manual update of the tool then do a hard refresh of the page.

5

Best bet on a phone might be to simply take a screen shot.

On both desktop and mobile browsers you can print to PDF.

Best results using Landscape as the print orientation.

Here is how you’d do it on an iPhone, would be a similar process on iPad.

In mobile Safari, click “Share”. In the sharing pane, scroll down a bit and click “Print”

On the “Options” pane for printing there is another “Share” button that will allow to save a PDF, email it, or transfer it to another iOS app.

Screen capture of the process:

6

All the processing is done in Javascript locally in the browser for both the Chromatic Tuner and the Real Time Tuning Analysis tool. There are no servers involved at all.

If you use my ABC Transcription Tools, with the latest update both tools get installed in the offline asset cache and will run offline.

The source code is in my GitHub repo, link to it at the bottom of the Instructions dialog (click the ? at the top left of the tool).

7

Wonderful, thanks for the additions! This will really come in handy.

8

Thanks very much . :slightly_smiling_face:

9

Hi Terry!

I’ve added the ability to save the RTTA graph as a JPEG file with a new download button at the lower right of the graph area.

On mobile devices, you’ll want to rotate the device to Landscape orientation before doing the export to get the best results.

Here are simplified links to the latest versions of my Chromatic Tuner and Real Time Tuning Analysis (RTTA) tools:

Chromatic Tuner

Real Time Tuning Analysis (RTTA)

10

Also added Pause/Resume to the RTTA.

11

Very good, Michael! I did try the screenshot method, but it’s a bit tedious. But the Save button is fabulous.

As is the Pause/Resume button. I’d found the need for that too!

13

Yes, I was demonstrating for my wife and when I’d talk, it would pick up my voice. That’s when I decided it needed a pause/resume button ASAP.

I can easily imagine someone taking some readings, pausing the tool, making some adjustments, resuming the tool, rinse and repeat.

14

Ha ha, I had a similar experience. Halfway through assembling an RTTA, the phone rang and I answered it. As we talked on the phone I realised I was racking up spurious data.

And yes, I can visualise starting an RTTA, pausing to check it was going OK, and then resuming to fill out any missed parts of the spectrum.

Now, when you find yourself really bored one evening, you could add another text-only output, that renders the data into a really simple list, such as below…

D5: +12

E5: +7

F#5: -13

G5: +2

Etc, etc, up to the highest note recorded, and perhaps then ending in a summary, eg:

Sharpest: D5, +12

Flattest: F#5, -13

Mean:

Any other calculated results?

Hmmm, not really sure the summary is needed! The advantage of the very simple list is how economic of space it is. And how easy to pop into a spreadsheet for any further processing. Hmmm, separating the note name and value with a tab would probably make it easier to add to a spreadsheet? And how to save it? A simple text file?

But no need to rush on that one. Just if you get bored….

15

Actually, I originally envisioned a CSV export option, but decided that the graph was probably more generally useful. I’ll give it some thought and see what I can come up with.

I’m heading out Saturday on trip for several days, will be back on Jan 28th so there may be a few days with no updates to the tool.

16

OK, it was easy to add a CSV export button along with the JPEG export.

The raw data looks like this with the note name and median cents offset value for each sampled note:

Note,MedianCents
G4,34.1
D5,-3.0
E5,-0.4
F#5,18.1
G5,7.3
A5,-14.6
B5,10.6
C6,-12.0
D6,8.5
E6,-2.2
F#6,16.8
G6,5.0

and appears like this if opened in a spreadsheet:

image
image368×824 51.7 KB

17

Stunning, Michael, well done!

Now I have no more excuses, and will have to go back to making improvements to my whistles…

18

I tried the RTTA, it was slow at picking up the pitches, I had to hold a note a while before it read it.

Then after the initial reading it froze on most notes, but still tracked a couple, until it froze altogether.

I’m guessing my mic doesn’t have a strong enough input. The low octave of a Low D Whistle isn’t very loud.

I’ll try an uilleann chanter later- my wife works from home :frowning:

19

Ah, I had the same experience when I tried to do an RTTA of my Killarney whistle. I cranked the level up +12dB using the Input Level Adjustment box near the top of the App and it suddenly worked fine.

20

Thanks Terry! I thought that might be what was happening.

21

Messing around with the RTTA reminded me how much the volume levels on whistles vary between highest and lowest notes, so much more than on flutes. I closed the door and windows so as not to antagonise the neighbours on those high B notes!

So it then occurred to me that as well as trying to optimise tuning, we whistle fiddlers should also be looking to minimising level difference across the range.

So then it occurred to me we would also benefit from RTLA - Real Time Level Analysis. (Yeah, I made that term up too, just like RTTA!). Then I wondered if there was such a thing, but couldn’t bring it immediately to mind. I have a Sound Level meter, but taking down all the data is the same issue that led to the RTTA concept.

And then I thought, I wonder if the RTTA could also collect sound level data? And how would you present it? A separate graph? Another column in the CSV file?

And what would you take as reference? Would be nice to have it in absolute dBA terms but that’s probably not so easy. But perhaps not so important.

Anyway, enough to float the notion. That’s probably enough to have Michael cowering under his bed, hoping I’ll go away!

Feel free to dismiss this as the ravings of a lunatic, or technically unfeasible, or whatever. Or point me to something that already achieves the same goal!