Shared publicly  - 
+Craig Grannell wanted to know why +Bruce Lawson likes +Robert O'Callahan's MediaStream Processing API and Bruce asked me. Here's what I think:

• Well integrated with the <audio> and <video> media pipeline.
• Same basic API for processing of both audio and video streams.
• Supports syncing processed streams with other (processed or untouched audio or video) streams.
• No premature optimization in the form of predefined effects, but allows adding them as time goes via createProcessor and createWorkerProcessor.
• Simple to offload processing to a worker.
• Integrated with WebRTC and its Stream API.

See also:
Bruce Lawson's profile photoJeaux Moer's profile photoPhilip Jägenstedt's profile photo
Thanks Philip.

Beverloo and Alex Russell (both Chrome cheerleaders) suggested that a benefit of the Chrome API was that there were predefined effects (so easier for authors) and chance of optimisation.

( I may be misrepresenting them; 140 characters allows for little nuance)
To whom can I send this: Problem signature:
Problem Event Name: APPCRASH
Application Name: opera.exe
Application Version: 12.0.1211.0
Application Timestamp: 4ee921dd
Fault Module Name: Opera.dll
Fault Module Version: 12.0.1211.0
Fault Module Timestamp: 4ee93158
Exception Code: c0000005
Exception Offset: 0000000000207f65
OS Version: 6.0.6002.
Locale ID: 7177
Additional Information 1: a57d
Additional Information 2: 5eaf3d3ab59d92839893036fdb50a15a
Additional Information 3: 7f3e
Additional Information 4: 0061a229c1bf64ecc8ff6613a77471bd
If Opera crashes you should get a crash report dialog and be able to submit it with the click of a button. Make sure to include your email address if you want someone to look for it later.
Add a comment...