View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002504 | MMW v4 | Synchronization | public | 2006-05-26 15:39 | 2006-05-28 07:12 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Fixed in Version | 2.5.3 | ||||
| Summary | 0002504: Auto-converted iTunes tracks stop playing partway through the song | ||||
| Description | I'm not certain of the repro steps for this issue, however, by doing the following steps, I'm able to cause a track to play only partially: 1) Synch/Auto-converted the file at 128kbps -->Playback on the iPod works correctly 2) Synch/Auto-convert using the following settings: Manual settings VBR V5 Joint stereo Advanced Sample 44100 (Mpeg1) Encoding quality 5 Bitrate min no limit Bitrate max no limit VBR method new (faster) Use Bit reservoir Strict Iso Complience -->Playback on the iPod is interrupted partway through the track (even though it plays correctly in MM from the iPod) 3) Synch/auto-convert again at 128kbps --> Playback on the iPod is interrupted partway through the track (even though it plays correctly in MM from the iPod)--even though this setting previously worked!! Also, now when I do an iPod DB Update, MM always generates an AV. Posting iPod db, original wma track, and mp3 track from the iPod to the ftp server. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1000 | ||||
|
|
Fixed in build 1000. |
|
|
Verified 2.5.3.964. re-opening just to confirm that the new behaviour is as-designed: If I previously copied a track Bob Marley | One Love and it was buggy (i.e. playback stops partway through) and then recopy the track using the new build, then the iPod ends up containing 2 versions of the song: the old buggy one and the new one. I don't think this is much of an issue, since users facing this problem will probably want to delete and resynch their entire collections, but I just want to make sure that this is what you'd intended. |
|
|
This shouldn't be related to this bug, it can happen if MM doesn't know it's the same track - e.g. if you synchronize it from another DB, the track has another internal ID and is synchronized as a new track. |
