View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002938 | MMW v4 | Burning / Disc Handling | public | 2007-03-22 17:38 | 2007-08-07 12:56 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.0 | ||||
| Fixed in Version | 3.0 | ||||
| Summary | 0002938: Disc spanning: user has no feedback or control over which tracks are on which disc | ||||
| Description | The design of the current disk spanning implementation renders the functionality useful more for backups than for creating mixes because of the fact that it gives users very little feedback/control over the manner in which tracks are spanned across disks (applies to both Audio and Data CDs/DVDs). More specifically: 1) It's unclear how many CDs/DVDs the tracks will fit on 2) Unclear which tracks are being burnt to which CDs/DVDs 3) No means of modifying which tracks are burnt to which CD/DVD, resulting in undesired splits (e.g. split of tracks by 1 artist or genre across 2 DVDs) 4) No means of identifying/customizing each disk with a different label 1) Can be resolved by indicating the number of CDs/DVDs the selected list of tracks will take up. However, 2) and 3) would seem to require a redesign of CD Burning functionality to use the NP List (more like WMP). Hoping for suggestions... | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1058 | ||||
| related to | 0002459 | new | Ability to Build Playlists for Portable Devices/CD Burners |
|
|
1) Could be implemented as suggested, i.e. there would be an indication of # discs to be needed. 3) MM could try to resolve this automatically, I could imagine e.g. this algorithm: If burning is going to split a folder between two CDs, it will rather move its whole content to the second CD, providing: a) The 'orphaned' content that was to be on the first CD doesn't occupy >10% CD capacity. b) This move operation won't create the need for another CD to be used. c) Maybe user could be asked to confirm this automatic operation. 4) This could be resolved by asking for a label for each new disk to be burned. I.e. user enters it for the first disk and when the second is to be burned, user is asked for confirmation whether the same label should be used also for the next CD. As for a more complex change, this would probably better be handled by what I have described on several occasions, i.e. some kind of Temporary panel for arbitrary track operations, including Burning, Synchronization, Playlist editing, etc. |
|
|
1) We could do this, however, it wouldn't be as simple as we're discussing since MM doesn't assume that the Disks in question are all empty/the same size. Thus, a potential solution: -if currently inserted disk isn't empty, indicate: 'Requires > 1 disc!' (this is the current message) -if currently inserted disk is empty, assume that other discs will be the same size, and that they will be empty as well: 'Requires x discs.' 2/3/4: I suggest that we defer these to 2459 since resolving 2/3/4 without resolving 2459 would yield an imperfect solution. |
|
|
Assigning to Ludek to implement 1) as suggested by Rusty. |
|
|
1) is fixed in build 1058. |
