vlc.audio.volume affects both player inst. of browserplugin
Posted: 20 Apr 2010 13:12
Has anyone an idea how to fix this strange behaviour of the browser plugin? 
It occurs on different OS and with IE and FF Browser ( others not tested by now ).
After i wrote a vlc based crossfading double webplayer with two vlc plugin instances called "vlc_0" and "vlc_1",
i noticed a strange behavior in the plugin ( vlc 1.0.5 ) volume control.
If the playlist of the other instance is not playing, both player instances are affected
although only the "audio.volume" for the first instance was modified.
For example by a "vlc_[0].audio.volume = 55;" or "vlc_[0].audio.volume += volOffset;" call from javascript
while the input.state is stopped.
If both of the player instances are playing or paused ( state 3 or 4 )
the new setting affects only the player instance for which it is called.
I noticed this issue during the development of the crossfader function,
because the crossfader only worked right while the two vlc instances were both playing a file.
At the moment i have a "vlcVolMem[0] / [1]" array to get rid of this curious behaviour,
but i am very unhappy with this #fix#.
It occurs on different OS and with IE and FF Browser ( others not tested by now ).
After i wrote a vlc based crossfading double webplayer with two vlc plugin instances called "vlc_0" and "vlc_1",
i noticed a strange behavior in the plugin ( vlc 1.0.5 ) volume control.
If the playlist of the other instance is not playing, both player instances are affected
although only the "audio.volume" for the first instance was modified.
For example by a "vlc_[0].audio.volume = 55;" or "vlc_[0].audio.volume += volOffset;" call from javascript
while the input.state is stopped.
If both of the player instances are playing or paused ( state 3 or 4 )
the new setting affects only the player instance for which it is called.
I noticed this issue during the development of the crossfader function,
because the crossfader only worked right while the two vlc instances were both playing a file.
At the moment i have a "vlcVolMem[0] / [1]" array to get rid of this curious behaviour,
but i am very unhappy with this #fix#.