1080i channels not working anymore (2 Viewers)

[HTPCSourcer]

After I updated, I get a "could not start graph" error on 1080i channels. I narrowed it down to the deinterlacing itself. When using Core AVC (on any of my MP clients, with any Core AVC versions), I get the graph error on 1080i channels with pure Software deinterlacing (Single Field or Bob). When I set the Core AVC configuration to hardware deinterlacing, the channels work.

Strange. It works for me (version 1.8.0) both at software and hardware deinterlacing. I actually set it to hardware right now and experience no frame issues like you.

Regards, HTPC_Sourcer

 

[Spooky]

I actually set it to hardware right now and experience no frame issues like you.

This highly depends on the graphics hardware. The Radeon HD 3200 does not seem to be enough for the type of hardware deinterlacing that Core AVC uses.

Hm, well I don't know how to tackle this problem right now. Only the MediaPortal version changed and nothing else. And the log does not seem to give any detailed information about this? Shouldn't there be some indication usually as to why the graph could not be created?

 

[Spooky]

Ah, it seems Catalyst 9.4 fixed it. I originally tried 9.3 a few weeks ago, but had to revert to 8.12 (or was it even 8.10) because of issues in Media Player Classic. I just tried Catalyst 9.4 today on the main HTPC and now 1080i channels work again without hardware deinterlacing in Core AVC.

Maybe a driver update will fix it for my Laptop too, but the most recent NVidia driver is not available for it yet.

 

[Andrew H]

I'm getting jittery 1080i after 1.0.1.0 upgrade... It gets better with the MPC s/w codec but the CPU is at 46%...

There is something not communicating that signals the deinterlacing...

 

[Andrew H]

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

 

[Spooky]

Seems plausible.

 

[Andrew H]

Thanks... but more my point is did the Team alter the TsReader and inadvertantly cause this?

Maybe I should post this as a bug report instead of here...