[libav-api] Resolution Change
ledererstefan at gmx.at
Sun Apr 24 15:31:35 CEST 2011
> Hi, could you please use the interleave posting style instead of top
Yes, no problem :-)
> Segmented streams can be considered either as
> small chunk of uniform bitstream that should be feed to the demuxer
> concatenated (e.g the mpegts case, applehttp protocol in libav) or
> as items in a playlist thus to be considered as unrelated files that
> should be demuxed and decoded independently and whose content has to be
> presented as a continuous stream (thus segment1:frame124 is followed as
> segment2:frame0 as if it were the segment1:frame125)
> Looks like the mp4 segmentation falls in this second case.
No, DASH (dynamic streaming over http) uses the first approach. In my case
I've created an initialization segment and several video segments which are
send to the demuxer like a uniform bitstream. See below.
If you need more information about the mp4 boxes used in DASH you could have
a look at . Unfortunately the standard is not finished yet, so there may
are some unclear parts...
> > I've also provided some of the content which I used for this in .
> > are one initialization segment and two video segments in the attached
> > zip-archive.
> Could you please also paste the instructions on how to try that?
I've concatenated the segments in  to one mp4 file . This file
consists of one initialization segment, two segments of about 2 sec. at
QCIF, and 2 segments of about 2 sec. of CIF video.
I've now tested this file using "ffplay foreman_concat.MP4" (which is the
file in ) and got the same problems like in VLC with my plugin.
> I hope we can clarify the issue soon =)
More information about the libav-api