Hi Ross,
My apologies, that was a bad attempt at trying to minimize the code
snippet. I actually do have it all in separate functions and scheduled
tasks, I was just trying to keep this email short but descriptive.
The issue I was trying to convey is that I have a rolling file buffer of
.ts files that seem filled with corrupted data even though the rolling file
buffer of QuickTime files work perfectly fine.
Do I need to add more filters to the h264 stream? I was expecting TS
headers with the 0x47 sync byte in the file.
Thanks,
Chris
On Mon, Feb 25, 2019 at 9:15 PM Ross Finlayson <finlay...@live555.com>
wrote:
> > while(true) {
> > TS_Sink = FileSink::createNew(*env, uniqueFileName);
> > TS_Sink->startPlaying(*streamTS, NULL, NULL);
> > sleep(2) // Continuous output of files with 2 seconds of video each
> > TS_Sink->stopPlaying()
> > Medium::close(TS_Sink)
> > }
>
> You MUST NOT call “sleep()” within a LIVE555 application, because LIVE555
> applications run in a (single-threaded) event loop. Calling “sleep()” will
> stop all other activity from happening during that time.
>
> Instead, have the calls to “stopPlaying()” and “Medium::close()” happen
> within a function, and have that function scheduled (to take place after 2
> seconds) using the “scheduleDelayedTask()” function. (You’ll see several
> examples of this in the “testProgs” directory.)
>
>
> Ross Finlayson
> Live Networks, Inc.
> http://www.live555.com/
>
>
> _______________________________________________
> live-devel mailing list
> live-devel@lists.live555.com
> http://lists.live555.com/mailman/listinfo/live-devel
>
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
