Flickering Tv-guide and other overlays with EVR enabled (5 Viewers)

[Realkane]

Hi,

I have an AMD Dual-Core CPU and an ATI 4350 (I hope, that this is the correct number, but it's a newer ATI card).
On Vista, I remember that I have the flickering too. But with Windows 7 RC1 and the Standarddriver which is included (I'm not using the ATI Catalyst!!!), there is NO flickering.

I hope, someone can confirm / discard this.

I forgot: I'am using the PowerDVD9 MPEG2 decoder.

Greetings,
Christian

 

[disaster123]

are you shure that you're using HW deinterlacing?

 

[Realkane]

Ah, sorry, I turned it off, because of seeking-problems.

But, now for testing, I turned it on and it seems to work too! No flickering on my htpc.

EDIT: Ok, I give up. After watching some time, it seems to flicker once a minute. This is not mutch, but also not zero

 

[Realkane]

Hi,

I played around with this problem. On my HTPC, the error does not occur very often. But with my actual changes, I didn't saw the flickering again.

Does anyone here has this problem very often?

Thanks,
Christian

 

[providers]

I have it all the time when using a codecs using DXVA (decoding through graphics chip)
But it only appears when watching tv on SD channels.

HD channels does not flicker in tvguide

/Providers

 

[MLH01]

I am getting confused here. I originally thought the flickering problem was related to the skin engine (where flickering was more prominent in the TV guide) and with EVR enabled, as per the thread title.

There has been a fair bit of talk on codecs, which are related to video playback.

Is there something I am missing? I didn't think the skin engine required codecs - at least for 'still' images like the TV guide or home screen.

Or are these 2 (what I thought were separate) issues related?

MLH01

 

[Spragleknas]

Not exactly true. On my machine only Cyberlink codecs expose this issue. If I e.g. use the ATI avivo codecs which make also use of DXVA I don't see any flickering at all. It also does not flicker using ffdshow software decoding with interlaced flag for the renderer to let the GPU do the deinterlacing.

IIRC ATi AVIVO codecs does not offload CPU as much as (newer) CyberLink. (I write newer, because I think I read somewhere that the AVIVO codecs are based on CyberLink).

Not sure, but it might be reøated to this:
ATI Avivo

During capturing, ATI Avivo amplifies the source, automatically adjust its brightness and contrast. ATI Avivo implements 12-bit transform to reduce data loss during conversion, it also utilizes motion adaptive 3D comb filter, automatic color control, automatic gain control, hardware noise reduction and edge enhancement technologies for better video playback quality.

In decoding, the GPU core supports hardware decoding of H.264, VC-1, WMV9, and MPEG-2 videos to lower CPU utilization (it should be noted that the bitstream processing/entropy decoding still requires CPU processing). ATI Avivo supports vector adaptive de-interlacing and video scaling to reduce jaggies, and spatial/temporal dithering, enabling 10-bit color quality on 8-bit and 6-bit displays during process stage.
Source: Wikipedia

I do sometimes think it is a bit hard to distinguish between ATI AVIVO codecs or the "function" (UVD for HD material).

 

[tourettes]

A quick test with additional D3D device locking code for EVR / GUI rendering. Please test following .dll (replace the one in MP folder). Most likely it won't work woth MP 1.0.2 version.

I have no clue if it solves the flickering, most likely not but as I have no ATI HW to test with (anymore) I need someone else to test it.

 

[Realkane]

Sorry tourettes, but it seems that it could not fix the bug.
But, your on the right way

Greetings,
Christian

 

[MLH01]

A quick test with additional D3D device locking code for EVR / GUI rendering. Please test following .dll (replace the one in MP folder). Most likely it won't work woth MP 1.0.2 version.

I have no clue if it solves the flickering, most likely not but as I have no ATI HW to test with (anymore) I need someone else to test it.

I would be interested in testing any new code, although I use MP 1.0.2 so will not try this particular test version.

Glad to see this issue being worked on though

MLH01.