googlewebcomponents / google-youtube-upload Goto Github PK

Chrome issue 601636 adds support for H264 encoder, it can be configured in MediaRecorder.start() the same way as VP8/9. Adding H264 allows for using certain hardware encoders (crbug.com/608385).

Micro-catch: The generated output file is a .webm for VP8/9, whereas it should be a .mkv when H264 is selected (see this demo)

Thanks to @jeffposnick, since version 2.0.0 <google-youtube-upload> supports capturing video directly from a camera via MediaRecorder API.

What about "Do one thing and do it well" philosophy and split <google-youtube-upload> to 2 web components:

1. web component for uploading video files to YouTube
2. full-featured (fully configurable via properties) MediaRecorder API web component for recording video from the camera or screen

and share data between these 2 web components use data binding?

From this point of view these 2 web components are independent, they only share data. If you want to replace MediaRecorder API web component with another component, you can easily do that. There is only one requirement, that another web component must provide video data. E.g. it may be a web component which receives a WebRTC video stream from another device or a web component which receives a video file from WebTorrent (BitTorrent over WebRTC) decentralized peer-to-peer network (for more info see https://github.com/feross/webtorrent, https://webtorrent.io).

Add options to disable/enable audio/video for MediaRecorder recording.

Upon clicking Sign in, I receive the following popup:

YouTube allows to run real-time broadcasts. See https://youtube.com/my_live_events.

What about live stream support by google-youtube-upload?

Currently there are 2 ways to run real-time broadcasts: 1. using Google+ Hangouts API and 2. using RTMP/DASH.

But according to https://developers.google.com/+/hangouts/support-faq, Google will close Hangouts API for video app developments starting from April 25, 2017.

For developers, this means we will not be able to create our own custom applications using Hangouts API that stream video (including YouTube).

I need to stream video and audio from the browser (web app) directly to YouTube Live without any intermediate server (for converting WebRTC to DASH or RTMP). Is it possible?

Currently YouTube Live Streaming API supports only RTMP and DASH, not WebRTC: https://developers.google.com/youtube/v3/live/docs/liveStreams#cdn.ingestionType

Is it possible somehow to create (segment) DASH stream from WebRTC on client-side in browser and stream it to YouTube endpoint? If yes, how?

According to https://developers.google.com/youtube/v3/live/guides/encoding-with-dash, YouTube Live DASH endpoint supports H.264 and AAC codecs in ISO BMFF (MP4) container and VP8/VP9 and Vorbis/Opus codecs in WebM container. All these codecs currently are native for WebRTC and browsers and do not requires transcoding on intermediate server.

Does google-youtube-upload support screen capture?

Chrome is introducing a new constraint {'chromeMediaSource':'screen'} for getUserMedia API, this says that Chrome should use the Screen as the Streams media source.

It's currently behind a chrome://flags#enable-usermedia-screen-capturing flag.

Due to an incompatibility with the underlying OAuth 2 flow exposed by <google-signin>, this element currently does not let you authorize access to upload to a YouTube account backed by a Google+ Page.

The core incompatibility is being addressed at the library level, and no change to this element will be needed to pick up the fix when it's available.