This message was deleted.

therefore, once it returns, i know i can try to connect to the room? what if i already created the room via a client connection?

It is part of the CreateRoom API, it should be in the server sdks. If the room already exists it will not apply

ah ok found it! thanks. internally - is the gstreamer pipeline setup before any clients connect? can i rely on the pipeline being ready when createRoom returns? in other words - if i connect a client very soon after calling createRoom, can i be sure that egress will work? and what would be the max latency from connection to first frame captured?

Yeah, it’ll reserve an egress instance and wait for someone to join Average latency for room composite or web egress is ~375ms, so with auto egress it should get everything unless the first person joins and publishes within that time

Great, thanks. And just to check - auto-egress can't currently be setup from the cloud interface? I.e. just set all new rooms to auto-egress?

Not currently, we do plan to add that later though

and this only support room composite, or individual tracks (but not HLS). so no track composite? no individual track HLS?

We also added participant composite, which is track composite without needing to know track IDs. I probably still need to update the sdks

oh that's a useful one!