Userscripts.org

The JSAPI is a little sporadic at times unfortunately. Its possible to set the number of retries to up to 15 attempts however its still not guaranteed to work. Usually on a dual core system its able to catch on the first few retries. On every Firefox system I've tested it at least works sometimes, but it will not always work reliably. I believe there is an alternative way I can implement the pause feature that may remove the dependency on JSAPI which would make it more reliable so I plan on looking into this more. If anyone else is experiencing problems where the JSAPI never works or if it starts working suddenly let me know!

The JSAPI also seems more likely to fail when reloading the same video repeatedly. The JSAPI does not work at all in Chrome yet since its difficult to interact with the wrappedJSObject of the player without double implementing everything.

The AutoPlay feature now has a more robust counterpart which also disables auto-buffering but always pauses the video even if the JSAPI fails. You can edit these settings under JSAPI preferences.

The JSAPI should be better in the latest version. Please let me know if you are still having trouble and I'll see what I can do.

I just solved some of the other issues and will be posting soon. Can you provide any more details/hints as to your system specs? I think that JSAPI working or not working is CPU related, and that at certain frequencies and conditions it just will not work, however usually there is a way to trick it into working at least sometimes by adjusting the timeout between attempts.

Right now for ubuntu, it always forces at least one re-load since we determined at one point that was necessary. Everything else is handled above that keyword by 23*autoplayFailedRegs, which is 23 miliseconds times the number of attempts so far (which computes the amount of delay between attempts) which increases with each re-attempt by another 23 MS until it finds one that works. Tweaking the 23 might very well fix things, however 23*15=345 + 23*14=322 ect.... where having too large of a delay and too many retries will make it take forever to start playing video, and still no guarantee it will work unless there is some new way to connect.

Anyone who is having problems with videos starting fullscreen needs to go into about:config and search for fullscreenmode and make sure its set to false, or install the next update I'll post after a few more tests.

Its possible it could be a flash plug-in version issue, however unlikely. If the JSAPI works normally with VidzBigger disabled then I'd still recommend tweaking the 23 at 23*autoplayFailedRegs, I have another idea to try as well, possibly any way you can delay the state change listener being added without missing the first state change.