When replying to a digest, PLEASE trim your post! If you fail to do
this again (especially because - as evidenced by your use of a
"@gmail.com" email address - you are just a casual hobbyist), you
risk being permanently banned from the list.
BTW, I plan to do some change to make livemedia t
ck::outputToAllMemberExcept(...), the member functions are called,
> but I cannot find any implementation in the project.
> I wonder what's this class used for?
> I guess it can be extended and used for stream forwarding? or application
> layer multicast?
>
> Daly
> -
Could you be running into sleep quantitization issues? 60 fps is down in
sleep quantitization issueland. The buffering on the receiver should take
care of things, but maybe it isn't, or the timestamps are not getting
generated correctly?
patbob
On Tuesday 10 March 2009 4:57 pm, Gbzbz Gbzbz
I found that under Linux a single threaded process such as one using
live555 only runs on one core of a multi-core CPU. My suggestion is to
run multiple processes if possible. This will let Linux distribute the
processes to the different cores.
- Brad
On Mar 11, 2009, at 6:31 AM, Marco Ama
I noticed that the RTSPClient class lacks a method for sending
RECORD requests for a whole media session; there's only a method for
sending RECORD requests for individual subsessions. Is this an
intentional omission, or has it just not been needed yet?
The latter.
I implemented such a method
Hi,
I noticed that the RTSPClient class lacks a method for sending RECORD
requests for a whole media session; there's only a method for sending
RECORD requests for individual subsessions. Is this an intentional
omission, or has it just not been needed yet?
I implemented such a method, see th
I'm reading the groupSock source code these days.
I found DirectedNetInterface is a pure abstract class,
In groupSock::outputToAllMemberExcept(...), the member functions are
called, but I cannot find any implementation in the project.
I wonder what's this class used for?
I guess it can be extend
Hi,
I think that SO_REAUSEPORT will continue introducing problems cause we
need to force a port when creating a socket for the RTCP channel (RTP
port + 1).
I believe that the best approach is to forget about SO_REAUSEPORT so we
can be sure that every socket requested to the OS will work just
I understand that it's hard to test bugs on modified code, I'd submit my
modifications to the project but you've already told me that you won't
accept some of them (I understand your reasons), and I'm not ready to
submit the others. I'm only trying to help you out by reporting what I
see, I hav
I'm reading the groupSock source code these days.I found
DirectedNetInterface is a pure abstract class,
In groupSock::outputToAllMemberExcept(...), the member functions are called,
but I cannot find any implementation in the project.
I wonder what's this class used for?
I guess it can be extended a
Hi all
Could anyone point me in the right direction please? I suspect that somewhere
within openRTSP there's some sort of "link timeout" to cope with timing issues
related to networking. I need to take a closer look.
I've got a much better idea of my problem now - my incoming streaming mpeg4
v
On Wednesday 11 March 2009, 10:28:25, liu yang wrote:
> I plan to develop an application which may support 500+ or even 1000+
> rtp session simultaneously. So anybody could tell me whether livemedia
> could support such load?
> BTW, I did some test based on testWAV sample program. The result is
>
Hi,
I plan to develop an application which may support 500+ or even 1000+
rtp session simultaneously. So anybody could tell me whether livemedia
could support such load?
BTW, I did some test based on testWAV sample program. The result is
not satisfactory, frankly speaking.
FAQ told me livemedia is
13 matches
Mail list logo
