Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[styxx10]

Hi,

I know this is possible, but my ability to navigate JRiver is in a learning curve,so any assistance would be appreciated.
I  have many CD's ripped that are of different format , quality bitrate etc...when they display they are are thrown together into
the one listed display as per example .

 I would like to have them separated with the Header for each Variation displayed. Any advise on how to achieve this would be appreciated.

[6233638]

1. Tools → Options → Library & Folders → Manage Library Fields
2. Add a new field and give it a name
3. Set this field to use "calculated data"
4. Now you can enter a custom expression to group by.

An example for this, slightly modified from what I currently use:

Code: [Select]

<font size="10" alpha="0" color="ffffff">[Year] [Channels] [Disc #] <//font>Delimit([Year],/]/ ,/[)[Album]Delimit([Description],/),/ /()Delimit(If(Compare([Channels,0], <, 3),,/ ‒/ Multichannel))
Though you probably want to customize this.
Anything within the <font> <//font> section should be mostly hidden. It just displays in white text that is very small: there's no way to actually hide it in MC.
I don't know what field you use for the "Mastersound" and "HDTracks; 24-192" information, but you probably want to use that in place of [Description] above.

5. In your view, click the drop-down arrow at the top and select Group By → More (sort groups a-z) → [New Field Name]

[styxx10]

Thanks for the detailed steps, It is exactly how I wanted to have the files display as I have Multi channel ISO also.
Will be able to follow the different codes you detailed to try to get more of an understanding to the power in using expressions
in the fields.

Appreciate you taking the time to step it out......Hopefully will be of assistance to others also.

[6233638]

Glad I could help.
You can't copy and paste it into the expressions editor like this, but to break it down:
 

• <font size="10" alpha="0" color="ffffff">[Year] [Channels] [Disc #] <//font>
• Delimit([Year],/]/ ,/[)
• [Album]
• Delimit([Description],/),/ /()
• Delimit(If(Compare([Channels,0], <, 3),,/ ‒/ Multichannel))

1. The <font> section displays a "hidden" prefix to the group, which I use to set the sort order. This ensures that albums are sorted by Year, Number of Channels, and Disc # in ascending order.

2. Delimit() only displays when the field has a value.
And you can specify a head/tail string to be applied when that field does have a value.
In this case, it wraps Year with square brackets. E.g. [2015]
To display brackets you must escape them first, using a forward slash.
The same applies to explicit spaces - that's why there are so many slashes everywhere.
If you use a space in the middle of a string it should be fine, but if you want to start with a space, you need to use "/ "

5. Here, we check to see whether the number of channels is less than 3. If it is, we do nothing.
If it is not less than three, it gets " ‒ Multichannel" added to the end of the name.
I'm not sure why I did it that way - you could just as easily do "greater than two". Probably because I was new to expressions at the time I wrote that.
 
 
When trying to figure things out, I find the easiest way to modify an expression is to right-click the columns in a view and add an Expression Column.
This is the quickest type of field that you can edit which will display an expression, and you can then copy and paste it elsewhere once you have it displaying what you want.

[dtc]

The simple solution that many use is to just give the different versions different album names - Like Bridge Over Troubled Waters and Bridge Over Troubled Waters - High Resolution. Or use the release date as part of the album name.

[kstuart]

The simple solution that many use is to just give the different versions different album names - Like Bridge Over Troubled Waters and Bridge Over Troubled Waters - High Resolution. Or use the release date as part of the album name.

That produces other problems.

There have been long threads about this, back in the MC19 or MC18 forums.

I use the existing "Description" field, since is a FLAC tag that is saved in the FLAC file and is read by other programs.

I wrote a long post describing how to do it, and the theory behind it.  Another user even came up with a little script that grabs the information and puts into "Description".

You can read the thread at:

Album friendly Media Library setup thoughts

[dtc]

That produces other problems.

There have been long threads about this, back in the MC19 or MC18 forums.

I use the existing "Description" field, since is a FLAC tag that is saved in the FLAC file and is read by other programs.

I wrote a long post describing how to do it, and the theory behind it.  Another user even came up with a little script that grabs the information and puts into "Description".

You can read the thread at:

Album friendly Media Library setup thoughts

Using separate album names works fine for most cases. You can complicate it as much as you like, but for the small number of duplicate albums that most people have, the simple solution is often the best.

[kstuart]

Using separate album names works fine for most cases. You can complicate it as much as you like, but for the small number of duplicate albums that most people have, the simple solution is often the best.

I think that most people have no duplicate albums.

The above scheme is for people who have lots of duplicate albums.