On Fri, Sep 25, 2015 at 3:20 PM, <li...@nanocosmos.de> wrote: > On Saturday, September 19, 2015 at 8:15:50 PM UTC+2, Eric Rescorla wrote: > > On Sat, Sep 19, 2015 at 11:09 AM, Oliver Lietz <oli...@gmail.com> wrote: > > > > > Hi, > > > our nanoStream plugin supports live encoding and streaming with > > > h264/aac/rtmp from live camera sources and capture devices. > > > We needed to replace this with a native extension on Chrome. > > > WebRTC is a possible future option but not a suitable replacement for > all > > > use cases. > > > > > > > One or both of WebRTC and MSE is intended to cover precisely these > > use cases. What are they missing here? > > > > -Ekr > > > > > > NPAPI stills works on Firefox, but how long will it remain? > > > What options do we have in the future for implementing native > extensions? > > > Thanks, Oliver > > > _______________________________________________ > > > dev-platform mailing list > > > dev-platform@lists.mozilla.org > > > https://lists.mozilla.org/listinfo/dev-platform > > > > > MSE is playback only, so no option for live broadcast. > WebRTC is VP9 and a peer protocol (RTP) not compatible to existing > streaming environments (RTMP, HLS).
Firefox WebRTC supports H.264. > It requires a proxy/transcoder. It also does not allow local recording in > mp4 properly, and the codec details cannot be accessed. I don't know what this means about codec details. > Many other features lacking which would be possible in native > capture/encoding/streaming code. > Can you elaborate what those features are. In any case, this is the set of use cases WebRTC is intended to support and so the right direction to be going is to work with WebRTC (potentially helping us enhance WebRTC to support your applications) rather than doubling down on NPAPI. -Ekr _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
