From: James Courtier-D. <Ja...@su...> - 2003-10-10 16:02:42
|
Michael Roitzsch wrote: > Hi Mike, > > >>>That's the internal demuxer API you are talking about. In the >>>public API our friend means, start_pos denotes a fraction of the >>>stream, ranging from 0 to 65535 with 0 being the start and 65535 >>>being the end of the stream as the demuxer sees it. >> >> Ah, right. I never work at that level. So...why doesn't that >>information get relayed down to the demuxer level? It would actually >>make a lot more sense than passing through the file offset which is >>what happens now. > > > I guess that internal file offset might be a relic from days where xine > only handled files. If you find someone who changes all the demuxers, > you could easily modify the internal API. But I suggest we wait until > after 1.0 with such a big job. > > Michael > 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. Implementing Trick mode will be the first step toward this aim. Cheers James |