More > JRiver Media Center 30 for Mac
Remove Hung Closing Parenthesis From Renamed Folder
zybex:
That's expected when not escaping the closing parenthesis. The problem is the escaping leaves the slash (bug?):
What about a workaround:
[Album Artist]//If(IsEmpty([Date],1),,[Date] -) [Album] If(IsEmpty([Catalog #,0]),,char(40)[Catalog #]char(41))
AudibleImagery:
--- Quote from: zybex on February 17, 2023, 04:14:15 pm ---That's expected when not escaping the closing parenthesis. The problem is the escaping leaves the slash (bug?):
What about a workaround:
[Album Artist]//If(IsEmpty([Date],1),,[Date] -) [Album] If(IsEmpty([Catalog #,0]),,char(40)[Catalog #]char(41))
--- End quote ---
Zybex and Lepa,
Thank you so much for taking the time to help me.
I'm all for a workaround at this point and it worked like a charm. Thanks again! Could you explain how the char function is supposed to work? I tried to look it up but the information on the JRiver wiki is sparse.
Regards,
John
zybex:
https://wiki.jriver.com/index.php/Miscellaneous_Functions#Char
The Char() function prints a single symbol corresponding to the given ASCII/Unicode character. Here's a table for the common values:
https://www.rapidtables.com/code/text/ascii-table.html
You can see 40 = open parenthesis and 41 = closing. Since MC isn't handling the /( and /) correctly in the rename tool on Mac, the function gives us another way of inserting those same symbols without breaking MC.
marko:
I have a quick question relating to text case...
I personally like things to be properly capitalised, but I'm also lazy... so, when I'm writing expressions, as they're never going to be displayed anywhere, and Windows is not case-sensitive, the expression functions and library fields are more often than not written 'all lower case'.
When using Mac (or Linux) do the expression functions and [library fields] all need to be cased correctly to work?
My laziness recently caused me much pain as I needed to go through all of my skin xml files and correct the case of the referenced image filenames. I did not enjoy that very much, at all :)
JimH:
As you found, file names on linux and Mac need to be explicit with respect to capitalization. The same is true for directories.
You can have files or directories named AA, Aa, aA, and aa and they are all different.
Anything MC doesn't. An expression, for example.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version