Chrome Capture for Channels

Playground Hacks
#2094

Those dont have proper guide data though right, or do some?

#2095

Does anyway have a already made spectrum TV channels list, I hate adding all the channels :sweat_smile:

#2096

Yeah...thats gonna be tough as Spectrum channels lineup differ based on location so no

#2097

The tmsid's should be the same?

2 Likes
#2098

Added Live News Stream: Watch FOX 5 New York to my CC4C list it opens fine has sound BUT wont open full screen stays windowed any ideas???

Capture.cJPG
Capture.cJPG1223×627 102 KB

#2099

You can get this Channel using tubi-for-channels. No need for CC4C

#2100

Mine seemed to stop working a few days ago. It looks like it was running chrome version 139 at the time it stopped.

The terminal window opens saying listening on port 5589. When I tune into a channel, it opens chrome for a split second, then both the chrome window and terminal close. Seems like something is crashing.

I have tried reverting to chrome version 135 and I am having problems from stopping Chrome from updating itself despite renaming the updater and doing registry edits.

The only other thing I can think of is 2025-08 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5063878) (26100.4946) was installed on 8/13, which was right around when it stopped working.

#2101

I ran into this same issue and here’s what I did. I uninstalled chrome. I completely deleted my chrome capture for windows install. I installed chrome version 135. I went into services.msc and found the 2 google update processes, right clicked and went to properties, then changed automatic to disabled and applied that. I then reinstalled chrome capture for windows. I use the node option as I customize my main.js file. After doing all these steps, it’s working like normal for me again.

2 Likes
#2102

I did the same. You have to disable the services very quickly or chrome will try to update. This happened to me the first time I did this.

#2103

I presume that is a prior version. Is there somewhere relatively safe to download that version? (My Chrome Capture setup stopped working recently, too, but I haven't had time to troubleshoot).

#2104

I got it from a site called uptodown. I researched them and it seems pretty secure and reputable. I scanned the file too and everything seems clean.

Here’s the link to the version I downloaded:

#2105

Have downgraded and disabled those services before and have still seen Chrome auto update at some point.

#2106

Well.... I had to disconnect the internet to the router so that I could install google chrome version 135 on my server and have time to disable all the services / rename stuff.

While it is stuck on ver 135, it is still having the same problem where the chrome window opens for a split second before crashing.

Both v0.1.10 and v1.4.1 have problems. V0.1.10 crashes the terminal as well, while v1.4.1 only has google chrome crash.

I am wondering if it was something in the latest windows update that is causing problems. Or is google chrome elevation service required for this to work?

edit:
Reverting the windows security update and enabling google chrome elevation service still doesn't change it. I'll have to do try the node option i guess.

#2107

Thanks (just getting to this now). I'm on a Mac, and found the Mac download on that site after wiping Chrome from my system using an app called App Cleaner. But Chrome version 135 immediately crashes for me, unfortunately. Not sure where to go from here.

#2108

Try the node option, that worked for me.

#2109

Do you mean running it via node main.js? That's how I do have mine setup. Will that work even with the crashes?

#2110

I was using the downloadable executable file before. Try following Accusitver's steps (uninstall and reinstall both Chrome and Chrome capture for channels.

#2111

Yes…using main.js although I use the customized version that someone on here created…ncc-7-something along those lines. I tweaked some code in there as well to my liking. But bottom line is, uninstalling everything and re-installing with chrome 135 and immediately disabling updates SHOULD work.

1 Like
#2112

Just to add for others...in my testing, Chrome 138.0.7204.169 was the last working version with CC4C. Chrome 139 seems to have broken things, though it's unclear (to me at least) whether that's intentional or unintentional breakage on Google/Chrome's part.

For those that need to download it: Download Google Chrome 138.0.7204.169 for Mac | Uptodown.com - that's the macOS link. You can find the other OSs at the bottom.

My suggested path for folks who want to pin versions on macOS:

  1. Download the above and install it, but don't start it.
  2. rm -rf ~/Library/Google/GoogleSoftwareUpdate ; mkdir ~/Library/Google/GoogleSoftwareUpdate/ ; chmod a-rwx ~/Library/Google/GoogleSoftwareUpdate - this will delete the Google software update cache directory, recreate it, and set permissions to prevent Chrome from being autoupdated.
  3. Delete chromedata directories under the CC4C directory (and possibly in ChannelsDVR as well if you're using TVE). The directories aren't downward compatible with older versions and generate errors.
  4. Reauthenticate for TVE as- needed for CC4C and ChannelsDVR.

Hope this helps folks like me who need it...and here's hoping future Chrome releases fix things.

6 Likes
#2113

Thank you!

That worked brilliantly, and confirmed my suspicion that a recent Chrome update was the culprit. I'm back up and running with my NBC-owned channels (the only ones I need CC4C for).

1 Like