If you could share an audio file to browse we may be able to offer help.
-
Take part in a short activity and share your valuable opinion on new design concepts for AVSForum! >>> Click Here
Open source timing software.
Hi guys,
I have a more or less usable version of my timing program that is ready
for initial testing, if anyone is interested.
First the goodies. Here are Windows binaries
http://ciovil.li/tg.zip
and here is the full source code
https://github.com/vacaboja/tg
Now some info on the program. This program is released under the GNU GPL
license, version 2 -- basically you can do what you want with it, free of
charge, no warranty, if you redistribute a (modified) version, you must
distribute also the source code. If you want to build from source, you
need gtk+ (I'm using v. 2.24), portaudio2, and fftw3, plus a C99 compiler
clearly. If you want to run the Windows version, just download the zip
archive, unzip, double click.
This program tries to pick up audio from the default audio input of your
computer, which should be the same that Audacity defaults to, so you can
test the audio setup with Audacity. It does not fiddle with the volume:
just check that it is set to a reasonable level. Of course the rate that
you get from this program, for any watch, is affected by the rate of the
clock of your sound card: the same holds for all timing programs and there
is no escape (except calibrating the card against a reliable time source).
The algorithm I decided to use is quite hungry of computing power, so I
made two versions: "tg" is the full version, "tg-lt" is a lighter version.
The light version sacrifices some accuracy and noise resilience for speed.
My intended audience is amateurs and tinkerers. This program has not been
written for professionals, neither do I want to compete with
professionally built hardware or software, nor with those that can write
better software on their own. In particular I have set to myself the
following three goals.
One. Try a less conventional algorithm to deal with bad audio, at the
expense of lots of number crunching (all other programs for which I did
find information online use possibly some band pass filter and a threshold
trigger, we do it differently). I can currently obtain satisfactory
results from the internal mic of my ThinkPad and a few other lower quality
mics. I don't know how it will perform with a good piezo, but I am
interested (probably, for clean audio, mine is not the best approach).
Your mileage may vary.
Two. To avoid complaints like this one
Review: TickoPrint Android App | Watch Guy
the entire operation of the algorithm is designed to be double-checkable.
In particular, the waveforms that the program associates to the tics and
tocs of the watch are shown in real time, so one can check that they are
properly recognized and properly aligned. The slope representing the
currently detected instantaneous rate is drawn (the blue lines) on the
timing-machine-like graph, etc. See also the discussion here for some
example of such double checking
https://www.watchuseek.com/f6/definition-beat-error-2394130.html
Three. Make it open source, so other people can tinker with the source
code (well, this one was the easy part).
Usage should be quite intuitive for those that know how an escapement
works. See also the thread referenced above for more info.
That's all for now. Any feedback is appreciated.
401 - 420 of 605 Posts
Anyone having problems measuring a rolex because of the chiming echoe sound of the movement ?
I pass the sound via Ableton to EQ it a bit but its a bit jumpy. My Omega is way easier and clean (sound).
I use a guitar piezo for tuning etc. Via a mixer with dedicated Mic input.
Some of my watches suffer from this problem also. I think the culprit is mostly the echoing from your case/movement ring/caseback.If you could share an audio file to browse we may be able to offer help.
Also it's possible that if you are using a standard piezo disk, it it deformed from the force of your watch crown and the audio signal is distorted.
https://reparacionderelojes.weebly....2213567/manual_for_tg_timming_machine_2.3.pdfI am having problems getting the program up and running properly. I am on Fedora 27. I used git to download the source and compiled it with no problems. I can run the "tg-timer" which seems to work fine with a logitech webcam microphone -- I have no problems picking up data from any of my mechanical watches using the logitech webcam.
View attachment 13292807
My problem is that I cannot get the software to calibrate.
I am attempting to calibrate by placing the webcam mic on one of my quartz watches. When I attempt to calibrate by checking the "calibrate" box in the upper right menu. the software responds by displaying the red clock and the "cal (wait) 0%" comments. Occasionally (rarely) the clock will turn green for a moment and the dialog will report "cal (acq) 0%" but then immediately goes back to "cal (wait 0%)" and nothing else ever happens. The calibration procedure is never completed.
Unfortunately, the "documentation" in the earlier post doesn't really explain what is supposed to be happening or what these cryptic comments mean, or how to troubleshoot if the system fails. That lack of disclosure makes it impossible to debug the failed calibration procedure.
by any chance is there a debug mode in which additional status information is displayed? or additional documentation somewhere that better explains the calibration procedure?
thanks.
It is important that the software clearly hear the ticking of the step-by-step motor of the quartz watch. When the indicator clock changes from green to red, it is indicating that the reference sound is not good. It is best to use a piezoelectric contact microphone, as this neutralizes any ambient sound.
not sure which version I need, 0.5.0 or 0.4.0 ? Assuming the 0.4.0 is still there for a reason (some advantage or preference over 0.5.0?) Any advice for a newbie to this application
Personally I prefer version 4 In a sense it seems more consistent. However, it may be due to how I use the software. Any of the 2 is excellent.
Here the difference between the versions. I like the paper strip simulation of version 4 more. The points look less scattered.
sorry to take so long to reply (hope you've solved the problem)... i use nothing special except a usb logitech webcam for the mic input (selected via Apple->System Preferences->Sound->Input)Did you do any changes in your mac other than switching to an external microphone as the input? I've tried using both a piezo mic and a Røde M3 mic and I can't get any readings in TG at all... I'm using a Steinberg UR22 connected to my mac and it seems that both mics are connecting and is giving audio (I can record the ticking fine in Logic), but nothing happens in TG timer. I've already calibrated with a quartz watch from the internal mic, but the program just won't pick up anything with external mics.
TIA
hth
willie
on the Gulf of Mexico
I realize that I am late to the party but I just saw this thread. First, I want to extend a thanks to the OP for putting so much time and effort into creating this software. I have not yet downloaded it and I have a question. Do I just need a microphone in addition to the software? I have a webcam that is on a movable arm and not built into my desktop. I'm not sure if the arm is strong enough to hold the weight of my larger watches. Any advice on how to place the camera/watch in different positions for testing? Should I consider buying a separate microphone? Does the software enable the mic or must you use the camera software, in my case Logitech. Thank you!
alas, although 0.4.0 and 0.5.0 both build under the latest Raspbian Buster distro on the Raspberry Pi, the code fails with errors in sound values during calls to ALSA libraries and code... i have been unable to effect a fix...
fortunately i still have an RPi with Raspbian Jessie installed - both 0.4.0 and 0.5.0 run fine on that distro version... i'll just keep backups until the issue can be sorted...
it would be great if tg-timer could get into the Raspbian repositories...
willie
on the Gulf of Mexico
fortunately i still have an RPi with Raspbian Jessie installed - both 0.4.0 and 0.5.0 run fine on that distro version... i'll just keep backups until the issue can be sorted...
it would be great if tg-timer could get into the Raspbian repositories...
willie
on the Gulf of Mexico
i will keep working on the issue, but frankly, don't have that deep-level expertise - i did get successful builds, which makes this frustrating...
I have just started to use this great program, and thank you for that OP! I am trying to figure out the best way to use it. I read about calibration and a bit about the sound cards but it is unclear, at least to me. I actually don't have any quartz watches so maybe there is another way? Below is what I'm running. Any help would be appreciated.
* Acer Desktop PC (unsure of the model)
* Intel Core i5-4590 CPU 3.3GHz
* 8 GB RAM
* Windows 10 Pro 64-bit OS
* Build in sound card
* Realtek Audio (soundcard?, software?, I don't know)
* Steelseries Headset
* Logitech HD Pro Webcam C920 (current default)
When I launch the program, it struggles to provide readings. If I hold the watch against the camera firmly, it reads for a few seconds but then jumps all over the place. When I leave it alone, sometimes it gives expected results but only briefly. The rest of the time everything is off the charts. To me, it looks like it's not able to pick up a steady stream of sound but I don't know. I have tried with both microphones with approximately the same results.
I do have a Witschi knock-off timegrapher that I use to regulate movements but I would love to switch to this system! Thank you again OP and WUS contributors!
* Acer Desktop PC (unsure of the model)
* Intel Core i5-4590 CPU 3.3GHz
* 8 GB RAM
* Windows 10 Pro 64-bit OS
* Build in sound card
* Realtek Audio (soundcard?, software?, I don't know)
* Steelseries Headset
* Logitech HD Pro Webcam C920 (current default)
When I launch the program, it struggles to provide readings. If I hold the watch against the camera firmly, it reads for a few seconds but then jumps all over the place. When I leave it alone, sometimes it gives expected results but only briefly. The rest of the time everything is off the charts. To me, it looks like it's not able to pick up a steady stream of sound but I don't know. I have tried with both microphones with approximately the same results.
I do have a Witschi knock-off timegrapher that I use to regulate movements but I would love to switch to this system! Thank you again OP and WUS contributors!
Sorry double post
GratisShark
have a look, if you can raise/adjust the input level of your microphone with Realtek Audio avoiding excessive hum at the same time prior to calibration. Give it a try with and without noise reduction and echo repression. For my setup both deactivated works best.
Re the availability of a quartz watch: next weekend is comming soon. Go out and ask somone "vintage enough" wearing a quartz watch instead of some smart gear, if - presumably she - is willing to give you a hand calibrating.
Be aware: a brandnew original Witschi might turn out less expensive over time :-d
Klaus
have a look, if you can raise/adjust the input level of your microphone with Realtek Audio avoiding excessive hum at the same time prior to calibration. Give it a try with and without noise reduction and echo repression. For my setup both deactivated works best.
Re the availability of a quartz watch: next weekend is comming soon. Go out and ask somone "vintage enough" wearing a quartz watch instead of some smart gear, if - presumably she - is willing to give you a hand calibrating.
Be aware: a brandnew original Witschi might turn out less expensive over time :-d
Klaus
Thank you for the suggestions Klaus Tickalot! I will try to play with the microphone settings. Maybe I'm missing something on your last sentence but what do you mean by a Witschi being less expensive over time? I have been contemplating buying one but the price has kept me from doing so.GratisShark
have a look, if you can raise/adjust the input level of your microphone with Realtek Audio avoiding excessive hum at the same time prior to calibration. Give it a try with and without noise reduction and echo repression. For my setup both deactivated works best.
Re the availability of a quartz watch: next weekend is comming soon. Go out and ask somone "vintage enough" wearing a quartz watch instead of some smart gear, if - presumably she - is willing to give you a hand calibrating.
Be aware: a brandnew original Witschi might turn out less expensive over time :-d
Klaus
Thank you for the suggestions Klaus Tickalot! I will try to play with the microphone settings. Maybe I'm missing something on your last sentence but what do you mean by a Witschi being less expensive over time? I have been contemplating buying one but the price has kept me from doing so.GratisShark
have a look, if you can raise/adjust the input level of your microphone with Realtek Audio avoiding excessive hum at the same time prior to calibration. Give it a try with and without noise reduction and echo repression. For my setup both deactivated works best.
Re the availability of a quartz watch: next weekend is comming soon. Go out and ask somone "vintage enough" wearing a quartz watch instead of some smart gear, if - presumably she - is willing to give you a hand calibrating.
Be aware: a brandnew original Witschi might turn out less expensive over time :-d
Klaus
Hi guys,
I have a problem with interpreting this graphs. I have two different amplitude readings. Which one is correct - 167deg or 307deg ?
View attachment 14392927
![Text Line Technology Font Parallel]()
I have a problem with interpreting this graphs. I have two different amplitude readings. Which one is correct - 167deg or 307deg ?
View attachment 14392927
Hi jackie01,
Short version: neither nor
Long version: I reckon the lift-angle of 39° isn't set correct for a 28.800 bph movement (if it isn't a co-axial). Try with 52°.
But even then you will get a poor amplitude of about 222°. A good clean and fresh oil will help, in particular escapement i.e. pallet stones and escape wheel.
At least in your first graph with 167° all three sounds have been detected, witch is "less wrong"
Tg0.5.0 isn't co-axial capable as far as I know.
Which movement did you test?
Klaus
Short version: neither nor
Long version: I reckon the lift-angle of 39° isn't set correct for a 28.800 bph movement (if it isn't a co-axial). Try with 52°.
But even then you will get a poor amplitude of about 222°. A good clean and fresh oil will help, in particular escapement i.e. pallet stones and escape wheel.
At least in your first graph with 167° all three sounds have been detected, witch is "less wrong"
Tg0.5.0 isn't co-axial capable as far as I know.
Which movement did you test?
Klaus
Hello Klaus. Thanks You for reply. I test a Citizen 8110A and i found 39deg lift angel for this movement somewhere. I will try 52.
Edit: Yeah You're right - with 52deg lift angel I have something about 225-230deg of amplitude.
![Text Line Font Technology Diagram]()
I am waiting for new piezo mic for the timegrapher. Now I use build-in notebook mic so i think that measurments don't be accurate now.
Edit: Yeah You're right - with 52deg lift angel I have something about 225-230deg of amplitude.
I am waiting for new piezo mic for the timegrapher. Now I use build-in notebook mic so i think that measurments don't be accurate now.
401 - 420 of 605 Posts
WatchUSeek Watch Forums
A forum community dedicated to watch owners and enthusiasts. Come join the discussion about watch collections, displays, watch winders, accessories, classifieds, and more! We welcome all manufacturers including Casio G-Shock, OMEGA, Rolex, Breitling, Rolex and Tudor, Seiko, Grand Seiko and others.
Full Forum Listing
Top Contributors this Month
View All
Russ1965
3087 Replies
Nokie
1474 Replies
bigclive2011
1225 Replies
Recommended Communities
