|
Streamlining the browsing tree & multiple configs
|
|
23-09-2013, 22:38
Post: #68
|
|||
|
|||
|
RE: Streamlining the browsing tree & multiple configs
Thank you. Most of your points clear up my queries, and need no further comment. This leaves only ...
(23-09-2013 21:23)simoncn Wrote:DavidHB Wrote:Group would not be displayed as such; but would only be used as a substitute for Track when displaying the group name rather than individual track names. The data in Group would typically be either the same as Work or (as in your example) a subset of the track data common to all tracks in the group. What I was trying to say (perhaps ineptly) was that the data in Group might just be the work name, or it might be a lower-level summary of the contents of the grouped tracks. An example with perhaps more general applicability than your fascinating Biber case (didn't Biber like to make things complicated!) would be an opera, where the work might be 'Porgy and Bess' and the Group names would be 'Porgy and Bess, Act I' etc. This makes a lot of sense if the whole opera is treated as a single album, which is what I like to do. I note what you say about Group sometimes replacing Album in the displayed data. I assume that this would not be the case in selection lists, as I had taken the statement in the User Guide "When you display the contents of an album that contains grouped tracks, the group will appear as a single item instead of appearing as separate tracks." to mean that, more normally, Groups would replace track data in the lists. David |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)

Search
Member List
Calendar
Help



