Post Reply 
Errors on first scan
18-06-2015, 09:57
Post: #6
RE: Errors on first scan
(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.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
Errors on first scan - FinstallPark - 16-06-2015, 23:21
RE: Errors on first scan - simoncn - 17-06-2015, 09:08
RE: Errors on first scan - simoncn - 17-06-2015, 10:01
RE: Errors on first scan - simoncn - 18-06-2015 09:57
RE: Errors on first scan - simoncn - 18-06-2015, 12:34
RE: Errors on first scan - simoncn - 18-06-2015, 14:11
RE: Errors on first scan - simoncn - 01-10-2015, 22:20

Forum Jump:


User(s) browsing this thread: 2 Guest(s)