[mythtv] VDPAU Fails after 3 prior successful plays

Brad DerManouelian myth at dermanouelian.com
Mon Sep 28 14:48:24 UTC 2009


On Sep 28, 2009, at 6:41 AM, Phil Linttell wrote:

> On 09/28/2009 08:00 AM, mythtv-dev-request at mythtv.org wrote:
>> Message: 3
>> Date: Sun, 27 Sep 2009 20:22:39 +0100
>> From: Richard Taylor<richard at artaylor.co.uk>
>> Subject: [mythtv] VDPAU Fails after 3 prior successful plays
>> To: Development of mythtv<mythtv-dev at mythtv.org>
>> Message-ID:<4ABFBB7F.2020008 at artaylor.co.uk>
>> Content-Type: text/plain; charset=windows-1252; format=flowed
>>
>> Hi,
>>
>> I am using an Acer Revo R3600, nVidia drivers 185.18.36 and Kernel
>> 2.6.31 with an svn build of MythTV (svn r.22076).
>>
>> I have noticed a couple of issues with VDPAU under MythTV - both of  
>> the
>> below are reproducible on my system.
>> I hope to help debug and fix if given an idea of where to start  
>> looking.
>>
>> 1) If VDPAU setup fails, the player does not fall back to the  
>> ffmpeg /
>> XV setting in the playback settings list, but simply hangs.
>> 2) The first 3 times I watch a recording work, at the 4th time of  
>> trying
>> to watch a recording it will show "Please Wait..." for longer than
>> normal followed by a corrupt image of a previously rendered UI  
>> screen.
>> The only way I have found to remedy this is to kill off  
>> mythfrontend and
>> restart.
>>
>> I haven't yet determined whether (2) is time related or not. The  
>> system
>> is solely used as a frontend, so there is nothing else happening on  
>> the
>> system.
>>
>> Any guidance appreciated!
>> Kind regards,
>> Richard.
>>

I've been living with this problem for a while on my Mac Mini (intel  
CPU) running Ubuntu, as well. All of my content is 720p. Sometimes  
killing MythFrontend was enough, but sometimes I had to kill the whole  
x-session in order to get anything to play back afterwards. On a whim  
last night, I changed the resolution of my display to native 720p and  
I haven't crashed at all so in my case it looks like stretching  
content was the culprit.

-Brad



More information about the mythtv-dev mailing list