Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[BumbleDawg]

Will the option of exporting a .m3u8 playlist be made available to the later versions of MC15?

Cheers and regards.

[JimH]

Did you try just renaming an m3u file?  MC supports unicode throughout.

[Matt]

Are you looking for this in the File > Export Playlist tool, or for a handheld?

Thanks.

[BumbleDawg]

Did you try just renaming an m3u file?  MC supports unicode throughout.

Which was what puzzled me when it couldn't export a unicode playlist. I did try renaming the m3u file to .m3u8, but that didn't convert the question marks to the proper characters. Probably since it was exported as an m3u and those don't support unicode period.

Neither Winamp nor foobar (both widely known as fully unicode supported) could correctly send track information with unicode characters to Foxytunes, while MC and WMP could. Another reason why MC is miles and one heaven better than the most media players. That said though, both winamp and foobar offers the option of exporting a m3u8 playlist.

Are you looking for this in the File > Export Playlist tool, or for a handheld?

In the File > Export Playlist and also the Recent Playing Nows > Export as.

Thanks for getting back so quickly.

Also, since I already possess my own thread (), any foxytunes/JRiver Media Center users here? I seem to be getting frequent Firefox crashes if I exit MC while FF is still running. Is that an isolated issue on my end for does anybody else experience the same? The FF error points to an "Runtime error". It happens sometimes with Winamp, but far more often with MC. Its not a dire issue per se, since I don't exit MC most of the time, but would be cool if it was looked into if there are enough Foxytunes users to warrant a fix.



Cheers again.

[JimH]

There was a foxytunes problem a while back.  I don't remember exactly what it was.  Not logged in?  Try a search here.

[BumbleDawg]

That was the problem of it opening MC when Firefox is closed.

No matter, I can overlook the Foxytunes error. All I want is for MC to have the option of exporting .m3u8 playlists. 

[JimH]

Here's a different one:
http://yabb.jriver.com/interact/index.php?board=3;topic=31967.13#msg219763

[Matt]

Coming in build 119 and later:
NEW: Added support for M3U8 playlists (both to File > Export Playlist, and also to import).

[BumbleDawg]

 

Thanks a lot for this guys. Salutes to the development team.

[BumbleDawg]

There seems to be some compatibility issues with MC15 exported .m3u8 playlists and foobar2000.

The exported playlist (from MC15) is only half loaded in foobar but loads fine in Winamp. That said, exported m3u8 playlists from winamp/foobar are fully compatible on all players.

Slight glitch perhaps?

[Matt]

Can you compare a working an not working version of the same playlist and see a difference?

UTF-8 is pretty simple, so I can't think what we could be getting wrong.

And since it works in Winamp and not Foobar, you might report it to Foobar.

Thanks.

[Alex B]

Winamp uses the extended format when it saves m3u8 playlists. Perhaps some programs expect that format.

Here is an example - exported from Winamp & MC (a Russian CD single):

Only the Winamp playlist works with foobar. The actual playlists are attached.


EDIT

I removed the playlist examples from this post. A new post is below. I added foobar.

[BumbleDawg]

Can you compare a working an not working version of the same playlist and see a difference?

I did, and as Alex already posted, Winamp has that extended format in its playlist, but the playlists exported from MC15 and foobar (same set of songs) are identical.

Yet the foobar exported playlist loads properly, while the MC15 playlist only loads 30 tracks (out of 150.)

And since it works in Winamp and not Foobar, you might report it to Foobar.

Almost did, but the MC15 playlist was the only one not loading properly, hence my "bug-report". Just a notification rather than a complaint really.

Thank you for your prompt responses.

[Alex B]

In Notepad, an m3u8 playlist from foobar looks identical with an m3u8 playlist from MC:

Winamp

#EXTM3U
#EXTINF:181,F.P.G. - Рок
E:\F.P.G. - Стихия\03 - Рок.mp3
#EXTINF:195,F.P.G. - Ломай
E:\F.P.G. - Стихия\01 - Ломай.mp3
#EXTINF:184,F.P.G. - Стихия
E:\F.P.G. - Стихия\02 - Стихия.mp3

MC

E:\F.P.G. - Стихия\01 - Ломай.mp3
E:\F.P.G. - Стихия\02 - Стихия.mp3
E:\F.P.G. - Стихия\03 - Рок.mp3

foobar

E:\F.P.G. - Стихия\01 - Ломай.mp3
E:\F.P.G. - Стихия\02 - Стихия.mp3
E:\F.P.G. - Стихия\03 - Рок.mp3

-- but there is a difference. The Winamp and foobar playlists have three additional "invisible" characters in the beginning of the file code. See the attached screenshot and the actual playlists in the zip package.


Log in to the forum if you can't see the attachments.

[BumbleDawg]

So if I'm understanding this right, there's nothing to fix in MC15? Just different ways the playlists are exported?

[Alex B]

I don't know what is the purpose of those three characters. Perhaps JRiver could add them to make the format more compatible.

[BumbleDawg]

Hex edited those 3 letters into the MC15 exported playlist lets foobar imported entirely. Works as intended. Well until the next build (if you plan on adding the weird letters), this hex edit workaround should suffice for the time being.

Thanks for your time Alex.

[Alex B]

I am not one of those who actually add things (I don't work for JRiver), but the JRiver developers may have an idea why the additional code is there and they might be willing to make this little change if it improves compatibility.

[Alex B]

A Google search helped: http://en.wikipedia.org/wiki/Byte_order_mark

The "EF BB BF" string is the byte order mark (BOM).

EDIT

A BOM may be problematic with some programs or devices. (E.g. Sansa Clip)
http://www.google.com/search?q=m3u8+playlist+BOM

Perhaps it would be good to have both variations available.

[Matt]

We write a BOM in UTF-16 files but not UTF-8 files.  It seems kind of pointless in UTF-8, because the byte order is always the same.

From Wikipedia:

While Unicode standard allows BOM in UTF-8 [2], it does not require or recommend it

I would call this a Foobar bug.  You might report it to them.