Not sure if this happens for you currently, but for me, the main.js does open chrome fine but does not load the kayo sports website, so not sure if its my setup or if kayo has blocked Puppeteer. this is what chatgpt tells me
So youâre using both the main.js and m3u I provided?
Still seems to be loading it fine for me, not sure what chrome version I have.
Yes correct. I'll have another go tomorrow at it. Does the m3u need to be loaded into the channels dvr app or can would another IPTV client like tivimate be able to access the channels from within the m3u?
Also, with the cc4c source, would it run ok on a nas or does it have to be installed on say a workstation/laptop/desktop that has access to the Google chrome browser?
Iâm honestly not too sure, I think the code seems to point to common installation paths of chrome. So I assume whatever machine youâre using needs to have chrome installed.
And Iâm not too sure about tivimate. Due to the chrome:// links in the m3u, im not sure what it would be compatible with.
Possibly both these questions could be answered on the main CC4C thread.
If you want it in tivimate you could always bring it into channelsdvr and then export the m3u. Can also bring some good guide data across from channels that way.
thanks for sending me the info on the cc4c blank page issue. I've got an older version of chrome which I'll install and retest and see if that helps.
ok, so update on my side. have been able to get a desktop and laptop to have the m3u launch chrome and then the stream from kayo does start playing. maybe a really dumb/noob question from me but i was assuming that this method for paying through channels dvr was so that the stream from kayo would actually end uo playing in channels dvr and not a chrome session. is this by design? so in essence the kayo stream does load in chrome but stays in chrome and does not end up in the channels dvr session when the channel i pressed.
So the m3u should go in your channels live tv sources now and then when you click on it on your device it should capture the video thatâs in chrome and stream it to your device.
Yes it will play on your desktop but thatâs only so it can capture it. Should be able to use your computer as normal with it in the background too.
1 Like
yeah cool thanks. so for me for now, it looks like the only thing that its not doing is capturing the playing stream in chrome and sending it to channels on my device. ill keep working on it - thanks mate
Finally got this working as designed. I'm unsure if I should be posting this next bit but the root cause of all my issues since trying to test this has been using the github instructions of "bun main.js". Using bun to start the main.js code pretty much rendered everything to be seriously unstable. When using "node main.js" (with node js being installed locally as well) the code works perfectly on windows.
Hey all,
Made some changes to make tuning more reliable, fullscreen more stable and help deal with concurrent streams, in particular changing channel when all streams are being used.
Here is the compiled files - let me know if you want to see the full code (vibe coded by chatgpt).
https://drive.google.com/drive/folders/1tYpZCB7Fd2FnaY2QaV86n8ScZAhoL3D8?usp=sharing
I recommend setting Original Quality playback to 'Stream' in order to get channels to accept a channel change while 2/2 tuners are being used.
Please give me any feedback.
EDIT: corrected a small error that could happen on first tune, uploaded the new versions to the same folder
Edit2: The first tune failing may be due your computers resolution, I will do some investigating and try come up with a one size fits all solution.
Edit3: Changed to a chrome scale tune instead of a scroll tune - getting more reliable and also quicker tunes. Uploaded to google drive