- Thread starter
- #51
Better multi-disc support - If you have an album that consists of multiple discs, MediaPortal will just add a 1 to the beginning of the CD1 track numbers, then a 2 to the CD2 track numbers etc. Can this be improved somehow? Like if you click on an album with "Enter"/"OK", you'd get a visual cue that this is a multi-disc album? I think that "101.Track title" looks too much like a "data list"
That's a really good point... Multi Disc is nowhere presented in a nice way
In the latest code (so will be in 1.2 beta) we have already removed the 101 etc tracks all together
What we have replaced it with is the disc# within the views. So now the defaults are things like
Album Artist Groups
Album Artist
Album
Disc#
Tracks
This however would be quite annoying for most albums only having one disc and still having to go through an extra level of view therefore what we have done is added some new logic that allows views to skip levels if there is only a single value. Therefore now if you browse an album with a single disc with the above view by default it will jump from album to tracks (as it does now) and you will not notice any difference except for tracks will have the correct number. If however you browse a multi-disc album when you select the album you will be presented with a choice of discs to look at and then under that you will only get the tracks on that disc.
The layout and navigation is from a few controls that everything in mediaportal uses. We basically have lists and image lists (including film strip and coverflow) and everything uses the same controls so we can not change something for music as they are all used in TV, videos, tv series, moving pictures......)It would look really cool if the two discs' contents where presented in two square fields side by side, and clicking right/left would take you directly from one disc to the next. The selected disc would be zoomed in so that you can view the track names better, perhaps some type of Film strip or Cover Flow animation? I can do a mockup picture later if this sounds interesting enough.
The solution we have implemented works and was possible without changing masses of code.