A Few Turntable Measurements using the RPM Android App


I found this Android phone app for TT rotation. Phone is Pixel 4a. Thought I'd try this app out. I'm skeptical of these phone apps. Accuracy is always an issue.

I have four tables. I took 5 readings for the first table in order to see what the repeatability is. The "absolute" RPM, RPM peak to peak, and 2 sigma  range readings were very, very repeatable. Consequtive RPM readings differed by a max of  0.01 RPM. Two sigma varied by 0.01% ( 2 sigma means that 86% of the readings were within the stated value). I personally would use 3 sigma, but that's a personal quibble.

I've measured all four of my tables. I am very certain that the results are very repeatable. I measured with no LP, LP rotating,  LP on and Stylus engaged, and phone offset from center. RPM was the same for all cases, The 2 sigma showed a  0.01% rise (really small). The reading at the edge of the LP was different. And scary to do!

Here's the results:

1. DD-40 #1, RPM = 33.32,  2 sigma = 0.07% (63 dB)

2. DD-40 #2, RPM = 33.27,  2 sigma = 0.09% (61 dB)

3. Acoustic Signature WOW XXL, RPM = 33.17,  2 sigma = 0.10% (60 dB). This varied 0.02% from reading to reading (after running the table for 10 minutes, this noise diminishes), but the 2 sigma stayed the same.

4. Denon DP-57L, RPM = 33.25,  2 sigma = 0.02% (74 dB).

 

I then went back to DD-40 #1. Using the RPM app, I set the mean speed to be 33.25. The strobe on the table was slowly moving! I checked against the strobe on the Cardas test LP and yes, the RPM speed accuracy was wrong. I reset TT speed using the strobe. The RPM app measured 33.23 again. I must conclude that although the RPM app is very repeatable, the absolute accuracy is not. The wow result (2 sigma variation) remains the same.

 

I measured the 45 RPM on DD-40 #1. RPM = 44.91, 2 sigma = 0.05%, so the 45 RPM is fairly accurate and the 2 sigma is lower.

 

This app makes no distinction between wow and flutter. It's all reported in the wow reading (wow and flutter are the same thing by nature, the only difference is the frequency range).

 

I'm surprised by the poor performance of the WOW XXL table. This a modern, belt driven table, with a massive platter. It is 5 years old. There's no way for the user to adjust the RPM. The variation in the speed is similar or slightly higher than the 40+ years old Micro Seiki DD-40 tables, which don't have crystal oscillator driven speed control. The WOW XXL takes about 10 minutes before the very high frequency variations settle. Now, I don't know much about the internal workings of the app. Helpful would be better accuracy (or the AC frequency in my house is not 60 Hz). Bandwidth is not reported.

The DP-57L performance is outstanding!. This TT was made in the 80s. And the DD-40 tables are not bad, but are as good as or better than the WOW XXL.

In summary, in my opinion, the RPM Android App is very useful. The absolute accuracy is a bit off, but the repeatability is very good The wow measurement is also quite good.

128x128Ag insider logo xs@2xkevemaher

Showing 7 responses by terry9

As is often the case, measurement is the issue. RPM is a continuous quantity only in the abstract. In all practical applications, it is an average. Maybe over a fraction of a millisecond, but that still is a far cry from continuous.

So the major issue, variations on the 10 - 20 KHz level, may be averaged out and not be addressed at all. Unless the specs indicate the time span over which the average is taken, the results don't mean much. As one of the greats from the glory days of audio once told me, "The best audio analyzer available is hardwired to your brain." (Jonas Miller)

I like the Nottingham sound too, which is why I built my air bearing with a 45Kg platter and a 1.8 watt motor.

@kevemaher  

With all due respect, keve, I think that you are putting the cart before the horse. Before one aggregates observations, one must make observations. The difficulty with making speed observations is that for practical purposes they must be averages: distance travelled divided by elapsed time. This is not an instantaneous quantity.

Even aggregating a finite number of observations implies discrete, not continuous. That means sampling frequency.

This is not a moot point because modern controllers tend to correct speed at about 10KHz. If it were easy, they would correct more frequently. I doubt that an app is better; in any case, it's important to quantify the limitations of the observations; in this case the granularity  imposed by sampling frequency.

Then one could aggregate the data into moments, from which the central moments of mean, standard deviation, skewness, kurtosis, etc. could be calculated, although perhaps a spectral or Fourier analysis would be more revealing.

There is no problem with the data arising from a process which is not perfectly random - it is data. The point at which randomness enters the picture is in identifying which inferences are valid, and which are not.

Yes, I think that speed stability is a problem. The question then is, "Which frequency?" I strongly suspect that most of the audible differences between turntables arise from small speed variations in the lower kilohertz range, which we hear as  brilliance or sibilance. It is obvious to suspect speed instability of causing this - but at greater frequencies than are usually measured. For example, bearing noise affecting speed.

By way of evidence, a common criticism of Nottingham turntables (high mass, low torque) is that they are 'dark', that is, without brilliance. I prefer the term 'smooth'. Also, that is how the bearing noise from my 1.8W motor manifests itself. Yes, it's repeatable.

As you point out, "Measuring performance parameters of instruments is crucial to product development." But unfortunately, associating numbers to phenomena is one of the most difficult human activities - doing it right, that is. It is therefore of cardinal importance to report the limitations of the measurement before reporting the results of the analysis. In my opinion.

@kevemaher I agree that wow, flutter, and rumble measurements are quantifiable and repeatable and agreed upon. I think, however, that this is not the whole story and that a 50KHz sampling rate would give us the data needed for a more robust analysis.

I think that both of you make good points.

For 40 years digital has claimed perfection, while getting better every year. It is still too bright for my ears, but an entire generation has been brought up to think that brighter is better. I have noticed that every major improvement to my system, US cleaning, reflex record clamp, Koetsu, air bearings, every one removed copious amounts of high frequency, yet after a few hours, it was obvious that the sound was closer to the concert hall.

So I concluded that what I was after was ’smooth’.

Raul talks about there being bright in a bad way and bright in a good way, which I also think is quite right. Mijostyn talks about this too.

Might both of you be referring to the leading and trailing edges of the signal? Electronically, this performance is dictated by odd-number harmonics (square wave Fourier Series). Unfortunately, distortion of the odd harmonics is notorious for being offensively bright.

I think that you are both onto something.

 

@kevemaher 

I refer you to a talk by Richard Krebs, and the considerations that went into his latest turntable design.

If you want to hear about higher order moments and their importance, though not in formal statistical terms, and the sampling frequencies required, please do take a look.

 

https://www.youtube.com/watch?v=smib6OJm-T8&t=2065s