Errors on first scan

[FinstallPark]

(18-06-2015 09:57)simoncn Wrote:  

(17-06-2015 11:11)FinstallPark Wrote:  OK, here it is (or should be!)

Paul

Thanks very much!

This file starts with the byte sequence 0xEF 0xBB 0xBF which represents the Unicode byte-order mark (BOM) in UTF-8 encoding (see this page). This byte sequence is legal (but not required) at the start of a UTF-8 file. When you save a file in UTF-8 format using Notepad, Notepad automatically inserts this byte sequence at the start of the file. Notepad doesn't display the BOM when you are editing the file and this is why you didn't see it whe you viewed the file in Notepad.

MinimServer isn't allowing for a BOM to appear at the start of a .m3u8 playlist file, so it is treating the # in #EXTM3U as the second character of the first line (with the BOM as the first character).

The next MinimServer update will detect and ignore a BOM at the start of a .m3u8 file. Thank you for letting me know about this problem.

=====
Thanks for that. The playlist files are generated by the ripping program, and I haven't edited them at all. I only used Notepad to see what was in the file I sent.
I use EAC and then run the rips through a FLAC converter. In the EAC Options/Tools menu there is a check box for "create '.m3u' playlist on extraction", with two further check boxes 'write m3u playlist with extended info' and 'write m3u playlist as UTF8 file (compatible e.g.with Winamp)'.
I have all three boxes checked. Should I uncheck the UTF8 box?

Thanks for your very knowledgable help!

Paul