View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update | 
|---|---|---|---|---|---|
| 0015773 | MMW 5 | Playlists (Auto) / Search / Filters | public | 2019-06-18 23:42 | 2022-09-14 14:31 | 
| Reporter | peke | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always | 
| Status | feedback | Resolution | open | ||
| Target Version | 2026 | ||||
| Summary | 0015773: Auto-Playlists with multiple criteria limits are not supported or imported from MM4 | ||||
| Description | Auto Playlists with Multiple Limits fail to import in MM5 as adding multiple limits to Auto-Playlist is not available in MM5 When Playlists have two enable Limits they fail to import and all but one limit is lost. | ||||
| Steps To Reproduce | Create Auto-Playlist in MM4 with these settings Using ALL Match and Entire Library: Status -> Is accessible Type -> Music Rating >= 5 Track Length <= 660 Seconds (To eliminate long Tracks) ----------- Sort -> Random -> Z..A ----------- Limit -> 100 Tracks (At that time my Car Stereo could read up to 100 tracks) Limit -> 80 Min (If I want to limit that to an Audio CD) | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | |||||
|  | The solution proposed at 0015777 could also resolve this problem. | 
|  | Note: 0015777 do not solve case with multiple Limitations eg. List up to 100 tracks that are < 650MB | 
|  | ok, this seems to be a small usability regression against MM4. The pros are the clearer, cleaner and compact UI. I guess that using multiple limitations is rather rare case, probably just the Audio CD example (100 tracks / 80 minutes) ? Assigned to Rusty to decide whether the UI should be re-designed because of this, but sounds rather as a low priority item to me. | 
|  | I agree that this is probably not that common, so, 1) In the short term: Assuming this isn't hard/risky to implement, MM5 should import such playlists from MM4, but with only a single limit (preferentially use limits of minutes, MB, files) 2) In the long term we'll see if this is really a problem. If it is, we can update the UI with a '+' to add a second limit (but not a second option to 'Select by' e.g. [ ] Limit to _50_ _files__v . . Selected by: _random_ [+] . . Limit to _100_ _MB_ . . [-] | 
