Chrome Capture for Channels

[Edwin_Perez]

@Ahwman

I noticed that development seems to have slowed down on this project or at least the frequency of updates. I’m just wondering if this is a stop gap for the time being as it is refined and ultimately bundled into Channels server or if it is more of a weekend project to appease those looking for a temporary work around…

This project appears to be a free for all as everyone has different needs... right now it is all over the place.

[Pasker17]

I just noticed that YTTV is not working for me using CC4C, I get the following error when logging in:

Chrome: Version 114.0.5735.198 (Official Build) (arm64), M1 Mac Mini.

[cyberskier]

I had this issue early on in the process, but forget what fixed it — perhaps a later build? Are you using the latest build on GitHub?

[mike_here]

I get this error when I'm not using the DNS servers for my ISP or not using a SSL connection.

[tmm1]

Does it works if you paste that url directly into the browser?

[kennyb3653]

yes. Same for all nbc brands like syfy

"https://www.nbc.com/live?brand=syfy&callsign=syfy_east"
"https://www.nbc.com/live?brand=syfy&callsign=syfy_west"

[tmm1]

Then you need to url encode it

Replace & with %26

[kennyb3653]

Thank you, Seems to work. I've been asking about this for a week with no success.

[Gregg_K]

This would be great, but I'm getting an error:
Get "chrome://127.0.0.1:5589/stream/msnbc":unsupported protocol scheme "chrome"
I've tried a few different clients, all with same results. Any ideas?

[kennyb3653]

chrome://127.0.0.1:5589/stream?url=https://www.nbc.com/live?brand=msnbc%26callsign=msnbc

[tyler.seip792]

Boy am I really hoping I can get this to work, but the directions are NOT friendly to those outside of the coding world... I am sure there is a hole in my setup somewhere... if anyone has a suggestion please let me know! I'm so lost!

I have the server on one old 2011 iMac, and the chrome and chrome capture terminal code running on another Mac (up to date) in the network.

This is all I am tying right now:
#EXTM3U

#EXTINF:-1 channel-id="MSNBC", MSNBC
chrome://192.168.86.22:5589/stream/msnbc

but I get "The connection to the tuner was lost" error and this in the terminal window:

[2023/07/05 21:33:53.749] GET /stream/msnbc from ::ffff:192.168.86.220 responded 500 in 1.726 ms
[2023/07/05 21:34:44.854] failed to start browser page https://www.nbc.com/live?brand=msnbc&callsign=msnbc Error: An executablePath or channel must be specified for puppeteer-core
at assert (/snapshot/chrome-capture-for-channels/node_modules/puppeteer-core/lib/cjs/puppeteer/util/assert.js:28:15)
at ChromeLauncher.computeLaunchArguments (/snapshot/chrome-capture-for-channels/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:96:36)
at ChromeLauncher.launch (/snapshot/chrome-capture-for-channels/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ProductLauncher.js:83:39)
at ChromeLauncher.launch (/snapshot/chrome-capture-for-channels/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:51:22)
at PuppeteerNode.launch (/snapshot/chrome-capture-for-channels/node_modules/puppeteer-core/lib/cjs/puppeteer/node/PuppeteerNode.js:151:105)
at Object.launch (/snapshot/chrome-capture-for-channels/main.js)
at /snapshot/chrome-capture-for-channels/node_modules/puppeteer-stream/dist/PuppeteerStream.js:83:34
at Generator.next ()
at /snapshot/chrome-capture-for-channels/node_modules/puppeteer-stream/dist/PuppeteerStream.js:31:71
at new Promise ()
[2023/07/05 21:34:44.855] GET /stream/msnbc from ::ffff:192.168.86.220 responded 500 in 1.305 ms

[mike_here]

Here is the entry I use for MSNBC. The difference is the URL. I'm using the full version of the entry instead of the short URL. I had issues with the short versions, but have not had any issues using full URL.

chrome://x.x.x.x:5589/stream?url=https://www.nbc.com/live?brand=msnbc&callsign=msnbc

[kennyb3653]

change & to %26

BETA: Chrome Capture for Channels

chrome://127.0.0.1:5589/stream?url=https://www.nbc.com/live?brand=msnbc%26callsign=msnbc

