Intelligent Frame Correction 2.0 *BEAST UNLEASHED* (2 Viewers)

[Marvman]

​

::: DOWNLOAD :::

.: wiki :.
​

Hi Folks,

I.F.C. 2 is out!

After a long rework and testing time, here we are with the next gen version.

Features:

+ automated black bar scanner
+ automated view mode selector
+ one click configuration (for beginner)
+ fully customizable (for advanced user)

The plug-in is optimized for the TV aspect ratio 16:9, but it supports the ratios 4:3 and 21:9 too.

Changelog:
[Hide]
2.0.2

- fixed HD disabling
- fixed wrong load of default view mode when I.F.C. is disabled (IFC uses the default view mode)
- optimized black bar detection (should be faster now)
- change the interval for the detection interval in I.F.C. GUI (hack)
- fixed cropping issue when 21:9 stuff were played
- fixed crash when I.F.C. were stopped (hopefully, cause I couldn't reproduce it)
+ decoupling the advanced view mode from the accurate pixel cropping, so a fixed cropping value (zoom factor) can be used like in the old version (previous 2.0), but configurable
- fixed fading on channel switch, it will now instantly reseted
- fixed configuration loading, that rarely occurs on some machines
+ added edge tolerance for a faster black bar detection
- fixed some issues with the screen shot tester

2.0.1

- optimized stabilizer
+ added HD switch
+ added video switch
+ added screenshot tester
- fixed some small issues

2.0.0.0 *BEAST UNLEASHED*
- complete rework of the previous versions of I.F.C.
- a way faster black bar scanner
- a way better black bar detection
- an user friendly back-end and front-end configuration interface
- 3 modes (snapshot, reset, auto) to control I.F.C. with one button
- supports all known formats (tested and optimized: German/USA/Italian/Dutch broadcasts)
- pixel accurateness (means: removes small black grubby edges as well)
- stabilizer for a smoother cropping behavior
- advanced view mode (an additional zoom factor can be set)
- independent verbose logging (no more log flooding)
[/Hide]

Special greets and thanks go to Dread Fury, I.F.C. would not be I.F.C.,if he has not been there. Further thanks goes to Pretoriano and Wouter, thank you guys for testing.

 

[wouter1971]

Martin, this one is a KILLER beast Fantastic! Thanks a million.

Greetings,

Wouter

p.s. You can add to "tested and optimized" also Dutch broadcasts.

 

[Jay_UK]

Hi there,

Many thanks for the update

J.

Hi there,

Just been looking into V2...

Are the default settings ideal? (or should we look into adjusting them?)

I had hoped that with verbose logging turned off, that the MePo log file would not be filled with IFC entries all the time (I have MePo set to debug). Eg:

2010-05-08 22:19:51.186774 [Debug][(24)]: PlaneScene: PixelRatio : 1
2010-05-08 22:19:51.186774 [Debug][(24)]: PlaneScene: src : (48,11)-(709,565)
2010-05-08 22:19:51.186774 [Debug][(24)]: PlaneScene: dst : (0,0)-(1920,1080)
2010-05-08 22:19:51.188774 [Info.][(10)]: PlaneScene: Crop: top:11, bottom:11, left:47, right:11
2010-05-08 22:19:51.198774 [Info.][(10)]: PlaneScene: Crop: top:11, bottom:11, left:46, right:11
2010-05-08 22:19:51.205774 [Debug][(24)]: PlaneScene: crop T, B : 11, 11
2010-05-08 22:19:51.205774 [Debug][(24)]: PlaneScene: crop L, R : 46, 11
2010-05-08 22:19:51.205774 [Info.][(24)]: PlaneScene: video WxH : 720x576
2010-05-08 22:19:51.205774 [Debug][(24)]: PlaneScene: video AR : 16:9
2010-05-08 22:19:51.206774 [Info.][(24)]: PlaneScene: screen WxH : 1920x1080
2010-05-08 22:19:51.206774 [Debug][(24)]: PlaneScene: AR type : Stretch
2010-05-08 22:19:51.206774 [Debug][(24)]: PlaneScene: PixelRatio : 1
2010-05-08 22:19:51.206774 [Debug][(24)]: PlaneScene: src : (46,11)-(709,565)
2010-05-08 22:19:51.206774 [Debug][(24)]: PlaneScene: dst : (0,0)-(1920,1080)
2010-05-08 22:19:51.208775 [Info.][(10)]: PlaneScene: Crop: top:11, bottom:11, left:45, right:11
2010-05-08 22:19:51.218775 [Info.][(10)]: PlaneScene: Crop: top:11, bottom:11, left:44, right:11
2010-05-08 22:19:51.225775 [Debug][(24)]: PlaneScene: crop T, B : 11, 11
2010-05-08 22:19:51.225775 [Debug][(24)]: PlaneScene: crop L, R : 44, 11
2010-05-08 22:19:51.226775 [Info.][(24)]: PlaneScene: video WxH : 720x576
2010-05-08 22:19:51.226775 [Debug][(24)]: PlaneScene: video AR : 16:9
2010-05-08 22:19:51.226775 [Info.][(24)]: PlaneScene: screen WxH : 1920x1080
2010-05-08 22:19:51.226775 [Debug][(24)]: PlaneScene: AR type : Stretch
2010-05-08 22:19:51.227775 [Debug][(24)]: PlaneScene: PixelRatio : 1
2010-05-08 22:19:51.227775 [Debug][(24)]: PlaneScene: src : (44,11)-(709,565)
2010-05-08 22:19:51.227775 [Debug][(24)]: PlaneScene: dst : (0,0)-(1920,1080)
2010-05-08 22:19:51.228775 [Info.][(10)]: PlaneScene: Crop: top:11, bottom:11, left:43, right:11
2010-05-08 22:19:51.238776 [Info.][(10)]: PlaneScene: Crop: top:11, bottom:11, left:42, right:11

Thanks,

J.

 

[Marvman]

Hi Jay,

the default settings should be fine.

Those lines comes MP from not from IFC, if you choose "information" instead of "debug" you'll get rid of those lines too.

 

[hirscho]

Hi Marvman

Thanks a lot for the new version of this great plugin. The old version has already worked perfectly on my system.

I performed some tests on the stabilizer function and I may found a bug.


1) I put the stabilizer on 100 to investigate the influence on cropping. The result was, that on all four sides the video was cropped (please have a look at the logs). The source material was a 4:3 letterbox movie, so my expectation has been, that the upper and lower black bar would have been cropped by a factor of 100 pixel, while the left and right side would have remained untouched.
2) Putting it to zero makes my system hang.

