Utility: ShowAnalyzer Beta

[Jere_Jones]

Originally Posted by evilpenguin

Out of curiousity, what would it do for letter boxed SDTV in a 16:9 HDTV stream (I saw this yesterday on Sci-Fi HD and I died a little on the inside )?

In theory it would zoom in so that the black bars on all sides were minimized and the 16:9 show filled the screen. It would be most excellent!

Jere

[evilpenguin]

Originally Posted by Jere_Jones

In theory it would zoom in so that the black bars on all sides were minimized and the 16:9 show filled the screen. It would be most excellent!

Jere

I was more wondering what aspect SA would report for that case? Its a bit of a wierd one

[Humanzee]

Yeah, I've seen that too quite frequently on our PBS stations. Wouldn't you need to output somehow in the aspects file where say the top left and bottom right pixels of content are? Otherwise you are assuming that all recordings have content out to one of the extreme edges of the recording. So to make a plug in I'd think you'd need 4 things.

• Time stamp of change
• Parent Recording Resolution
• Content Resolution / Ratio
• X,Y coordinates of where in the frame the content starts and/or where in the frame it ends relative to the parent resolution.

0.233567 1280x720 640x480 320,120
30.345678 1280x720 1280x720 0,0
etc.
I suppose that the resolution of the parent recording could only be written once at the top or something.

[geogecko]

Originally Posted by Jere_Jones

As far as I know, nothing does it. There hasn't been anything that made this information available until now. I'm hopeful that someone will make an STVi soon.

And remember, it isn't a 'per-file' switch. It is a 'per-frame' switch.

Jere

That is what I thought you meant. So if I'm watching a show in HD, and say for some strange reason, I wanted to watch the commercials (no idea why I'd want to), it would automatically switch the aspect ratio for the commercials that were in SD?

[erik]

Originally Posted by Humanzee

• Time stamp of change
• Parent Recording Resolution
• Content Resolution / Ratio
• X,Y coordinates of where in the frame the content starts and/or where in the frame it ends relative to the parent resolution.

How about?

• Time stamp of change
• Current resolution
• X pixel of upper left of the content
• Y pixel of upper left of the content
• X pixel up lower right of the content
• Y pixel of lower right of the content

[Jere_Jones]

I believe that you all are over-complicating it. As recently posted in the thread about nielm's aspect switcher, you really only need 4 zoom levels:

1) 16:9 file, 16:9 video
2) 16:9 file, 4:3 video
3) 4:3 file, 16:9 video
4) 4:3 file, 4:3 video

The file information comes from the file itself. Is it HD? If so use 1 or 2. If not, use 3 or 4. Then there is a threshold that you set and if the aspect ratio is above that, use 1 or 3. If not, use 2 or 4.

While it would be interesting to use a pixel accurate rectangle to define what is displayed, there is no point. I say this because, generally, the video DOES go to the edge of the rendered frame. It may not go to all 4 edges, but it typically goes to at least 2 of them.

Also, maybe we should create a whole new thread for this? I'm sure erik will implement this in Comskip soon, if he hasn't already, and therefore it isn't a ShowAnalyzer only feature.

Jere

[Humanzee]

Originally Posted by Jere_Jones

generally, the video DOES go to the edge of the rendered frame. It may not go to all 4 edges, but it typically goes to at least 2 of them.

Typically yes, however not always. A pixel accurate solution, though complicated, would work for all formats. If the community is putting in the work to do this, it might as well be as complete a solution as possible. I guess what I am saying is that if you can supply the extra data in your .aspects file, an plug in developer could use it or not. But if its not there, there is no possiblility. I would think that it being interesting is as good a reason to supply the info as any.

[erik]

This is what I implemented in the next build

0:00:00.04  704x 576 1.24 minX=  10, minY=  10, maxX= 694, maxY= 566
0:03:12.91  704x 576 0.98 minX=  82, minY=  10, maxX= 622, maxY= 566
0:03:18.31  704x 576 1.24 minX=  10, minY=  10, maxX= 694, maxY= 566
0:03:27.52  704x 576 0.98 minX=  82, minY=  10, maxX= 626, maxY= 566
0:03:37.87  704x 576 1.24 minX=  10, minY=  10, maxX= 694, maxY= 566
0:04:07.80  704x 576 0.98 minX=  82, minY=  10, maxX= 626, maxY= 566
0:04:56.27  704x 576 0.92 minX=  98, minY=  10, maxX= 606, maxY= 566
0:05:27.51  704x 576 0.00 minX=  86, minY=  74, maxX= 618, maxY= 502
0:05:30.36  704x 576 1.24 minX=  86, minY=  74, maxX= 618, maxY= 502
0:05:43.12  704x 576 0.00 minX=  90, minY=  38, maxX= 618, maxY= 530
0:05:46.19  704x 576 1.09 minX=  86, minY=  46, maxX= 618, maxY= 530
0:05:53.07  704x 576 1.24 minX=  82, minY=  70, maxX= 626, maxY= 506

An aspect ratio of 0.00 means the aspect ratio could not be determined for that segment, the plugin can choose to keep the same aspect ratio as the previous segment or chose the next segment depending on your preference.

This is another example

0:00:00.03 1920x1088 1.36 minX= 554, minY=  10, maxX=1366, maxY= 534
0:00:43.10 1920x1088 1.78 minX=  10, minY=  10, maxX=1910, maxY=1078

