[contrate_wheel]

Great !

I tried to compile on OSX, but the executable crash at launch because he's not able to find the font, even if they are in the same folder. The result was the same when I installed the font on the system.

I tried a few things, but I was not able to find a workaround. Maybe the solution is to use relative path ? Or maybe the system for selecting a font is fundamentally different on OSX.

Thanks, I am baffled. I added some error reporting, could you please update your source and tell me the error message?

 

[Baillive]

Here it is : error #1 in FT_New_Face()

 

[Halda]

I tried to compile the latest update on my Mac (OS X 10.11.1) and it fails at "#include <cairo/cairo-ft.h>"
If I change it to "#include <cairo-ft.h>" it works. Any ideas why?

Anyways, I'm getting the same error as Baillive does for what it's worth.


Edit: I did some further debugging this morning and found that using the full path to the font file in FT_New_Face will make the error go away, so it must be a problem with locating the file.

I'm not sure where Freetype is looking for relative file names, but changing #define INTERFACE_FONT "VeraMono.ttf" to "./VeraMono.ttf" will fix the problem on Mac (assuming the font is located next to the executable).

However, no text will show up in the interface. The FreeType font does seem to load properly because it reports a valid number of glyphs available etc.

I did manage to get text showing up by replacing cairo_set_font_face(c,cr_face) in cairo_init with something that didn't use that specific font:

cairo_select_font_face (c, "sans-serif", CAIRO_FONT_SLANT_NORMAL, CAIRO_FONT_WEIGHT_NORMAL);

 

[contrate_wheel]

@Halda

Beautiful, thanks a lot!

I was about to ask you to try more or less the same experiment, in fact I just updated the code in such a way that it builds a path. I also replaced FT_New_Face() with FT_Open_Face(), that should follow the same code path under linux and OS X. It would great if you could try again, but I believe that the same result will follow (no text visible).

If it still does not work, I will just use a default font as fallback. The problem with using the default font is that, at least under Windows, not always the monospace one is really monospace. Yet it's better than nothing I guess...

 

[Halda]

It would great if you could try again, but I believe that the same result will follow (no text visible).

The updated code compiles fine now, and it does load the font file. |> You're right that the result is the same though, no visible text showing...

I haven't worked with any of these libraries before, but my guess would be that Cairo is to blame. Maybe the conversion from Freetype doesn't work or it needs more initialisation? Is there a way to probe the cr_face object for details? I checked the cairo_text_extents during the text rendering and it reported a height of 0, which might be a clue?

 

[Halda]

Another weird thing happening when the text won't show up is that not all lines in the interface renders:

Some further tests show that if I disable all cairo_show_text calls in expose_waveform then the lines will show up. So there's definitely something weird happening when trying to show text.
I also noticed that the line width changes to 2.0 after the failed calls to cairo_show_text (instead of the expected 1.0).

 

[contrate_wheel]

Yep, only the lines drawn before the first call to cairo_show_text(). So apparently the first misbehaving cairo_show_text() messes up the cairo context, and from that moment on nothing else is drawn. This also explains the zero height, because probably everything cairo-related is just garbage. Font file corrupted? The md5 of mine is 37d8aff129ecd7d3fc495b7239f834db.

As an experiment I tried to set cr_face to NULL and, on debian, cairo just reverts to the default. Apparently cairo_ft_font_face_create_for_ft_face() is not supposed to ever return NULL, but there is a function cairo_font_face_status(cairo_font_face *f) that should check whether an error has occurred with f. Except for this, these objects seem to be pretty opaque. There is a function cairo_font_extents() that is more or less like cairo_text_extents(), however it works on the cairo context, not on the font face itself.

Thanks a lot for this...

 

[Halda]

Font file corrupted? The md5 of mine is 37d8aff129ecd7d3fc495b7239f834db.

Yep, same md5 here. Font shows up fine in the OS inspectors too.

As an experiment I tried to set cr_face to NULL and, on debian, cairo just reverts to the default.

I tried that too and it seems to revert to some default because now text shows up.

I also tested to use another random ttf file (from Microsoft) and it failed in the same way; no text shows up. Looks like something goes wrong with cairo_ft_font_face_create_for_ft_face()

 

[Ticonderoga]

