I've been using MM to synchronize my entire library (approx 5,000 tracks) to my iRiver H340. One of the great features was that my playlists and autoplaylists copied over as well and were automatically translated to work with the directory structure on my device.
With DRM support in Beta 4 I'm now synching my subscription music but as a separate step from my owned music (because DRM synching requires a USB1 connection which is *much* slower than USB2). I basically have two synch configs (one in d_iRiverH.dll and one in d_WMDM.dll) which synch different Location nodes. Unfortunately my playlists aren't copying to my device now. I'm assuming this is caused by changing my synch approach.
I've read the documentation and searched the forum but haven't found any options/settings to change to make this work. Any help would be appreciated.
To be clear, I'm looking to synch the playlists not the songs within the playlists and to have those playlists work with the device's directory structure.
- James
Synching playlists to iRiver H340
Moderator: Gurus
Synching Playlists to iRiver H340
James,
Can you clarify:
-Is playlist synchronization still working correctly for tracks & playlists synched via d_iRiverH.dll? i.e. is it only a problem for the tracks synched via d_WMDM.dll?
-If you synch 'normal' non-DRM tracks via d_WMDM.dll, does the problem persist?
Important note: The d_WMDM.dll driver does NOT update the iRiver H340 database. Since playlists are not stored in the DB, it would not be surprising if tracks/playlists synched via this plugin did not appear in the DB (that said, it should be possible to synch the .m3u file and play the .m3u file via the device).
Thanks.
-Rusty
Can you clarify:
-Is playlist synchronization still working correctly for tracks & playlists synched via d_iRiverH.dll? i.e. is it only a problem for the tracks synched via d_WMDM.dll?
-If you synch 'normal' non-DRM tracks via d_WMDM.dll, does the problem persist?
Important note: The d_WMDM.dll driver does NOT update the iRiver H340 database. Since playlists are not stored in the DB, it would not be surprising if tracks/playlists synched via this plugin did not appear in the DB (that said, it should be possible to synch the .m3u file and play the .m3u file via the device).
Thanks.
-Rusty
Rusty,
To clarify a couple of points:
(1) I was synching by location node not by playlist. Synching by playlist worked for both plugins. My goal was to get all my MM playlists automatically transferred as m3u playlists on my device without synching each one and recopying duplicated tracks. I used to synch using "Synch Entire Library" and all playlists transferred beautifully but this stopped happening when I changed to synching by location. After further research I don't think there's anyway around this since any option other than synch entire library could have different output masks and MM wouldn't know how to translate the playlists to the device's directory structure.
(3) I can synch non-DRM tracks via the USB1 connection but it significantly slower and would take an impractical amount of time due to the number of tracks. To give you a sense -- the 1400 subscription tracks take about 24 hours to copy using USB1 while my 4700 owned tracks can be copied in about 2 hours using USB2.
After testing several different scenarios I've settled on the following solution:
- Synch DRM tracks using the WMDM plugin and selecting by location
- Then, synch entire library using the iRiver plugin, which recopies the DRM tracks again but doesn't seem to affect the license or my ability to play the songs. Since I'm synching the entire library, the playlists come over and work perfectly. For example, I can have MM autoplaylists that select from both owned tracks and DRM tracks that will work on my iRiver.
I hope that clarifies. I'm going to make some observations of the DRM synch process in a separate post...
Thanks,.
James
To clarify a couple of points:
(1) I was synching by location node not by playlist. Synching by playlist worked for both plugins. My goal was to get all my MM playlists automatically transferred as m3u playlists on my device without synching each one and recopying duplicated tracks. I used to synch using "Synch Entire Library" and all playlists transferred beautifully but this stopped happening when I changed to synching by location. After further research I don't think there's anyway around this since any option other than synch entire library could have different output masks and MM wouldn't know how to translate the playlists to the device's directory structure.
(3) I can synch non-DRM tracks via the USB1 connection but it significantly slower and would take an impractical amount of time due to the number of tracks. To give you a sense -- the 1400 subscription tracks take about 24 hours to copy using USB1 while my 4700 owned tracks can be copied in about 2 hours using USB2.
After testing several different scenarios I've settled on the following solution:
- Synch DRM tracks using the WMDM plugin and selecting by location
- Then, synch entire library using the iRiver plugin, which recopies the DRM tracks again but doesn't seem to affect the license or my ability to play the songs. Since I'm synching the entire library, the playlists come over and work perfectly. For example, I can have MM autoplaylists that select from both owned tracks and DRM tracks that will work on my iRiver.
I hope that clarifies. I'm going to make some observations of the DRM synch process in a separate post...
Thanks,.
James