Thanks for the information. If I got it correctly for the server
side the new "RTPSink" subclass handless the interface to the
livemedia library and to the dedicated hardware interface for
controlling the hardware RTP packetization (payloadtype,
...). "OnDemandServerMediaSubsession" control's the streaming
(init, start, stop, ...). It is not clear how it works with the SDP
parameters that are needed during RSTP init if the data stream isn't
available at all on the host.
Only some of the SDP lines (namely: "a=fmtp:") require reading data
from the stream, and - in any case - these lines are often the same
for every stream (if the codec stays the same), so you may be able to
figure this data out in advance, and reuse it for each stream, rather
than actually reading it from the stream each time.
The hardware is controlled by a very simple interface (start/stop
RTP packetization with parameters x, y, z).
Just to have a tought, since you know the livemedia library better
then me, how many hours/days/month would you think is needed to do
the changes?
I don't know nearly enough about your system to estimate this (and
I'm usually bad at such estimates anyway).
Good luck!
--
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
[email protected]
http://lists.live555.com/mailman/listinfo/live-devel
