next »

[Roj]

XMPlay gives me nothing, not even an error.  I click on the file, XMPLay starts and that's it.  The file tests and decodes properly using FLAC Frontend.  Using MP3TAG to remove tags doesn't change anything.

Where can i upload it for testing?

[Roj]

Never mind, latest build fixes it.  I had thought I was running the latest but aparrently not.

[blammoAMS]

unfortunately, i am having the same problem as of yesterday. i've re-installed xmplay (the latest 'stuff' version) and the latest flac decoder - but to no avail. yesterday, i had some trouble with flac'ing a cd; might have something to do with mp3 tags. but that was resolved, and now no flacs, also no older ones, will play. i don't know what to try anymore.
please advise!
blammo, amsterdam

[Dotpitch]

i've re-installed xmplay (the latest 'stuff' version) and the latest flac decoder - but to no avail. yesterday, i had some trouble with flac'ing a cd; might have something to do with mp3 tags. but that was resolved, and now no flacs, also no older ones, will play. i don't know what to try anymore. please advise!

Be sure to use the latest XMPlay and the latest xmp-flac. Start XMPlay, open Options and stuff and check whether xmp-flac is present on the 'Input' page. Also, on the 'Playlist' page, check that flac is not in the 'Ignore filetypes'-box. Try opening a flac by using the 'Open file'-dialog, as well as by dropping the file on the main window. If all that doesn't work, re-check your flac file with a different decoder. If it does work there, upload the file to http://ftp://ftp.un4seen.com/incoming/ and mention the filename in this thread, so Ian can take a look at it.

[blammoams]

dotpitch, thanks for the quick reply. i was under the impression "ignore filetypes" meant i wouldn't be seeing the .flac extension in the playlist. so i put "flac" in & since then xmplay ignored them. so that was the snag. i've removed "flac" from the "ignore filetypes" list & everything works fine again.

[Dotpitch]

i've removed "flac" from the "ignore filetypes" list & everything works fine again.

Good to hear that.

i was under the impression "ignore filetypes" meant i wouldn't be seeing the .flac extension in the playlist.

Do you mean the additional column in the extended playlist? Close XMPlay, open xmplay.ini with Wordpad (or whatever you use, just don't use Notepad!) and add

NoListExt=1

to the [XMPlay] section. Start XMPlay, and the file type column is gone. If you want to keep the column but want to have the playlist show 'filename' instead of 'filename.flac' for files without tags, tick 'Omit filename extension' on the Titles page of Options and stuff.

[saga]

open xmplay.ini with Wordpad (or whatever you use, just don't use Notepad!)

why's that? i would assume it the other way around.

[Dotpitch]

open xmplay.ini with Wordpad (or whatever you use, just don't use Notepad!)

why's that? i would assume it the other way around.

I've repeatedly had Notepad corrupting the ini file by adding junk up front, so XMPlay would revert to default settings. Wordpad will save it as plain text and shouldn't corrupt it (neither should Notepad, but it still did ).

[edit]
The attached image shows xmplay.ini in a hex viewer, before and after is was saved with Notepad (WinXP Pro SP3). Wordpad saves the file correctly.
[/edit]

[saga]

EFBBBF indicates an UTF-8 file, so you would have to change the encoding back to "ANSI" in the "Save as" dialog.

[Dotpitch]

EFBBBF indicates an UTF-8 file, so you would have to change the encoding back to "ANSI" in the "Save as" dialog.

Ah, good to know that it's not just junk. I didn't expect Notepad to default to UTF-8, even when saving files that were originally ANSI.

[saga]

Well, it doesn't here... The file stays ANSI for me (I'm on Vista, but it was the same with WinXP). I would suspect that Notepad detects some funky characters in your INI file (for example in a recently accessed folder or something like that) and then switches to UTF-8 automatically.

[Zarggg]

Notepad is rather retarded about the BOM. But considering that Unicode is becoming more prevalent in general, would it not be a good idea for XMPlay to account for a possible BOM indicating Unicode for the .ini? Or is it better for XMPlay to assume that the .ini is generated only by XMPlay to avoid potential errors from manual modification?

[Tsorovan]

Or is it better for XMPlay to assume that the .ini is generated only by XMPlay to avoid potential errors from manual modification?

.ini files are supposed to be editable, so no.

[saga]

I wonder if anything can be done against that, though, since I guess that Ian uses standard WinAPI calls (that would be the most simple thing to do at least), so he might only have access to their ANSI versions.

[Ian @ un4seen]

It looks like the problem is that the prepended "EFBBBF" is meaning that the "[XMPlay]" line is no longer just "[XMPlay]". A possible solution to that is to insert an empty line at the start of the file.