Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Microphone bug? Microphone index always 0.

Avatar

Avatar
Level 1
Vasilij_M
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile

Avatar
Level 1
Vasilij_M
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile
Vasilij_M
Level 1

27-07-2011

LCCS Microphone bug? Microphone index always 0.

LCCS 1.5.0.    Flash Player 10.3.181.34

When a user changed the microphone (using right click -> settings -> microphone, or Security.showSettings(SecurityPanel.MICROPHONE)) AudioPublisher  still using mic with 0 index.

I look into code and find:

MicrophoneManager

protected var _micIndex:Number ;  //TODO what is this initially (default)?

...

/**

* Returns the currently selected microphone.

*/

public function get selectedMic():Microphone

{

   // trace('get selected mic, player');

   _if(!_mic)

   _{

      _mic = Microphone.getMicrophone(_micIndex);        <--- Here

Solution:

1. Now: Create my "Settings" panel, where user must manually change mic (not by Flash Security).

2. Want:

   Set "_micIndex" default value to -1;

Than check:

   if(!_mic)
   {

      _mic = _micIndex == -1 ? Microphone.getMicrophone(_micIndex) : Microphone.getMicrophone();

Or another solution. But it will be good if it work wright.

Replies

Avatar

Avatar
Boost 50
Level 7
Nigel_Pegg
Level 7

Likes

103 likes

Total Posts

909 posts

Correct Reply

81 solutions
Top badges earned
Boost 50
Boost 5
Boost 3
Boost 25
Boost 100
View profile

Avatar
Boost 50
Level 7
Nigel_Pegg
Level 7

Likes

103 likes

Total Posts

909 posts

Correct Reply

81 solutions
Top badges earned
Boost 50
Boost 5
Boost 3
Boost 25
Boost 100
View profile
Nigel_Pegg
Level 7

27-07-2011

Hi There,

  First of all, thanks for taking the time to report your issue - it always helps.

  Interesting. We'll test to see if we see the same bug, and if so, we'll include a fix for the release-after-next. The next release is coming up very shortly, so we're out of time for fixes there.

  thanks again!

   nigel