Ability to Mass Generate PLS Files

[dotdissent]

Using WACUP with NSFE files and it appears the only way to make shadowed NSFE playlist files work correctly is to open each one individually and export a Winamp playlist. I suppose a better method would be to offer a setting to default importing NSFE's to the playlist as shadowed entries, but I figure that would be a higher bar to clear than this (hopefully) much simpler ask.

Cheers!

[bbbradsmith]

I don't know the term "shadowed playlist", could you explain what you mean? I'm also unfamiliar with WACUP. Is this about the Winamp plugin or the stand-alone NSFPlay? Does NSFPlay currently have any actual support for playlist files?

[dotdissent]

Shadowed playlist was a term from other NSFE compatible plugins of the past. It just means outputting the playlist entries of an NSFE with their tagging to Winamp's playlist/a playlist file. WACUP is the Winamp Community Update Project, a feature-rich and frequently updated variant of Winamp. NSFPlay itself I'm not sure of, NSFPlug can just export them to .PLS/the active Winamp playlist.

[bbbradsmith]

I see. That was a feature that existed since a long time before I took over this project, and I never really understood what it was used for.

However, looking at this, if I use an NSFe, it does use the NSFe playlist and titles if NSFe playlists are enabled. What did you want this to do that it doesn't already do?

[bbbradsmith]

Hmm, so is the request to automatically generate PLS files for a whole directory? Like as a command line thing, or what? I'm not sure if it's a great feature for NSFPlay 2, but I'll definitely try to make this kind of thing possible for NSFPlay 3.

I'd like to ask, are these PLS files used for NSFPlug only or do they work with other NSFe players, you mentioned that "shadowed playlist" came from a different plugin? Which one?

I'm curious about how these are used. What do you use to play them back? Because, I'm not sure the plugin generator is doing the "right thing" for NSFe. It will do a different thing depending on whether you have the option to use NSFe playlist on or off. The tracks are indexed to that playlist rather than to the NSFe in absolute, which means the PLS would break if you switched to the other setting. This was just a consequence of the same old playlist generator code running even though I'd added NSFe support after.

To me the right thing would be to give absolute track numbers in the playlist always, but this is not how it currently works, and I'm wondering about prior usage and the consequences of changing this. I also don't quite understand how it's appending ::NSF and a track and a title to the PLS File# directives. I can't find any documentation of the format that explains this possibility. ...and finally it generates absolute filenames which seems like yet another problem. So, if working on this feature it might be a good time to fix all of these issues.

Example line: File1=C:\Users\rainwarrior\Music\NSFe\10-Yard Fight.nsfe::NSF,$01,Start Half (001/006) 10-Yard Fight - Koji Kondo\, Ichiro Takagi

Example NSFe that demonstrates this. The NSFe playlist is actually 6 tracks (2, 1, 9, 0, 4, 3) but there are 17 underlying NSF tracks.

NSFe: 10-Yard Fight NSFe.zip