[krazijoe]

@hjd

Let me add to this terrific guide. For those on Macs who want to autostart without Platypus or anything else:

Go to ~/Library/LaunchAgents on your Mac and create a file called com.getchannels.chrome.capture.plist and put the following in it:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>RunAtLoad</key>
    <true/>
    <key>KeepAlive</key>
    <true/>
    <key>Label</key>
    <string>com.getchannels.chrome.capture</string>
    <key>UserName</key>
    <string>yourusername</string>
    <key>WorkingDirectory</key>
    <string>/path/to/chrome-capture-for-channels</string>
    <key>StandardOutPath</key>
    <string>/path/to/chrome-capture-for-channels/chromecapture.log</string>
    <key>StandardErrorPath</key>
    <string>/path/to/chrome-capture-for-channels/chromecapture.log</string>
    <key>ProgramArguments</key>
    <array>
      <string>/opt/homebrew/bin/node</string>
      <string>/path/to/chrome-capture-for-channels/main.js</string>
    </array>
</dict>
</plist>

Substitute your own username for yourusername and the right path to Chrome Capture for Channels for /path/to/chrome-capture-for-channels in the various places.

Then run:

launchctl load ~/Library/LaunchAgents/com.getchannels.chrome.capture.plist

Remove / stop the service with:

launchctl remove com.getchannels.chrome.capture

Logs will be in chromecapture.log in the main Chrome Capture for Channels directory.

Enjoy.

I am trying to set this up but I apparently have no idea what I am doing as all I get is an error
"Load failed: 5: Input/output error
Try running launchctl bootstrap as root for richer errors."

I am using the all in one package for OSX. I am on a Mac Mini M2.

[ert]

@krazijoe

Load failed: 5: Input/output error

Is it already running ?
Try

launchctl unload ~/Library/LaunchAgents/com.getchannels.chrome.capture.plist

Then

launchctl load ~/Library/LaunchAgents/com.getchannels.chrome.capture.plist

[babsonnexus]

@tyler.seip792

the directions are NOT friendly to those outside of the coding world... I am sure there is a hole in my setup somewhere... if anyone has a suggestion please let me know! I'm so lost!

Delete everything you have done, start over, and do this:

BETA: Chrome Capture for Channels

Simplified Installation Instructions (as of 2023-07-05 at 6:30pm ET | v0.1.10) Chrome Capture for Channels will open a Chrome browser and literally capture what is being shown on that tab and project it to Channels DVR. It works based on the browser's built-in capture functionality and other programs that have taken advantage of that in the past. It requires no interaction after initial setup and only will display a specific tab to Channels DVR. It does not take over your system as it is basica…

Confirm each step along the way in a checkbox fashion. Don't do any of the "optional" steps. Be sure to review "Troubleshooting / Common Issues" and attempt those. If none of this resolves your issue, tell us where in the entire process it failed for you.

[mike_here]

This issue reminds me of an issue from a long time ago. When watching CNBC using Chrome Capture for Channels, when the program goes to a commercial, the video playing in the Channels App (Android) the video freezes (not always, but often). Sometimes it recovers after a few minutes but the audio continues to play without issue. I've only observed this while watching live, not recorded content on CNBC. The source is the NBC website.

When I look at Chrome on the server, it's still playing without issue, so it appears that the Channels App is causing the video to freeze.

I am using the Experimental TV Everywhere MPEG-TS Rewriter feature. All apps are the latest versions.

[krazijoe]

Not sure what the issue is, but I am using the OSX Package so I will just get it started manually on login. Or at least try lol...

[scottuf]

Are you running this on an M1 or M2 Mac? Homebrew installed to /opt on M1/2 and to /usr/local on Intel Macs so you may need to correct that in the file.

When I get home tonight I can paste mine for Intel if you think it would help.

[krazijoe]

@scottuf

Are you running this on an M1 or M2 Mac? Homebrew installed to /opt on M1/2 and to /usr/local on Intel Macs so you may need to correct that in the file.

When I get home tonight I can paste mine for Intel if you think it would help.

M2, I am not going to mess around with any files, so I don't even know if I am doing the install right. It works the way I am using it now, which is just running the all in one ARM64 package.