Figured it out: getNextFrame wasn't called during the setup process, but
some 50-100ms later. Haven't realized background socket handling isn't
configured until the first call to that method.
This old post has been instrumental to resolution :
http://lists.live555.com/pipermail/live-devel/2005
> On May 17, 2022, at 3:33 PM, Alex Agranovsky wrote:
>
> Server-side: using stock live555MediaServer running on macOS.
>
> Client-side:
>
> - The problem occurs regardless of transport (both TCP and UDP)
> - The problem is seen with our code using RTSPClient API
> - The problem doesn't occur
Server-side: using stock live555MediaServer running on macOS.
Client-side:
- The problem occurs regardless of transport (both TCP and UDP)
- The problem is seen with our code using RTSPClient API
- The problem doesn't occur with testRTSPClient. Currently looking at
possible implementation diffe
> On May 17, 2022, at 11:36 AM, Alex Agranovsky wrote:
>
> Hi,
>
> I'm debugging a situation, where the first frame on the connection is always
> dropped by live555 RTSP client.
Can you say more about your configuration?
What are you using as your RTSP server (for streaming your video file
