> On Jan 17, 2020, at 9:48 AM, James Bowley wrote:
>
>> Your *real* solution, however (other than not using Windows; geez, it’s 2020
>> :-) is to avoid having huge key frames. Instead, you should reconfigure
>> your encoder so that each key frame is encoded as a sequence of ’slice’ NAL
>> u
Hi Ross,
Thank you for your quick reply again.
We are using the latest version of the software and your suggested "fix"
works perfectly on both the Media and Proxy server.
Your *real* solution, however (other than not using Windows; geez, it’s 2020
:-) is to avoid having huge key frames. I
> On Jan 17, 2020, at 5:42 AM, Avramoni, Sorin wrote:
>
> Dear all,
>
> I am trying to send video H265 and audio AAC from a camera and a mic using
> MPEG-TS, I previously sent video and audio using two rtsp sessions
> withH265VideoRTPSink and MPEG4GenericRTPSink and it works.
If you have a
Dear all,
I am trying to send video H265 and audio AAC from a camera and a mic using
MPEG-TS, I previously sent video and audio using two rtsp sessions with
H265VideoRTPSink and MPEG4GenericRTPSink and it works. Now with the
configurations for mpeg-ts, openRTSP can only play audio but video s
First, as always, make sure that you are using the latest version of the
software (the only version that we support); see
http://live555.com/liveMedia/faq.html#latest-version
> writeSocket(412), sendTo() error: wrote -1 bytes instead of 1456:, 10035
> Packet count 105, Seq num 21061
[…]
Thank you for your quick reply. I would like to clarify a few points if
possible because I am not sure I explained myself correctly in the
previous message.
I believe the packets are not being written to the server socket and are
not being lost on the network. To check this I have included t
