Author Topic: Bug: extended M3U playlists  (Read 5695 times)

Haze

  • Guest
Bug: extended M3U playlists
« on: 5 Feb '03 - 10:55 »
Summary: with the introduction of the subsong feature support for the extended M3U playlist format has been broken.

Extended M3U is a playlist format used by many, mainly non-western, WinAmp-plugins. Most of these plugins are meant to read and play either ripped or logged musical data. As you may understand these files are mostly made up out of "memory dumps", where different musical data is within located at different offsets. Extended M3U formats allowed to create playlists where the entries would not only point to a specific file but also a specific offset.
With the introduction of the subsong feature to XMPlay two things have happened. As an "unexpected" bonus the offsets are now treated as subsongs, allowing easy navigation within such a file. However compatibility with the extended M3U formats has been broken! Using such extended M3U playlists mostly results in XMPlay crashing.
Though I'm not certain as on how this behavior actually comes to be, I'm quite certain it has something to do with the way XMPlay now handles subsongs. I've already eliminated the possibility of any plugin conflicts and I've also tried generalizing the extended M3U files, to no avail. This behavior was not present in earlier XMPlay versions, those which didn't support subsongs, and also is not present when using WinAmp. But who in their right mind would want to use that piece of soft? ;)

Related plugins and some documentation on the extended M3U formats can be found at http://nezplug.sourceforge.net/. Some examples of songs that use extended M3U's can be found at http://www.geocities.com/q_321/. I hope this is enough information for you to work with, Ian. If needed I'll upload some specific files which, at least in my case, give errors.

Elrinth

  • Posts: 130
Re: Bug: extended M3U playlists
« Reply #1 on: 17 Dec '09 - 01:32 »
I can't see from which date this is from and I'm really sorry for reviving a 120 day old... but I'd like to see if anything's been done to fix this? (he didn't get a response so)

Because I'm having trouble with my .m3u (tried with .pls aswell)... in xmplay it doesn't work in winamp it does. Here's the only line I have in it:
entry056.nsf::NSF,0x01|0x01,Test,00:05:10,00:00:00,00:00:00,0

In xmplay I get: "0x01,Test,00:05:10,00:00:00,00:00:00,0" as songname

When I right click and select track info I get that filename is: "entry056.nsf::NSF,0x01|0x01,Test,00:05:10,00:00:00,00:00:00,0"

Found documentation on it HERE.

I'm tried with XMPLAY versions 3.4.2.101 and 3.4.2.148
« Last Edit: 17 Dec '09 - 01:38 by Elrinth »

saga

  • Posts: 2179
Re: Bug: extended M3U playlists
« Reply #2 on: 17 Dec '09 - 08:23 »
I'm not completely sure, but I think the :: notation might be used by XMPlay to detemine whether the actualy playlist entry is "inside" the file on the left side (e.g. a zip file) or not. That might cause conflicts here.

Dotpitch

  • Posts: 2871
Re: Bug: extended M3U playlists
« Reply #3 on: 17 Dec '09 - 09:53 »
I can't see from which date this is from and I'm really sorry for reviving a 120 day old... but I'd like to see if anything's been done to fix this? (he didn't get a response so)
Extended m3u support has been broken and fixed a couple of times since Haze posted this. It should work, but I think your syntax is wrong.
Because I'm having trouble with my .m3u (tried with .pls aswell)... in xmplay it doesn't work in winamp it does. Here's the only line I have in it:
entry056.nsf::NSF,0x01|0x01,Test,00:05:10,00:00:00,00:00:00,0
Really? Is there a FAQ on that somewhere?
No FAQ AFAIK, but they are just standard text files. Here's the entry syntax:

filename::NSF,[1 based songno|$songno],[title],[time(h:m:s)],[loop(h:m:s)][-],[fade(h:m:s)],[loopcount]

Here's an example list:

# Solstice (CSG Imagesoft) [1989]
# Composer: Tim Follin

Solstice (1989)(CSG Imagesoft).nsf::NSF,$06,Title - Tim Follin - Solstice - 1989 CSG Imagesoft,2:57,,1
Solstice (1989)(CSG Imagesoft).nsf::NSF,$01,Begin - Tim Follin - Solstice - 1989 CSG Imagesoft,26,,1
Solstice (1989)(CSG Imagesoft).nsf::NSF,$02,Main Theme - Tim Follin - Solstice - 1989 CSG Imagesoft,112,113,7
Solstice (1989)(CSG Imagesoft).nsf::NSF,$05,Ending - Tim Follin - Solstice - 1989 CSG Imagesoft,81,,1
Solstice (1989)(CSG Imagesoft).nsf::NSF,$04,Success - Tim Follin - Solstice - 1989 CSG Imagesoft,18,,1
Solstice (1989)(CSG Imagesoft).nsf::NSF,$03,Failure - Tim Follin - Solstice - 1989 CSG Imagesoft,12,,1
Solstice (1989)(CSG Imagesoft).nsf::NSF,$07,Unknown 01 - Tim Follin - Solstice - 1989 CSG Imagesoft,168,,1
Solstice (1989)(CSG Imagesoft).nsf::NSF,$11,Unknown 02 - Tim Follin - Solstice - 1989 CSG Imagesoft,10,,1
Solstice (1989)(CSG Imagesoft).nsf::NSF,$12,Unknown 03 - Tim Follin - Solstice - 1989 CSG Imagesoft,4,,2
Solstice (1989)(CSG Imagesoft).nsf::NSF,$13,Unknown 04 - Tim Follin - Solstice - 1989 CSG Imagesoft,4,,2

   

Ian @ un4seen

  • Administrator
  • Posts: 20393
Re: Bug: extended M3U playlists
« Reply #4 on: 17 Dec '09 - 17:53 »
Because I'm having trouble with my .m3u (tried with .pls aswell)... in xmplay it doesn't work in winamp it does. Here's the only line I have in it:
entry056.nsf::NSF,0x01|0x01,Test,00:05:10,00:00:00,00:00:00,0

In xmplay I get: "0x01,Test,00:05:10,00:00:00,00:00:00,0" as songname

When I right click and select track info I get that filename is: "entry056.nsf::NSF,0x01|0x01,Test,00:05:10,00:00:00,00:00:00,0"

I don't have files to test with, but I suspect the problem is the '|' character, which XMPlay uses to indicate an archive.

Elrinth

  • Posts: 130
Re: Bug: extended M3U playlists
« Reply #5 on: 18 Dec '09 - 19:05 »
indeed the pipe was the problem