Ian is there a way to clear the 'Find Track' without the windows critical stop sound?
Here's an update with a "NoBeeps" secret INI setting to disable all beeping... www.un4seen.com/stuff/xmplay.exe
Btw, from now on, I've decided to increase the version number even in "stuff" versions (at least in the Options'n'stuff window). Release versions will be "3.4.x.0", while stuff versions will be "3.4.x.y".
I've tweaked it a bit (updated EXE above), so that it doesn't misdetect the year of that file.
1. There's a bug with output device naming in cyrillic:
2. There is a cosmetic bug with string's place in "Options and stuff":
3. There is a cosmetic bug with an end of time string in "Track info" dialog.
Please try the update above, and let me know if you still have these problems.
I have assigned F12 to minimize/restore from tray.
It minimizes ok, but doesn't restore.
It does if I assign other shortcut (I have tried ctrl + .)
Is that a global shortcut? It'll work when XMPlay is in focus, but it appears that Windows doesn't allow global hotkeys to use F12 - I guess it's already taken/reserved.
I read in the xmplay history :
* Support for embedded CUE sheets
Does this refer to tracks having the cue as part of their tags?
I am asking this because I tried playing such a track but xmplay didn't recognize the cue.
Yep, it'll check APEv2 tags (and FLAC via the plugin) for a "Cuesheet" tag, as used by Wavpack (and FLAC) and maybe others. What format is your file? Please upload it to have a look at... ftp.un4seen.com/incoming/
There would be a problem when using fullscreen visuals. I don't know how or why, but sometimes, when in fullscreen, XMPlay just closes. No errors, no crashes, no nothing. It just closes. Has anyone else had this problem?
Yep, some vis are a bit picky about the res they run at, particularly changing the res. If you have a plugin like that, you could try going fullscreen with another vis, and then switch to the picky one.
XMPlay should actually catch the vis crashing, but it'll then continue to run the vis, in the hope that it was a one-off
... Instead of doing that, it'll now unload the vis in the update above, which should avoid further problems (like XMPlay closing).