Chrome Capture for Channels

Thanks @sheepy, I'll try a remux as well to see if that clears up the audio. I used Spectrum as the source for this recording.

1 Like

FYI, when I used ffmpeg, I also converted the audio to aac.

Well thanks to @turtletank I started re-looking at Philo using the URLs and noticed that the feeds from Philo run at a significantly lower rate than YTTV or NBC and Philo feeds were hard to view.

NBC Feed:
Watching ch1465 from AppleTV (Remux Running at 1mbps: 20s @ 0.93x (40.90fps)): buf=0% drop=0%

YTTV Feeds:
Watching ch1465.01 from AppleTV (Remux Running at 917kbps: 16s @ 1.18x (78.86fps)): buf=0% drop=0%
Watching ch1493.01 from AppleTV (Remux Running at 903kbps: 12s @ 1.22x (81.22fps)): buf=0% drop=0%
Watching ch1493.01 from Web (Transcoder Running at 800kbps: 9s @ 1.21x (56.59fps)): buf=0% drop=0%

Philo Feed:
Watching ch1627 from AppleTV (Transcoder Running at 310kbps: 9s @ 0.74x (35.16fps)): buf=0% drop=0%
Watching ch1493 from AppleTV (Transcoder Running at 207kbps: 29s @ 0.96x (32.55fps)): buf=0% drop=0%
Watching ch1493 from Web (Transcoder Running at 315kbps: 23s @ 1.01x (28.45fps)): buf=0% drop=0%

CC4C and CDVR are both running on the same Windows 11 box so any thoughts or knobs that can be used to improve the performance of the Philo feeds?

Over the last few days this was working very well for me. Chrome updated and now it will not work. I can see the Chrome video capture page open, but then it closes and I get an error message on the Channels client.

The source is on a Mac and I am using chrome-capture-for-channels-macos-x64. After the error message on the client appears, it shows a problem with a "flag" but the page will not stay up long enough for me to jot it down. On terminal I get this message:

[2023/07/11 17:22:58.465] Chrome Capture server listening on port 5589
[2023/07/11 17:23:13.131] streaming https://tv.youtube.com/watch/toLh6iOl_Zk
node:internal/process/promises:288
triggerUncaughtException(err, true /* fromPromise */);
^

[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "undefined".] {
code: 'ERR_UNHANDLED_REJECTION'
}

Node.js v18.5.0
logout

Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]

Appreciate any help on how to fix the flag issue. Thanks!

@tmm1 has anyone found a solution to getting all the keystrokes necessary ("." by example) to pass through to solve authentication prompts when using the docker CC4C (running on a remote, headless, CLI only server)?

I’m also wondering the same thing…

It's nice to be able to record USA again. Thanks to all the people getting this to work! I appreciate it!

@tmm1 BETA feedback. Using chrome-capture-for-channels-win-x64.exe I have been getting occasional CC4C crashes when changing channels that I thought were random. However, I can now reproduce these crashes and relate them to specific circumstances.

-crashes occur only when changing from one CC4C channel to another CC4C channel. (I am using primarily YTTV with CC4C)

-crashes do NOT occur when changing from a CC4C channel to a non-CC4C channel

-crashes occur only when changing channels using the quick guide, last channel (>|| double click), and channel surfing with CH+ CH-. (in these cases the CC4C stream is NOT stopped prior to the new channel being selected)

-crashes do NOT occur when changing channels using the grid guide with no PIP (In this case the CC4C stream is, of course, stopped prior to the new channel being selected)

I hope this is helpful in making Chrome-Capture-for-Channels more stable. I really love this feature.

2 Likes

Version of windows and Chrome?

I don't know if you have already resolved your issue, but thought I would comment on what I am seeing different on my end to see if there is something to be learned and invite others to weigh-in.
What stood out to me (see screenshot below), don't know why or what it means:

  1. Your stream Type shows "HLS Local" versus mine that is "Direct". Perhaps that is a Firestick thing?
  2. On the Video description yours has "hwdec: mediacodec" mine does not
  3. Bitrate. You are running at a whopping 15.1Mbps vs. mine at 7.8 Mbps. I have been playing around with increasing/decreasing this in the main.js to see what difference it might make. Not sure if that code is specifying a "sampling" rate for the capture or is the "ask" from the provider. I have raised that up to 12Mbps (12000000) and then see a bitrate on the screen as high as that specified. But never that high. In any case, wondering how/why it is at that level

Did you figure this out also for the E! East and West channel feeds and the USA East and West channels are get different guide data?

1 Like

Do you get different guide data for the East and West feeds of USA? If so, how did you do it?

I went in and to the source on CHannels and edited the lineup and assigned them USAHD and USAP for E I just assigned them WEST coast as I couldn't find an East coast as searching for E took FOREVER.

1 Like

That seemed to work for USA. At least I have two different guide informations now. I'm seeing the same thing about E with taking forever to pull up anything...

Are you getting two different guides for Bravo too?

Anyone getting this setup for a Bally Sports RSN? I'm trying to get it setup for Bally Sports Midwest source code should be...

I have Bally Sports Wisconsin set up and working well. When searching for the listings, I had to click on "check all listings" and then fully type "Bally Sports Wisconsin". When I only typed Bally, the options that came up didn't include Wisconsin, oddly.

Also added MLB and MTV Live, but I couldn't find any listings to match my time zone. So, I added those channels to a new source, and set that guide provider to my local Spectrum cable listings. Then was able to map MLB and MTV Live, which matched the Fubo schedule. I guess maybe I could have done that for all the other, CC4C channels, as well?

1 Like

But what did you enter into channels for the source code for Bally Sports Wisconsin?

Yes I am.

2 Likes

You need "EHD" for E East feed. I got it to pull up with E Entertainment East HD or something really close

1 Like

Mulliganman, sorry I misread your post. Thought you were looking for guide listings. You will need to find the url, for the source that you have for Bally Sports, and edit the stream argument. Here is mine for Fubo.

#EXTINF:-1 channel-id="{Bally Sports Wisconsin}",{Bally Sports Wisconsin}
chrome://192.168.0.170:5589/stream?url=https://www.fubo.tv/watch?channelId=16348

#EXTINF:-1 channel-id="{Bally Sports Wisconsin 2}",{Bally Sports Wisconsin 2}
chrome://192.168.0.170:5589/stream?url=https://www.fubo.tv/watch?channelId=74217

1 Like