More > JRiver Media Center 31 for Windows

Black bar detection not updating tag correctly

<< < (4/12) > >>

mattkhan:
it seems every film I watch is a problem film, possibly because I'm watching a lot of older films recently....

Dirty Harry appears to be a ludicrously dark film and totally trips up the detection (somewhat understandably as I could barely see anything myself at times)

I know the manual profile selection is coming (soon?) which I am now minded to think is, in the end, the pragmatic solution to this problem.

However i do think there is one simple change that could be added which would improve quality of life enormously in this regard, namely just another field that can be used to indicate whether there is significant "doubt" over the reported crop.

This could be one or more of

* a boolean (true if it's doubtful)
* the max crop (currently the crop is the min crop so output the maximum crop instead)
* the most common crop
* the no of distinct crops

from the logs, all such info seems to be available so just storing that in the library would then enable the user to decide what to do next (which might simply be "watch a bit of the film and decide what to do" or it could be run some other custom analysis)

jmone:
In testing (31.0.24) I too see the issue where (as an example) John Wick 2 was populated with 0x0x3840x2160 in the database instead of 0x280x3840x1880 (I guess) even though looking in the log summary this was in the minority, eg:

0020225: 21544: Playback: CJRVideoAnalyzeExtended::BlackBarDetection: Crop Window: 0x0x3840x2160, with 48 hits
0020225: 21544: Playback: CJRVideoAnalyzeExtended::BlackBarDetection: Crop Window: 0x280x3838x1880, with 132 hits
0020225: 21544: Playback: CJRVideoAnalyzeExtended::BlackBarDetection: Crop Window: 0x280x3840x1880, with 553 hits
+ many many other lines

I'll see if I can find the no crop scene.   

jmone:
Nope can't see any areas without a crop in manually scrubbing through the film.  Plenty of all black, but none I could see with content in the letterbox per say.  Can we interpret the log for time stamps (eg the t:xxx)

0001385: 21544: Encoders: CJRVideoAnalyzeExtended::AVLog: [Parsed_cropdetect_0 @ 0000020A63643900] x1:0 x2:3839 y1:0 y2:2159 w:3840 h:2160 x:0 y:0 pts:382027863 t:382027.863000 crop=3840:2160:0:0

mattkhan:
I am finding it too unreliable so far, too many errors and no way to know (without playing the track) whether it got it right or not. Richer logic in choosing a value would obviously be great but just exposing the analysis info in a useful form would be sufficient for me
 For example, dump a file next to the sidecar with scan info in a parsable format.

jmone:
The only weird impact for me so far (I'm a all 16:9 display user) is when the crop is too much (rather than too little), eg the John Wick 4 I posted in the beta build thread.  I guess I'm not a user that would take advantage of black bar detection. 

Navigation

[0] Message Index

[#] Next page

[*] Previous page