I have a drm vsync question
I'm currently getting myth working on a VIA CN400 unichrome-pro board...
the current problem I've got is that the mythplayer is running away with
itself and seems to have problems with the drm timing calculation.
A log from a cn400 (@75Hz) playing back a 25fps
Ivor Hewitt wrote:
I have a drm vsync question
I'm currently getting myth working on a VIA CN400 unichrome-pro board...
the current problem I've got is that the mythplayer is running away with
itself and seems to have problems with the drm timing calculation.
A log from a cn400 (@75Hz)
Blammo wrote:
Just wanted to say a big thank you to all those involved in helping
make Myth a better tool, both testers and developers.
For the first time, since 0.17 came out, I actually had an HD
recording of Alias this week that didn't drop audio completely at some
point in the recording. (most
Hi Glenn,
On 31/3/05 6:09 PM, Glenn Moloney [EMAIL PROTECTED] wrote:
Hi All,
I have a feature (well - I call it a feature) I want to implement:
Allow overlapping recordings on one tuner.
I am interested in feedback on how best to implement this feacture - in
a manner
Doug Larrick wrote:
Ivor Hewitt wrote:
This is not a Myth problem and bound to be a driver problem, but I
wondered if someone who knew how the DRM calculation code worked could
suggest why it would have concluded that the refresh rate matched rather
than just failing.
Looking at the code...
Ivor Hewitt wrote:
Doug Larrick wrote:
Looking at the code... refresh rate comes from the videoout method, not
the vsync method. Unichrome uses XvMC, right? I can't see anything
weird in Myth's computation. What does xvidtune say about your vertical
sync rate?
Hi Doug,
I'm not at the machine at
Doug Larrick wrote:
Ivor Hewitt wrote:
# xvidtune -show
1280x1024 0.00 1280000 1024000
Hmmm, could that be the problem? The driver is using a synthetic
modeline which isn't fully populated?
That's definitely weird. At 0 MHz pixel clock, it should take an
infinite
Ivor Hewitt wrote:
Would it be more accurate for mythtv to actually time the drm sync
interval to establish the refresh rate rather than use the refresh rate
reported by X? or does it just use that value as a guide?
Probably not. Reading what's specified to the hardware should be more
Doug Larrick wrote:
Ivor Hewitt wrote:
Would it be more accurate for mythtv to actually time the drm sync
interval to establish the refresh rate rather than use the refresh rate
reported by X? or does it just use that value as a guide?
Probably not. Reading what's specified to the hardware should
Folks,
Im still having problems playing back about half of
my HD content. With CVS as of last night I am closer but no where near the
level we should probably be at. I realize were making significant
progress and I want to let you all know how much it is appreciated.
So, with CVS as
On Wed, Mar 30, 2005 at 07:51:16PM -0500, Daniel Kristjansson wrote:
Ok, this is a big patch.
It merges the XVideo and XvMC video output implementations.
I spent most of my evening last night watching 1080i programming
played back on an FX5200 using XvMC on a 720p display with bob
On Thursday 31 March 2005 05:21 pm, Daniel Kristjansson wrote:
What happens is that MPEG has a series of frames, say: IBBBPBBBI
The I frames don't depend on any other frames, but the B frames depend
on an I and a P, and the P frame depends on the previous I. But once
MythTV displays a frame,
This is a version of a patch that I've been applying to mythtv since
0.11. It adds an option in the Mythfrontend/Setup/TV/General settings
which causes the backend to delete the oldrecorded entry for any show
which is auto-expired due to lack of disk space. (I don't think this
effects the
This is a version of a patch that I've been applying to mythtv since
0.11. It adds an option in the Mythfrontend/Setup/TV/General settings
which causes the backend to delete the oldrecorded entry for any show
which is auto-expired due to lack of disk space. (I don't think this
effects
On Friday 01 April 2005 12:21 pm, Isaac Richards wrote:
On Thursday 31 March 2005 05:21 pm, Daniel Kristjansson wrote:
What happens is that MPEG has a series of frames, say: IBBBPBBBI
The I frames don't depend on any other frames, but the B frames depend
on an I and a P, and the P frame
Quoting Sami Röppänen [EMAIL PROTECTED]:
Correct me if I'm wrong.. But disenabling 'use dvb card on demand'
causes the dvb card(s) to run hot all the time, and that is not good for
a quiet, long lasting system. At least this was the case down 0.15.
Is this really the case? I haven't noticed
HI!
Ivor Hewitt wrote:
Yay. Thanks for the tip Doug, forcing the driver to use a real modeline
and we have smooth video. Magic.
Is this also possible with NVidia cards?
I always get:
DRMVideoSync: Could not open device /dev/dri/card0
Thomas
___
Thomas Börkel wrote:
HI!
Ivor Hewitt wrote:
Yay. Thanks for the tip Doug, forcing the driver to use a real
modeline and we have smooth video. Magic.
Is this also possible with NVidia cards?
I always get:
DRMVideoSync: Could not open device /dev/dri/card0
nVidia cards don't
This is a version of a patch that I've been applying to mythtv since
0.11. It adds an option in the Mythfrontend/Setup/TV/General settings
which causes the backend to delete the oldrecorded entry for any show
which is auto-expired due to lack of disk space. (I don't think this
Hi,
I encountered this annoying bug with the CVS head, I entered it also into
the Bugzilla (Bug 264):
I have a dual head setup in which I use the screen 0 for my primary
monitor, and screen 1 for output to projector (for watching TV and
movies). With the current CVS head, mythfrontend cannot
Oh, almost forgot:
The -geometry switch of mythfrontend didn't seem to work at all either :(
Sorry, I was too hasty. This switch does work, and thus allows me to
circumvent this
bug. The real switch is --geometry, not -geometry like --help states :)
--
--PJ
Oh, almost forgot:
The -geometry switch of mythfrontend didn't seem to work at all either :(
Sorry, I was too hasty. This switch does work, and thus allows me to
circumvent this
bug. The real switch is --geometry, not -geometry like --help states :)
Looks like both should work:
Am Freitag, 1. April 2005 21.38 schrieb Joel Anderson:
This is a version of a patch that I've been applying to mythtv since
0.11. It adds an option in the Mythfrontend/Setup/TV/General settings
which causes the backend to delete the oldrecorded entry for any show
which is
Attached patch adds a setting to MythMusic, when set, will start playing an
inserted audio CD automatically. Also, an option has been added to the
menu (M), from which you start playing an inserted CD immediately without
going through the Edit playlist screen. This latter option is mainly
On Thu, Mar 31, 2005 at 11:23:12PM -0700, Blammo wrote:
Just wanted to say a big thank you to all those involved in helping
make Myth a better tool, both testers and developers.
For the first time, since 0.17 came out, I actually had an HD
recording of Alias this week that didn't drop audio
On Fri, 2005-04-01 at 12:53 -0500, Isaac Richards wrote:
Actually, if the release_buffer callback from libavcodec is accurate as to
when it's done with the frame, it could be as simple as just refcounting the
frames (2 to start, -1 when displayed, -1 when marked unused by
release_buffer),
Jonas,
I tried applying your patch to my Debian64 system. It didn't apply and instead
gave me this
[EMAIL PROTECTED]:~/src/mythtv$ patch -p1 patch.txt
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
Hi,
I've got a myth box set up on my home server / capture box. When I set up
the system I wasn't able to get an additional harddrive as I was already
getting 3 for the software raid array. As a result to prevent the myth
system from crashing the box, I set up a quota for the use that mythtv
On Mar 23, 2005 2:20 AM, Isaac Richards [EMAIL PROTECTED] wrote:
I don't really like all the ifdefs in this - possible to factor it out so it's
a bit cleaner?
Isaac
Sorry, I somehow didn't see the reply for a week or so. I'm not happy
about the number of ifdefs, either, but I also didn't
Jarod Wilson wrote:
On Wednesday 30 March 2005 00:39, Juha Kuikka wrote:
running CVS from a few days ago, and I've noticed for awhile now that
many buttons (next, No, leave my card settings alone, etc) won't
click with enter/space. Well, they change color as if they're
depressed, but they don't
30 matches
Mail list logo