Despite what sounds a lot like Chinese to me in this thread (I don't know much about computers and all), I have to say that this is about the coolest program I've seen in a while.

I wasn't even sure how to use the software, just unzipped, clicked on the nearest .exe file, ignored the Microsoft and Norton doom announcements and plugged in my mic.

Well, I don't have a mic, save for the one on the iPhone earphones:



And there you have it:



Too cool.

I just went through my entire watch-box and timed all of my watches.

All I did was loosen the band one notch and then slide the mic under the watch - between it's watchbox pillow and then slide it back on the pillow. Wedged between the watch and the pillow with the mic hole pressed against the watch back, just sit it down and watch the magic.

thanks

 

[Apollonaught]

Hi contrate-wheel,

I tested the program with Vista and the internal microphone,it works great!......


The watch i tested was an late 1940`s Accurist with unknown service history,my question is...........if the amplitude is too low in a given watch will it not show at the top of the screen,because after 5 min or so of testing i think i saw the amplitude reading twice and then it disappeared again,somewhere between 230-240?

Edit:Ok ,cool it has something to do with volume,i tried a watch with a louder tick and it shows the amplitude

Anyways,cool program.

 

[contrate_wheel]

@Apollonaught

Thanks for your review.

The figures on page 3 of this manual
http://www.witschi.com/assets/files/sheets/Test and measuring technology mechanical watches.pdf
show how the noises produced by an escapement are supposed to look if recorded with a perfect mic. The amplitude is determined by the timing between the first and the third of the three events. The first watch of your screenshots is perfectly fine, however, as one can see from the graphs, the first pulse is too weak to stand out above the noise, so tg is unable to compute the amplitude. This happens only because you are using the internal mic of your computer, and, you might try, but I believe that no other publicly available program would perform better than tg in this situation. I would venture to say that here one can not extract the amplitude from the audio data, because this information has been completely destroyed by noise.

So, strictly speaking, it is not volume, rather it is signal-to-noise ratio. In your other watch, the first pulse is just about visible above the noise level, so tg can, and in fact does, pick it up.

 

[Apollonaught]

@Apollonaught

Thanks for your review.

The figures on page 3 of this manual
http://www.witschi.com/assets/files/sheets/Test%20and%20measuring%20technology%20mechanical%20watches.pdf
show how the noises produced by an escapement are supposed to look if recorded with a perfect mic. The amplitude is determined by the timing between the first and the third of the three events. The first watch of your screenshots is perfectly fine, however, as one can see from the graphs, the first pulse is too weak to stand out above the noise, so tg is unable to compute the amplitude. This happens only because you are using the internal mic of your computer, and, you might try, but I believe that no other publicly available program would perform better than tg in this situation. I would venture to say that here one can not extract the amplitude from the audio data, because this information has been completely destroyed by noise.

So, strictly speaking, it is not volume, rather it is signal-to-noise ratio. In your other watch, the first pulse is just about visible above the noise level, so tg can, and in fact does, pick it up.

Excellent,thank you.
That link explains everything.

 

[adamant365]

I might be a little slow, but I'm definitely not computer illiterate...but I can't get the application to run at all. I'm using Windows 7 Pro 64-bit and when I extract the files from the .ZIP, install the font, and attempt to run the program, nothing happens. I don't see any errors in the Windows error logs. I get a second or two of Windows "spinning wheel" but the program never launches. Could I be doing something wrong?

 

[contrate_wheel]

I might be a little slow, but I'm definitely not computer illiterate...but I can't get the application to run at all. I'm using Windows 7 Pro 64-bit and when I extract the files from the .ZIP, install the font, and attempt to run the program, nothing happens. I don't see any errors in the Windows error logs. I get a second or two of Windows "spinning wheel" but the program never launches. Could I be doing something wrong?

Do not install the font: leave it where it is. Extract the zip archive to a folder. Do not move anything. Double click.

 

[adamant365]

Weird, I don't get it. I have it up and running on a very old Toshiba "test" laptop running Windows 10 and my work laptop running Windows 7 Enterprise 64-bit and it's working just fine. My powerhouse desktop PC won't even launch it. Go figure.

EDIT: For what it’s worth, it is a brilliant program. A million kudos to you contrate_wheel. My Omega Speedy Pro shows beautifully. When I switch to my Omega AT8500, I get everything but balance amplitude, but I expected this due to the co-axial escapement.

Does anyone know why the CoAx amplitude can’t be derived with the standard timing algorithms?

 

[contrate_wheel]

Weird, I don't get it. I have it up and running on a very old Toshiba "test" laptop running Windows 10 and my work laptop running Windows 7 Enterprise 64-bit and it's working just fine. My powerhouse desktop PC won't even launch it. Go figure.

Thanks. So there is a bug! It might be this font thing: I will get rid of that, as it is producing nothing but annoyance. I made a Windows build with the latest version, which has a little of error reporting. May I ask you to try again with the new version (just re-downoad, version number should be 0.2.2) on that desktop computer and tell me the error message?

 

[adamant365]

Thanks. So there is a bug! It might be this font thing: I will get rid of that, as it is producing nothing but annoyance. I made a Windows build with the latest version, which has a little of error reporting. May I ask you to try again with the new version (just re-downoad, version number should be 0.2.2) on that desktop computer and tell me the error message?

I’m pretty sure the issue was that I didn’t have a mic plugged in. Duh…your error reporting spotted this fact immediately and forced me to exit. I plugged in a mic and tried again and off she went. Brilliant! I don’t think it was the font thing after all.

 

[adamant365]

Oh, and here's an obligatory screen shot. You think this 1860's pocket watch needs a service?? :-d


EDIT: I had the lift angle set at 38 previously to time my Co-Axial Omega. I think this old pocket watch is 50 degrees. Either way, 140 amplitude isn't very good.

 

[contrate_wheel]

Oh, and here's an obligatory screen shot. You think this 1860's pocket watch needs a service?? :-d
View attachment 6200929

Your audio looks very clean!

May it be that the nominal beat rate is not 18000 bph? If you know the correct bph, you can just write it in the bph field, even if it is not among those in the drop-down menu. Tg should be able to work with anything in the range 12000-72000.

I would love if you could send me a 30sec sample of your co-axial to play with...

 

[dom_]

I am late to this thread, mic wise are people using amplifiers or straight in?