The W&F numbers for both tables are typical of belt/idler drive, but speed accuracy is more problematic. The Holbo has a DC motor which has a negative torque/speed curve
Yes. I posted here for several reasons.
One was to provide a data point (I cannot personally detect wow and flutter with my tables). Maybe that's two data points.
With a plethora of standards and measures within those standards, just quoting a number is pretty meaningless unless you also quote the standard and the measure. I was impressed with the way Garrard describe exactly what their measurements involved, and that they individually test every 301.
As I mentioned, the Holbo is pretty much a black box to me - two black boxes if you count the power / air supply box. There is a four-wire cable from the power / air supply box which powers a DC Japanese motor (about 4-Watts) and transmits switching information, at the very least to tell the power supply when to switch on, and that the turntable has been switched off.
Garrard goes to great lengths to allow speed accuracy to be observed and corrected via a big front knob which adjusts its eddy inducing magnet. The feedback loop is via the operator and big strobe markings cast into the rim, though. In my experience it hardly ever needs adjusting.
Another reason behind my post was to suggest that wow and flutter can be measured and reported separately. When these measures are combined, the same number could arise from low wow and high flutter, or high wow and low flutter. There are unlikely to be equally annoying.
The various standards have differing filter curves, presumably to prevent rumble from affecting the flutter results, and long-term instability from affecting the wow results. The separation of wow and flutter is at 4-Hz, as far as I know, and the curves are designed to reflect human sensitivity. Most tests last only a second - you can't get a long-term speed stability measure in that timeframe.
At first glance, a wow and flutter measure seems to tell a casual observer the % range which a turntable's speed variation won't exceed. Unfortunately there is much more to the standards than meets the ear ![]()

