[Live-devel] Two liveMedia components sharing Groupsock. Shutting down one stops the other
Alex Anderson
alex.anderson at videon-central.com
Thu Aug 6 09:04:49 PDT 2015
Hello,
I have implemented a multicast out component using SimpleRTPSink and
RTCPInstance, and a multicast in component using SimpleRTPSource and
RTCPInstance. When the multicast in component is receiving from a multicast
out component on the same device, I have them share Groupsocks for RTP and
RTCP.
The issue I'm having is when I go to shutdown one component, it seems to
stop the other component. The code tracks how many components own the
Groupsock, so I know the Groupsock isn't being deleted.
Say for example I'm shutting down the multicast out component like so:
rtp_sink->stopPlaying();
Medium::close(framed_source);
Medium::close(rtcp_instance);
Medium::close(rtp_sink);
This will cause the multicast in component to stop working and stop
receiving any more streams, Even if I re-instantiate multicast out using
the same shared Groupsocks, the multicast out works just fine, but the
multicast in continues to be stopped (unless of course I re-instantiate the
multicast in). Keep in mind, this is only the case where the multicast in
is receiving the multicast out on the same device, and the Groupsocks are
shared.
The only link between components is the shared Groupsocks. I've looked into
the Live555 code, but I can't find how this sharing of Groupsocks would
cause one component to be stopped when another is shutdown.
Could you point to how exactly the sharing of Groupsocks would cause this?
Even better, do you know a solution, while still being able to share
Groupsocks?
Thanks!
Alexander Anderson
--
*EMAIL CONFIDENTIALITY STATEMENT: This email, including any attachments
hereto, may contain confidential and/or proprietary information of Videon
Central, Inc., and/or may include information controlled for export
purposes under the U.S. International Traffic in Arms Regulations (ITAR)
and is intended for the recipient only. No export, sale, transfer,
release or other disposition of this information is permitted without prior
authorization. If you are not the intended recipient please 1) do
not disclose, copy, distribute or use this message or its contents to any
other person or entity. 2) advise the sender by return e-mail, and 3)
delete all copies, including attachments, from your computer. Your
cooperation is greatly appreciated.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20150806/3be071c1/attachment.html>
More information about the live-devel
mailing list