A comment, or clarification: measurements are a means to an end, not an end in themselves.
When building something it can be very useful to measure certain parameters, in order to quantify progress in design changes, especially changes that might be below the threshold of audibility. Or it might also be useful to measure in order to discern what quantitative measures correlate with listener preference. Keith Herron for example once told me he believed people were sensitive to as little as 1/4dB in a certain circuit. This is far too low a level for anyone to identify as being louder or pick that out as the reason, they simply preferred one over another and only Keith knew the reason.
The takeaway, what I got from it anyway, was three-fold:
First, his testing was double-blind. So there is a use case even for this so often abused method.
Second, measurements can be essential. It was only by rigorously measuring output that he knew what it was his test subjects were hearing, or more precisely choosing between.
And third and most crucially, the end goal was listener preference. Not the measurement. The experience.
Say again, measurements are a means to an end. If you can keep this simple fact in mind any time you see anyone putting the cart before the horse, it can save you a whole lot of misery, wasted time, and money.
And now, at the risk of beating a now hopefully dead horse, I was not looking for a way of measuring cable vibrations to prove Cable Cradles work. Simply listen, it is obvious. I was looking for something that might help me figure out how to make them even better. There is always better. The proof is in the hearing. That is all.