Thank you for sending this! This is what I was looking for, can't believe I missed it. I am still having issues and will do my best to describe them:
- I am using a 2011 iMac as my Channels server running High Sierra 10.13.6. When I run the chrome capture for channels program from GitHub it comes back with this. Does this mean my Mac is too old for this?
dyld: lazy symbol binding failed: Symbol not found: ____chkstk_darwin
Referenced from: /Users/channelsimac/Desktop/chrome-capture-for-channels-macos-x64 (which was built for Mac OS X 10.15)
Expected in: /usr/lib/libSystem.B.dylib
Thats what I assumed, so I wen't to a different iMac in the house which is running the latest MacOS, and ran the program and Chrome on there and it seems to behave better since it says:
[2023/07/09 10:14:41.541] Chrome Capture server listening on port 5589
I thought I read somewhere in one of these threads, that you can use a different computer from the DVR server for Chrome Capture. All you have to do is replace LocalHost with the IP of the other computer on your network, so here is what my custom channels look like:
#EXTM3U
#EXTINF:-1 channel-id="MSNBC",MSNBC
chrome://192.168.86.22:5589/stream/msnbc
#EXTINF:-1 channel-id="NBC Sports Philadelphia",NBC Sports Philadelphia
chrome://192.168.86.22:5589/stream/nbcsphiladelphia
When I attempt to launch the channel from my phone, the Channels App says The Channels DVR Server had a problem. Press play to try again. (Transcoder)
The Crome Capture app reports the following:
[2023/07/09 10:18:17.825] failed to start browser page https://www.nbc.com/live?brand=rsn-philadelphia&callsign=nbcsphiladelphia 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 (<anonymous>)
at /snapshot/chrome-capture-for-channels/node_modules/puppeteer-stream/dist/PuppeteerStream.js:31:71
at new Promise (<anonymous>)
[2023/07/09 10:18:17.828] GET /stream/nbcsphiladelphia from ::ffff:192.168.86.220 responded 500 in 4.202 ms
I also failed to get the auto launch plist to work right, but for now I figured I would try and see if I can even get a channel to load first. I'll circle back to that if/when I can get the above figured out...
Your help so far as been greatly appreciated.