Comment 14 for bug 229949
Revision history for this message
| Cory Maccarrone (darkstar6262) wrote | #14 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
That hadn't been my experience. Actually, with my configuration, I find bob deinterlacing to be less CPU intensive than any other deinterlace filter. Under normal TV, my CPU is at ~60% load, and in previous releases where this was working, the load wouldn't go up much when in the guide. Also, I don't have this issue with other deinterlacers that consume more CPU, so I believe it has more to do with recent changes that were introduced into the deinterlacer.
I didn't start seeing this problem until I upgraded my machine to hardy with 0.21.0. Previously I was using an SVN revision of the 0.20 line with Feisty and bob deinterlacing was working perfectly, even in the guide. Something in 0.21 broke it.
Anyone else have these experiences?