I haven't used freestream in a while but I didn't have that issue when using it.
I was only using it to get Zona TUDN but Samsung+ has Zona TUDN already so I could add the m3u from that and not use CC4C for that
Have been running CC4C and my DVR Server off a dedicated Win 10 (tiny 10 image 48gb ram I5 6 core only on board graphics) using the basic NBC login since that's all i have access to. System runs fast etc except still get the NBC freeze hicup etc
Today i moved all my chrome cache to a ram drive and added chrome to the graphics settings "high performance" mode and disabled the paging file 48gb ram should qualify as not needing a paging file. Well system seems much better i can swing to diff NBC stations and they start playing in seconds. stuttering and freezing have gone way down too.
Sunday Night Football will be the big test.
so I have the docker image loaded and the tuning web page opens in the viewer, but how do I access the page to complete the login?
I tried the "x.x.x.x:5589/debug?url=...." and it opened, but it did not respond to any clicks or typing. I could see in the docker log window it was accepting the movements, but still nothing happened. I also tried to open in VNC on port 5900 but it would not connect. I turned off the accelerate hardware feature also to use YTTV.
any ideas?
Just to clarify, did you follow the directions for the Portainer Stack method and not the Docker Command Line method?
Hello,
I've been trying to run Chrome Capture on a Raspberry Pi. So far, I've had limited success, as running it from source doesn't seem to work well as chromium seems to struggle with the DRM. Any suggestions? Should I try a docker method? If so, do I need any special types of containers that are compatible with my Raspberry Pi's architecture?
Thanks!
I've been testing this for a few weeks now and so glad we have options to get around Drm'd issues. I've been using a new Ryzen powered Synology NAS initially, with so many Hulu issues. I switched to a stand alone Win10 pc for the both DVR and CC4 for the last week for testing and that solved that - Hulu added perfectly, not using the NAS for anything but the media dvr storage now. Much more responsive - plus Hulu started working after a month of trying get it on the NAS.
Currently using a decent Win10 pc running both DVR & Chrome Capture. I use both Fubo & Hulu as main sources, and capturing channels like NBC, USA, NFL etc... I get a little video stuttering the sessions that are being used.
I've order one the Beelink Ryzen mini's to handle to the capturing. I've seen a few suggestions that running in a Portainer is getting better results than in Windows? Also, is it better to separate the DVR to a separate device as well? Like some feedback on the best setup moving forward....
1 Like
For NBC are we still getting freezing after 2 hrs. ? I can add a script to reload it so it can keep going
Thanks to all who built and are continually improving this. I finally was able to get a new computer to dedicate to this and, after installing, it mostly works, I am having issues.
Core I7-10700T Windows 11 PC with 32 GB of ram and NVME drive. CPU/memory usage is under 30%.
When I start watching a show, the stream might run fine for a minute on my android client and then gets worse and worse until it freezes. Same thing is observed in the Chrome window on the PC.
Any suggestions on how to troubleshoot this? I used the simplified install method referenced above (awesome instructions by the way).
Had the same issue with a dedicated machine on windows. Docker install works MUCH better. If that is a machine that you are dedicating to this, i would put Ubuntu Server on it and install docker. Then install portainer and follow the instructions. Plus you will have thw ability to run other docker containers as well...
I need to make a guide to make it easier.
" i would put Ubuntu Server on it and install docker. Then install portainer and follow the instructions. "
Thanks @slampman for the idea. This machine also runs my Christmas and Halloween light shows(minimal resources), so I need to keep it on Windows, I do have Docker running for Pluto and Frndly, so perhaps Docker is still an option?
"I need to make a guide to make it easier."
Actually, the simplified guide at post 130 was fantastic and worked well.
I've followed all the troubleshooting here that seemed relevant, and I had no issues installing, adding channels, populating the Guide, or watching - just some performance issues (garbled recordings and the Chrome window freezing), so just hoping that some more knowledgeable folks can share some performance optimizations to try.
I'm using a very low powered laptop for this (i3-2330m) with no dedicated graphics card. I have this running on Linux Mint with the Portainer method and CPU usage seems to hover around 70% with some significant stuttering for a single stream (all I'll ever need). I'm using this to record hockey so the stuttering is a real downer.
Any tips on how to change the Portainer stack or main.js file in order to minimize the stuttering? I've been playing around with it changing the bitrates from the default settings, but my tinkering only seems to have made it worse.
1 Like
I think I'm having similar issues as @hofs1
I can get the node to load when I launch it manually using PowerShell, but can't get it to autolaunch using the ps1 file I created. If I enter the text in the PowerShell directly, node.exe appears as expected in my Task Manager. Then I End Task and try again by right-clicking on the ps1 file in Windows and select Run with PowerShell. A box briefly opens and closes, but node.exe never appears. What am I missing here?
Where in the main.js file do you make this change to modify the 8mbit to 5.65mbit?
Is it here? Would I change the 8000000 to 5650000?
const stream = await getStream(page, {
video: true,
audio: true,
videoBitsPerSecond: 8000000,
audioBitsPerSecond: 192000,
mimeType: 'video/webm;codecs=H264',
videoConstraints: {
mandatory: {
minWidth: viewport.width,
minHeight: viewport.height,
maxWidth: viewport.width,
maxHeight: viewport.height,
minFrameRate: 60,
@augie0041, It's probably your Powershell security settings ("Execution Policy"). You can modify it for manual testing if you want...
However, you'll notice in the directions above, I specifically say to set up Task Scheduler to run:
That command overrides whatever your security settings are, so I'd go ahead and just skip the test you are trying to do as this is doing the same thing anyway. Otherwise, you could do a manual run with the same commands if you still want to test it outside of Task Scheduler.
Thanks for this helpful reply. I was following your instructions on the above post and couldn't get the Task Scheduler to work, so I was testing the ps1 file directly to troubleshoot. But no matter what I do, I can't get it to work. I see the error The system cannot find the file specified. (0x800700002) but I've double-checked my file paths and file names... can't really figure out what I'm missing here.
Maybe change folder and file names to something shorter.
I realize it shouldn’t matter but I hate long folder/filenames.
I’m old school when they all had to be 8 characters or less.
1 Like
Thanks everyone, I finally figured it out. I wasn't following the Task Scheduler tasks properly. I was missing entering the word "powershell" in the Program/script area and then entering the -ExecutionPolicy Bypass -File "C:\chrome-capture\cc4c-node\chrome-capture-for-channels-win-x64.ps1" in the arguments area.
1 Like
I previously tried the manual, Docker version of CC4C but the difficulty in entering credentials made me move to trying Windows in a VM. That works but stutters some. I'm still messing with trying to pass through a GPU to Windows and/or a LXC running Linux but decided to give the new Docker via Portainer method a try.
I'm beginning to think I'm cursed when it comes to CC4C because even the Portainer version isn't working for me. There seems to be a problem with opening the X session but I'm stumped as to why. I set the VIDEO, AUDIO and TZ environment variables. Is there some extra configuration that is needed?
Here's the log from my most recent attempt to captured NBC.
#@ and then starting x11vnc via: @#
#@ @#
#@ x11vnc -rfbauth /path/to/passfile @#
#@ @#
#@ an existing ~/.vnc/passwd file from another VNC @#
#@ application will work fine too. @#
#@ @#
#@ You can also use the -passwdfile or -passwd options. @#
#@ (note -passwd is unsafe if local users are not trusted) @#
#@ @#
#@ Make sure any -rfbauth and -passwdfile password files @#
#@ cannot be read by untrusted users. @#
#@ @#
#@ Use x11vnc -usepw to automatically use your @#
#@ ~/.vnc/passwd or ~/.vnc/passwdfile password files. @#
#@ (and prompt you to create ~/.vnc/passwd if neither @#
#@ file exists.) Under -usepw, x11vnc will exit if it @#
#@ cannot find a password to use. @#
#@ @#
#@ @#
#@ Even with a password, the subsequent VNC traffic is @#
#@ sent in the clear. Consider tunnelling via ssh(1): @#
#@ @#
#@ http://www.karlrunge.com/x11vnc/#tunnelling @#
#@ @#
#@ Or using the x11vnc SSL options: -ssl and -stunnel @#
#@ @#
#@ Please Read the documentation for more info about @#
#@ passwords, security, and encryption. @#
#@ @#
#@ http://www.karlrunge.com/x11vnc/faq.html#faq-passwd @#
#@ @#
#@ To disable this warning use the -nopw option, or put @#
#@ 'nopw' on a line in your ~/.x11vncrc file. @#
#@ @#
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
###############################################################
24/10/2023 14:50:15 x11vnc version: 0.9.16 lastmod: 2019-01-05 pid: 9
24/10/2023 14:50:15 XOpenDisplay(":99") failed.
24/10/2023 14:50:15 Trying again with XAUTHLOCALHOSTNAME=localhost ...
24/10/2023 14:50:15 ***************************************
24/10/2023 14:50:15 *** XOpenDisplay failed (:99)
*** x11vnc was unable to open the X DISPLAY: ":99", it cannot continue.
*** There may be "Xlib:" error messages above with details about the failure.
Some tips and guidelines:
** An X server (the one you wish to view) must be running before x11vnc is
started: x11vnc does not start the X server. (however, see the -create
option if that is what you really want).
** You must use -display , -OR- set and export your $DISPLAY
environment variable to refer to the display of the desired X server.
- Usually the display is simply ":0" (in fact x11vnc uses this if you forget
to specify it), but in some multi-user situations it could be ":1", ":2",
or even ":137". Ask your administrator or a guru if you are having
difficulty determining what your X DISPLAY is.
** Next, you need to have sufficient permissions (Xauthority)
to connect to the X DISPLAY. Here are some Tips:
- Often, you just need to run x11vnc as the user logged into the X session.
So make sure to be that user when you type x11vnc.
- Being root is usually not enough because the incorrect MIT-MAGIC-COOKIE
file may be accessed. The cookie file contains the secret key that
allows x11vnc to connect to the desired X DISPLAY.
- You can explicitly indicate which MIT-MAGIC-COOKIE file should be used
by the -auth option, e.g.:
x11vnc -auth /home/someuser/.Xauthority -display :0
x11vnc -auth /tmp/.gdmzndVlR -display :0
you must have read permission for the auth file.
See also '-auth guess' and '-findauth' discussed below.
** If NO ONE is logged into an X session yet, but there is a greeter login
program like "gdm", "kdm", "xdm", or "dtlogin" running, you will need
to find and use the raw display manager MIT-MAGIC-COOKIE file.
Some examples for various display managers:
gdm: -auth /var/gdm/:0.Xauth
-auth /var/lib/gdm/:0.Xauth
kdm: -auth /var/lib/kdm/A:0-crWk72
-auth /var/run/xauth/A:0-crWk72
xdm: -auth /var/lib/xdm/authdir/authfiles/A:0-XQvaJk
dtlogin: -auth /var/dt/A:0-UgaaXa
Sometimes the command "ps wwwwaux | grep auth" can reveal the file location.
Starting with x11vnc 0.9.9 you can have it try to guess by using:
-auth guess
(see also the x11vnc -findauth option.)
Only root will have read permission for the file, and so x11vnc must be run
as root (or copy it). The random characters in the filenames will of course
change and the directory the cookie file resides in is system dependent.
See also: http://www.karlrunge.com/x11vnc/faq.html