Author Topic: Error when connecting MTP device (v2.5)  (Read 12005 times)

Steven

  • Administrator
  • Sr. Member
  • *****
  • Posts: 34364
this should address the folder.jpg file contention. For the progress indicator i can see if the encoding or volume leveling fails it doesnt increment the progress and this version fixes that if that was the cause.
As to the crash, i dont know as i abort synching all the time while testing and never had that problem

unzip and replace the existing musicbee files:
http://musicbee.niblseed.com/V2_5/MusicBee_Exe_Patched.zip

Ellis

  • Newbie
  • *
  • Posts: 15
I had made a test after this update.

http://i.imgur.com/N3gYLCa.png
the message under the indicator is Encode Failed - cause by another process is using the file 'C:\Users\EllisCheng\AppData\Local\Temp\folder.jpg', so it could not be accessed. It is file contention, but I don't have any idea what process would occupy that file, I had go to that directory once the error appears, there does not exist such a file named folder.jpg, I also checked for that path after the sync, still no folder.jpg there.

http://i.imgur.com/hohHSQT.png

The first screenshot is the error message, though the song encode failed is not that one, the status had some problem when I scrolled up to that position, the file that failed to encode is BRIGHT STREAM.

The progress still stays as the second screenshot for a long time but will continue just like I mentioned before, no other encoding or volume leveling fail happened except that one.

http://i.imgur.com/UOBslPv.png
This is the after all report, looks like musicbee will have a retry on the file which failed to encode, so BRIGHT STREAM appeared twice, and I had take a look under the path where it should be saved, it's perfectly converted and put to there.

Steven

  • Administrator
  • Sr. Member
  • *****
  • Posts: 34364

Ellis

  • Newbie
  • *
  • Posts: 15

Steven

  • Administrator
  • Sr. Member
  • *****
  • Posts: 34364

Ellis

  • Newbie
  • *
  • Posts: 15
The sync result is fine, only with these warnings. That won't be a problem. Thanks!