News:

Latest versions:
Server plugin: 0.5.1
MVP dongle: 0.5.2
Raspberry Pi client: 0.5.2
Windows client: 0.5.2-1

Main Menu

16:9 SD channels shown with wrong aspect ratio

Started by sirwio, December 30, 2013, 09:09:34

Previous topic - Next topic

sirwio

Noticed this behaviour at first while watching some old recordings made in SD but can confirm that its the case while watching live tv as well.

Our tv's are all 16:9 tv's and the vompclient settings are:
[TV]
Widemode = Letterbox
Aspect = 16:9

16:9 HD (720p and 1080i) channels fill the whole tv screen as one would expect but SD channels show something that is more like a 4:3 ratio with big black bars on the sides. If the Wideomode is changed to "Chop Sides" the picture fill the complete tv screen but with a huge overscan. This behaviour is seen on both 704x576i and 720x576i broadcasts.

I have attached a log file where I start out watching a channel in HD (1280x720) resolution and then switching to the same channel in SD (704x576). Note that this is a slightly modified vompclient where I print out the reason for failures in the mp3 audio decoding. It is what I use while troubleshooting the audio chirps described in other posts.

Noteworthy is that the log entry where the VideoType is shown says:
15:30:17.836841 [notice] 2079 Video - VideoType 148 x 2001 i: 1
after the switch. If one choose the channel from the channel list instead one get the correct printout of VideoType 704 x 576!

The same wrong log entry has also been observed while switching from an SD channel to an HD channel. Below is some channel switches made grep'ing only VideoType. Observe the weird resolution 14x480 (Should really be 1280x720).

20:17:32.143785 [notice] 2314 Video - VideoType 1280 x 720 i: 0
20:17:38.653976 [notice] 2314 Video - VideoType 1280 x 720 i: 0
20:17:44.114826 [notice] 2314 Video - VideoType 1920 x 1080 i: 1
20:18:02.565919 [notice] 2314 Video - VideoType 1920 x 1080 i: 1
20:19:36.850602 [notice] 2314 Video - VideoType 704 x 576 i: 1
20:20:14.184033 [notice] 2314 Video - VideoType 14 x 480 i: 1
20:20:44.583299 [notice] 2314 Video - VideoType 1280 x 720 i: 0
20:20:52.330869 [notice] 2314 Video - VideoType 1280 x 720 i: 0
20:21:21.655706 [notice] 2314 Video - VideoType 1920 x 1080 i: 1
20:21:59.436071 [notice] 2314 Video - VideoType 720 x 576 i: 1
20:22:24.227793 [notice] 2314 Video - VideoType 704 x 576 i: 1
20:22:31.549092 [notice] 2314 Video - VideoType 720 x 576 i: 1
20:22:36.798217 [notice] 2314 Video - VideoType 720 x 576 i: 1
20:22:47.891242 [notice] 2314 Video - VideoType 704 x 576 i: 1
20:22:54.617073 [notice] 2314 Video - VideoType 704 x 576 i: 1
20:23:16.594869 [notice] 2314 Video - VideoType 1280 x 720 i: 0
20:27:06.148200 [notice] 2314 Video - VideoType 704 x 576 i: 1
20:29:50.728992 [notice] 2314 Video - VideoType 1280 x 720 i: 0
20:30:07.083192 [notice] 2314 Video - VideoType 704 x 576 i: 1
20:30:33.556668 [notice] 2314 Video - VideoType 1280 x 720 i: 0
20:31:10.611470 [notice] 2314 Video - VideoType 1280 x 720 i: 0



MartenR

#1
Please test the current git. I hope it is fixed now.

You can ignore the weird frame sizes, they are in deinit first frame log messages correct.

Marten

sirwio