5 ms·
Calling shenanigans. I wrote a couple of fairly complex publishers and Chrome isn't the problematic browser (if you use ExtermalInterface correctly). It's Safar
by brokenparser 13y ago
Calling shenanigans. I wrote a couple of fairly complex publishers and Chrome isn't the problematic browser (if you use ExtermalInterface correctly). It's Safari which doesn't handle plugins well, but Camera and Microphone devices should still work as Flash handles those by itself.
- MacsHeadroom 13y agoSafari has how much of the browser market share? Nobody gives two glances about Safari, mate.
- vermontdevil 13y agoPretty large if you count mobile devices.
- base698 13y agoThere was a well publicized audio problem with Pepper. It broke nearly all audio playback for weeks. Happened on every platform.
- brokenparser 13y agoOkay, but playback problems don't negate the ability to record or stream input devices.
- mtrimpe 13y agoApart from the fact that until February this year it was impossible to keep PepperFlash disabled [1], we've so far had: - Frequent crashes when acquiring video camera [2] - Recorded sound being choppy and broken (still not fixed for Red5) [3] - Audio delays and broken echo cancellation in Speex [4] - Microphone sound levels not reported, breaking apps like ours which check if a microphone worked properly. (resolved together with [3]) - Sound stopping to record after a few minutes [5] - Inability to give camera access on retina displays [6] - Rushed fix for a click-jacking attack introduces horrible UX that gets into an unrecoverable state by default [7] All in all I can personally confirm that Chrome has not been good for people doing video recording on the web. [1] https://code.google.com/p/chromium/issues/detail?id=150596 https://code.google.com/p/chromium/issues/detail?id=150596 [2] https://code.google.com/p/chromium/issues/detail?id=140831 https://code.google.com/p/chromium/issues/detail?id=140831 [3] https://code.google.com/p/chromium/issues/detail?id=136624 https://code.google.com/p/chromium/issues/detail?id=136624 [4] https://code.google.com/p/chromium/issues/detail?id=144554 https://code.google.com/p/chromium/issues/detail?id=144554 [4] https://code.google.com/p/chromium/issues/detail?id=152314 https://code.google.com/p/chromium/issues/detail?id=152314 [4] https://code.google.com/p/chromium/issues/detail?id=140724 https://code.google.com/p/chromium/issues/detail?id=140724 [5] https://code.google.com/p/chromium/issues/detail?id=168859 https://code.google.com/p/chromium/issues/detail?id=168859 [6] https://code.google.com/p/chromium/issues/detail?id=177621 https://code.google.com/p/chromium/issues/detail?id=177621 [7] https://code.google.com/p/chromium/issues/detail?id=155437 https://code.google.com/p/chromium/issues/detail?id=155437
- brokenparser 13y agoBoy, am I glad these bugs were fixed around the time I wrote my publishers. Remind me to check all the relevant bug trackers before going full steam ahead with a rewrite, ha ha.