The Direct2D frontend may very well be misbehaving after making it behave in high DPI scenarios (in which it's broken again).
... Is this a bug with Direct2D?
feature request: it seems that people started to customize the seekbar appearance, would it be possible to add an option to select different effects instead of overwriting the seekbar.fx every time we want to try a new one?
Not with Direct2D itself, just with my use of it. Well, it has some rather annoying DPI semantics that tends to destroy beautiful code.
What about identifying tracks using the audio MD5 where possible?
I prefer methods where collisions do not occur.
MD5 audio checksums for verification and identification
In any way, a MD5 of the audio data would be a bit error-prone unless the decoder provides bit-exact identical output on multiple runs.In any way, computing the MD5 of the data would cost about as much as analyzing it, as most of the cost is in I/O and decoding.If you mean to take the MD5 of compressed audio, I do not believe that that data is exposed by the input or decoder services.The direction I'm going to take files with changing locations is to provide per-directory databases and tag-based storage, prioritized via preferences.
Version 0.1.5 does not work on one of my systems (Lenovo T60, Intel G945 Graphics, XP SP3).I now have the two options (GDI and Direct3D 9.0) but none of them is working (the panel remains blank and is never refreshed). When I select Direct3D 9.0c, then close and reopen the preferences panel, GDI remains selected.Version 1.0.4 was working fine with Direct3D 9.0c only after installing the August 2009 Direct X runtime redistributable.