What exactly are you doing? What is your setup? And do you really need to set reportError=y for any reason?

Why would your target path start and end with ""? "E is not a valid drive designation, nor is " a valid path character in general, especially not at the beginning or end of the path. You pass in characters that shouldn't be there at all.

{hpi} literally does give you height + progressive/interlaced so it's not odd heights, it's the actual heights. Only {vf} tries to interpret and classify it into one of these standard formats.

Your formats are not compatible with the new version. There's some info on other threads, as well as the release notes. Have you read the post above? Now you should see the difference between these: ({d}) {'('+d+')'} Basically none of your formats take into account that a variable could be undefined ...

It's your format. And you are adding the extra space somewhere in your format.

1. I assume you did not read the link I just gave you.
2. Unless you paste your format here I cannot tell you how to fix your format.

No.

Besides, you have all the bindings, nothing stopping you from making your own implementations with your own error handling:

I suppose the Progressive/Interlaced MediaInfo field isn't available for some files. You can check Video > ScanType field.

1. If you report any mismatch, it's always useful to give me the filenames as well. 2. red doesn't mean the file doesn't fit, it means there is a chance that the file doesn't fit 3. I suppose they don't make that information available via the anonymous HTTP API. 4. {group} isn't perfect. It only ...

1.
Added step for 720x304 => 480p

2.
People don't understand p/i and get confused when they suddenly get 720i which most people have never seen before. The {vf} gives you the lies you wanna see.

If you want the real values use:

The two examples you gave are identical. And surely not generated by the default format.

@see http://www.filebot.net/forums/viewtopic ... 5&t=2#p783

Try the latest beta build and see if that makes a difference.

See FAQ. You need to replace the jar.

I just can't seem to reproduce the issue... something must be different: Input: D:\workspace\testdata\AMC-TEST\mnt\freebox\ext_hdd\downloads\[www.Cpasbien.pe] Joe.2013.LIMITED.FRENCH.720p.BluRay.x264-LOST.mkv [www.Cpasbien.pe] Joe.2013.LIMITED.FRENCH.720p.BluRay.x264-LOST.mkv [series: Joe, movie ...

I've added www.**.pe to the blacklist, even though it works for me without. Try doing filebot -clear-cache once.

Then I'm out of ideas. These are the functions that are used in the amc script, and if they work it can't not work. If you can really reproduce this every single time, you try debugging the amc script (just clone from GitHub). It's pretty complicated, but other than that I'm out of options ...

You could try along the same advice I gave on this thread:
http://www.filebot.net/forums/viewtopic ... 254#p10242

Still a permission issue. Somewhere you got a folder where the java process doesn't have permission to list files. Instead of crashing it will no ignore these folders.

Unable to confirm: Input: D:\workspace\testdata\AMC-TEST\[www.Cpasbien.pe] Joe.2013.LIMITED.FRENCH.720p.BluRay.x264-LOST.mkv [www.Cpasbien.pe] Joe.2013.LIMITED.FRENCH.720p.BluRay.x264-LOST.mkv [series: www Cpasbien pe Joe, movie: Joe (2013)] Exclude Series: www Cpasbien pe Joe Group: [tvs:null, mov ...

Yes, but only for files that match your episode / movie files.

e.g.
Avatar.avi
Avatar.eng.srt
Avatar.xml
Avatar.xyz

Should automatically be moved as expected. That won't work with other random clutter, but then that I would just regenerate.

I'd guess it's a permissions issue.

EDIT: Fixed with r2268.

Remove libmediainfo.so since it's not working anyway and is just crashing the process.

If you report crashes you should really include a uname -a as well.

I only checked for a minute, but from what I can tell xattr (not to be confused with named attributes) is not supported on NFS.

Try setting xattr from console. I'm sure you'll get the exact same error message.

Are these warnings in anyway affecting the desired outcome?

You can disable xattr with:

FYI it works just fine if you give FileBot enough hints that this is a TV Show Episode and not a Movie: Input: D:\workspace\testdata\AMC-TEST\TV Shows\Only Fools And Horses - 1989 Christmas Special - The Jolly Boys Outing.avi Group: [tvs:only fools and horses] => [Only Fools And Horses - 1989 ...

This is a shitty episode filename, far from any kind of standard naming, don't you agree? 1. Episode name looks like a movie name 2. Thus FileBot looks for a matching movie, since there is no correct movie FileBot is set up to fail 3. FileBot picks the most likely match, despite difference, because ...