I like the idea too!! But it would be hard to distinguish the exact spot where the tip hit the CB and the exact spot where the cb hit the pack i would think. Also, it is hard to measure such a small length of time. You would have to try it though, who knows, maybe there is a definite high spike for each moment of impact. Sound like a sweet idea, i wanna see the VB app. Do you think you would need a high quality microphone to distinguish between exact contact moments? Do you think it would help?
Thunk.... Crack... MPH
- Thread starter Billiard Architect
- Start date
F
Fred Agnir
Guest
whitewolf said:
Wouldn't the time delay simply cancel out since there would be two distinct peaks and the measurement would be peak to peak?
Even if someone did the measurement and didn't put the sound recorder equidistant, the result would max out at under 0.5% "error" due to the speed of sound. Not bad for a quick measurement.
Fred
whitewolf said:
Well, for sure I am not a Civil Engineer ... I am an Electrical Engineer
The timing error to which I refer is contained in the timing mechanism itself, the PC. If the PC's real time clock is running fast or slow, the time measurement will be wrong, as will the calculated speed. Then there is the issue of resolution. It would not do much good if the PC can accurately time to 1/10 of a second, you'd need about 5/1000 of a second resolution to get an error of about 1% in the final answer (notwithstanding the error introduced by the ball placement).
As far as deciding at what point the tip hits the CB and at what point the CB hits the OB, I think one should be able to define them fairly accurately in any reasonable graphical view of the sound. This statement is based on some limited exposure to Pro Tools, which is a high end digital audio recording and post-production system. I'll have to look at the software mentioned, it too may be precise enough ... assuming the original time source is up to the task.
Dave