Hi Pawel,
Sorry to respond months after the fact. I scanned the list for RTSP and found
this one.
Daniels comment is really important. You must set the CURL_RTSPREQ_RECEIVE
before adding it to the multi, otherwise the handle has nothing to do and will
fall-through like you observed.
So:
Hi
first of all thanks for the interest in this case.
I've made some traces :
code: http://pastebin.com/sxUhybck
easy trace: http://pastebin.com/jNWXFdRQ
multi trace: http://pastebin.com/LHDFhzcM
Well, in general I'm still stuck I took easy_perform and made some traces
there the receive function
On Tue, 13 Sep 2016, Paweł Kopalko wrote:
You remove the same easy handle twice? And you set an option in between
which looks really strange?
I found out I remove the handle twice after I posted the example I fixed
that but there is no change in the behaviour. The idea about the "strange"
Hi,
>What libcurl version are you using on what platform?
sorry I forgot to state the "what-where-why" ;)
I'm using a curl-7.49.1 compiled as static library with a ubuntu 16.04
32bit (for POC, the target system is MIPS), the rtsp server is spook on a
webcam, I use interleave since I plan to
On Mon, 12 Sep 2016, Paweł Kopalko wrote:
I'm using curl with RTSP/RTP streams, until now I've used easy_perform,
which worked ok for me, but since I had to move to several threads there are
complications, and thus I need to use multi interface since I understand
that it will help me to
Hi,
first of all hello to everyone (since this is my first mail here ;) )
I'm using curl with RTSP/RTP streams, until now I've used easy_perform,
which worked ok for me, but since I had to move to several threads there
are complications, and thus I need to use multi interface since I
understand
