[mythtv-commits] Ticket #7571: Mythfrontend 0.22 VDPAU "Sparkle" / Error noise
MythTV
mythtv at cvs.mythtv.org
Sun May 16 04:37:24 UTC 2010
#7571: Mythfrontend 0.22 VDPAU "Sparkle" / Error noise
--------------------------------+-------------------------------------------
Reporter: blammo@… | Owner: markk
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: unknown
Severity: medium | Resolution:
Mlocked: 0 |
--------------------------------+-------------------------------------------
Comment(by blammo@…):
I'm currently running the following:
MythTV Version : 24265
MythTV Branch : branches/release-0-23-fixes/mythtv/
Network Protocol : 56
Library API : 0.23.20100314-1
QT Version : 4.6.2
Options compiled in:
linux release using_oss using_alsa using_pulse using_jack
using_pulseoutput using_backend using_dvb using_firewire using_frontend
using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu
using_libfftw3 using_lirc using_mheg using_opengl_video using_opengl_vsync
using_qtdbus using_qtwebkit using_v4l using_x11 using_xrandr using_xv
using_xvmc using_xvmc_vld using_xvmcw using_bindings_perl
using_bindings_python using_opengl using_vdpau using_ffmpeg_threads
using_libavc_5_3 using_live using_mheg
And yes, the problem is still occurring. I'm not the only one having this
issue:
The problem appears to be unique to:
-- Motherboard with integrated Nvidia video chipset
-- add on video card of newer NV chipset
-- MPEG2 playback
-- mythTV
See the following thread:
http://www.nvnews.net/vbulletin/showthread.php?t=136817
Nvidia has an idea how to fix/work-around the behavior, but their side of
the fix isn't in any shipping drivers yet. I'm curious what can be done
from the MythTV side, since it only appears to happen in Myth playback.
(Mplayer/XINE/etc don't exhibit the behavior)
--
Ticket URL: <http://svn.mythtv.org/trac/ticket/7571#comment:16>
MythTV <http://www.mythtv.org/>
MythTV
More information about the mythtv-commits
mailing list