I had been going under the assumption that I could interpret the
presentation times in terms of the server's wallclock. I just realized
that, in fact, presentation time appears to have been converted to the
client's local time, i.e. accounting for time zone, etc. Is this the case,
and if so, is t
> Is there any reason this buffer is so small by default?
This value is not 'small'. On the contrary - it's your cameras that are
generating ridiculously 'large' frames :-)
"OutPacketBuffer::maxSize" defines the largest possible 'frame' that a server
(or a proxy server) can send. It's importa
> How do i modify live555ProxyServer so i can create a new session whenever a
> client asks for getting proxy stream comes from new sources
> (just like live555MediaServer open a different file and offer this stream
> when it received a new client'ack)
You would need to do something similar to
Hey,
Every camera I use these days seems to exceed the
default OutPacketBuffer::maxSize by quite a large margin, e.g.
MultiFramedRTPSink::afterGettingFrame1(): The input frame data was too
large for our buffer size (60804). 116669 bytes of trailing data was
dropped! Correct this by increasing "
How do i modify live555ProxyServer so i can create a new session whenever a
client asks for getting proxy stream comes from new sources
(just like live555MediaServer open a different file and offer this stream
when it received a new client'ack)
normly the proxyserver only links one or more
