> You mentioned previously that fDurationInMicroseconds in important for the
> client to request data at a correct rate. I haven't found out exactly if this
> should be relative to a video frame or relative to a MPEGTS frame
It should be the duration of whatever data you’re feeding to the downst
Ross,
I've been seriously poking at my (mostly) working MPEGTS FramedSource
and OnDemandMediaSubsession derivatives for my MPEGTS RTSP server. I
posted here
(http://lists.live555.com/pipermail/live-devel/2015-June/019441.html) a
few days ago from my gmail address (sorry about that). I quickly
Thanks for the quick reply!
Yes, I'm still developing an RTSP server. Below is my pipeline.
H264 Baseline 4.0 source (I and P frames only) -> ffmpeg (2.5) mpegts muxer
-> custom FramedSource (based on DeviceSource) getting 1316 (188 * 7) byte
output chunks from the mpegts muxer and writing all *c
> I have an MPEGTS muxer (ffmpeg) that spits out 1316 (188 * 7) byte chunks of
> valid data at a time. In my FramedSource subclass, I can write this to a file
> via fwrite and have a perfectly playable mpegts file. I've been sending data
> to `fTo` in 1316 byte chunks (as hinted in our previous
Ross and all,
I have an MPEGTS muxer (ffmpeg) that spits out 1316 (188 * 7) byte
chunks of valid data at a time. In my FramedSource subclass, I can write
this to a file via fwrite and have a perfectly playable mpegts file.
I've been sending data to `fTo` in 1316 byte chunks (as hinted in our
