Windows > Third Party Plug-ins, Programs, and Skins
MC iTunes Synchronizer (using MC with an iPhone or iPod Touch) [v6.0.2]
prod:
--- Quote from: escaflo on February 09, 2013, 10:00:54 am ---Hi Prod,
I thought by choosing the playlists to sync over, I am suppose to be only syncing the playlists songs?
That's what I want to do, to sync only the playlist songs and not all 65,000 songs.
The problem is I can't figure out how to do that.
Thanks for all the help and this is a great program. Just that maybe it is the stupid me that can't get it to work the way I needed.
--- End quote ---
Hi Escaflo
Thanks for the nice feedback - as Winnie says you can do this with the /Playlist argument. Not very intuitive I guess, there seems to be a common misunderstanding that checking the playlists alters the scope of the sync. If /Playlist isn't specified the whole library is sync'd. Any playlists checked are simply playlists to be exported to iTunes.
So, MCiS will COMPLETELY ignore any tracks not in the playlist specified using /Playlist. For instance, if a track appears in a checked playlist, but is not in the playlist specified in the /Playlist command line argument, the track will NOT be in the resulting playlist in iTunes.
I hope that's a little clearer.
PS: You can specify smartlists using /Playlist, when I talk of playlists, I'm not making a distinction between playlists and smartlists.
simonmason:
So if i specify:
/Playlist:"PlaylistName" /startsync /exitaftersync
It should only sync that playlist?
I am currently running with this command line and it is analyzing all tracks. Does it have to perform this step? Thanks.
prod:
It will sync only items within that playlist, yes.
You need to specify the full path to the playlist. So if the playlist is located within a number of groups, such as:
Group1
Group2
AnotherGroup
MyPlaylist1
You would specify;
/Playlist:"Group1\Group2\AnotherGroup\MyPlaylist1"
More info here:
--- Quote from: prod on April 30, 2009, 11:38:37 am ---The following command line arguments can be used:
* /StartSync - starts synchronization immediately on startup
* /ExitAfterSync - exits once synchronization is complete
* /RunMinimized - runs minimized
* /ExportAggregatesOnlyFrom:MC - Overrides the aggregated field calculations and performs a simple export from MC to iTunes of these fields instead
* /ExportAggregatesOnlyFrom:iTunes - Overrides the aggregated field calculations and performs a simple export from iTunes to MC of these fields instead
* /LibraryName - The name of the MC library to sync
* /ViewScheme - The MC view scheme path to use. Only tracks in this view scheme will be sync'd.
* /Playlist - The MC playlist (or smartlist) path and name to use. Only tracks in this playlist will be sync'd.
* /Settings - use an alternative .settings file, if not specified uses the default MCiTunesSynchronizer.
You can not specify both a view scheme AND a playlist. If neither are specified the whole library is sync'd.
Argument usage:
MCiTunesSynchronizer.exe [/StartSync] [/ExitAfterSync] [/RunMinimized] [/ExportAggregatesOnlyFrom:[MC|iTunes]] [/LibraryName:"sss"] [[/ViewScheme:"vvv"] | [/Playlist:"ppp"]] [/Settings:"xxx"]
Where sss is the name of the library to use, vvv is the name of the viewscheme (e.g. "Audio\Albums\MyView"), ppp is the name and path of the playlist (e.g. "Tasks\Miscellaneous\MCiS Sync Playlist"), and xxx is the name of the settings file.
--- End quote ---
glynor:
--- Quote from: prod on February 09, 2013, 07:33:30 am ---I support it when required and have the time. There's little I can do about iTunes being slow/crap.
A trick is to keep iTunes thin by only syncing over the files/playlists you want on your device. You can also reduce the scope of the sync by using the /Playlist command line argument. Both these things can drastically reduce your sync time.
--- End quote ---
I found, with my system, just the opposite... If you have a reasonably small number of files you want to get into iTunes, and those stay reasonably static, then yes, don't do more than you need.
However... If you are trying to send a "changing shuffle" of files from MC to iTunes, then you're going to have trouble. Because, with each sync, it has to essentially rip everything (or mostly everything) out of iTunes, and then ingest new stuff into iTunes. You want to avoid the "ingest into iTunes" phase as much as is possible, because that's the part that is slow. Updating Playlists (even big ones) is pretty fast.
So, another solution is to sync your WHOLE library over to iTunes, once. That'll take forever (mine took 16 hours or so). But once it is done, you can accomplish handheld-sync related tasks (shuffling and whatnot) via Playlists that you have MCiS sync to iTunes, rather than adding and removing files from iTunes. As I mentioned, Playlist sync is fast, if the files themselves didn't move.
That way, MCiS only needs to "change" iTunes when you acquire new content, which should be relatively static (just adding the new/changed stuff since the last sync).
You can do this in concert with using the special MCiS File Key tag and having MC sync your full library to a "handheld" if you want to avoid having iTunes "touch" your "real" files, and to deal with conversion from non-supported file types (FLAC and whatnot).
prod:
--- Quote from: glynor on February 10, 2013, 01:15:42 pm ---I found, with my system, just the opposite... If you have a reasonably small number of files you want to get into iTunes, and those stay reasonably static, then yes, don't do more than you need.
--- End quote ---
Thanks glynor, yes you're right, I guess you've got to find the best method to suit your own setup. I tried to make MCiS largely flexible for that reason.
--- Quote from: simonmason on February 10, 2013, 01:06:12 pm ---I am currently running with this command line and it is analyzing all tracks. Does it have to perform this step? Thanks.
--- End quote ---
Sorry Simon missed that question - no it should only analyse the tracks in the playlist you specify.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version