[Live-devel] JPEGVideoRTPSource and JPEGVideoSource

[Raphael KINDT]

Hello and thank you for your reply.

I'm trying to develop a streamer process that send JPEG images receive from
another process (I use pipes to do it) to a remote client (VLC client, etc).

I must be able to add new stream to this streamer.  To do it I use a pipe
control (with mine protocol). This pipe control indicate  to the streamer to
add a pipe for the new streaming AND add a new server media session
(addServerMediaSession) for this new stream. I use the same name for the new
pipe and the new session (i.e. "Process0", etc)

Here a representation of this architecture:

 APPLICATION         PIPES       APPLICATION
+-----------+                   +-----------+
|  Grabber  |<----- ctrl ------>|           |
|     +     |                   | Streamer  |
|   image   |--- stream  0  --->|   LIVE    |--- Process  0  --->
|  processs |--- stream ... --->|           |--- Process ... --->
+-----------+                   +-----------+

At this time we must use JPEG image (because it's simple) but after we want
to send raw image...

I hope you understand the global mechanism I want to construct.
Could you tell me if it's possible to do that for the LIVE side?

In short, the main point is to add new server media session dynamicaly.
This means that the scheduler is already started like this
env->taskScheduler().doEventLoop(&watch_scheduler)   before the call of
rtspServer->addServerMediaSession   and   sink->startPlaying

Thanks in advance for your help.

Best regards,

Raphael


-----Message d'origine-----
De : live-devel-bounces at ns.live555.com
[mailto:live-devel-bounces at ns.live555.com]De la part de Ross Finlayson
Envoye : jeudi 10 avril 2008 15:33
A : LIVE555 Streaming Media - development & use
Objet : Re: [Live-devel] JPEGVideoRTPSource and JPEGVideoSource


>What's the difference between JPEGVideoRTPSource and JPEGVideoSource?
>What JPEGVideoRTPSource do that JPEGVideoSource doesn't do (and
vice-versa)?

"JPEGVideoRTPSource" encapsulates an incoming stream of motion-JPEG
RTP packets.  This class is used by clients that receive network
packets.

"JPEGVideoSource" encapsulates a stream of motion-JPEG frames that
are *not* RTP packets.  For example, if you have a video camera, or
video encoder, that produces a sequence of JPEG frames, then you
would use a subclass of this class to encapsulate it.  (Note that
"JPEGVideoSource" is an abstract base class that you would need to
subclass, and implement a handful of virtual functions, for your own
JPEG source.)
--

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
live-devel at lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel