With chrome v135 I get this error:
TargetCloseError: Protocol error (Target.setAutoAttach): Target closed
So probably puppeteer 24 needs a newer chrome.
It works for me with v138:
winget install google.chrome.exe -v 138.0.7204.184 --force
With chrome v135 I get this error:
TargetCloseError: Protocol error (Target.setAutoAttach): Target closed
So probably puppeteer 24 needs a newer chrome.
It works for me with v138:
winget install google.chrome.exe -v 138.0.7204.184 --force
I tested on 140 and 142 and neither worked for me. Maybe just me.
Same here on 140, no go.
Since I run docker containers on a mini PC with Ubuntu Server, I decided for the heck of it I'd try the docker container version of CC4C and holy cow I wish I would have done this sooner! Now granted, I'm only using CC4C for Weatherscan and then various live web cams, but for these particular things, the docker container version of CC4C loads waaaaaay quicker and flawlessly all the time compared to the node setup I had been using through Windows. Thank you so much @tmm1 !!!!
Is there a way to convert custom main.js back into a docker ?
I'm not certain that NESN is DRM'ed. I posted about this in the ESPN+ & FOX Sports with Custom Channels via EPlusTV - #2635 by DaveTheNerd thread, and @tonywagner indicated there might be a way to test for that. Happy to do that testing, I just don't know how to confirm it (but I'm fairly nerdy and happy to learn! LOL).
If you have the m3u8 for the channel, I have some scripts that can see if it is DRM protected.
I just PM'ed you.
UPDATE:
I figured out how to use 142.x+ Chrome (or whatever build you want from the chrome testing builds)
Step 1)Install Chrome 142.x using this script
npx @puppeteer/browsers install chrome@142
or
npx @puppeteer/browsers install chrome@stable
This will give you the latest testing build <139 are not supported any longer.
Step 2)Uninstall Chrome & Delete folders & Copy the folder with chrome to
C:\Program Files (x86)\Google\Chrome\Application
&
C:\Program Files\Google\Chrome\Application
or the appropriate folder for your mac.
Step 3)Run Chrome capture. I just released a new one ncc-08-0.js on github
This will have to work until Google patches the issue.
All testing builds will have this banner and you cant remove it afaik
Thanks for doing this! I've never used your unified stream EPG. Do we have to do this in order to make Chrome Capture work with 142.x+? Apologies for the confusion.
Edit: Never mind. I found Unified Stream for EPG + M3U - Chrome Capture + HDMI Capture Compatiblee and now I am understanding.
Thanks!
I have custom main.js that needs more refining but any node main.js or docker should work but going to increase support for other sites
For Proxmox users, I've updated the instructions for creating an LXC version of cc4c. This works with the latest stable Chrome (140.0.7339.80 as of this writing), Node v22.19.0, and uses the most recent code base (2.0.1) from the fancybits/chrome-capture-for-channels repo:
Apologies for the ignorance, but:
Sounds like you're not a Proxmox user:
Yes.
Yes to Docker.
That's what the step-by-step linked above is for -- but it's targeted at existing Proxmox users.
Would it be possible to have a 1 click installer? Regardless, I will attempt to do as stated on the guide sometime soon. I apologize for frustrating you, has anyone else been able to install it as per the guide?
Project One-Click is strictly for Docker projects utilizing Portainer.
Do you already have a system running Proxmox? If not, that's the bigger project -- adding a cc4c LXC is trivial in comparison.
No frustration on my end, though focusing on quality of posts rather than quantity helps to keep the content on the forum the most useful for everyone.
Multiple people have used the LXC guide successfully in the past, but I'm sure I'm the only one who's used the updated version I posted a few hours ago.
One of the beauties of virtualization though (like Proxmox), is that it's easy to spin-up a new container to test a step-by-step, after all the steps are determined -- and I did that before posting the update.
Wow guys so many random ways sports are on now I need to do YouTube too apparently YouTube has live sports as well chargers game so paolo
It keeps updating to 139 on Mac. Any other things I should be doing? For the first command, I used sudo rm -rf.
Windows or Mac?
Mac