We have make a try using thread local storage that is quite simple.
Adding "__thread" before OutPacketBuffer::maxSize declaration and definition
give a different variable for each threads.
Do you think this fix is acceptable ?
Michel.
[@@THALES GROUP RESTRICTED@@]
De : live-de
Hi Ross,
We try to find a way to send a range in absolute, it seems that a way could be
to specify in the RTSP PLAY command :
- Range: clock=19961108T142300Z-19961108T143520Z
Reading the clock of RTSPClient it seems that no overide is possible.
In RTSPClient.cpp this seems done
Thanks for the reply Ross.
Our application reads frames from a camera at the rate of 33ms (30fps) which
are encoded by a Hardware Codec and then fed to the H264Source::deliverFrame
method. But when receiver is not connected ping is gives below response after
some duration with streaming:
ping
Network transmission (over WiFi, or any other network interface) is handled by
the operating system and its device drivers, and has nothing to do with our
software, which operates at a higher level.
However, I suspect that your problems are being caused by you attempting to
transmit packets too
Hi Ross,
I am facing a strange issue when streaming the frames over Wifi interface, when
there is no receiver to receive the frames. I am guessing like frames are being
queued up in the network buffer and causing the wifi module to collapse.
As indicated by below prints:
NETDEV WATCHDOG: uap0 (
