Print

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

[CrouchingOwl]

I had been using Version 26 of JRiver for quite some time very happily but my attempt to transfer to version 30 isn't going well.  Where it's breaking is in transfering the custom views I had set up in version 26.  I created two of these by putting the name of a collection in the field named Custom and then using the "Set Rules for File display" to limit the view to only that collection.  For example, in version 26 filtering for "Early Music Collection" gets 29 albums but nothing shows at all using the same rules for version 30.  The other albums appear to be accessible, they just don't show up in the views.  I also checked and the appropriate collection name still shows in the "Custom" Tag.  Does version 30 handle the "Custom" field or the "set Rules for file display" differently so that I'd need to define the search differently to make it still work?  I've tried setting up a view from scratch using the same rules as well as importing and I just can't tell what is going wrong.  When I set these up in version 26 everything was intuitive and worked more or less on the first try, now I seem to be stuck.

I've attached an image of the settings I created for the view that isn't working in case that helps.  And yes the name filter gets split into multiple words.  When I tried using just one keyword it seemed to provide results based on any tag field not just the one named "Custom".  For example if I tell it to filter the "Custom" field for the word "Early" it includes Peter Paul and Mary's "Early Mornin' Rain" even though that text is from the "Name" field not the "Custom" field.  Oddly, the search by "Custom" seems to apply to any field except the one named Custom.

[EnglishTiger]

One reason why the view is not working the way you want is because the Rules are set up wrong.

To get a View to show files based on the content of a Single Tag then you should use a Standard 'Tag is Value', or 'Tag contains Value', rule and not the rule you are using.

So for a View that only shows the Albums from your "The Early Music Collection" the rule should read "[Custom] (in 1st dropdown box)  is (in 2nd dropdown box) The Early Music Collection (in 3rd dropdown box)"

[CrouchingOwl]

Hmm, I'm not following you.  If I choose "Custom" it doesn't give me a "Is" drop down and then the option to enter a phrase.  It gives me a single text entry field which if I type anything into it and save it the text is broken into individual words.  I noticed the "Custom" option shows up twice in the list but neither of them behaves differently.  Can you be more specific on how I'd get it to behave the way you describe?

[CrouchingOwl]

I just figured it out, took a few tries to find a search syntax.  Apparently what it wanted was choosing the word custom from the drop down list of search items, then entering the search [Custom]="Early Music Collection".  There are two items named Custom in the drop down menu so I am suspicious the programmers intention was that one of them would refer to the tag named custom and another would but a custom search field based on the syntax found here: https://wiki.jriver.com/index.php/Search_Language.  But instead both "custom" rule types do the advanced syntax language.