Maybe these links will help:
http://cnyack.homestead.com/files/modulation/ntsc_sig.htm
http://en.wikipedia.org/wiki/Frame_rate
http://en.wikipedia.org/wiki/NTSC
http://www.afterdawn.com/glossary/terms/ntsc.cfm
http://www.fixya.com/support/t174610-ntsc_frame_rate_29_97_hz
- Original Message --
On Monday 05 January 2009 18:35:26 Tony Houghton wrote:
> I expect you've already checked this, but have you set the
> "TVStandard" option in xorg.conf?
Also it seems that 640x480 even in PAL mode comes out at 60Hz. Set it to
800x600 instead and you get full field rate at 50Hz.
On Mon, 5 Jan 2009 12:57:41 +0200
"Theunis Potgieter" wrote:
> Please do not always _assume_ that it is actually PAL or NTSC, since
> PAL or NTSC defines colour encoding, but the most of the time the
> usual frame rates are associated with the colour encoding. However
> like I've stated before nv
On 05.01.2009 13:49, Artur Skawina wrote:
> Klaus Schmidinger wrote:
>> On 05.01.2009 13:31, Artur Skawina wrote:
>>> Klaus Schmidinger wrote:
Detecting the frame rate is done by looking at the PTS values, so
it is independent of the actual broadcast system.
Using this code for
Klaus Schmidinger wrote:
> On 05.01.2009 13:31, Artur Skawina wrote:
>> Klaus Schmidinger wrote:
>>> Detecting the frame rate is done by looking at the PTS values, so
>>> it is independent of the actual broadcast system.
>>>
>>> Using this code for converting frame numbers into hh:mm:ss.ff...
>>>
>
On 05.01.2009 13:31, Artur Skawina wrote:
> Klaus Schmidinger wrote:
>> Detecting the frame rate is done by looking at the PTS values, so
>> it is independent of the actual broadcast system.
>>
>> Using this code for converting frame numbers into hh:mm:ss.ff...
>>
>> ---
Klaus Schmidinger wrote:
> Detecting the frame rate is done by looking at the PTS values, so
> it is independent of the actual broadcast system.
>
> Using this code for converting frame numbers into hh:mm:ss.ff...
>
>
> #include
> #include
On 05.01.2009 11:57, Theunis Potgieter wrote:
> On 05/01/2009, Theunis Potgieter wrote:
>> On 05/01/2009, Klaus Schmidinger wrote:
>> > In order to correctly handle the progress indicator for NTSC
>> > recordings I'm now determining the frame rate from the
>> > actual data. With PAL's 25 fra
Klaus Schmidinger wrote:
> In order to correctly handle the progress indicator for NTSC
> recordings I'm now determining the frame rate from the
> actual data. With PAL's 25 frames per second the distance
> between two frames is 3600 "ticks" of 1/9s. With NTSC
> this number is 3003, which resul
On 05/01/2009, Theunis Potgieter wrote:
> On 05/01/2009, Klaus Schmidinger wrote:
> > In order to correctly handle the progress indicator for NTSC
> > recordings I'm now determining the frame rate from the
> > actual data. With PAL's 25 frames per second the distance
> > between two frames
On 05/01/2009, Klaus Schmidinger wrote:
> In order to correctly handle the progress indicator for NTSC
> recordings I'm now determining the frame rate from the
> actual data. With PAL's 25 frames per second the distance
> between two frames is 3600 "ticks" of 1/9s. With NTSC
> this number
11 matches
Mail list logo