As I mentioned before, I was able to sync that iPod with no issues to Musicbee, without using any driver plugin(the serial number and name would show up in MB, and the iPod would show up in file explorer as an iPod, not a hard drive. On a second, more depressing note, I recently had to replace the logic board on my iPod video 5.5 due to a battery issue, and I replaced it with an identical board. The thing that confuses me the most about this is that for my iPod Video 5.5, I was able to convert on-the-fly with no issue, and that was without the plugin. I have a few updates(and mostly bad news) surrounding this problem now.Īs far as the plugin, I've tried running iTunes and Musicbee in compatibility mode, admin mode, and uninstalling iTunes. That will definitely speed up the sync on a large library. Maybe try running it in administrator mode, that might get past a permissions issue.Įdit: Also its a good idea to exclude antivirus.Ĭ:\Program Files(x86)\itunes (might be C:\Program Files\iTunes for the 64 bit version)Īnd the folder where your music is stored. There is nothing in the code that could be messing that part up and it's working for me so best guess is some kind of permission issue or settings problem that is preventing MB from creating the converted file.Īre you using the portable version of MB? That error means the filename MB is returning doesn't exist. If it doesn't match, MB just returns the same filename, if it does match, MB converts the file to the temp folder I got you to check earlier and returns the filename of the converted file. If everything is on SSD's you will probably see a much better result.Įach file is sent to MusicBee to see if it meets any of the conversion criteria. 22 minutes for that many songs is more realistic sync time if you store your tracks on a mechanical drive or network drive. I'm just going to assume it's a quirk with iTunes.Īnyway, all this overly long post is trying to say is, ignore my previous post where I said 36,000 songs took 8 minutes. If I restart MusicBee and iTunes without restarting windows it still performs the sync quickly so it's windows caching that is speeding it up, not something with either program. If I restart the PC and do a full sync it takes 22 minutes again and thrashes the HDD. (I assume because whatever info it's accessing got cached by windows in the first sync.) I do another full sync straight after, no HDD activity occurs and the sync takes less than 10 min. I do a full sync, HDD gets thrashed and it takes about 22 minutes for 36,000 songs. So here is what happens when I do a sync and no sync changes need to happen, it's just going through the database to check if something needs to be synced. If the files have previously been synced the HDD shouldn't need to be accessed at all if metadata refresh is disabled. I'm not sure why as technically the sync process is just sharing information between the MB database and the iTunes database (both stored on NVME C: drive). Disabling metadata refresh certainly makes it faster but the mechanical drive where my music is stored still gets thrashed during the sync but only the first time. No matter what I do, I can't stop the sync process from accessing the actual media files (track files). Just a note about some of the estimates I have listed previously for sync times, I may have been a bit optimistic due to file caching (I think). Just tick the delete files option, untick the "confirm deletion" box then untick the deletes option again. This version will throw an error if you have "delete files that are not on the auto-sync list from the device" unticked but the "confirm deletion" box is ticked, like in the picture below. End of the day it's not a huge deal, the plugin still works fine, it's just a display issue. The logic above will assume 50 tracks need to be deleted instead of the required 150. User unticks the playlist of 150 tracks and ticks another playlist of 100 completely different tracks. Tracks in itunes - 200 made up of 2 playlists of 50 tracks and 150 tracks. Something like the following would trigger it. In certain situations this logic will fall over and the progress bar will go over 100%. It's not perfect but it's the best I can do without a major rewrite (I'm sure this time). If tracks to be deleted is less than zero it's assumed to be zero. The basic logic is No of Tracks in iTunes - Tracks to be synced = Tracks to be deleted. The best I can do is make an assumption on the number of deletes based on the number of tracks to be synced and the number of tracks in iTunes. The counts displayed will now be more accurate (not include playlists) and deletes are handled a little better but still not perfect.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |