> On Dec 15, 2020, at 9:21 PM, Lionel Koenig <lionel.koe...@codemill.se> wrote:
>
> I just wanted to clarify the use case here: In our application, the end user
> decides when to SETUP and PLAY the stream which is presented to her/him after
> the DESCRIBE succeeded. It is also the end user deciding whenever to TEARDOWN
> the stream. Usually the end-user is not part of the event loop (i.e. on
> another UI thread).
Nonetheless, you must not call LIVE555 code from this (non-event-loop) thread.
You have no choice here. LIVE555 code - apart from “triggerEvent()” - must all
run within a single-threaded event loop. If you don’t do this, unpredictable
errors may occur, and you will not be supported.
I suggest that, instead, your non-event-loop UI thread call “triggerEvent()” to
signal - to the LIVE555 event loop - that it needs to start a stream. Once
again, read
http://live555.com/liveMedia/faq.html#threads
and
http://live555.com/liveMedia/faq.html#other-kinds-of-event
> I just wanted to provide the patch in order to make it this use case more
> flexible
It doesn’t make “this use case” more flexible, because “this use case” is not,
and never will be, supported.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
