[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)

[Jason Wood]

On Sunday 12 Jan 2003 12:04 pm, Rolf Dubitzky wrote:
> On Sunday 12 January 2003 12:58 pm, Rolf Dubitzky wrote:
> > On Sunday 12 January 2003 08:22 am, Chris Clayton wrote:
> > the file you tried is NTSC. In principle supporting NTSC is not a big
> > deal,
>
> Err, well, when I said that, I was thinking of piave only. I don't know how
> many hardcoded 25fps are in kdenlive. Since piave does not even report back
> the format of the clip, even if kdenlive could handle NTSC, it wouldn't
> know about it. And also, as NTSC fps is not as easy to convert from
> milliseconds to integer we might see more rounding errors.
>
> I guess NTSC is something we should really fix before beta 1.

Assuming that I get passed the frame rate in getFrameProperties, kdenlive will 
be able to specify the correctly length for the NTSC clip.

All of the 25fps references have now vanished, and instead they ask the 
document via framesPerSecond() to get the correct framerate. However, this 
value is hardcoded to PAL (25 fps) at the moment, it is a bit of work to fix 
this properly, because I need to be able to tell piave what framerate to 
render to.

Exactly how piave handles the conversion of NTSC to PAL and PAL to NTSC is out 
of kdenlive's hands. However, if we want to prevent this from happening (i.e. 
tell kdenlive not to allow clips of different frame rates) we need to choose 
a paramter to the <getCapabillities/> call in the <general> area I hinted at 
when we were talking about transitions. It would say something like :

<capabilities>
	<general>
		<fps canconvert="false"/>
	</general>
</capabilities>

Or to put it another way, handling NTSC, whilst it should not be difficult, is 
quite a bit of work, which overlaps with the "file format support" quite a 
lot.

Cheers,
Jason

-- 
Jason Wood
Homepage : www.uchian.pwp.blueyonder.co.uk