I believe Quicktime uses 600Hz for their clock, it can be factored
by 24, 25, 30, 50, and 60 so it can be used for film, PAL, and NTSC
with a very small framerate error.
I don't recall exactly, but I think I tried this first and found that at
least my RTC clock wouldn't have 600 as a valid
I think you have interlace sync issues. If you are running MythTv with
25Hz output frame rate the 50Hz fields can be either in sync or out of
sync. When there is motion in the picture all is smooth when the fields
are in sync. If they go out of sync you will ge a lot of motion jitter.
If you are
On Apr 12, 2005 2:58 AM, Tom Hughes [EMAIL PROTECTED] wrote:
I've done some investigating now and it seems that despite
glXQueryExtensionsString indicating that GLX_SGI_video_sync is
supported any call to glXGetVideoSyncSGI or glXWaitVideoSyncSGI
will fail.
Unfortunately by that time myth
In message [EMAIL PROTECTED]
Robert Johnston [EMAIL PROTECTED] wrote:
On Apr 12, 2005 2:58 AM, Tom Hughes [EMAIL PROTECTED] wrote:
I've done some investigating now and it seems that despite
glXQueryExtensionsString indicating that GLX_SGI_video_sync is
supported any call to
I just tried the 20050407 CVS build from ATrpms and it seems to have
terrible audio sync problems on my system.
If I start playing a recording then it starts with the audio playing
more or less normally but within a few seconds it has speeded up to
a ridiculously fast speed.
I've attached the
On Sunday 10 April 2005 10:39 am, Tom Hughes wrote:
I just tried the 20050407 CVS build from ATrpms and it seems to have
terrible audio sync problems on my system.
If I start playing a recording then it starts with the audio playing
more or less normally but within a few seconds it has
In message [EMAIL PROTECTED]
Isaac Richards [EMAIL PROTECTED] wrote:
On Sunday 10 April 2005 10:39 am, Tom Hughes wrote:
I've attached the frontend log output in case it helps - the only
thing in there that I noticed that is new is the use of OpenGL vsync
support. Previous
I've attached the frontend log output in case it helps - the only
thing in there that I noticed that is new is the use of OpenGL vsync
support. Previous ATrpms builds have not had that and so RTC timing
has been used.
There's a reason that that defaults to off.
FYI: I get lots of
Ed W wrote:
I've attached the frontend log output in case it helps - the only
thing in there that I noticed that is new is the use of OpenGL vsync
support. Previous ATrpms builds have not had that and so RTC timing
has been used.
There's a reason that that defaults to off.
FYI: I get lots
On Sunday 10 April 2005 12:14 pm, Tom Hughes wrote:
In message [EMAIL PROTECTED]
Isaac Richards [EMAIL PROTECTED] wrote:
On Sunday 10 April 2005 10:39 am, Tom Hughes wrote:
I've attached the frontend log output in case it helps - the only
thing in there that I noticed that is
10 matches
Mail list logo
