More > JRiver Media Center 25 for Mac

Don't unify different versions of the album (16 and 24 bits)

(1/4) > >>

LETRA:
Hello. I wish that JRiver don't unify different versions of the album (16 and 24 bits). I have tried a couple of solutions found in the forum but I need to have the "expand complete albums" switch activated in the library view because I organize the views by publisher and sometimes some tracks of the album don't carry the publisher tag. How can I do it? Is there any solution?

blgentry:
In Albums view, the rule for MC is that it groups albums by album name.  So if your 16 bit and 24 bit version of an album both have the exact same album name, they will be considered the same album.   "unified" as you put it.  I kind of like that word choice actually.  :)

One solution is to change the album name of one of them to something like "Dark Side Of The Moon (24bit)" or "Dark Side Of The Moon (DVD-A)", or something else that makes sense for it.

Another way is to change your albums view to group your albums using both the [Album] field and another field like [Bit Depth].  That would automatically separate albums out based upon the properties of the files themselves.  But then you would end up with:

Dark Side Of The Moon - 16
Dark Side Of The Moon - 24

...or something very similar depending upon how you define your view.

You could also make a custom field for this to contain identifying information for the album.  I called mine [Album Info].  My Albums view groups albums based on [Album Artist (auto)], [Album], and [Album Info].  In the [Album Info] field, I put things like "SACD" or "DVD-A" or "Mobile Fidelity".  So it can contain all kinds of information about different versions of the same album.

But...  (you knew this was coming right?) ... It's not perfect.  Because JRemote ignores all of this grouping stuff and does it's own!  So if you use JRemote (or other remote views) this might not work for you.

Because of the JRemote problem, I gave up on the (somewhat) elegant solution above, and just rename Albums to include information that identifies the particular album (like adding DVD-A to the title).  Simple is simple and it works well with all of MC's interfaces.

Our member here @ferday has a huge number of different versions of the same album.  I can't remember what his final solution was.  I'm not sure if he will read this or not.  You might PM him or start a thread about this on the Windows forum where he will be more likely to see it.  As will other knowledgable members.

I hope that helps.

Brian.

LETRA:
Thank you very much Brian for your complete response. There are several solutions that work but without the "expand albums" modifier. I have two thousand albums in 24 bits and I can't change everyone's name. One solution would be some kind of parameter that limits "expand albums" to the bit depth or, at least, to the path (24-bit albums are in a different hdd). Perhaps this parameter could be implemented or an expression that allows it.

Thank you.

blgentry:
I'm not clear on what you are doing with "expand albums" or why.  All of my albums in my views show as I want them to without using expand albums.

What happens when you do not use expand albums?
Is that part of this 16 versus 24 bit grouping problem or is it separate?

Brian.

wer:
Letra,

Brian's solution works perfectly, and changing the Group By setting of the view, as he suggests, would be the most flexible and least "invasive" solution.

But if you want to modify the Album names, you can in fact do that all at once:

Select the tracks you want to change the album field for, and paste this into the Album field in the tag window:
=[Album] - [Bit Depth]

That will change all the album names according to that rule in one step.  Try it first by pasting it into the comment field (or some other unused field) to see if you like the results.  It would also be possible to only change the 24 or 16 bit files, by using an IfElse expression.

Regarding what you refer to as "expand albums" I guess you're talking about in Smartlists.  Modifying your Album names may be the only way around some of the limitations there...

-Will

Navigation

[0] Message Index

[#] Next page