getmusicbee.com
Support => Questions => Topic started by: Bizy on March 31, 2019, 11:29:24 PM
-
Hello,
Quite often, I got this feedback message:
"The file(s) being edited have been updated outside of Musicbee - you might have to rescan..."
Why?
What could possibly 'have updated' those files when it's not me?
All those files are part of MusicBee, part of the monitored folters, part of the scanned files. So they are definitely not 'outside' of Musicbee.
Better question might be: what can I do to avoid this?
Thanks for any possible answer.
b.
-
The message means that the tags in the file do not match the tags in that MusicBee library and must be rescanned to pick up those changes. It's a pretty clear message.
It's likely because you're updating the files in one library and opening in another. Either that or you edited them in another tool like mp3tag, but I'm guessing it's the first thing.
It says "outside of Musicbee" but in this case it's "outside of this library." Most people don't have multiple libraries that contain the same files, so the message matches most people's usage.
Did you rescan them like the message said to do?
To answer your question about avoiding it, if you're going to have the same files in multiple libraries you can't avoid it. You need to rescan to pick up the changes you made in one library in other libraries. There's not much to "avoid." It's a useful instruction.
I don't know if "on startup check for missing or updated files" under Library settings would do the rescan automatically for you or not but it's worth checking into.
-
Frank:
It's likely because you're updating the files in one library and opening in another. Either that or you edited them in another tool like mp3tag, but I'm guessing it's the first thing.
I can assure you it's none of those two!!!!
(not using another program NOR doing any changes in another libary on the same file)
I agree it's a pretty clear message, but as I wrote: it's NOT ME changing/updating anything whatsoever...
-
It's likely because you're updating the files in one library and opening in another. Either that or you edited them in another tool like mp3tag, but I'm guessing it's the first thing.
I can assure you it's none of those two!!!!
(not using another program NOR doing any changes in another libary on the same file)
But you said here you were trying to run three different MusicBee libraries, which have some overlap:
I have three libraries (libraries L1, L2 and L3).
I want to keep L1 and L2 separate (reasons don't matter here).
L3 includes L1 and L2.
-
Frank:
It's likely because you're updating the files in one library and opening in another. Either that or you edited them in another tool like mp3tag, but I'm guessing it's the first thing.
I can assure you it's none of those two!!!!
(not using another program NOR doing any changes in another libary on the same file)
I agree it's a pretty clear message, but as I wrote: it's NOT ME changing/updating anything whatsoever...
Really? Because in this post (https://getmusicbee.com/forum/index.php?topic=28307.msg156962) you say you're doing exactly that.
Either way, good luck figuring out your myriad issues.
-
L1 and L2 are totally different.
Tags/album art/lyrics I update in L1 do not affect songs in L2 and the other way round.
L3 contains both L1 and L2.
But I don't do updates in L3.
For now, I only use it to do the backup.
-
It happens while I'm working in one library (especially L2, the biggest library, on an external disk). Not leaving it, not doing anything else...
-
Hi,
Just want to share that I was experiencing the same error, even without multiple libraries and I fixed it with a simple change - perhaps this is unique to the setup I have. Sharing for community benefit. My setup:
1. While, the PC has the MusicBee Library, my scanned folders (media files repository) are temporarily hosted on LAN on an Android media box, over samba.
2. However, Android or a media player running on it - inbuilt or PowerAmp seems to be updating these files, even though PowerAmp is not configured for this specific folder hosting the repository.
3. All I did is that I made the root folder of the repository "hidden" and since then I am not getting the "The file(s) being edited have been updated outside of Musicbee - you might have to rescan..." notice.
4. The final intended location for the repository is a linux based NAS box, where this sort of touching is unlikely.
-
I also get this message 100% of the time. My experience has been it is unreliable and I simply ignore it.
-
Something is updating the music files outside of musicbee eg. just by opening WMP can cause your files to be updated by WMP.
-
Occasionally and randomly I have the same problem, even on newly added mp3 files to the library. I simply ignore it, because apparently everything is fine.
-
Something is updating the music files outside of musicbee eg. just by opening WMP can cause your files to be updated by WMP.
Here is an example that just happened moments ago:
(https://dl.dropboxusercontent.com/s/8rx8cki3sgofbsj/musicbee_file_updated.png)
MusicBee itself updated the file when I lowered the rating from 4 to 3. No other applications or processes have this file open other than MusicBee. The file in question is on my network storage and is an APE file. All I did was lower the rating, skip to the next file in my Auto DJ playlist, followed by clicking Edit in the right click menu for the file in the playlist.
-
MusicBee itself updated the file when I lowered the rating from 4 to 3. No other applications or processes have this file open other than MusicBee. The file in question is on my network storage and is an APE file. All I did was lower the rating, skip to the next file in my Auto DJ playlist, followed by clicking Edit in the right click menu for the file in the playlist.
Could you send me a link to that file
-
I copied the file to my dropbox site. This is a direct download of the file available. It is 33.1MB in size.
https://dl.dropboxusercontent.com/s/gpe18rtstwn9lgs/11-Gloria%2C%20Lonely%20Boy.ape
-
I am not having any issues with that file. I am assuming the file really was updated (you can confirm by viewing it with the tag inspector which is available in the tag editor window).
Could you send me a link to your settings file (help/ support/ view settings)
-
The file was indeed updated exactly how I described in my use case. MusicBee itself updated the rating tag. The question is why is it claiming that this file was updated outside of MusicBee? I actually used to rescan my entire library when I initially saw this message. Now I know it's an incorrect message and to ignore it.
-
If the files are in a designated Media folder on the QNAS, it could be the Multimedia Manager scanning the updated metadata tags in your audio files that is causing the issue.
-
No. They are not. Only MusicBee has modified these files and nothing else touched them.
-
FYI I also get "File has been updated outisde of MusicBee" when I rate songs from a remote install.
My setup:
Music Files in network share \\DESKTOP\Music\Organized\* and Library in network share \\DESKTOP\Music\MB on my desktop computer
Main listening area is via a laptop accessing that library and those files over network share
Now Playing is "Playing Tracks" and I usually rate by clicking the stars, which I've added as a field in the track listing.
I've taken to just rescanning the files via "recently played" when I get to my desktop computer. The ratings are there, but MB thinks something else wrote them.
Interestingly, if I rate the files using the android Remote app connected to the laptop install, they do not show up as "Updated Outside of MusicBee" Only the ones I update in the MB interface do.
If I update tags using the tag editor at the laptop, this does not happen. Only if I rate a song by clicking the stars.
-
That happens to me when I update an album but MusicBee suddenly closes. My library is on auto-organize.
-
If I update tags using the tag editor at the laptop, this does not happen. Only if I rate a song by clicking the stars.
only when you rate the song while it is playing?
Also how quickly are you opening the track in the tag editor - while it is still playing and sever seconds after it has finished playing?
-
I will play with it when I get a chance. I want to say it's only when I rate a song as it is playing, but I can't confirm 100% that it doesn't happen if I rate the song after it is done playing or before it plays as well.
Are you asking when I notice that I am getting the flashing ! and message that it's been updated outside MusicBee? That I do know. It doesn't matter. I can open the tag editor right after and I will get that message or I can open the track in tag editor several hours/days/weeks later and I will also get the message.
If I edit the track in tag editor at the laptop and save, then it doesn't happen whether I do it as the song is playing or after the song is over.
-
OK. I did a quick experiment. Played some songs on the laptop and then closed MB there and came over and opened it on the Desktop to check tag editor.
Rated song when it was done playing: Got ! message
Rated song as it was playing: Got ! message
Rated song in the upcoming tracks before it played: Got ! message
Rated song in MusicBee Remote as it was playing: No Message
"Everyone" has "Full Control" over the network share. Read, Write, Modify, etc.
-
Two more:
Rated song as it was playing in the player panel rather than track list: Got ! message
Rated song by opening tag editor and rating it there while playing: No Message
-
I cant reproduce this but I have a theory why it might not work. If you are able to do a test on a file on the local computer then that would provide useful info
-
I can do a test on the host computer.
-
if anyone is happy to run a debug version to see whats going on then let me know
-
Sure will.
-
https://www.mediafire.com/file/l544dztc32uik3p/MusicBeeDebugFileUpdate.zip/file
unzip and replace musicbee.exe
after setting the rating for a file and checking in the tag editor, can you send me the new info at the end of the error log
-
Just to be clear, this is on the host computer and not the laptop "listening" computer, right?
-
no, this is on the computer you normally use and that already has the problem
-
OK, so the one where I rate the tracks. It'll be about 24 hours before I'm able to get the results back, but I will report back then.
-
Notably, the debug version did not display the flashing error when I opened the tag editor on the laptop immediately after playing and rating tracks on the laptop. This had not been the case before.
4/13/2020 6:40:23 PM - tag editor check date cached=1/20/2018 6:47:43 AM,636520276639497386,file=1/20/2018 6:47:43 AM,636520276639497386
4/13/2020 6:48:32 PM - save rating: \\DESKTOP\Music\Organized\The Thermals\(2016) We Disappear\04 - If We Don't Die Today.mp3
4/13/2020 6:48:32 PM - url=\\DESKTOP\Music\Organized\The Thermals\(2016) We Disappear\04 - If We Don't Die Today.mp3,before=1/20/2018 6:47:43 AM,after=1/20/2018 6:47:43 AM
4/13/2020 6:48:32 PM - save rating: \\DESKTOP\Music\Organized\Alejandro Escovedo\(2016) Burn Something Beautiful\08 - Beauty of Your Smile.mp3
4/13/2020 6:48:32 PM - url=\\DESKTOP\Music\Organized\Alejandro Escovedo\(2016) Burn Something Beautiful\08 - Beauty of Your Smile.mp3,before=4/24/2019 3:14:30 AM,after=4/24/2019 3:14:30 AM
4/13/2020 6:48:42 PM - tag editor check date cached=4/24/2019 3:14:30 AM,636916724702656175,file=4/24/2019 3:14:30 AM,636916724702656175
But then I put the debug version on the desktop computer, opened the tag editor for the tracks I had played and rated before on the laptop, and they both showed the flashing error.
4/13/2020 6:53:31 PM - tag editor check date cached=4/24/2019 3:14:30 AM,636916724702656175,file=4/13/2020 10:48:34 PM,637224149145665531
4/13/2020 6:53:34 PM - tag editor check date cached=1/20/2018 6:47:43 AM,636520276639497386,file=4/13/2020 10:48:34 PM,637224149145089556
Then I closed MB on the desktop, went back to the laptop and opened it, and checked the tracks over there. Now they are showing the error on that machine, too.
4/13/2020 6:57:03 PM - tag editor check date cached=1/20/2018 6:47:43 AM,636520276639497386,file=4/13/2020 10:48:34 PM,637224149145089556
4/13/2020 6:57:07 PM - tag editor check date cached=4/24/2019 3:14:30 AM,636916724702656175,file=4/13/2020 10:48:34 PM,637224149145665531
-
It looks like its what I feared it might be - that the server is not immediately updating the file modification date.
Could you try this non-debug version for mp3 files only to see if it makes a difference. If it works I will change it for other files types.
If it doesn't work I will probably remove the check from the tag editor for files on network drives
https://getmusicbee.com/patches/MusicBee33_Patched.zip
unzip and replace the existing musicbee application files
-
It works! I played and rated songs on the laptop, closed MB there, opened MB on the desktop and checked the tag editor to find no flashing error. Beauty, thanks!
-
This has the fix for all other file types:
https://getmusicbee.com/patches/MusicBee33_Patched.zip
unzip and replace the existing musicbee application files
-
Thanks for the fix. My MusicBee version is now 3.3.7411. I am not sure if only rating was addressed with this fix. I have not reproduced the issue with rating. However, I just edited a media file on my NAS to set it for exclude from playback: Full Ban. After doing this, I see the same issue where it shows another application modified the file. No other applications did though.
-
This issue happened for me again earlier today with lowering rating for a currently playing song again.
The change may have lessened the likelihood of it happening, but it still happens under version 3.3.7411