[LIST=1] [*]sudo apt-get install libgtk2.0-dev # install first of several various packages needed for compilation [*]sudo apt-get install libjack-jackd2-dev # the order of installation is important [*]sudo apt-get install portaudio19-dev # because libjack must be installed before portaudio [*]sudo apt-get install libfftw3-dev [*]sudo apt-get install git # if you don't have git, this is just for downloading the source, which you might prefer doing directly [*]cd # go to home directory [*]git clone [EMAIL="[email protected]:vacaboja/tg.git"][email protected]:vacaboja/tg.git[/EMAIL] # this downloads the source from [URL]https://github.com/vacaboja/tg[/URL] [*]cd tg # change directory to location of source code [*]make # build the program [*]./tg # run it! [/LIST]
This is expected because tg currently doesn't have a calibration option. PC sound cards are usually not exact enough, and will give more or less invalid results. However, the error rate is always stable. In your case it seems to be about 4 sec/day. Once tg implements the ability to adjust the rate calculations, it should match up perfectly.I'd like to explicitly note that tg consistently gives a reading of +4s/d higher than the Ace Timer. It may vary from +3 to +5, but after stabilization it always settles in around that same difference. That's a clue to something though I'm not sure what.
Just WOW |> very impressive |>Here are more details of a side-by-side comparison ...
I feel more comfortable with 60 seconds or more because it can help detecting issues on the gears or at least exclude possible causes. (Not to mention the additional graphs of the sound with a lot of information)The Ace Timer had its test period set to the default 12 seconds
your question and Snakepottery post #123Snakepottery what it says is correct. One can just see the numbers. However, a better understanding of each screen will contribute to better enjoy every feature of the program. As I already understood some things. I is the scale in degrees that allows corresponds to the location of escape steps very useful. I have only one question: Does the point 360 deg. corresponds to the rest position the balance wheel?
Hi, sorry, I didn't notice your post. I really do not have much information here to give any meaningful answer. Can you send me a relatively long (say a couple of minutes) recording demonstrating the problem? With it, I can try to figure out if the variability that you see is a bug in tg or what.I have used two apps for iOS for timing (Hairspring & Watch Tuner) and they both seem very accurate with observed results as well as agree with each other. The s/d seems to vary more with tg however using the same mic setup and generally seems to report slower than the two iOS apps. Is there a technical reason why the timing doesn't seem as stable on tg?
I would say you probably aren't magnetizing it with the microphone, but rather with the magnetic components inside the laptop. If your Mac has a headset jack that you can plug an iPhone headphone set (the ones with the integrated mic), try that and that will keep you away from the computer itself. I have a non-Mac laptop and I use the iPhone headset mic and it works really quite well. Even with my POS work laptop, I get a good clean signal through the iPhone headset.
EDIT: And I didn't even answer the question...no, I'm not magnetizing my watches by testing them because I keep them away from strong magnetic sources.
I think you actually answered it in a previous post. My issue was tg is reporting 5s slower than the iOS apps I'm using (which reflect reality so I assume is accurate). It could be the explanation is the sound card I'm using in my Mac is just running at an offset than my iPhone with the iOS apps..Hi, sorry, I didn't notice your post. I really do not have much information here to give any meaningful answer. Can you send me a relatively long (say a couple of minutes) recording demonstrating the problem? With it, I can try to figure out if the variability that you see is a bug in tg or what.