The subject says it… At least on Linux since today Chrome stable is autoupdated to version 20, which means Gibber or audiolib.js doesn’t work for now…
Best
.p.
Hi Rainer,
This sucks. There was an update to sink.js (the part of audioLib.js that handles the audio drivers in different web browsers) but even running the official sink.js demos just gives me silence at the moment (although no errors).
I assume Chromium has the same problems? I’m checking in with the audioLib.js / sink.js developer here if you want to follow:
https://github.com/jussi-kalliokoski/sink.js/pull/16
Hei, I’m Panca, hahaha! How do you know my secret name is Rainer?
I am sure Chromium current/beta has the same problem. I have frozen Chromium 18 specifically for Gibber, so for me personally no problem. But most people don’t even know how to prevent Chrome from updating and Google is very aggressive with “single-version” reinforcement for Chrome – so in a few weeks there won’t be many people around that can still use Gibber…
Best
.p.
Already fixed. How cool! Thanks, .p.
Hei Charlie,
nice to have Gibber working now in Chrome 20 but us poor Linux-users still get a strange timing effect. Things are very slow and quite distorted… It’s fixed in the dev-Version, but not here…
Best
.p.
Maybe I didn’t push to master. Is it fixed in the online version? I thought I changed it there… let me know if it doesn’t work on the website. Thanks!
It’s in master but not in the online-version. Sorry for being unclear…
Best
.p.
OK, it’s fixed now in Chrome 20 under OS X… hopefully it’s OK in Linux as well.
