A question about the 'Generate M3U playlist' plugin

MusicBrainz Picard
1

I may misunderstand how this plugin is supposed to work:

What I am trying to do is when matching and saving an album release (all it’s songs being in that album’s folder), having the plugin automatically create an .m3u8 playlist file in that folder.

But, the plugin is activated, and nothing seems to happen…
(and there are no setting options)

2

This plugin ads a context menu entry for albums, so you can right click on an album and select Plugins > Generate Playlist…

3

There are still two problems with that:

  • You will need to navigate to the album folder again. Which is no fun to do for every album all over again. The plugin doesn’t seem to know where the files are by itself?

  • Even when you do select the album folder to save it, it will not save a relative path playlist.

While the plugin notes state: “Relative pathnames are used where audio files are in the same directory as the playlist”.

4

Same issue. Needing to navigate to the correct folder for Every. Single. Album. in my collection already makes this plugin entirely useless. Is there an alternative to the plugin?

5

I was surprised too this wasn’t automatic.

So I did


and

and have this working when combining my two branches.

2 Likes
6

@thomasvs can you explain how to install those additions please.

7

@thomasvs Same question as the dude above. If you could explain that, would be nice.

8

This issue still present in latest Picard stable v2.10 (Dec 2023)

Not sure if any progress on merging these improvements from @thomasvs into Picard yet? Feature improvements seem to be still open for two years.

However I found this one: Fixes for “Generate M3U playlist” #245
With a potential alternative approach to the fix (Sept 2022): #325
Unfortunately this was only blocked from merge due to request to remove a possibly unnecessary str conversion.

Since the Picard-generated M3U8 playlists are unusable for me through a network share path (UNC path), I’ll try a beta release. Currently working around the issue by using Mp3Tag beta & custom export script instead.