Issue with membrane rtsp after v0.7.2

[gBillal]

Since v0.7.2 where the tcp socket is set to active mode. This causes issues when someone want full control of the underlying tcp socket.

In my case I get the socket and set active to false, so once I try to :gen_tcp.recv and the socket try to send a message in another process, I get the error {:error, :einval} (because the socket is set to active mode)

[Noarkhh]

Hi, I see the issue. In membraneframework/membrane_rtsp#44 the behavior changes (after transferring control the session no longer tries to receive from that socket). Would it be okay if it's fixed there?

[gBillal]

That's great, I'll wait for 0.10.0 release

[Noarkhh]

I just released v0.10.0, give it a try :) Also gBillal/membrane_rtsp_plugin#12 is now ready for review

[gBillal]

unfortunately this is still not fixing my issue. The fact that the rtsp session update the active mode of the socket creates a problem. Since I have another process that always using recv to read from the socket which fails when the socket is in active mode.

[Noarkhh]

are you calling RTSP.transfer_socket_control/2 before that? Calling this function should stop the process from changing the socket's options

[gBillal]

Made a mistake, forgot to set the socket to non-active mode.
It works fine now, thanks