[mythtv] A need for advanced player settings
adeffs.mythtv at gmail.com
Wed Jun 1 17:11:21 UTC 2011
On Tue, May 31, 2011 at 1:48 PM, Kyle Rose <krose at krose.org> wrote:
> This is one of the first emails I found when searching for a solution
> to this problem. While the problem I am seeing is likely to be a
> variant of cause #1, the "solution" of disabling VDPAU decoding is not
> possible with 1080p h.264 content on an Atom system, while my own
> solution of increasing the size of the ring buffer demonstrably works.
> So I would not cite without comment this email as the complete,
> authoritative list of potential causes and solutions.
no, I never said it was, just pointing out the information therein,
which from your response I don't think you read.
the VDPAU issue is a known issue, and apparently there are dev's
working on it. It may have even be "solved" in trunk with a newer
ffmpeg sync from what one user reported in initial testing.
for the listed issue #2: Personally, I've upped the vdpaubuffersize on
my atom and GT220 systems and it has helped in that the issue is
"shorter" or less annoying, but it does not solve the problem. This is
on 3 atom systems and two GT220 systems. Worse, because of the short
drop in audio some receivers, when using digital audio, take longer
than others to resync, so for instance it can take anywhere from 1/2
second to re-establish audio to 4 or 5 seconds for some.
#1/#3 For the issue that has to do with the backend just not sending
the data for whatever reason, that too looks to be a well known issue
amongst the dev's and also being looked into and hopefully will be
fixed for 0.25 as well.
Before you ask, read the FAQ!
then search the Wiki, and this list,
Mailinglist etiquette -
More information about the mythtv-dev