1080i material not deinterlacing under 1.0.1.0 (1 Viewer)

[Andrew H]

TV-Server Version:
MediaPortal Version: 1.0.1.0 Upgrade
MediaPortal Skin: the latest Blue3Wide
Windows Version: WinXP-Home/SP3
CPU Type: AMD BE-2350 (45W X2)
HDD: Various -- 2.4TB
Memory: 2 x 1GB
Motherboard: Abit AN-M2HD
Video Card: On-Board NVidia 7050PV
Video Card Driver: 181.20
Sound Card: On-board RealTek
Sound Card AC3: On-board Optical out
Sound Card Driver: R181
1. TV Card: ATi HDTV-Wonder
1. TV Card Type: ATSC/NTSC + A/V
1. TV Card Driver:
2. TV Card: Hauppauge HVR-1600
2. TV Card Type: ATSC/NTSC + A/V
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec: PureVideo, PDVD7
MPEG2 Audio Codec: AC3Filter v1.09a
h.264 Video Codec: Cyberlink
Satelite/CableTV Provider:
HTPC Case: Antec Sonata II
Cooling: AMD stock HSF
Power Supply: Antec Earth 430W
Remote: Hauppauge 45-key
TV: Sony VPL-AW15
TV - HTPC Connection: HDMI 1280x720

I'd been using Cyberlink and Purevideo for my decoding on MP 1.0.0.0 with excellent picture quality. After my upgrade to 1.0.1.0 I was shocked by the jitteryness of the 1080i material - whether Live-TV or recorded-TV playback; however, 720p format broadcast/playback is fine. I looked into the logs and believe to have found where the TsReader is classifying the interlace flag as false on 1920x1080 rez... While this could be the issue I don't know if the TSReader was modified, or if it's only an indication of the root cause.

When I press <Shift><1> and display the VRM framerate I get 60 on 720p but only 30 on 1080i which VRM used to show 60 on both formats (indicating VRM output is post-deinterlacing). Low VRM framerates causes a jittery appearance, I know because I had to disable AMD's Cool & Quiet a long time ago because it dropped the framerate...

Could the following entry in Mediaportal.log be pointing to the root cause of MP 1.0.1's 'failure' to deinterlace my 1080i broadcast/TV material?

2009-04-13 18:09:07.765625 [Info.][MPMain]: TsReaderPlayer: OnVideoFormatChanged - streamtype=MPEG2 resolution=1920x1080 aspect ratio=16:9 bitrate=13150000 isInterlaced=False

Which is also reported in the TsReader.log:

13-04-2009 18:09:07.765 [a8c]DeMultiplexer: 30 video format changed: res=1920x1080 aspectRatio=16:9 bitrate=13150000 isInterlaced=0

For now the jitteryness is lessened on slow shots by using the MPC-Video codec, but panning is really bad and the CPU hovers at 46%... I can't believe more folks using interlaced format haven't noticed this!

Thanks
Andrew

 

[bellzz]

I'm having the exact same problem. I can't believe that more people haven't seen this too.

However I believe that my working MP 1.0 logs show False and 0. So I'm not sure if this is the root cause.

 

[philhend]

Hmm - this is the same problem I have been tackling - just started trolling the forums - everything was working well on 1.0.0 but after 1.0.1 on my client the 1080i signals went to pack - set the resolution to 720p and it is ok.. Have upgraded drivers etc...

Will investigate more and reinstall 1.0 to see if this is a problem.

On more thought main tv server using vista/evr - no problem - client windows xp sp3/vm9.... more investigations forthcoming.....


Phil

 

[Andrew H]

This isn't really a function of your screen rez -- I see you have a 1080p PJ. When you say you set the rez to 720p and it's OK what do you mean? I'm speaking of the source material not deinterlacing from 1080i hence I'm getting 30fps - essentially the even or odd frames only.

 

[philhend]

When the video card is set at anything like 1080p/60 /50 /25 it jitters badly with 1080i source files - 720p files are ok. - this was ok with 1.0.0,

If I set the video card to 720/ anything it works ok on both the tv or or PJ....

But I am not 100% sure what the 'delta' change was...

I am going to investigate more - i thought the network was playing up to the client - but not so sure now......

I will Probably go back to 1.0.0 SVN and get a stable place and then detla the upgrade to make sure it is not source problem or driver....

Could be many things including my thumbs....

 

