[
https://issues.apache.org/jira/browse/OPENMEETINGS-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14355008#comment-14355008
]
Paul Gregoire commented on OPENMEETINGS-1178:
---------------------------------------------
In an effort to prevent possible confusion about "webm", I'd like to note that
a Red5 compatible version of this Matroska subset container would use h264 and
PCM instead of the standard webm codecs of VP8 and Vorbis. The h264 / PCM
codecs were suggested due to their support in both WebRTC and Flash players.
> GSOC: WebRTC support for OM
> ---------------------------
>
> Key: OPENMEETINGS-1178
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1178
> Project: Openmeetings
> Issue Type: Improvement
> Components: Audio/Video, HTML5
> Affects Versions: 3.1.0
> Reporter: Maxim Solodovnik
> Assignee: Maxim Solodovnik
> Labels: WebRTC, gsoc2015, java, mentor
> Fix For: 3.1.0
>
>
> Currently OM is using Flash to send/receive video we need to move to WebRTC
> This will require:
> 1) webm file writer: the writer would be a drop-in replacement for the
> default flv writer. With the assumption that when the non-webm codecs are
> recorded that the files would only be playable on red5 or some other player
> if they implement our media types.
> 2) webm file reader: for VOD playback
> 3) webrtc input to flash output: this would accept h264 video and PCM audio
> only; producing a flash compatible stream without requiring any transcoding.
> 4) webrtc datachannel
> 5) make OM to be able to send/receive WebRTC audio/video (most probably using
> existing wicket library)
> Links:
> [1] WebM container description: http://www.webmproject.org/docs/container/
> [2] WebRTC video format:
> https://tools.ietf.org/html/draft-ietf-rtcweb-video-04
> [3] WebRTC datachannel format:
> https://tools.ietf.org/html/draft-ietf-rtcweb-data-protocol-09
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
