BETA: Chrome Capture for Channels

Yes it should. Note that it can use a bit of CPU to encode the video so you may not be able to run more than a couple tabs concurrently depending on your computer.


Would this take advantage of a GPU for encoding?


I don't think so, but that's not something that's easy to change because it's built into Chrome by google.


What does this mean exactly? Just a media video/audio stream being played, say a YouTube video? Like a Cast to feature?
Or is this full desktop screen capture and stream?

How is latency?


It might have support? I'll have to dig in a bit more. Cannot enable GPU acceleration · Issue #3637 · puppeteer/puppeteer · GitHub

1 Like

I may be mistaken.

The software encoder build into Chrome has seen a lot of performance improvements:

and it seems like they enabled hardware support on macOS as well:

EDIT: Full support list here: mediacapture-record-implementation-status/ at master · yellowdoge/mediacapture-record-implementation-status · GitHub


Excellent. This might be a far better approach then trying to record a full desktop via Xvfb that I have been toying with. Have a 3060 RTX out for delivery today - I'll play around with this on Linux and MacOS. Thanks again for giving us alternatives for TVE.


It captures the entire visible contents of the tab.

Currently the code will look for a playing video on the page, size it to fit the screen, resize the Chrome window to fit the video so there's no black borders, then minimize the chrome window while it's recording.

But it could easily be adapted to record a dynamic webpage instead.


So could we feasibly make a channel out of any tabbed web page, even ones without video? Status dashboards, weather pages, stock prices, sports scores, headline news, calendars, etc.

Is there any allowance to "auto-refresh" the page?

Just brainstorming ideas here. Gamechangers inspire such direction! Thanks again @tmm1



I just added support for


This needs to be installed on the same machine as channels, eh? I have it installed on a linux box and can see its listening on port 5589 but do not see a request coming in. Guessing chrome:// URL handler is expecting localhost only?

1 Like

That is freaking awesome. Now I have to restart tinkering with the weatherscan project.

1 Like

No, it can be installed on any LAN machine and you can use it's IP.

However you do need DVR prerelease which is still uploading.. :sweat:


AHA! I'll sit tight for a bit.


Fantastic work, @tmm1! :clap:

I've been hoping for a solution like this for a long time and now it's happening! :partying_face:

Very excited to give it a try later. :smiley:


Sorry for jumping the gun

It started to work - Chrome launched, tuned to the channel but then abruptly closed.

Now I am seeing the error:

throw new Error("Could not find START_RECORDING function in the browser context");
exports.getStream = getStream;
function assertExtensionLoaded(ext, opt) {
    return __awaiter(this, void 0, void 0, function* () {
        const wait = (ms) => new Promise(res => setTimeout(res, ms));
        for (let currentTick = 0; currentTick < opt.times; currentTick++) {
            // @ts-ignore
            if (yield ext.evaluate(() => typeof START_RECORDING === "function"))
            yield wait(Math.pow(opt.each, currentTick));
        throw new Error("Could not find START_RECORDING function in the browser context");

Any ideas?

PS: while it WAS working the encoder rate was surprisingly very low in terms of CPU usage!

Does this only work with Google Chrome? Or will it work with Chrome based browsers, like Edge, Brave, Chromium etc.


I've seen that but am not sure why it happens. If you rm -rf chromedata then it seems to work reliably again for a while.

1 Like