How to know currently active (speaking) publisher in a videoroom?

[Anil Wadghule]

Is there any Janus API to know currently active (speaking/voice is on) publisher?

In my video chat, I need to highlight currently active speaker and put in the middle like hangouts does.

thank you,

Anil

[Mirko Brankovic]

there is a 'talking' state which is based on the audio level of the rtp header, you should receive start and stop talking events on chosen transport. levels are configurable per room and you have an example in the sample config

--
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-janus+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Regards,

Mirko

[Anil Wadghule]

Hi Mirko,

Sorry, did not understand it.. does it come as an event?  Could you point me to documentation?

Thanks,

Anil

Best,

Anil

[Mirko Brankovic]

If you enable it in room config or in create room api call, you should see it on your transport type. So if you use websocket, you will get that event like user joined or left events.

[Mirko Brankovic]

https://github.com/meetecho/janus-gateway/blob/master/conf/janus.plugin.videoroom.cfg.sample#L17

And few next settings in config

[Anil Wadghule]

Hello Mirko / Lorenzo,

I create a Janus video room with the following request,

But I don't see

      Janus.Plugin.message(handle, %{
        request: "create",
        description: room_name,
        bitrate: 2_000_000,
        videocodec: "h264",
        publishers: 20,
        permanent: true,
        audiolevel_ext: true,
        audiolevel_event: true,
        audio_active_packets: 100,
        audio_level_average: 120
      })

But Janus room is getting created with following options only.

[4132959083230403]
description = old-shape-1580
bitrate = 2000000
publishers = 20
audiocodec = opus
videocodec = h264

Ami I missing something?

Thanks,

Anil

[Mirko Brankovic]

seems like you did it ok, but lets make some things clear:

I tested this with chrome cause they are putting audio level ext into rtp

Event is only firing towards listeners, there is no point in publisher to get one (you should see initial state in publisher joining now, ex. talking:true/false

Make sure you are making noise for 2sec (100 packets) so to trigger the event.

Hope it helps ;)

[Mirko Brankovic]

I tested this with static files, maybe I did something wrong with api call

[Anil Wadghule]

Mirko,

When I *manually* put following values in Janus created room in janus.plugin.videoroom.cfg

audiolevel_ext = yes
audiolevel_event = yes
audio_active_packets = 50
audio_level_average = 40

it works as expected..

But I want these values to show up in created room config when I created Janus room when I pass these options.

But noticed Janus doesn't respect that while room creation. I also notice, putting these values in [general] doesn't help.

I wonder, now how to make it work now. This is blocker.

Thanks,

Anil

[Anil Wadghule]

Hi Lorenzo,

Need your answer here.

Looks like audio related params are ignored while creating new Janus room. And putting those in [general] doesn't work too. Only current way is to manually put those for each room.

Thanks,

Anil

--

Best,

Anil

[Mirko Brankovic]

I just tested it on dynamically created room and I got events, but I used average of  25.

{"request":"create","description":"test", "room":12345, "bitrate":512000,"publishers":5,"secret":"topsecret", "fir_freq":10, "audiocodec":"opus", "videocodec":"vp8", "record":false, "audiolevel_ext": true, "audiolevel_event": true, "audio_active_packets": 100, "audio_level_average": 25},"transaction":randomString(12),"session_id":session_id,"handle_id":handle_id}

So what I think is that your average of 120 is not crossing that limit and then there is no change in audio level.

127 is muted, so try to mute one side and probably you will get event.

you can observe audio_dbow_level on publishers handle together with talking property

--

Regards,

Mirko

[Anil Wadghule]

Thank Mirko, I noticed I get events too. But I noticed it doesn't write down those settings in a video room config file. 

I wonder how it finds that next time when I just join room as settings are not persisted there.

Lorenzo, any inputs?

Thanks,

Anil

[Mirko Brankovic]

Hmm that part im not sure

[Lorenzo Miniero]

Looks like a bug, where we don't store all properties when permanent is true. I'll work on a fix when I have some time.

L.

[Anil Wadghule]

Thanks, Lorenzo! I assume, for now, I can send configure request each time to enable these settings for a video room.

Thanks,

Anil

[Lorenzo Miniero]

No, configure is just for users, not rooms.

L.

[Lorenzo Miniero]

The missing features when saving to config should be fixed here, let me know if that's not the case:

https://github.com/meetecho/janus-gateway/commit/fb6ddbf2cdcdde1ef850f9c9bf698f2e7f73f4ae

L.

[Mirko Brankovic]

You changed ice.c loop on purpose or by accident in this pr?

[Lorenzo Miniero]

On purpose, it's changes we made yesterday that I forgot to push.

L.

[Mirko Brankovic]

Oh oki thanks ;)