INTERACT FORUM
More => Old Versions => JRiver Media Center 18 for Mac => Topic started by: thunderlips222 on September 07, 2013, 11:36:06 am
-
So I'm trying to clean up some sub-folders in the Files view for my [Music] folder and even though there are sub-folders, they're not showing up in Media Center. I've tried importing the folder to no avail. Thx for any help!
-
This is indeed a bug when brackets are in the folder name.
-
Thanks, we'll get this fixed on Monday.
-
John - I was looking at the release notes for the new Mac build you posted today and I did not see a fix listed for this item. Is this defect still open?
Thanks.
Barr
-
Yes, that one is still open. We'll get it next build.
-
Great, thanks so much John. Also thanks for adding the following feature: When media files stored on network drives cannot be found (drive not mounted), files are not longer removed from library - just not playable
Barr
-
This appears fixed in .218.
-
thx for the head up MrC. I am LOVING the frequent updates. Now I just have to learn the expression language so I can dice up this overly large and unorganized music collection in my library
-
Some words to assist your studies:
http://wiki.jriver.com/index.php/Media_Center_expression_language (http://wiki.jriver.com/index.php/Media_Center_expression_language)
-
Yep I've been looking through the wiki page but to be honest it's been way more helpful just looking through threads and seeing how people are using the expressions.
isEqual and isEmpty are my confusion points right now I'd say.
I'm also just trying to get my head around any long nested formulas. feeding one output of an expression to the input of another expression that generates the output you want..
-
Hint. Use expression columns to work out the small pieces of your larger functions. Then, when you have the sub-components working, place them into the larger expression.
IsEqual() tests for equality against some value.
IsEmpty() tests that the field is empty (or sometimes a 0 value). IsEmpty() would usually be supplied with the raw field value, so that the pretty, human-readable display value isn't being used in the expression. If you're testing for emptiness, then you wouldn't want to have the expression testing against the string value "Unknown", which is the human-readable version of an empty field (in many cases).
-
This makes more sense to me. So essentially you're creating custom expression tags so that you don't have to create crazy long, complicated formulas.