Regards

hirscho

 

[Marvman]

Hi Hirscho,

you misunderstand the stabilizer, look at the wiki.

Confirmed the Bug, don't set the Stabilizer to 0 atm until i found the reason.

how the stabilizer works:

First detection sequence
a small 5 pixel edge was found -> crop 5 pixel

second detection sequence
a small 2 pixel edge was found -> crop 2 pixel

to prevent this behavior that you see every time a small cropping, the stabilizer comes into the play.

A Value of 10 works as follow:

First detection sequence
a small 5 pixel edge was found -> crop 10 pixel

second detection sequence
a small 2 pixel edge was found -> crop 10 pixel

third detection sequence
a small 10 pixel edge was found -> crop 10 pixel

fourth detection sequence
a small 11 pixel edge was found -> crop 20 pixel

fifth detection sequence
a small 19 pixel edge was found -> crop 20 pixel

and so on hope you get it

For German broadcasting the default settings working very good.

 

[hirscho]

Hi Marvman

Thanks for the fast reply. Understood. But why is IFC always cropping the number of pixels specified at each side, even if there are no black bars at all, e.g. in a 16:9 movie trailer?

Best Regars

hirscho

 

[Marvman]

You are right left and right was 0.

Thanks for the hint I'll look at this.

 

[Jay_UK]

Hi there,

A quick question (I have read the wiki - but still not sure)

There was originally talk of just doing frame analysis on change of screen content (eg channel change, or movie/series start) and not continously.

Is this implemented in 2.0? (I know it has the snapshot mode??)

Thanks,

J.

Thanks,

J.

 

[grubi]

AW: Intelligent Frame Correction 2.0 *BEAST UNLEASHED*

Just a hint.
Download link is broken on first post.

Cheers.
grubi