[Live-devel] Storing MPEG-2 TS data over multple 2GB files

[Morgan Tørvolt]

If you need to support random access on the files, you should find a
TS packet that contains a sequence header for the video stream. It
will be followed by a GOP header, and an I frame. If you don't need
random access, then any TS packet boundary should work.

-Morgan-

On 02/12/06, Daniel Robbins <drobbins at fsmlabs.com> wrote:
> In this case, the 2GB limit isn't an operating system or filesystem
> limitation per se, but is required for other reasons.
>
> Thanks for the information.
>
> Regards,
>
> -Daniel
>
> Ross Finlayson wrote:
> > Is it not possible to upgrade to a more modern operating system that
> > supports files larger than 2 GBytes?  (Note that this will work even
> > with 32-bit CPUs.)  That would be the best solution.
> >
> >
> >> Specifically, I'm interested in knowing:
> >>
> >> 1) What is the best place to "split" the stream (on an I-frame boundary?)
> >>
> >
> > I'd say: Split the file on a Transport Stream frame boundary - i.e.,
> > on a 188-byte boundary.
> >
> >
> >> 2) Can live555 be instructed to treat these multiple files as a single
> >> logical stream, so that the resultant segmented MPEG-2 data could be
> >> later streamed to clients without significant additional complication
> >> such as manually concatenating the files?
> >>
> >
> > While I'm generally disinclined to add hacks to the code to support
> > broken (or archaic) operating systems, in this case there is a
> > mechanism in the code (the "ByteStreamMultiFileSource" class) that
> > could support this.  So you're in luck...
> >
>
>
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live555.com
> http://lists.live555.com/mailman/listinfo/live-devel
>