I’m not very knowledgable in anything programming really…
But somehow I managed to install licode with the installation instructions,
and was able to then start styling and making some modifications with the
simple demo that comes with it.
There’s only one big thing I’m unsure about and that is how to implement
push2talk. I want people to be able to hold in a button to activate the
microphone. I don’t want audio sent out without the button pressed in.
How easy is that to implement? If it’s easy could you give an example
please?
Thanks!
Push to talk is a privacy feature. If I understand it correctly, in your
example the audio would still be received but just not played (correct?),
users could easily override this with a tool or modification to the client.
Also, if an error occurred and the mic did not mute for all, then sensitive
stuff could be leaked without the broadcasters knowledge.
People also like to cough or sneeze or whatever without the entire web
conference room hearing 
.
To clarify, your suggestion was to just mute and unmute the incoming
stream’s audio based on data stream cues?
Or is there a way to adjust the volume of your own microphone within the
javascript client??
Thanks for the tip :)On Friday, December 19, 2014 7:47:48 AM UTC+10, Jeremy Noring wrote:
I think you’d just unmute/mute the stream when a user hits a particular
button that allows them to talk.
out of curiosity, why do push to talk? WebRTC has very good echo
cancellation so it’s a full-duplex channel. Or is it just something you
want for fun?
On Wednesday, December 17, 2014 2:43:54 PM UTC-7, Stephen Pearson wrote:
I’m not very knowledgable in anything programming really…
But somehow I managed to install licode with the installation
instructions, and was able to then start styling and making some
modifications with the simple demo that comes with it.
There’s only one big thing I’m unsure about and that is how to implement
push2talk. I want people to be able to hold in a button to activate the
microphone. I don’t want audio sent out without the button pressed in.
How easy is that to implement? If it’s easy could you give an example
please?
Thanks!
I think you’d just unmute/mute the stream when a user hits a particular
button that allows them to talk.
out of curiosity, why do push to talk? WebRTC has very good echo
cancellation so it’s a full-duplex channel. Or is it just something you
want for fun?On Wednesday, December 17, 2014 2:43:54 PM UTC-7, Stephen Pearson wrote:
I’m not very knowledgable in anything programming really…
But somehow I managed to install licode with the installation
instructions, and was able to then start styling and making some
modifications with the simple demo that comes with it.
There’s only one big thing I’m unsure about and that is how to implement
push2talk. I want people to be able to hold in a button to activate the
microphone. I don’t want audio sent out without the button pressed in.
How easy is that to implement? If it’s easy could you give an example
please?
Thanks!
See answers below.
Push to talk is a privacy feature. If I understand it correctly, in your
example the audio would still be received but just not played (correct?),
users could easily override this with a tool or modification to the client.
No, in my example the audio would never be sent. You would mute the
outgoing stream. Incoming streams would be muted/unmuted by their
respective owners.
People also like to cough or sneeze or whatever without the entire web
conference room hearing .
To clarify, your suggestion was to just mute and unmute the incoming
stream’s audio based on data stream cues?
No, you would mute and unmute the outgoing stream. That can all be done
in javascript pretty easily; google “getUserMedia mute” and I’m sure you’ll
find something useful.On Thursday, December 18, 2014 3:40:34 PM UTC-7, Stephen Pearson wrote: