|
Have you checked that you have Vector Adaptive de-interlacing enabled in your Catalyst Control Center in the de-interlacing options?
AIUI when you use hardware acceleration, stuff like de-interlacing is offloaded from the codec to the graphics hardware and graphics drivers, and the quality of de-interlacing is thus dependent on the graphics card and drivers, not the codec itself. (Things can get confusing when the codec is produced by a graphics card manufacturer as they may provide hardware acceleration tweaks in their codec settings) In other words - two people may be running the same codec on different set-ups and get different results.
Theoretically the codec converts the H264 or MPEG2 encoded video - which for broadcast purposes is always interlaced (whether the source within is interlaced or progressive) to uncompressed video - but still interlaced. This then needs to be de-interlaced as PC screens are progressive. Some codecs additionally do this - but this isn't actually strictly a codec function - and most graphics cards that use DXVA will de-interlace as well.
De-interlacing is complicated - and can be done in various ways depending on the processing power available from the CPU or GPU - and performance varies on the source material.
Simple de-interlacing can get defeated where the source has a mix of interlaced and progressive content (say an interlaced rolling or crawling caption over a progressive background), and in some cases where a straight Bob (interlaced source) / Weave (progressive source) motion adaptive technique is used it can take a while to switch modes or not switch correctly at all. Better systems will use Vector adaptive techniques, where the screen is divided up into blocks and different de-interlacing techniques are used for each block, and the motion of objects around the screen is tracked to improve the resulting progressive de-interlaced picture.
If you can select Vector Adaptive - then do so.
You may find in some situations that you can't have Edge Enhancement and Noise Reduction options enabled at the same time as Vector Adaptive de-interlacing - as the processing requirement is too high. My advice in those situations is get the de-interlacing right and don't bother with EE and NR.
ISTR that the HD 3200 Radeon's would only run Vector Adaptive with high-end AMD processors, because they needed a faster Hyper Transport level than the slower CPUs could manage (though they don't use the CPU for video) - but this may have been to do with shared memory issues. I don't know about the HD 4200.
Certainly my nVidia 9400 IGP does a good vector adaptive de-interlace and has no problems with tickers etc., and neither does my ATI 4450, but my old Radeon HD 3200 IGP wasn't as good.
Additionally, make sure that your desktop refresh rate is matched to your video source, to avoid judder from frame repetition or dropping.
UK SD/HD TV and European DVD, and some recent BBC 1080i Blu-rays - 50Hz
1080p Blu-rays - 23.976/23Hz or 24Hz
Most 1080i Blu-rays - 59.94/59Hz or 60Hz
|