> What's happening is that the BasicUDPSource::incomingPacketHandler1()
> function is being called too many times.
This is apparently happening due to a flaw in your runtime library and/or OS:
“select()” (called each time within the event loop) is returning an indication
that the UDP socket has
- development & use
Subject: Re: [Live-devel] 100% cpu usage when 1 or more client connects to RTSP
server
1. Actually it seems that reuseFirstSource variable is not used in the original
testOnDemandRTSP for the UDP mpegts example(and in my code too).
Yes, you’re correct. The “MPEG2Transpo
> 1. Actually it seems that reuseFirstSource variable is not used in the
> original testOnDemandRTSP for the UDP mpegts example(and in my code too).
>
Yes, you’re correct. The “MPEG2TransportUDPServerMediaSubsession”
implementation sets the “reuseFirstSource” parameter to True when it calls the
Original Message
From: Ross Finlayson
Sent: Tuesday, March 10, 2015 04:35 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] 100% cpu usage when 1 or more client connects to RTSP
server
Boolean reuseFirstSource = False;
FYI, because your input source is a live st
> Boolean reuseFirstSource = False;
FYI, because your input source is a live stream, you should change this from
“False” to “True”, so that multiple clients can connect to the RTSP server to
receive the stream, without the input stream being recreated each time. (This,
however, has nothing to
Hello everyone!
I would be very grateful if someone could help me out with the issue below, I'm
new to live555.
I've got nine audio streams that I'm pulling in via ffmpeg and then re-encoding
them to AAC-LC and pushing to udp://127.0.0.1:port_num?pkt_size=1316 (where
port_num is replaced by re