[bellzz]

TV-Server Version:
MediaPortal Version: 1.0.1.0 Upgrade
MediaPortal Skin: the latest Blue3Wide
Windows Version: WinXP-Home/SP3
CPU Type: AMD BE-2350 (45W X2)
HDD: Various -- 2.4TB
Memory: 2 x 1GB
Motherboard: Abit AN-M2HD
Video Card: On-Board NVidia 7050PV
Video Card Driver: 181.20
Sound Card: On-board RealTek
Sound Card AC3: On-board Optical out
Sound Card Driver: R181
1. TV Card: ATi HDTV-Wonder
1. TV Card Type: ATSC/NTSC + A/V
1. TV Card Driver:
2. TV Card: Hauppauge HVR-1600
2. TV Card Type: ATSC/NTSC + A/V
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec: PureVideo, PDVD7
MPEG2 Audio Codec: AC3Filter v1.09a
h.264 Video Codec: Cyberlink
Satelite/CableTV Provider:
HTPC Case: Antec Sonata II
Cooling: AMD stock HSF
Power Supply: Antec Earth 430W
Remote: Hauppauge 45-key
TV: Sony VPL-AW15
TV - HTPC Connection: HDMI 1280x720

I'd been using Cyberlink and Purevideo for my decoding on MP 1.0.0.0 with excellent picture quality. After my upgrade to 1.0.1.0 I was shocked by the jitteryness of the 1080i material - whether Live-TV or recorded-TV playback; however, 720p format broadcast/playback is fine. I looked into the logs and believe to have found where the TsReader is classifying the interlace flag as false on 1920x1080 rez... While this could be the issue I don't know if the TSReader was modified, or if it's only an indication of the root cause.

When I press <Shift><1> and display the VRM framerate I get 60 on 720p but only 30 on 1080i which VRM used to show 60 on both formats (indicating VRM output is post-deinterlacing). Low VRM framerates causes a jittery appearance, I know because I had to disable AMD's Cool & Quiet a long time ago because it dropped the framerate...

Could the following entry in Mediaportal.log be pointing to the root cause of MP 1.0.1's 'failure' to deinterlace my 1080i broadcast/TV material?

2009-04-13 18:09:07.765625 [Info.][MPMain]: TsReaderPlayer: OnVideoFormatChanged - streamtype=MPEG2 resolution=1920x1080 aspect ratio=16:9 bitrate=13150000 isInterlaced=False

Which is also reported in the TsReader.log:

13-04-2009 18:09:07.765 [a8c]DeMultiplexer: 30 video format changed: res=1920x1080 aspectRatio=16:9 bitrate=13150000 isInterlaced=0

For now the jitteryness is lessened on slow shots by using the MPC-Video codec, but panning is really bad and the CPU hovers at 46%... I can't believe more folks using interlaced format haven't noticed this!

Thanks
Andrew

What I have noticed is that this problem was introduced between SVN 01/23/09 (1080i still works) and 02/15/09 (no longer working).

What was the difference between these two builds?


I will try to submit some logs from 01/23/09 vs 02/15/09 to see if someone can decode this.

No skins/No SAF/No Haali...just blue normal. on a PC for test ATI HD 3200. ASUS M3A78-EM.

 

[bellzz]

Attached are the two logs from Working (1.23) to not working (2.15)

Help Please!!!

 

[Andrew H]

I'm gonna suppose it's a real minor issue to fix but doesn't draw a great deal of attention because the bulk of the users are European and not subject to interlaced format?

 

[Owlsroost]

TV is interlaced in Europe too....

I don't have HD TV capability but I do play a lot of 1080i material in MP 1.0.1 - it's deinterlacing correctly (both 50Hz and 60Hz material).

Are people having the problem with 1080i video files other than recorded TV, or is it just with material using tsreader.ax for playback ?

Tony

 

[Andrew H]

That's an excellent point. Maybe I'm showing my ignorance... It is from my ATSC (digital) TV tuner where my 1080i is jittery and I'd switched over from .mpg recordings to .ts format back when I had issue (on MP 1.0.0) with consistant audio on (what seemed like) only the 2nd tuner's recorded file. I'll go run a test... WOW -- MP 1.0.1 has changed and now only allows you to record TV in .ts format... no more .mpg files. So I do not have any interlaced 1080i that isn't .ts format, TV-based. OR is that in itself a clue?