Export to iTunes

[nynaevelan]

Ok I ran a test and all the playcounts are not being imported into MM when I use the sync and recover because it is skipping the tracks that are not a part of the playlist. Here is what I did.

1. Played various tracks from 4 different playlists in itunes.
2. ran sync and recover and entered one of the playlists which I exported to itunes, it only updated the 5 tracks which are in the playlist, the other 13 were ignored.

3. Exported the playlist from itunes of the tracks that have been played.
4. Used Trixmoto's iplaylist imported to import the playlist into MM.
5. exported the playlist so that it would be in itunes in order for me to use the sync and recover feature.

All 18 tracks were updated in MM after the second test, so the two playlists need to match in MM and itunes in order for the sync and recover to work. Doing the second test is kind of labor intensive, any thoughts on a way to streamline this?? Maybe have it update all the playlists which are in iTunes rather than just 1 that the user selects?? Or maybe do something like what Trixmoto's iplaylist importer and have it create the playlist first and then import the playcounts? If you have a better suggestion, I am all ears...

Nyn

[markstuartwalker]

Ok I ran a test and all the playcounts are not being imported into MM when I use the sync and recover because it is skipping the tracks that are not a part of the playlist

Yes, that is what I would expect. My normal practice is to have a sync-playlist which is a superset of all tracks in MM and so playing ANY track in AND playlist gets picked up. It's effective and surprisingly quick). It does have the effect that the normal add/delete playlists work very quickly as no files move around, they are just added/removed from playlists.

I have not played with iPlaylist but perhaps that could be integrated into my script. It would needs know the date range of interest to work. How is this derived? I also expect that internally it parses the entire iTunes DB anyhow so is no more efficient than my approach.

[nynaevelan]

Yes, that is what I would expect. My normal practice is to have a sync-playlist which is a superset of all tracks in MM and so playing ANY track in AND playlist gets picked up. It's effective and surprisingly quick). It does have the effect that the normal add/delete playlists work very quickly as no files move around, they are just added/removed from playlists.

Now there is an idea that never occurred to me and one which would eliminate the problems I am having.

I have not played with iPlaylist but perhaps that could be integrated into my script. It would needs know the date range of interest to work. How is this derived? I also expect that internally it parses the entire iTunes DB anyhow so is no more efficient than my approach.

I have no idea, this is something that goes beyond my brain capacity but the above solution would eliminate the need for this wouldn't you think??

I am off to try the above idea now.

[markstuartwalker]

I am off to try the above idea now.

Happy to help.

I've just had a look at the iPlaylist script and it simply pulls ALL the playlists out of a manually exported XML file - far too clunky for this solution. As a side issue I have all the script bits to pull back iTunes scripts and build them in MM already.

One thing did occur to me as I can traverse iTunes playlists easily enough. Within iTunes folders are the same as playlists and they 'contain' the superset of the tracks from their contained playlists (the same effect as when they are selected in the browser tree. Thus, I can get the implied scope of synchronised playlists by simply traversing the <MM> folder. Ace!

Mark

[nynaevelan]

One thing did occur to me as I can traverse iTunes playlists easily enough. Within iTunes folders are the same as playlists and they 'contain' the superset of the tracks from their contained playlists (the same effect as when they are selected in the browser tree. Thus, I can get the implied scope of synchronised playlists by simply traversing the <MM> folder. Ace!

Mark

Do you hear the wind as that went whishing over my head!!

[nynaevelan]

BTW, I do not know if you or any of the other users are interested, but I have this Magic Node in order for me to keep track of the updated tracks from the export:

Code: Select all

<Group|Name:Exports>\Export to iTunes|Filter:<ISRC> <> ''\<Isrc|Trim:13|Substring start:15>

[nynaevelan]

2.16 ready

The playcounts are still not updating in MM.

[markstuartwalker]

There is something differenct about the tests that we are both running as my testing works ...

1. define a large (200+ track) playlist and set this as the sync playlist
2. define 2 subset playlists , each aout 20 tracks
3. empty iTunes entirely
4. Sync and recover
5. Note initial rating and playcounts values in iTunes
6. Sync to iPhones
7. Play a few tracks in MM, itunes and iPhone
8. Sync iPhone
9. Note playcounts into iTunes
10. Sync and recover script
11. total playcounts in MM and iTunes

I still occassionally get the "Track not modifiable" error message - it appears to be random.

[nynaevelan]

I think my tests might have been failing because the link was lost between the versions?? I am not sure but once I cleared the playlists from iTunes and started over, they are working now. I am just guessing so...

[markstuartwalker]

I think my tests might have been failing because the link was lost between the versions?? I am not sure but once I cleared the playlists from iTunes and started over, they are working now. I am just guessing so...

Well, I've straightened out the code and put a few speed improvements in but I've repeatedly tested it and the logic seems sound. Its odd that you coment on the sync data being out of step - I added a button on the optioned page to flush this out. (v2.17)

I do get an intermittent "Track cannot be updated" from iTunes when assigning the initial playedcount figure. I think this is a race within iTunes where the freshly added track is still being worked upon when I try to update the playedcount immeadiately afterwards. I've put an error traps around it to stop it killing the system for now.

[nynaevelan]

I do get an intermittent "Track cannot be updated" from iTunes when assigning the initial playedcount figure. I think this is a race within iTunes where the freshly added track is still being worked upon when I try to update the playedcount immeadiately afterwards. I've put an error traps around it to stop it killing the system for now.

I haven't received this error, usually the only error I run into is when the track which is playing in MM is trying to be synced to iTunes, which of course causes the sync to fail. Is there any way to skip past the playing track? Or maybe pause the playing track until it syncs? But other than that it is an awesome script and I am now ready to install it on my son's computer to show him how to use it. Great work and thanks for all your patience with me.

Nyn

[markstuartwalker]

I haven't received this error, usually the only error I run into is when the track which is playing in MM is trying to be synced to iTunes, which of course causes the sync to fail. Is there any way to skip past the playing track? Or maybe pause the playing track until it syncs? But other than that it is an awesome script and I am now ready to install it on my son's computer to show him how to use it. Great work and thanks for all your patience with me.

Nyn

Well, I wish you luck with that

My next step with this script is to re-write it as an MM device driver. Will you be ready for more testing for that?

Mark

[nynaevelan]

I have no idea what a MM device driver is but it is the scripter's (you) job to create the script and my job to test it, so yes I am still willing to be your guinea pig!!

[nynaevelan]

The script is working very well for my son, once I set it up I am now able to update his itunes plays in MM, thanks for your hard work and patience.

[markstuartwalker]

Version 2.18

I have rewritten the application to use DB SQL to update values to improve the speed for adding and synchronising playlist tracks.

The only negative with this approach is that it cannot used Auto Playlists. If one is found it will (quickly) create a playlist called "<oldname>-copy" and then work with that. This additional step takes about 10 seconds for a 6000 track playlist. If the playlist length is the same next time around the copy is not repeated.

Mark