The default border is 10 so the min/max values always are at least 10 away from the borders

[Jere_Jones]

If everyone is happy with what erik came up with, so am I.

Jere

[Jere_Jones]

erik,

Can you post the format string you are using so we can make sure our outputs are the same?

Jere

[erik]

Sure

"%s %4dx%4d %.2f minX=%4d, minY=%4d, maxX=%4d, maxY=%4d\n"

where the first %s refers to the time converted to a string.
Its designed to generated fixed positions on a line, easy to scan (I hope).

[Jere_Jones]

Originally Posted by erik

"%s %4dx%4d %.2f minX=%4d, minY=%4d, maxX=%4d, maxY=%4d\n"

Thanks!

Jere

[erik]

Here is a more complex example of output
Notice the two 1280x720 segments

0:00:00.03 1920x1088 1.78 minX=  10, minY=  10, maxX=1910, maxY=1078
0:00:04.83 1920x1088 2.17 minX=  10, minY=  98, maxX=1910, maxY= 990
0:00:43.20 1920x1088 1.78 minX=  10, minY=  10, maxX=1902, maxY=1078
0:03:43.08 1920x1088 2.30 minX=  10, minY= 130, maxX=1910, maxY= 958
0:04:08.91 1920x1088 1.78 minX=  10, minY=  10, maxX=1910, maxY=1078
0:04:38.94 1920x1088 2.17 minX=  10, minY= 114, maxX=1910, maxY= 982
0:05:24.02 1920x1088 1.78 minX=  10, minY=  10, maxX=1910, maxY=1078
0:05:39.03 1920x1088 2.88 minX=  10, minY= 218, maxX=1910, maxY= 878
0:05:56.38 1920x1088 2.57 minX=  10, minY= 178, maxX=1910, maxY= 918
0:06:09.03 1280x 720 1.39 minX= 154, minY=  10, maxX=1126, maxY= 710
0:07:09.26 1920x1088 1.78 minX=  10, minY=  10, maxX=1910, maxY=1078
0:07:19.37 1920x1088 2.07 minX=  10, minY=  82, maxX=1910, maxY=1006
0:07:23.94 1920x1088 1.78 minX=  10, minY=  10, maxX=1910, maxY=1078
0:21:02.16 1920x1088 2.17 minX=  10, minY= 106, maxX=1910, maxY= 982
0:21:32.09 1920x1088 1.78 minX=  10, minY=  10, maxX=1910, maxY=1078
0:23:06.01 1920x1088 2.17 minX=  10, minY= 106, maxX=1910, maxY= 982
0:23:32.04 1280x 720 1.39 minX= 154, minY=  10, maxX=1126, maxY= 710
0:24:32.07 1920x1088 1.78 minX=  10, minY=  10, maxX=1910, maxY=1078

I later forced the removal of the border of 10 in the .aspects output, so 10 would become 1 and 1078 would become 1088.

0:00:00.03 1920x1088 2.60 minX=   1, minY= 178, maxX=1920, maxY= 918
0:00:00.96 1280x 720 1.36 minX= 154, minY=   1, maxX=1126, maxY= 720

[Jere_Jones]

I would recommend keeping the border. It would provide an easy way to give the user some clipping control. In the US, a lot of shows have some black and white noise at the top that is the Closed Caption information. Being able to clip that out would be nice.

Jere

[Humanzee]

Thanks guys, this seems to cover all of the possible scenario's I could think of. I suppose that the border clipping could be an additional value stored in the configuration files for SA and Comskip.

This way a user could set it to 0 if they wanted to correct for and clip borders via overscan settings in Sage. Or set a value like 10px to have the yet to come auto aspect plug-in clip the borders for you based on the zoom level and the adjusted output in your files.

Would you want 4 separate values for each border? I.e. isn't cc data only on the top or bottom of SD broadcasts not the sides? In this case should the border clipping values be stored distinctly from those used for evaluating frames while commercial detecting?

[erik]

Originally Posted by Humanzee

Would you want 4 separate values for each border? I.e. isn't cc data only on the top or bottom of SD broadcasts not the sides? In this case should the border clipping values be stored distinctly from those used for evaluating frames while commercial detecting?

Why not let the plugin developer determine how much border to skip as minimum.
I prefer not to couple settings for different application that have a different purpose.

[Humanzee]

either way

[Jere_Jones]

0.9.4 - March 21, 2008
- Added exception for Stream ID 0xBD in VideoRedo files. Stream ID will now report as 0x81.
- Added Teletext support for DVRMS files.
- Updated automatic aspect ratio output to comply with discussion here

Enjoy,
Jere

[oshapir]

Originally Posted by Jere_Jones

0.9.4 - March 21, 2008
- Added exception for Stream ID 0xBD in VideoRedo files. Stream ID will now report as 0x81.
- Added Teletext support for DVRMS files.
- Updated automatic aspect ratio output to comply with discussion here

Enjoy,
Jere

Can NOT go to your Web Site and upgrade - it was hacked

Please check it...

Oren.

[geogecko]

Got a copy before it got hacked I guess...

ShowAnalyzerWithSchoolHouseSetupBeta.0.9.4.exe

I'll leave up this host for a while, until everything is back to normal.