Author Topic: Is playlist based 'locate missing file' functionality reliable f multi playlist?  (Read 1310 times)

alec.tron

  • Hero Member
  • *****
  • Posts: 738
Heya,
as I have not seen this documented, but it exists as a workflow, and I would like to use this as it makes maintaining a vast library of .m3u based playlists a bit easier...

Can anyone, ideally Steven, confirm that using MB's 'locate' on a missing track/file from inside a playlist is meant to replace all occurrences of the same file/track in all other playlists in MB's playlist manager ?

I have tested this and it seems safe and after a 'locate file' trigger on a missing file and pointing it to a different file, it does update all playlists files (.m3u) it occurs in in my tests, but, this might just be lucky happenstance....
So, before I rely too heavily on this I just wanted to check that this is how this is meant to work from MusicBee's official end and not a by-product of the way playlists / collection logic exists under MusicBee's hood and could lead to inconsistencies along the way or is not consciously maintained functionality...?

Thanks.
c.

alec.tron

  • Hero Member
  • *****
  • Posts: 738
Hm.
Seems like I stumbled upon another piece to the puzzle...  I'm just setting up a win10 (64bit) desktop, and after copying my portable MusicBee 3 install w 3.1 patch over to the new machine, turns out the 'feature', which lead me to believe the above 'workflow'/feature is intended, does not seem to exist / work on Windows10 (at least not the 64 bit version...).

On windows7 (32bit) and the same MusicBee version: If there was a folder in the Playlist Manager holding multiple playlists, selecting the 'parent' folder would populate the file-list and act as an aggregator (= showing the contents of ALL child-playlists it holds - but only 1 of each track, even if there were multiple occurrences of the same file/track across multiple child playlists - replacing this [or one of the occurences in ANY of the playlists replaced them across multiple playlists... which I thought was awesome...]).

Now on Windows 10 & the same MusicBee version/setup, if I now select any of the 'parent' folders, I do not see the 'aggregator' view of the folder anymore (= tracks list remains empty)...
I'll test some more how this behaves when replacing playlists items, and if it still affects multiple occurrences of the same across playlists.

Would be great if anyone, ideally Steven, can confirm which of the 2 different behaviours I have now seen is the one to be expected ?

Cheers.
c.

alec.tron

  • Hero Member
  • *****
  • Posts: 738
And another piece to the puzzle of understanding the inner workings of MusicBee...

Now, around 7 days after setting MusicBee up on a new computer, and letting it idle (seemingly...  i.e. it's open as an application and able to do things in the background [btw,  worth mentioning that I'm still an advocate of the philosophy, that any program spending more than a few minutes on background tasks, should really have a console to be able to see if/what it is doing. As it is, MusicBee is very cryptic/mystic way too often imo]).
Anyhow, now after 'idle-ing' for 15-20 hrs, the Playlist Manager once again shows the 'aggregated view' when I now click on a folder holding multiple playlists.

I would still really love to know if this is intended behaviour or not, and if this is safe to use for re-locating (the same) files across multiple playlists this way.

Cheers.
c.