[xine-devel] Re: [xine-user] how acurate is xine ?

[Mike M. <mel...@pc...>]

[taking this discussion from xine-user -> xine-devel]

On Fri, 10 Oct 2003, James Courtier-Dutton wrote:

> Please keep file offsets, and file length values in xine-lib.
> I will want to use them for certain new features I am thinking about.
> I want to be able to use xine-lib as part of a video editing tool, so 
> that the user can select a particular video frame to do a cut. It will 
> be a visual editing system, so the user uses xine to select all the edit 
> points visually, and then some external re-encoder program uses these 
> edit points information to create the final edited movie.

	There are some other experimental API features to facilitate such
things as video processing. And I really don't understand how the file
offsets would help in a video processing app. API functions that specified
the number of frames and keyframes would be more useful to that end.

	Passing the 0..65535 offset to the demuxer makes a lot more sense.
If there is a 100000-byte file, with 10000 bytes of header data and 90000
bytes of body data, the seeking will be more accurate if the demuxer is
allowed to decide internally that seek position 0 maps to file offset
10000 rather than file offset 0.

--
	-Mike Melanson