Existing technologies
A main takeaway from the workshop is that the web
platform already provides suitable building blocks to
enable core media production scenarios in a proXY_
based architecture: media streaming and rendering
technologies (eg_
the video element;
canvas based
rendering; MSE
the Web Audio API), transport
technologies (Fetch; WebRTC), processing
technologies (through JavaScript; WebAssembly; or
WebGL) and storage technologies (File API;
IndexedDB) are widely supported and used across
authoring applications
It seems clear; however; that the web platform cannot
easily accommodate
no-proxy_architecture today for
professional media production scenarios
Technical
gaps raised during the workshop mean that the
scenarios can be achieved in web applications but only
to some extent: For instance; media authoring
applications running on client devices may need to
clamp the resolution of videos
480x270 when
they have to decode and process the video themselves
because they cannot leverage hardware decoders
They may also run into hard-to-solve synchronization
issues, jeopardize color fidelity; or may run poorly
compared to native applications because they cannot
easily leverage optimizations for processing media such
as advanced SIMD instructions.
Ongoing standardization efforts
Workshop talks and discussions show that ongoing
standardization efforts will bring advanced features and
performance improvements that the media production
industry needs.
These include low-level access to
media as exposed by WebCodecs
better latency
measurement capabilities in the Web Audio API;
enhanced performances in WebAssembly (advanced
SIMD
64-bit memory heap support) , smoother Uls
when APIs are all available in workers, and production