cssarma / flowplayer-plugins

Automatically exported from code.google.com/p/flowplayer-plugins
0 stars 0 forks source link

bwcheck's setBitrate isn't working #7

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Install the plugin
2. Try to use the function

I first noticed it and opened a thread about it in the forum:
http://flowplayer.org/forum/5/41690

Please provide any additional information below.

I've browsed the code on the repository and on file:

http://code.google.com/p/flowplayer-plugins/source/browse/flash/bwcheck/trunk/sr
c/actionscript/org/flowplayer/bwcheck/BitrateProvider.as?spec=svn1033&r=1033

Line number 651 the function is declared like this:

public function set bitrate(bitrate:Number):void

I'm not familiar with actionscript, but I believe the problem is there.
Also, I've noticed some other functions (getBitrate, getLabels) are also
like this.

Thank you for your time. 8)

Original issue reported on code.google.com by more...@gmail.com on 20 May 2010 at 8:40

GoogleCodeExporter commented 8 years ago
hmmm... actually I looked for more about actionscript syntax, and it seems this 
is a
proper way to do getters/setters. But I still can't use setBitrate.

Original comment by more...@gmail.com on 21 May 2010 at 1:17

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
the correct syntax is $f("player").getPlugin("bwcheck").setBitrate(bitrate);

Original comment by dani...@electroteque.org on 29 Nov 2011 at 12:01

GoogleCodeExporter commented 8 years ago
I've been following this for a while as we've never sorted this on our site, 
meaning we effectively only have one bitrate despite having three options.

When I enter the following into the console:
$f("flow_player").getPlugin("bwcheck").setBitrate(150);

The video restarts to indicate a bitrate change, but the bitrate isn't actually 
switched at all.

Example here:
http://www.designindaba.com/speaker/presentation/laduma-ngxokolo

I've really tried everything to rule out my own error here, and am pretty sure 
this is a bitrate bug actually.

Apologies for thread hijacking!

Original comment by guybedf...@gmail.com on 29 Nov 2011 at 12:10