BETA: Chrome Capture for Channels

Let's try a few things if you wouldn't mind:

First, let's try making the VNC server a one shot deal, by eliminating the -forever option. And second, let's write our desired bitrates directly to the main.js file (just like you did in your modification), rather than using env vars in the .js. The new docker-compose would look like this:

version: '3.9'
    image: fancybits/chrome-capture-for-channels:latest
    container_name: cc4channels
      - sh 
      - -c 
      - |
        Xvfb :99 -screen 0 1920x1080x16 &
        x11vnc -display :99 &
        sed -i '/videoBitsPerSecond/c\        videoBitsPerSecond: ${VIDEO},' main.js;
        sed -i '/audioBitsPerSecond/c\        audioBitsPerSecond: ${AUDIO},' main.js;
        exec node main.js
      #- /dev/dri:/dev/dri # Uncomment for Intel Quick Sync (GPU) access
      - 5589:5589 # cc4channels proxy port
      - 5900:5900 # VNC port for entering credentials
      - VIDEO=${VIDEO}
      - AUDIO=${AUDIO}
      - TZ=${TZ} # Add your timezone in the Environment variables section with "name" set to TZ and "value" to your local timezone
      - cc4channels:/home/chrome # Creates persistent Docker Volume in /var/lib/docker/volumes for Chrome data and main.js
    restart: unless-stopped

Other than the one shot VNC server we're exactly the same as the original.

I think its chrome capture in general that is not up to my picky standards.
When I was watching it last night, I thought it was pretty good.
Today, with or without portainer, it just seems like the framerate isn't up to snuff.
Its watchable, just kind of jerky I guess....

1 Like

Had a chance to do some testing. I think when I started this I was at 116.0.5845.96. Forgot I re-enabled updates. Everything seems to be running fine with NBC Streams shuddering/buffering but video continues instead of freezing. Checked the version and it was at 116.0.5845.111. It updated to 116.0.5845.141 and also seems to be working fine. Not sure when the freezing video started, but at this moment running fine like it was on v114. I'll do some random recordings and see if they all are fine and report back.

My setup for reference is a Mini PC running Windows 11 with just CC4C running and video output at 4K. CDVR is on a Pi4B. Not endorsing but I got it off Amazon: "KAMRUI Mini PC,AMD Ryzen 5 5560U (6C/12T, up to 4.0 GHz), Mini Computer Tower with Dual Channel 16GB DDR4 512GB SSD,Small Desktop Computers Windows 11 Pro,4K Triple Display,BT4.2/WiFi 5/Dual LAN" Looking at the resources, way more power than CC4C needs but if it's stable, I'll just leave it dedicated. Thanks.

1 Like

So I think I figured out my problem. I had a little custom-made .exe program running minimized (a cmd window) that automatically creates .ts streams from my web-cam and puts them in a folder which then gets turned into an .m3u. I have this setup for Channels to be able to show my webcam as a channel. I used to use a simple rtsp link as a custom channel which seemed to work fine, but then several months ago, all of a sudden I started noticing Channels either taking too long to load the camera, or, there would be no sound. So I came across this other method which has been working. But to finally get to my point...LOL! It seems when this program is running, that's when I get all kinds of buffering and freezing issues on a client with CC4C. Sure enough, I closed the program, and then tried loading up the various CC4C channels, and wallah...they play just fine. I wonder if it has something to do with FFMPEG. My aforementioned custom program heavily utilizes that, and I think CC4C does as well? Perhaps with my hardware setup, you can't have multiple things running at the same time which utilize FFMPEG if you want something to operate smoothly?

Does anyone got a list of services that works with this?

We know Hulu, Paramount+, the Roku Channel, Spectrum, Peacock, Philo and YTTV works

From my experience

Sling works. Tried with freestream and it worked well
Fubo works.
DTV don't work.
VIX somewhat works but the audio is muted so only way VIX will work is as a channel for YTTV or Sling.

For anyone looking for a solution for PBS Kids:

1 Like

I have a Mikrotik router that has a built-in Wireguard server which uses udp protocol, will CC4C work over that protocol? I have a pc in a remote location that I can connect to (two-way connection) on which I would like to install CC4C and then run through my router at home. Any ideas? Thanks.

Not my area of expertise, but CC4C is pretty simple to get up and running. So, I'd get it working locally, and then give the remote PC a try.

1 Like

Thanks @sheepy, I was able to get it running on a local machine already. I also tested it in a different pc in the same household and was able to get it running there too. Now is the big test... :smile:

The Roku Channel, Spectrum, Peacock.

I tried this again this morning and its working perfectly.
No Idea why.....

Things like this drive me crazy.
I have it working with Showtime on Paramount +
Maybe the framerate of movies is more agreeable.
I will try some sports later and see if that is what I am seeing.

Thanks again!

How do you get Peacock to default to Volume On? It always starts Muted for me.

I have the same issue.

I have tried several things - it's strange that Peacock's web player would default to Mute. I can't figure out a good workaround. Was hoping someone here did.

Same issue on Yes Network Ive tried a few things BUT don't understand coding to force the Un-Mute button to be "clicked"

For those who need it, yes, this can be a solution for NFL Network:

Wonder if @tmm1 has a solution?

1 Like

So just my feedback on my experience thus far: I'm running this as the exe on an M1 Mac Mini with 8GB of RAM, and the streams start out great...but quickly devolve into stutters and stops. It makes for a poor watching experience. Has anyone had any luck optimizing things? Just wondering if it's something about my setup, or Chrome itself. Chrome is the latest version, FYI.

1 Like

@radioboy, sounds like we are both having same issue. I'm on Windows 11 and thought the latest Chrome v116 resolved my issues, but not. I thought it was fixed but after trying a few recordings, looks like they froze in the middle and never unfroze. I'm watching the stream on my PC and it seems to recover from the buffering fine. Just seems when it's launched in a sandbox from CC4C, it shudders and will freeze. I will test some more in the evening and see if there is more buffering to cause the freezing on my PC. Thanks.


i've added these to the args. (running manually via command line: node main.js)


not sure encode is necessary but can't hurt. decode has improved performance. definitely worth a shot if you have a gpu integrated or discrete... my opinion.