mnkdon / flash-videoio

Automatically exported from code.google.com/p/flash-videoio
0 stars 0 forks source link

Microphone not enabled by default when security dialog shows up #41

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
First reported by marcin.kurylak@innodia.pl on Oct 9, 2012.

---

I'm using VideoIO11 ver 3.3

1) Publishing audio when security dialog shows up.

If I start the component with these flashvars:
var vars = {};
vars.url = [[URL]];
vars.controls = true;
vars.publish = [[user_id]];
vars.microphone = true;
vars.sileneceLevel = 5;
vars.gain = 0.4;
vars.camera = true;
vars.cameraDimension = '160x120';
vars.echoCancel = true;
vars.echoSuppression = true;

If security dialog shows up and I accept it the microphone is off by default, 
if I enable it - it does not work. To make it work I have to enable, disable 
and enable it again from controls.
If security dialog does not show up (flash remebers the selection for current 
domain) microphone is enabled by default and everything works fine.

It should be enabled by default in both cases.

Original issue reported on code.google.com by theinten...@gmail.com on 13 Oct 2012 at 5:30

GoogleCodeExporter commented 9 years ago
Fixed in SVN r57 and r58. 
Will be available in download version 3.4+, until then please get a copy from 
http://myprojectguide.org/p/flash-videoio/VideoIO-3.4.zip

The bug was because the version of Flash Player sends dubious mic status event 
after the user clicks on "allow" for the first time in the security panel. The 
bug manifested because of the "deviceAllowed" property which tried to tie 
together with "camera" and "microphone" properties. Now I have decouples the 
"deviceAllowed" property from "camera" and "microphone" and always correctly 
set the "deviceAllowed" instead of using the status event values. This seems to 
fix the problem.

Hope I haven't broken any other features...

Original comment by theinten...@gmail.com on 14 Oct 2012 at 5:46

GoogleCodeExporter commented 9 years ago
I can confirm, that this issue is fixed now

Original comment by marcin.k...@innodia.pl on 17 Oct 2012 at 11:56