multistream with simulcast reaciving event

[Mirko Brankovic]

Hi,

I was testing Multistream branch and client supports simulcast, so I notices that I receive one event for audio stream and three video receive: true events (same event).

SO same sender same type and same mid:

%{

  "janus" => "media",

  "mid" => "1",

  "receiving" => true,

  "sender" => 6945281661313245,

  "session_id" => 4502199652640075,

  "type" => "video"

}

Is that because of all 3 layers in simulcast?

Thanks,

Mirko

[Lorenzo Miniero]

I don't remember anything changing there. Do you get one event or three when doing the same on master? (can't test myself now)

L.

[Mirko Brankovic]

On master it is similar:

https://pastebin.ubuntu.com/p/76fKMXkpNQ/

after webrtcup, but this time I got one audio and 2 video events

[Mirko Brankovic]

this event is meant for publisher only, so doesn't matter how many other participants I have in room.

Also now 2 events is a bit confusing :D

[Lorenzo Miniero]

Maybe the browser only sent to substreams at that time?

L.

[Mirko Brankovic]

That could very well be, i need to verify it.

But if it is for substreams i think it would be very usefull to know which substream started/stopped

--
You received this message because you are subscribed to the Google Groups "meetecho-janus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meetecho-janu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/meetecho-janus/05cd819a-f2dd-4eda-ad06-ea1192f1333cn%40googlegroups.com.

[Mirko Brankovic]

Just to confirm it is based on substream.

Is it ok if I push PR with substream: 0/1/2 based on vindex?

Something like this:

https://pastebin.ubuntu.com/p/Ns6XKMHkRV/

[Lorenzo Miniero]

Sure, as long as the index only appears when simulcast is indeed in use. Have you checked if the video:false is also sent for each substream independently, though? Not sure if that's actually the case.

L.

[Mirko Brankovic]

Well seems that I wrongly understood it, since I can't seem to get receiving: false event unless track is stopped.

But even though client didn't start sending rid: h at all (but negotiated it correctly):

 janus gives me event "receiving": true, so this is something I can't rely on as an event

Thanks Lorenzo for suggestion to investigate it further though.