BETA: Chrome Capture for Channels

[Anvil_DVR]

Yes.
There was a Windows update yesterday as well.
Maybe that is what caused it.

[babsonnexus]

@witty_username

Do you know of a good tutorial that will let me decipher Github to add some of these TVE channels back?

I'd start with reading the directions

BETA: Chrome Capture for Channels

Simplified Installation Instructions (as of 2023-07-19 at 10:30am 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 basic…

[maddox]

Has anyone run into the issue of the aspect of the webpage being incorrect? When I first started using CC4C it worked fine, then it went narrow and I can't get it back to 1920x1080.

I'm using the docker container. I've deleted and recreated it, and can't get it back to wide. Has anyone run into this and resolved it?

[witty_username]

Reading the directions is always a good place to start hahaha - sometimes things can become overwhelming. I will try the simplified installation instructions. Thanks!

I guess my question for this (after reading) would be is there a way to permamently link a stream displayed on a browser to a specific channel? For example, can I link the NBC stream to a custom channel and be able to watch that on my TV without NBC open on my computer? Maybe along the lines of the VLC configuration your older post mentioned.

I'm trying this out now and hope I'm creating the correct pathways - will let you know how it goes. A few questions:

• Do you delete the { when creating the pathways? (I did not)
• I'm stuck at Stage 4 / adding the custom channels (I removed my local NBC identifier). It appears in the source list, but says 0 channels. Clicking on the + only allows me to search via zip code. I'm also using Edge instead of Chrome if this is an issue (and may switch to Brave on a new laptop)

[babsonnexus]

@witty_username

is there a way to permamently link a stream displayed on a browser to a specific channel?

It is a permanent link to a temporary browser session. This solution is the super upgraded version of what PC Stream for Channels did.

@witty_username

Do you delete the { when creating the pathways? (I did not)

Yes.

@witty_username

I'm stuck at Stage 4 / adding the custom channels (I removed my local NBC identifier). It appears in the source list, but says 0 channels.

I can see several ways you are not following the directions correctly. You need to follow them exactly as written and do not deviate:

• In your Text field, you completely skipped the beginning of the m3u, the part that says #EXTM3U. That is why it says you have 0 stations.
• Step 3 is for creating the stations, Step 4 is for mapping them to guide data after they are created. You are clicking on "Set Provider". Per directions, you need to select "Manage Lineup". But this will only work when have your source text m3u fixed.

[babsonnexus]

@maddox

I'm using the docker container.

What are you running your Docker on? Most people with Macs are saying they have to go more than 1920x1080 on their display settings, so it could be similar...

@babsonnexus

(8) Troubleshooting / Common Issues

• If you are seeing black bars border or cropped windowed video: Adjust your display settings to be at least 1920x1080 or install an HDMI Dummy Plug to do the same. On some Macs, it appears necessary to be more than 1920x1080. WARNING: on a Mac, higher resolutions takes slightly more memory consumption.

Or it could be just related to the Docker command line. This seems like it would help:

@bnhf

I spent some time yesterday on a Portainer-Stack (docker compose) to support VNC connections to a cc4channels container specifically to allow for easy entry of credentials:

@bnhf

version: '3.9'
services:
  chrome-capture-for-channels:
    image: fancybits/chrome-capture-for-channels
    container_name: cc4channels
    command:
      - sh 
      - -c 
      - |
        Xvfb :99 -screen 0 1920x1080x16 &
        x11vnc -display :99 &
        node main.js
    #devices:
    #  /dev/dri:/dev/dri 
    ports:
      - 5589:5589 # cc4channels proxy port
      - 5900:5900 # VNC port for entering credentials
    user: '0:0'
    environment:
      - TZ=US/Mountain # Set to your local timezone
    volumes:
      - /data/cc4channels:/home/chrome/.config # Map to desired storage location on the host (left side of ":")
    restart: unless-stopped

I haven't had a chance to fully document (with screen shots and whatnot) this solution yet, but will in the near future and add it to the directions.

[Ahwman]

It seems like development has stopped on this project as we haven’t seen any updates since last month…

[maddox]

@babsonnexus

What are you running your Docker on?

On a headless server.

[bweezy21]

so the black borders issue is definitely tied to the viewport sizing. setting the entire chrome window to 1920x1080 in the main.js is the issue. i'm not setup for dev now but need to take into account the tab row and the omnibox row when sizing the window to get a 16:9 aspect ratio. However, when resizing the viewport your also resize the video output (smaller window = compressed video)

additionally every now and then i get some weird audio interference, robotic sounding, after a few seconds of it the audio completely cuts out and then a minute or so later the audio will return.

windows server, ccwgtv client

[sheepy]

@babsonnexus, for sure the "manage lineup" is the easiest, but there is a way to map guide data using the "set provider" feature. I have two channels (outside the NBC group) that I could not find appropriate guide data for. So, I created a completely separate source, moved those channels there, and set the provider to my local Spectrum cable listings. I was then able to use that guide data for those channels. I was going to create a custom xmltv file for these channels, but stumbled onto this solution.

[gill]

Running into an issue where some Fubo channels don't like the capture. Anyone getting this on ABC affiliates?

[sheepy]

@gill Are you running an HDMI dongle that is not HDCP compliant?

[gill]

Works fine when this app isn't capturing it, so if it were a dongle it would error on my regular chrome profile. It's only particular channels it appears: Reddit - Dive into anything

[sheepy]

Interesting. What is your setup?

[Anvil_DVR]

Usually an HDCP issue.
Most dongles are not compliant.
I ran into the same thing.
Somewhere earlier in this topic I posted a link to dongles that are compliant.

[Anvil_DVR]

This project is dead in the water for me.
Chrome appears to no longer capture video.
Worked perfect for a week, now it just launches chrome, video is playing, channels sits waiting for the stream which never arrives.

At least ADB Tuner is working.

[sheepy]

@Anvil404 , so you have not been able to get CC4C working again? Very strange. No issues on my end, it's been working well for about a month, recording a baseball game from Bally's just about every day.

[Anvil_DVR]

No, it refuses to work.
It would seem something changed with a recent windows update.
I'm running Windows 11 Pro for Workstations. OS Build 22621.1992
I tried installing the development version, does the exact same thing.
Chrome launches, The channel starts playing just like you would expect.
ChannelsDVR just spins waiting for the stream which never arrives.

[sheepy]

I'm running Windows 11 Pro, 22621.1992. I see my Chrome has updated and is waiting to be relaunched, there's a baseball game recording, currently. Not sure if this is the current version of Chrome, or what it's going to update to? 114.0.5735.248

[hjd]

I ran into this issue as well…see my notes above:

BETA: Chrome Capture for Channels

I had issues until I had a greater width than 1920. I’m using a headless Mac mini though…with an HDMI dongle installed, I set it to 2560X1440. Works like a charm. Alternatively, you could edit the source to resize to 720p instead of 1080p. TL;DR: I believe, though I’d defer to the experts, your issue is that your width isn’t set to greater than 1920. Equal to 1920 won’t do the trick. Best of luck.

That was the solve that worked on a headless Mac mini.