2014-01-14, 17:12
After a few weeks of being lax I rebuilt xbmc-git last night and installed it this morning only to find that a problem I've never had before with my setup is occurring. Tearing. I'm running it on a low power atom based HP thin client and crystalhd and Arch x86.
I thought at first maybe the upgrades to intel-dri,mesa et al. that occurred at the same time doing package upgrades may have been the cause but downgrading all of them didn't change anything. Also booted into the last kernel version since a kernel upgrade also took place but no change. This leaves only last night's pull of xbmc-git.
I was able to fix the tearing by disabling the option to match display refresh to video. Normally this has always worked fine, switching my TV to 24p during movie playback... it still does change the mode to 24p but I get all sorts of tearing. When I leave the option off and let it play videos in 60hz the tearing is gone.
Can anybody else with access to regular intel video hardware (or even other, just using the aforementioned playback option) confirm that there is a regression in xbmc gotham here?
I highly doubt crystalhd is at fault since I don't think they have updated the codebase upstream for many moons now. BTW I use xbmc-standalone on this machine with no desktop environment running at all so there cannot be any kind of conflict here.
I thought at first maybe the upgrades to intel-dri,mesa et al. that occurred at the same time doing package upgrades may have been the cause but downgrading all of them didn't change anything. Also booted into the last kernel version since a kernel upgrade also took place but no change. This leaves only last night's pull of xbmc-git.
I was able to fix the tearing by disabling the option to match display refresh to video. Normally this has always worked fine, switching my TV to 24p during movie playback... it still does change the mode to 24p but I get all sorts of tearing. When I leave the option off and let it play videos in 60hz the tearing is gone.
Can anybody else with access to regular intel video hardware (or even other, just using the aforementioned playback option) confirm that there is a regression in xbmc gotham here?
I highly doubt crystalhd is at fault since I don't think they have updated the codebase upstream for many moons now. BTW I use xbmc-standalone on this machine with no desktop environment running at all so there cannot be any kind of conflict here.