Print

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

[dasfoo]

I use a few custom fields in my movie/TV library and then a bunch of "if..." statements in the path rule when moving files, in order to get the folder hierarchy I want, like:

Code: [Select]

if(isequal([Media Disk],unknown,8),,\[Media Disk])if(isequal([Media Share],unknown,8),,\[Media Share])if(isequal([Media Drive],unknown,8),,\[Media Drive])if(isequal([Grouping],unknown,8),,\[Grouping])if(isequal([Movie Title],unknown,8),,\[Movie Title])if(isequal([Series],unknown,8),,\[Series])if(isequal([Season],unknown,8),,\Season [Season])
In 99.99% of cases this works great. However, I have one movie that skips one of these conditions and ends up in the wrong place, and I think it's because the word "Unknown" is in the value of the field getting skipped. Is there a workaround for this?

(I tried inserting 7 random characters for "unknown" in the code above, which fixed this one field but broke how it handles all of the empty fields.)

[wer]

You'll have to provide more information if you want a diagnosis.

Code: [Select]

if(isequal([Media Disk],unknown,8),,\[Media Disk])if(isequal([Media Share],unknown,8),,\[Media Share])if(isequal([Media Drive],unknown,8),,\[Media Drive])if(isequal([Grouping],unknown,8),,\[Grouping])if(isequal([Movie Title],unknown,8),,\[Movie Title])if(isequal([Series],unknown,8),,\[Series])if(isequal([Season],unknown,8),,\Season [Season])

This expression structure is odd, but valid. I can see what it does.  I have no way of knowing if that's the same as what you want it to do.

I can tell you that doing a case insensitive negative substring search for the string "unknown" against [Movie Title] and [Series], in the way you are, is flawed, as it will fail to insert your path info for any video that contains that word in its actual title, and there are at least 200 such movies listed on IMDB, plus a lot of TV shows.  If that is your problem, the solution is for you not to use a common word, "unknown", to indicate a special condition in a field that might normally contain that word.  Why would the word "unknown" be in there in the first place? Either it's there naturally because it's part of the title, or some external program put it there, or you put it there.

In 99.99% of cases this works great. However, I have one movie that skips one of these conditions and ends up in the wrong place, and I think it's because the word "Unknown" is in the value of the field getting skipped. Is there a workaround for this?

Workaround for what, specifically? You haven't described what exactly goes wrong. "wrong place" isn't meaningful without describing the actual output, and the desired output. All you've essentially said is you get a result you don't like.

You will need to provide the contents of all the relevant fields for the file that's causing the undesired behavior, and also a precise statement of what you actually want the result to be for that file.  Then we'll be able to see what's wrong with your code.  Please be as descriptive and precise as possible.

If your problem is your code doesn't properly process Liam Neeson's 2011 movie "Unknown" then that's what I said above. It's just bad programming: don't use the word unknown for a marker in a place where you might encounter it normally. Use a string you will never encounter as part of a title. Like @UNKNOWN@ or !INVALID! or something like that.

[RoderickGI]

I haven't looked at the detail, but generally test for an empty field, and not a field containing "unknown", which is placed in a path when a field used for RM&CF uses an empty field.

But that could be completely wrong, because I didn't read everything.

[wer]

That would be the right advice in a normal situation, but he's apparently not in a normal situation.  He says his expression works always works except for this one file, so for some reason he has some "unknown" strings written to some of those fields.  I'm guessing he has some other utility that is entering those values, or maybe they are downloads, and so he's seeing those "unknown" values in the fields and that's why he wrote his expression that way.

Dasfoo, I presume you know that if MC doesn't have a value to put in a field, it leaves the field empty, and you can test for that with something like:
If(!IsEmpty([Movie Title]),\[Movie Title])

[marko]

Remembering that, when using the RNM&C tool, even empty fields are not empty unless you specifically tell it to use the raw field data by adding ",0" inside the field. I'm not sure if that's relevant here... feels like it might be though.

If(IsEmpty([Movie Title,0]),\[Movie Title])

Re: isempty()...

If you imagine asking MC to create a directory structure using [series] without first testing its 'emptiness', and it was empty, MC would be attempting to create a directory with no name, which is not good. For this reason, if the field is actually empty, the rename tool replaces the emptiness with "Unknown [field]", and it does this before handing things over to the expression evaluator, meaning that as far as it's concerned, the field is not empty.

You can use the same method to turn this off, ie...

[Media Type]\[Media Sub Type]if(isempty([series,0]),,[series])\if(isempty([album,0]),[name],[album])

You just need to be careful you're not asking MC to create illegal file paths or names, although in my testing, MC appears to gracefully and quietly correct any illegal double backslashes that appear in the new path, so you just lose a level in the path, which might not be what you want, but would be easy to correct.

-marko

[zybex]

Marko's solution should work for you.
https://yabb.jriver.com/interact/index.php/topic,92425.0.html