Author Topic: 'In' and 'outside' MusicBee  (Read 5105 times)

Steven

  • Administrator
  • Sr. Member
  • *****
  • Posts: 34312
no, this is on the computer you normally use and that already has the problem

frankz

  • Sr. Member
  • ****
  • Posts: 3834
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.

frankz

  • Sr. Member
  • ****
  • Posts: 3834
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

Steven

  • Administrator
  • Sr. Member
  • *****
  • Posts: 34312
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

frankz

  • Sr. Member
  • ****
  • Posts: 3834
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!
Last Edit: April 15, 2020, 04:20:14 AM by frankz

Steven

  • Administrator
  • Sr. Member
  • *****
  • Posts: 34312
This has the fix for all other file types:
https://getmusicbee.com/patches/MusicBee33_Patched.zip
unzip and replace the existing musicbee application files

Dryst

  • Jr. Member
  • **
  • Posts: 86
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.



Dryst

  • Jr. Member
  • **
  • Posts: 86
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