3.2.6827 monitoring of folders fails on .M3U playlists

[chrisjj]

If I engage 'monitored folders' e.g.



and add a .M3U playlist to the monitored folder, MB fails to add the new file to the library.

It ought to have dont so: 'new file action: (*) add to library'.

It seems this works on tracks but not playlists.

It would be great to have it work on playlists.

Meanwhile, amending the label to: 'new track file action' would remedy the discrepancy.

[phred]

1- You've posted the same info in Bug Reports and in the Wishlist. It can't be both. If it's a verifiable bug, it will probably be fixed. If it's a wishlist request, it's up to Steven whether to implement or not.

2- Monitoring looks for music files - mp3, flac, etc. M3U files are text files, not music files. They contain -links- to where the music lives.

3- In order to create a playlist, the files contained within are (typically) already in your library, so a playlist file in the library makes no sense.

4- Playlists are found in the playlist node and, as previously stated, already have the tracks in the library.

5- Unless I'm completely misunderstanding you, this is not a bug. Nor is there a need for it to be on the wishlist.

[Coogan]

@Phred.
I appreciate you having the latest version of MusicBee in your sig.  Would it be possible to put the actual version in there, instead of just 3.2?

Thanks...
Coogan

[psychoadept]

Would it be possible to put the actual version in there, instead of just 3.2?

3.2 is the actual version. 3.3 has been posted only for testing the new default skin. There have been 3.2 patches since then that would not be included in the 3.3 test version.

[phred]

I think what Coogan is asking for is "3.2.xxxx" and if so, while it is possible to put that in the sig, it would be a waste of my time. Sometimes there's more than one patch issued in a day. Sometimes not for a couple of days.

Steven doesn't publish the xxxx so in order to find out which version it is, I would have to download, install, help, about, copy version number, go to the forum and edit the sig. And I don't download every patch.

If you want the latest patch, simply follow the link (or bookmark it) and download.

[chrisjj]

If it's a verifiable bug, it will probably be fixed. If it's a wishlist request, it's up to Steven whether to implement or not.

Thanks for the confirmation that I've covered it either way.

5- Unless I'm completely misunderstanding you

It does look that way.

Scan from the menu will add playlists. Scan on start-up/continuously won't. Meaning MB can't automatically keep up-to-date with playlists in my folder.

[Coogan]

I think what Coogan is asking for is "3.2.xxxx" and if so, while it is possible to put that in the sig, it would be a waste of my time. Sometimes there's more than one patch issued in a day. Sometimes not for a couple of days.

Steven doesn't publish the xxxx so in order to find out which version it is, I would have to download, install, help, about, copy version number, go to the forum and edit the sig. And I don't download every patch.

If you want the latest patch, simply follow the link (or bookmark it) and download.

Exactly what I'm talking about.  Because when I go to the latest version section on the forum I'm  completely lost.
That thread really doesn't show that anything has been updated, but there are releases on other threads.  I'm so lost.

Coogan

[psychoadept]

Gotcha, sorry for the confusion. With very rare exceptions, like if the Latest Version forum has been updated in the last day or so, you can count on the links in phred's and my signatures to have the most recent update. But like phred says, it's way too much overhead to try to keep the version number up to date.

[phred]

Scan from the menu will add playlists. Scan on start-up/continuously won't. Meaning MB can't automatically keep up-to-date with playlists in my folder.

Are you creating these playlists outside of MB? And if so, why not create them from within?

[chrisjj]

Are you creating these playlists outside of MB?

Yes. But the same applies regardless e.g. if I'd created them inside MB and then exported to M3U.

And if so, why not create them from within?

The functionality required for creating these .M3U playlists isn't present in MB. These playlists are exported from a specialist audio content management system.