Summary: | DAL DCE 10 missing CEA interlaced modes | ||
---|---|---|---|
Product: | DRI | Reporter: | Andy Furniss <adf.lists> |
Component: | DRM/AMDgpu | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | enhancement | ||
Priority: | low | CC: | fdsfgs |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Andy Furniss
2016-03-23 22:37:39 UTC
Feature request. :) We originally didn't see much use of interlace anymore so it was never a priority. The implementation shouldn't be particularly hard and we might be getting around to it sometime but it's definitely not at the top of our list. Do you see any advantages to the TV's deinterlacer as opposed to SW (or HW decoder) deinterlacing? OK, fair enough, I guess very few would ever make use like this anyway. From a UK resident POV, interlace is likely to be around for plenty of time to come, as we get DVB 1080i (or p) for FTA TV. Whether it's better than (realtime) s/w or GPU - a bit but not vastly. Current GPU does artifact a bit and doesn't do diagonal interpolation so it's a bit jaggy on the right scene. yadif is probably better, but it's not motion adaptive like my TV is, so a bit softer (though sometimes that can be good at hiding artifacts). I use a desktop PC - so have enough CPU and GPU power not to really need anything else. I suppose someone with a weaker set up may benefit - but now I'm just making up untested hypotheticals. They would still need enough (single thread) CPU perf to interlace aware convert 420 to 422 and run ffmpeg tinterlacex2 filter. So no real need for me, other than always wanting as many options available as possible, maybe one day I will upgrade my TV to one that has the best de-interlacer in the world, or maybe not :-) -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/67. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.