More > JRiver Media Center 27 for Windows
Feature Request: Better Support for Classical Music
newsposter:
Weekend plans here are to rip in another dozen or two classical CDs. Will chime back in on preferences / suggestions after that fresh experience.
Also doing some research into Apples best practice recommendations as well as anything the multitude of library and professional music associations might have.
The wikipedia article on music cataloging is a pretty good primer on the meaning/usage of catalog notations that are composer specific.
No sense in reinventing the wheel if there is a real/defacto standard or three that could be implemented.
HaWi:
I am very much in favor of what @wer suggests for [Composition] support.
hoyt:
--- Quote from: wer on March 12, 2021, 12:38:53 pm ---The Composition can't be the source for interpreted data, because it is the destination.
--- End quote ---
Can you explain your workflow with this, or link to your prior discussion? I searched around a bit, but didn't find something that I thought was step-by-step enough to understand why you would rather go from Name -> Composition, Movement, Movement # vs the other way around. Or are you saying that when you rip the CD and use YADB, it is automatically formatting the name like you're stating? I'm going through the classical albums I have now and am finding it much easier to shift+click 6 tracks, note them as Composition = Cello Suite No. 1 in G Major, Catalog Reference = BWV 1007, then go through each one and enter the Movement and Movement #. Once I'm done with that, I enter the Name as =[Composition]: [Movement Number]. [Movement]. I find that easier to make the name consistent, but you've put more thought and work into this, so I'd like to better understand your reasoning. Plus my CDs are all already ripped and I don't recall how it named things.
wer:
Hoyt, I'd be glad to, but I don't want to do it here because it further sidetracks the discussion.
Here are links to tutorials I've done that deal with this subject. I've responded to your question in the newer one, so let's follow up there if you want. Thanks...
newer How to Automatically Parse Composition and Movement info in Classical Music
older Here's how to get Album Ratings in your views
wer:
A few days have passed and no one has refocused on the bigger issue, so I have edited the original proposal to remove any automatic parsing to fill out the Composition field.
People could not agree on a standard for automatic parsing for Composition, even when the standard proposed was the simplest, easiest one possible: using a single colon. People focused on their personal issues with automatic parsing to the exclusion of consideration of all the other points of the proposal.
When asked to refocus to choose between automatic parsing, customizable parsing, or no parsing at all, people would not focus on that question.
So I have removed automatic filling of the Composition field from my proposal, so that people can try and focus on the remaining benefits of MC recognizing Compositions.
I've also combined points 5 and 6 for clarity since they were closely related.
I feel it's a shame to not be able to provide any automation of this to users, but oh well. Users who are incapable of writing their own expressions to populate the Composition field will have to fill it out manually, or do without.
That leaves us with this:
So I'm proposing that MC be enhanced to support Compositions. I think that means the following:
1. The ability to treat a Composition as a unit.
2. Recognize the user-defined Composition field. All tracks on the same album that have a common Composition field shall be considered part of the same Composition.
3. Composition support in Playlists and Smartlists
4. In Views file list (bottom pane) and playlists/smartlists, be able to expand/contract Composition as with Stacks
5. Compositions can have ratings, and composition stats (rating, duration, etc) are accessible from the search language like with tracks, to support "Files to include" in views and lists.
6. Compositions can have relational fields, like an Album can.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version