No, but I am re-running it now to see what happens.
You sure? It remembers files you added manually from sync-to-sync, so even if you did this previously (when first figuring the system out) it won't ever remove them from the sync list until
you remove them from the sync list. Just to be clear. When you drag to the little sync list icon in the Action Window (or drop files directly on the device in the Tree), it adds them for the next sync, and
all subsequent syncs, until you remove them.
Deleting them off of the device you synced to won't do any good, because the server will just re-sync them again next time. You have to find them (turn off all your other lists, like you did) and remove them from the sync list.
10.6 hours
You'll have less trouble with long transfers if you take a few steps.
1. Use a set of Smartlists to drive the sync, and include in some of them a "core group" that changes infrequently. Those files will get synced, and stay there, so you won't have to update them as often (or at all).
So, for example, in my lists, I have some "shuffles" that sync over (which are loosely defined by genre) and change all the time. But I also sync some Favorites and Top Hits lists (4+ stars and lots of Plays, respectively). This ensures I always have my set of "good stuff", first of all... It kind of prejudices my sync list towards the "good". But, because those lists don't change very much or very quickly (things might shift around in "ranking" on the lists, and new things get added, but overall they're pretty stable), they only get synced over once. I also use some sets of manual lists
You can even go further. I have some of my shuffle lists, set (via the ~mix modifier) to use a percentage of the tracks included in the other Smartlists (the rarely-changing ones). So even those are "biased" to use tracks that are probably already in the sync list.
2. De-select the option to Resync if Date Modified has changed, if not required.
You probably don't need this, especially if you're syncing to MC and you include the shiny new MPL playlist option. The MPLs generated include all metadata for the files, including any changes. If you import the MPLs (or the database.mpl file it makes automatically anyway) then it will sync over any changed metadata.
The thing is, if you have writing to tags enabled, especially if you enabled additional non-default tags to store in the files, then it has to completely re-write the files every time the smallest tagging changes happen. If, for example, you write [Last Played] or [Number Plays] to the files? Then each time a file is played, then the file date will have changed, and it'll have to re-sync.
So, disable that if you don't need it. If you don't edit your files much after importing them into MC, then you can probably leave that turned off.
3. Limit Conversion
Consider converting fewer files. The conversion time often more-than-doubles the length of time it takes to transfer each file. Use the Conversion > Mode > Audio: Specified output format only when necessary option. If you're worried about taking up too much space on the tablet's relatively small disk, and so converting your high-quality FLAC library to smaller MP3s on purpose, then set the Files, Paths, and More > Supported File Types option to a semicolon separated list of all the various lossy compressed formats. For example, I use this:
mp3;mp4;m4v;m4p;m4b;m4a;m4r;jpgThat way, it doesn't waste time converting my things that are already MP3s. Yes, it will save some space if you downconvert the relatively high-quality MP3 or M4A files you have in your Library, but really you're getting "bang for the buck" on size savings from converting from FLAC to MP3 -v4 or whatever,
not from going from MP3 -v2 to MP3 -v4. Mostly wasting time for saving a gigabyte or three (at best). Plus, going from lossy to lossy is inherently "re-damaging" the files, and doing it twice is bad. So, just copy over your M4As and MP3s as they are, and convert the other, really big stuff.
4. If you can, use conversion cache. This costs disk space on your server machine, but saves time.
5. Consider doing it "backwards", and "pulling" from the server rather than "pushing to" the device.
This is actually what I do. I
do not sync using MC's Handheld tool directly to my laptop or other network devices. Especially with Windows file sharing, for whatever reason, copying
from a network share (from the tablet or other device to itself from the network) is way faster than writing
to a network share. I have guesses why this is the case, but for whatever reason, it is true. Plus, this will be more reliable. Copying via MC's Handheld tool, to a destination over the network is just too slow if you have a large sync list.
Instead, I sync to a special "Handheld Cache" folder on a disk connected directly to my main server, and then have my network devices sync themselves to this folder. This does "cost" disk space as well, but it makes syncs faster, and much more reliable. Plus it has the benefit that it is asynchronous, so you don't need to have your device and your server "ready to go" all at the same time. You can sync this "virtual handheld" on the server whenever you want. And then set up the device to always keep itself synced to that folder as it feels like it. And, you'll probably have fewer sync errors to boot (because the tablet goes to sleep and turns off wifi or whatever).
I use GoodSync to do this on my Laptop. It is great. I use the feature to auto-sync when the folder connects, so that my laptop just automatically syncs itself to this folder every time I come home. I don't have to "start it up" or get it ready or whatever... I just plug it in, and GoodSync does it when I'm not thinking about it.
If you do this last bit, I'd recommend you do not keep this Handheld Cache folder on the same disk as your regular media disk as well. This also makes the syncs faster, assuming you're not using SSD storage for media files (because it is faster to copy from one disk to another, than to copy from one disk onto itself, which makes the drive twice as busy moving those heads back and forth). Plus, it gives you one more "oh crap everything broke and my backup strategy was flawed and now I'm hosed" backup spot.
This will particularly help you if you sync lots and lots of little files.