Author Topic: I cannot remove a Playlist! Help Please?  (Read 777 times)

Flourgrader

  • Jr. Member
  • **
  • Posts: 27
Hi All,
I have M/Bee version 3.4.8033
Windows 11

I have a bit of an irritating problem here, that I am hoping someone can help me out with it.
In the centre panel where I display all my record from A to Z.
If I wish to add a song to my playlist I right click on the record
Drop down menu appears
Add to playlist
I see 2 duplicate playlist
It looks like this on my screen.

Press Ctrl to multi-select
Steve’s-Playlist
Steve’s-Playlist
<New playlist>
External playlist

I only created one playlist.
I have tried removing both playlist from within M/Bee and starting again,
which does not work.
I have located the program installation folder
C:\MusicBee\Library\Playlists\
and deleted "Steve's-Playlist.mbp"
and re started M/Bee version 3.4.8033
The playlist is still there?
How can I remove it?
Is there an *.ini file I can edit to fix the problem?
Any suggestions in how to fix this problem are welcome.

As A side Issue:
I have another PC sat at the side of this one I am using,
and this is running the same version of M/Bee version 3.4.8033.
There is no problem with the playlist on this one?
Thank You...... :)

WizofOz

  • Newbie
  • *
  • Posts: 1
I know this has been here a while.
I had a somewhat similar problem in that every time I deleted a playlist it would just reappear when I did a rescan.
I tried everything including clearing the playlist before deleting, directly deleting the relative mbp files from their MusicBee directory, and emptying the recycling bin before rescanning.  When I re-scanned a new mbp file with the playlist songs in it was being created from "somewhere" which was odd as the original mbl had been cleared and deleted.

Eventually after scanning (I use Everything) I found that new files with same name and a nfo and a pls file extension were being created when I deleted a playlist.    Once I manually deleted the playlists with the pls extensions (deleting the nfo files did nothing) the problem seemed to have resolved itself (at least for now).

FYI I'm on version 3.4.8033 Store