[Live-devel] Mechanism of passing data from source to sink

[Alan Martinovic]

Sorry for double posting, was a mistake.

From: live-devel [mailto:live-devel-bounces at ns.live555.com] On Behalf Of Alan Martinovic
Sent: Friday, October 17, 2014 11:38 AM
To: live-devel at lists.live555.com
Subject: [Live-devel] Mechanism of passing data from source to sink

Hi,
I've read how the control flow mechanism works (http://www.live555.com/liveMedia/faq.html#control-flow)
and I'm trying to get the idea of how it works in practice by following the Elphel example (http://www.live555.com/Elphel/).

I've traced the actual payload to the fTo variable

#ElphelJPEGDeviceSource.cpp 95-96
// Then, the JPEG payload:
fFrameSize = fread(fTo, 1, fMaxSize, fFid);


But when grepping through all the *Sink* and *Session* files, I found no traces of fTo. Plus, the fTo is protected.
At first, I was thinking that when triggered, the JPEGVideoRTPSink was getting the raw data by accessing the FramedSource.fTo and then adding the RTP headers to that data (which represent raw video).

By which method (variable?) do sinks and sources actually share the raw video data?


DISCLAIMER:
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message.

DISCLAIMER:
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20141017/75cec7dd/attachment.html>