getmusicbee.com
Support => Portable Devices => Topic started by: psychoadept on December 23, 2024, 05:36:25 PM
-
I've noticed weird behavior for a while with playlists not being on my phone when I would expect them to be. I wasn't sure at first whether MusicBee was the issue, but after monitoring a few syncs (wired) today and checking the results, something is definitely not working as exepcted.
There should be 19 playlists. MuiscBee always says it syncs all of them, but it's not. Sometimes it looks like it's adding the playlists that aren't there and removing the ones that are. I started one round with 2 playlists in the folder (the result of the sync before that), and ended with 17. The two that were there at the start were missing.
But on the next run, I removed all the playlists through the phone and synced again. That time I ended up with 1 playlist on the phone. Since then, I've gotten none. I've checked that they're not elsewhere on the phone, but nothing turns up. Any ideas?
...
More follow-up: I restarted the phone, then changed the playlist folder in the sync settings. I got 14/19 in the new folder. Changed it back, synced again, 14/19. Not exactly the same 14, either.
-
I'd be interested in seeing a screenshot of the preview window.
For existing playlists, what does it show under the "action" column?
Under the sync settings, you wouldn't happen to have the 3rd option from the top enabled, right? (the "delete files that are not...")
Are these autoPlaylists by the way?
Still on the device settings, maybe a screenshot of the Music section and the 'playlist storage' too.
-
I'll see if I can get a screenshot later. It's a mix of static and auto, I can't tell that that makes any difference. It's set to delete files, and it does that correctly for audio files. It always claims to have synced all 19 playlists. Makes me wonder if the phone isn't communicating updates correctly.
The computer is Windows 11 and the phone is an S22 with Android 14, for what it's worth. All internal storage on the phone.
-
A sync preview shows 19 playlists that all say "Copy." They range in size from <2k to >38k.
Here's the settings:
(https://i.imgur.com/XyzDl02.png)
I can't say exactly when this started, but I first noticed it at least a couple of months back.
-
Sorry, I can't say I have a clue what's going on. Best thing would be to isolate things a little bit:
- Fresh portable installation.
- A small sample of 5 tracks or so
- About 5 playlists maybe, each with a single song
- Then turning off the ...delete files... setting mentioned earlier
- then rerunning the sync on a playlist path outside the music files folder
-
What happens if you change the path to the playlists from MusicBee\Playlists to MusicBee\Music\Playlists?
Personally I want my playlists (on my S22) to be in their own directory, but I've found that starting with Android 14 (or maybe 13) I had to have the playlists directory under the music directory. I didn't want to do it, but it cleared up all playlist syncing issues when I did.
-
This is similar to the issue I'm having.
-
I'd say it's probably a device issue more than a Musicbee issue.
Maybe try a different USB cable and plug it into a USB 2.0 port instead of USB 3.0
-
I'd say it's probably a device issue more than a Musicbee issue.
Maybe try a different USB cable and plug it into a USB 2.0 port instead of USB 3.0
I don't have a choice between 2.0 and 3.0 but I do have a choice between A and C. I'll see if switching helps. If not, I'll try phred's suggestion.
-
Personally I want my playlists (on my S22) to be in their own directory, but I've found that starting with Android 14 (or maybe 13) I had to have the playlists directory under the music directory. I didn't want to do it, but it cleared up all playlist syncing issues when I did.
Android 13 is when scoped storage was fully implemented and you couldn't add a flag in your app to ignore it anymore. The all files access permission gets around it but google is very strict on what apps it will allow on the play store with that permission. I don't think it has a good time when you mix different media types in the same folder which is why the version of the wifi sync app on the play store has issues with artwork that isn't embedded.
But all of that should only effect apps on the phone, it "shouldn't" interfere with wired file transfers. Once you set your phone up for file transfers your PC has full read/write to the external storage on the phone.
Maybe it has issues with folders created by the PC and not on the device. Scoped storage usually just allows apps access to folders\files created by the specific app so there could be some quirk with folders created by the PC.
-
Well, I tried changing USB type and got 13/19. Tried phred's sunfolder suggestion and got 17/19. 🤷🏽
I guess I will try a new installation and see if that makes any difference.
-
@Psychoadept what do you use to play the playlists on your phone? I use VLC for Android and have a similar problem:
I tried syncing playlists to my Samsung S10 and only half of them appeared complete on my phone (in VLC). For example: MusicBee has 200 songs in one of my PC playlists, my phone only showed 116.
After creating a new playlist and renaming it, but putting the same 200 songs in there, it synced more, but still not all. (131/200)
I repeated this test and it's still 131/200.
When I open the playlist on my PC with a text editor, it does show that all 200 paths to the files are there and are all the correct format.
When I view the playlist on my S10 as a file in VLC (so via the 'browse tab' in stead of 'playlists'), it says that there are 200 songs in there. (But I can't play it from there.)
Only when I look at the playlist on the 'playlists' tab, it says there are only 131 songs, and only shows that many when I press play.
I re-installed VLC on my phone, but it still has the same problem.
-
I use gone mad music player, but the issue isn't the player. I've been checking the actual folder in the file browser while testing. I haven't noticed any problems with the playlist contents, I just can't get all the playlists to sync at once for some reason.
-
are you saying that if you check with the android file explorer some of the playlists are not there? and if they really are all there and you edit the .m3u file, do the music file paths look ok?
-
This probably isn't the issue but figured it's worth mentioning.
I found quite a few posts where file copying would just cut out with no errors. They were all related to the path length. From what I can find the max length for android is 255 bytes. Which makes the max character length somewhere between 127 and 255 depending on the encoding. Unicode characters are 2 bytes.
And don't use any of these in the path - |\\?*<\":>/'
edit: actually some utf-8 (default) characters can use 4 bytes so the range is actually 63 to 255. It would be a pretty funky file path to use all 4 byte characters though....
-
are you saying that if you check with the android file explorer some of the playlists are not there? and if they really are all there and you edit the .m3u file, do the music file paths look ok?
Are you asking me or basseken?
All my results have been based on the Android file explorer. Whatever playlists are there load and work fine in gone mad, I've never had a reason to think the playlist contents were incorrect.
I found quite a few posts where file copying would just cut out with no errors. They were all related to the path length. From what I can find the max length for android is 255 bytes. Which makes the max character length somewhere between 127 and 255 depending on the encoding. Unicode characters are 2 bytes.
And don't use any of these in the path - |\\?*<\":>/'
No, I don't think that would be relevant here. Some of the audio files have longish names, but limits are already built into my file naming. Playlist names are very short, 3 characters up to a few words, like "Best of Christmas."
-
I have found the MTP protocol is quite flaky on some android devices. As an experiment, i have added a small delay after the playlist is written to see if that helps
https://getmusicbee.com/patches/MusicBee36_Patched.zip
also could you check the error log for any entries that start with "Add playlist"
-
I have found the MTP protocol is quite flaky on some android devices. As an experiment, i have added a small delay after the playlist is written to see if that helps
https://getmusicbee.com/patches/MusicBee36_Patched.zip
also could you check the error log for any entries that start with "Add playlist"
I have implemented the patch and still have the same problem: playlists only partly syncing.
I checked the %appdata% ErrorLog.dat , and it had no entry that started with "Add playlist".
Some other things I found on the forum, but also didn't work:
-Switching around "\" and "/" in the device options path names.
-Exporting the playlists as ".m3u8" in stead of ".m3u" files (then all the playlists were completely empty).
Could it be something with an arbitrary file amount limit? All my playlists with 74 songs or less are syncing correctly, yet:
My 200 one is stuck at 131
My 305 one is stuck at 230
My 966 one is stuck at 263
-
Could it be something with an arbitrary file amount limit?
it might be. Try this version
https://getmusicbee.com/patches/MusicBee36_Patched.zip
-
I implemented the patch, this is what happened (all with relative paths, bc without it, nothing shows up besides sub-maps):
Syncing playlists as .m3u:
-Nothing shows up on phone's playlist player.
-Also no files when I check via PC.
-I can export the m3u files to desktop and then move them to phone, but, as always, I can only see the playlist content amount in file explorer, not in the playlist player (there it says it's an empty playlist).
As .m3u with sub-folders:
-Same as above, except the sub-folders show up with the right amount of songs, but no .m3u files.
As .PLA (I don't think I had this option before the patch?):
-The playlists show up, just like they originally did with the m3u sync: only the smaller playlists were complete, the rest is missing songs.
-The playlists are missing the exact same amounts of songs as before the last patch.
As .PLA with sub-folders:
-The playlists show up, the smaller ones the same as above, but the larger ones still have missing songs. I deleted everything, synced again and now they still have the same songs missing, but show every synced song twice, like the phone adds up the .PLA and .m3u or any combination with the sub-folders, yet still only so with the larger playlists, everything 74 songs and under -> still normal.
-Sub-folders have the right amount of songs if I check via PC.
.WPL:
-Doesn't show up, just like .m3u
I think I got it to work during one of the first tries when I used the .PLA container with sub-folders, but after I did other tests, I couldn't recreate it anymore...
And sub-folders wouldn't be a great solution since it nearly triples the memory size needed for the songs.
-
I implemented the patch, this is what happened (all with relative paths, bc without it, nothing shows up besides sub-maps):
I think your issue might be different to psychoadept as you are stating that songs are missing as well as playlists. Your issue could be due to the character length problem I previously posted about.
Instead of checking in VLC, check the actual folder on the device and see if the playlists copy over to the playlist folder you have set in device settings.
-
I implemented the patch, this is what happened (all with relative paths, bc without it, nothing shows up besides sub-maps):
Syncing playlists as .m3u:
-Nothing shows up on phone's playlist player.
there was a mistake i made - try this one
https://getmusicbee.com/patches/MusicBee36_Patched.zip
-
I implemented the patch, this is what happened (all with relative paths, bc without it, nothing shows up besides sub-maps):
Syncing playlists as .m3u:
-Nothing shows up on phone's playlist player.
there was a mistake i made - try this one
https://getmusicbee.com/patches/MusicBee36_Patched.zip
Fixed it for me! Thank you for all your work
-
Fixed for me as well!
Thank you!
-
I implemented the patch, this is what happened (all with relative paths, bc without it, nothing shows up besides sub-maps):
Syncing playlists as .m3u:
-Nothing shows up on phone's playlist player.
there was a mistake i made - try this one
https://getmusicbee.com/patches/MusicBee36_Patched.zip
Is this patch also in the most recent version? I am getting the error again (it may have never fully went away). Im getting about half my playlists. I may have thought it was fixed as I lucked out on first sync and it synced the main playlist I was looking for
It also removes some playlists if they dont sync over. According to musicbee everything syncs fine and is "completed"
I am currently on 3_6_9171, Galaxy S24 Ultra Android 15 (which is Samsung's beta at he moment)
-
Is this patch also in the most recent version?
Yes, patches always brought forward to new(er) patches/releases.
-
Is this patch also in the most recent version?
Yes, patches always brought forward to new(er) patches/releases.
That is what I would assume, so about half my playlists are still not syncing over, at least on Android 15, my old phone with Android 10 is fine
-
I'm also running into this on two Samsung phones (S10e on Android 12 and S25+ on Android 15). Using two different computers.
The music all syncs correctly, but the playlists won't copy. On earlier versions I was getting the same behavior where it would randomly copy some playlists and not others. Playlists are a mix of .mbp and .xautopf, and they are being synced as .m3u8. Phones are connected via USB.
Using 3.6.9177 and 3.6.9178
From ErrorLog
2025-02-15 4:34:33 PM - Add playlist "D:\Music\MusicBee\Playlists\Devices\Phone\Meditation\name.xautopf" Stream does not support reading.
2025-02-15 4:34:33 PM - Stream does not support reading.
-
2025-02-15 4:34:33 PM - Add playlist "D:\Music\MusicBee\Playlists\Devices\Phone\Meditation\name.xautopf" Stream does not support reading.
2025-02-15 4:34:33 PM - Stream does not support reading.
is should be working now
https://getmusicbee.com/patches/MusicBee36_Patched.zip
-
is should be working now
https://getmusicbee.com/patches/MusicBee36_Patched.zip
Yep, it is. Thanks.
-
Well, apparently, it's not quite working.
On the Android 12 device it worked correctly. On the Android 15 device it still only synced a subset of the playlists that were selected.
Samsung Android 15 seems to be the common factor so far for the two of us having issues.
-
Well, apparently, it's not quite working.
On the Android 12 device it worked correctly. On the Android 15 device it still only synced a subset of the playlists that were selected.
Samsung Android 15 seems to be the common factor so far for the two of us having issues.
Yep, can get it to work on Android 10 but not 15. I end up just syncing to my old phone, and then uploading those playlists to the cloud and download them on my current phone
It wouldnt be so bad if the playlists that arent synced stayed on device if already there, but they seem to disappear/get deleted
-
I was going to suggest maybe Musicbee could change to using ADB copying instead of MTP.
There is an app here that implements it - Link (https://github.com/T0biasCZe/AdbFileManager)
The source code is there and I can't see any limitations listed for using it.
But I just noticed USB debugging needs to be enabled on the phone for ADB to work so maybe not that practical.
-
But I just noticed USB debugging needs to be enabled on the phone for ADB to work so maybe not that practical.
I imagine most people who are using musicbee to wirelessly sync and keep music library would be able to turn on debugging quite easily
-
But I just noticed USB debugging needs to be enabled on the phone for ADB to work so maybe not that practical.
I imagine most people who are using musicbee to wirelessly sync and keep music library would be able to turn on debugging quite easily
Giving any 3rd party code ADB access isn't really a great idea though.
What is most likely the best option would be using something like an FTP SFTP/SSH server on the phone (of which there are a few) and then using something on Windows to map that as a drive letter (of which there are a few). Then you could just easily sync as a Virtual Device. And since it's using basic Windows FS stuff, it avoids all the stupid MTP problems, and it also avoids some of the wifi sync issues by reversing the direction. But you would lose play count/rating merging, if that matters to anyone.
-
OK, now that Samsung has released it's first update to the S25 phones with A15 I thought I'd try again. I also used the latest 3.6.9189 patch.
And it synced all the playlists correctly now! So, like we suspected, it seems it was more of a Samsung bug than an issue with MB after Steven made the other fixes.
-
I apologize it's taken me so long to get back to this. I can report that with MusicBee 3.6.9202 P, on three consecutive syncs I got 17/17 playlists, 16/17 playlists, and 1/17 playlists. It looks like I'll have to try one of the workarounds suggested.
-
Hey there,
I was having a very similar problem with Musicbee saying it had synced all my playlists to my DAP running android, and when I looked in the file explorer, multiple playlists were not there. I have some playlists that are several thousand songs, and a couple of those were not carrying over, and then randomly some of the smaller ones. Also another weird behavior was that the syncing process would slow to a crawl once it got to syncing the actual playlist files themselves once all the music had been copied over.
I changed one setting and suddenly the issue has been fixed so I want to share it. I changed the playlists being synced to the DAP from .m3u files to .m3u8 files, and they suddenly work fine every time and they get moved over almost instantly. Not sure if this might help but I wanted to share since this thread is what started me playing with setting trying to figure out what was going on.
-
Hey there,
I was having a very similar problem with Musicbee saying it had synced all my playlists to my DAP running android, and when I looked in the file explorer, multiple playlists were not there. I have some playlists that are several thousand songs, and a couple of those were not carrying over, and then randomly some of the smaller ones. Also another weird behavior was that the syncing process would slow to a crawl once it got to syncing the actual playlist files themselves once all the music had been copied over.
I changed one setting and suddenly the issue has been fixed so I want to share it. I changed the playlists being synced to the DAP from .m3u files to .m3u8 files, and they suddenly work fine every time and they get moved over almost instantly. Not sure if this might help but I wanted to share since this thread is what started me playing with setting trying to figure out what was going on.
I just got a brand new Samsung Galaxy S25 and had the same sync problems as everyone here. Syncing music files was lightning fast and stable as you would expect, but as soon as it began copying playlist files, it was a slog. Even with the latest patched version 3.6.9245. But when I changed the playlist format from M3U to M3U8 it worked like a charm. It took merely seconds and all 60 playlists were copied successfully :-*
-
I must have laughed too soon, because the next sync again resulted in a painfully slow sync process for the playlists, as well as numerous error messages.
The requested value cannot be determined. (Exception for HRESULT: 0x802A0006)
The shutdown function has already been called for this object or for the object that is the owner of this object. (Exception of HRESULT: 0x802A0002)
:'( Has anyone had similar errors and been able to fix them permanently?