Introducing PrismCast: Browser-based Live TV Capture for Channels DVR and Plex

This is not a project I would recommend spinning-up from the command line. Docker Compose via Portainer is the way to go. Too easy to get things wrong, and to keep track of what you used. Just to give you an example, this would be about the equivalent docker run command:

docker run -d \
  --name prismcast \
  --hostname prismcast \
  --dns-search localdomain \
  --shm-size=2gb \
  --device /dev/dri:/dev/dri \
  -p 5589:5589 \
  -p 5900:5900 \
  -p 6080:6080 \
  -p 5004:5004 \
  -e PORT=5589 \
  -e VNC_PORT=5900 \
  -e NOVNC_PORT=6080 \
  -e HDHR_PORT=5004 \
  -e DISPLAY_NUM=99 \
  -e SCREEN_WIDTH=2560\
  -e SCREEN_HEIGHT=1440\
  -e SCREEN_DEPTH=24 \
  -e TZ=America/Chicago \
  -e LIBVA_DRIVER_NAME=iHD \
  --health-cmd='wget -q --spider http://localhost:5589/health || exit 1' \
  --health-interval=30s \
  --health-timeout=10s \
  --health-retries=3 \
  --health-start-period=30s \
  -v prismcast-data:/root/.prismcast \
  --restart unless-stopped \
  ghcr.io/hjdhjd/prismcast:latest

I'm running PrismCast natively on a headless Mac mini as well. I got a 4K HDMI dongle, which allows me to set a screen resolution of up to 3840x2160, however this still didn't seem to enable at least 1080P. I believe the developer said you have to have a display greater than 4K to enable 4K.. and with my dongle setting to 4K, remotely connecting to the tiny screen was more headache than it was worth, so I gave up.

A Mac doesn't need an HDMI dongle.
I run it natively on a M4 Mac Mini with Display set to 3840 X 2160.
I attached it to my 4K monitor to set it, then it runs headless, as I switch the monitor to my Windows PC.
I use Remote Ripple to connect to its screen sharing.

1 Like


I definitely don't get other display options running headless. Even after plugging in the dongle, setting to 4K and then removing it, I'm only presented with these options. Mac mini M4 on MacOS 26.5

Thanks, I do have portainer as well. Used a textpad file for the command line. So I kinda did the same thing as portainer ;-). I was just installing this for the first time and wanted to make sure most of it works before I buy a service I can try with it.

Personally, and this probably because I'm away from home base for half the year, but I find the GL.iNet Comet to be far superior to a dongle.

I set mine to a 2K resolution, which works great for PrismCast @ 1080p, and gives me a very robust way to access my Mac-Mini-M4 in a KVM fashion -- which is the closet thing to having a monitor and keyboard attached sitting locally:

PrismCast:

GlKVM browser tab:

Same Mac and OS as yours
M4 Mac Mini Tahoe v26.5

This is a screenshot from Remote Ripple with no display attached.
Appears it remembers the display I had attached when I set the resolution.

Anyone having issues with TBS/TNT/truTV authentication? I upgraded to the latest and noticed some of my channels had to be re-authenticated. The "Triple Ts" are all doing the same thing where the screen is washed out and when I try and click on signin, it's not registering the click so just stays in this persistent mode?

I did wait out the countdown clock but nothing changed in terms of the screen registering my clicks. All other channels authenticated fine.

I get all these with TVE and my provider creds, can you not get them that way?

Cant get any of these on TVW after latest pre-release via Optimum Had to set them up via PrismCast

1 Like

I can but like to have a working backup at all time.

Well I finally got around to trying this out. I went to setup my sling credentials and I ran into an issue getting to the Login screen. It just has the blue circle of death with no popup window. I am stump at the moment of how to fix this so I can setup the credentials. I have this setup in docker. I would guess I'm missing something obvious.

Here is the config file setting for Chrome.

image

image

I found this and it talks about VNC. But if I don't have a graphical interface. Is that possible?
image

I think I figured it out. I had to go to http://10.10.0.205:6080/ so I could get to the login for sling. Good lord new things :wink:

Hey all. I have this setup and works pretty good for the most part. The only time I run into issues is when a channel has a frame rate faster than 30 fps. I normally only loose a frame maybe 1 in every 5 to 10 seconds. But if the channel is outputting 60 fps I am losing 7 to 15 fps about every 5 seconds when using the GPU. If I change the container to remove the GPU as an option then I can get a pretty smooth 60 fps on average for those channels but at 33 percent cpu usage vs 8 percent with the gpu (using 720P High).

I am running a mini pc on debian 13 with a i9-12900hk processor. I know its using the GPU as intel-gpu-top is showing it working.

However went to the Capture Codecs screen everything is showed grayed out. I would have thought this would have not been grayed out if a GPU is present.

I checked the logs when starting a channel and it is stating its using h264 for the channel.
[2026/06/08 12:57:17.113 PM] [fs1-u4ow41] Streaming FS1: Sling TV, slingLive, FFmpeg [H264]. Tuned in 3.7s (direct).

Just trying to figure out if I am missing something to get the GPU to output a smoother experience when 60 fps is offered from Sling TV.

1 Like

I would think if Chrome is using GPU you should get HEVC/H.265

Are you running it in a container/LXC or bare metal?
Strange that HEVC is checked, but grayed out.

I get dropped frames too. See this post

When PrismCast uses screen capture (e.g. YTTV), Chrome's encoder produces the video. Chrome doesn't guarantee fixed frame timing

I am running Debian bare metal. I know its supposed to but the log provided shows its rendering with h.264. I expect there to be dropped frames due to it capturing. But it fluctuates from low 52s on average to upper 30s when using the GPU. Its enough to notice often when watching. If I remove the GPU from the docker (this line. --device /dev/dri:/dev/dri) then it uses my cpu at around 33% but it stays pretty consistent at 60 fps with dips maybe to 58. So it seems maybe the GPU isn't fast enough on this chip or maybe a kernel issue. Just trying to figure out if its more of a hardware limitation or if its something else. I am starting to lean toward it being a gpu limitation. I do have a desktop 12400f in storage. I was going to play around with it and see if it handles better than the mini pc that had a laptop chip in it. But still not sure why the h.265 doesn't seem to be respected.

Seems like a bug if the selection is grayed out.
You're supposed to be able to toggle HEVC on and off (personally, mine is off, but I can toggle it).
What does your .prismcast/config.json look like.

"streaming": {
  "captureCodecs": ["h264"],
  "qualityPreset": "1080p-high",
  "videoBitsPerSecond": 6000000
}

Here's what my log shows at startup
[2026/06/07 04:41:25.535 PM] Starting PrismCast v1.10.3 with configuration:
[2026/06/07 04:41:25.535 PM] Configuration file: /Users/chDVRuser/.prismcast/config.json
[2026/06/07 04:41:25.535 PM] Chrome profile: /Users/chDVRuser/.prismcast/chromedata
[2026/06/07 04:41:25.535 PM] Server port: 5589
[2026/06/07 04:41:25.535 PM] Quality preset: 1080p-high (1920×1080)
[2026/06/07 04:41:25.535 PM] Capture codecs: h264

1 Like

I am not sure if im looking in the right place.
I opened this config.json file. But I did not see the streaming section listed.

[2026/06/08 04:22:26.307 PM] Starting PrismCast v1.10.3 with configuration:
[2026/06/08 04:22:26.307 PM]   Configuration file: /root/.prismcast/config.json
[2026/06/08 04:22:26.307 PM]   Chrome profile: /root/.prismcast/chromedata
[2026/06/08 04:22:26.307 PM]   Server port: 5589
[2026/06/08 04:22:26.307 PM]   Quality preset: 720p-high (1280×720)
[2026/06/08 04:22:26.307 PM]   Capture codecs: h264, hevc
[2026/06/08 04:22:26.307 PM]   Video bitrate: 12000000
[2026/06/08 04:22:26.307 PM]   Max retries: 4
[2026/06/08 04:22:26.307 PM]   Max concurrent streams: 10
[2026/06/08 04:22:26.307 PM]   Circuit breaker threshold: 10 failures in 5 minutes
[2026/06/08 04:22:26.307 PM]   Chrome executable: /usr/local/bin/chrome-no-sandbox
[2026/06/08 04:22:26.307 PM]   HLS segment duration: 2s, max segments: 10
[2026/06/08 04:22:26.307 PM]   HDHomeRun emulation: disabled
[2026/06/08 04:22:26.330 PM] Using FFmpeg at: /usr/lib/node_modules/prismcast/node_modules/ffmpeg-for-homebridge/ffmpeg.
[2026/06/08 04:22:26.344 PM] Loaded 1170 channels.
[2026/06/08 04:22:26.345 PM] Loaded health state for 84 channels and 2 domains.
[2026/06/08 04:22:27.290 PM] Chrome ready: Chrome/148.0.7778.167 (GPU: Mesa Intel(R) Iris(R) Xe Graphics (ADL GT2)).
[2026/06/08 04:22:29.090 PM] Capture system verified successfully.
[2026/06/08 04:22:29.218 PM] CDP proxy listening at /cdp.
[2026/06/08 04:22:29.219 PM] PrismCast is now listening on 0.0.0.0:5589.

Also downloaded the backup file and didn't see a section in there which matched the config.json file too.

I thought you said you're running it bare metal?
Why are you looking in a docker volume?
Try looking here

Looks like it's configured for HEVC.

I tried but I don't see anything there which is why I went to the volume.

When I started up the container this is what I used from the website.

docker run -d \
  --name prismcast \
  --shm-size=4g \
  --device /dev/dri:/dev/dri \
  -p 5589:5589 -p 5900:5900 -p 6080:6080 -p 5004:5004 \
  -v prismcast-data:/root/.prismcast \
  -e SCREEN_WIDTH=2560 -e SCREEN_HEIGHT=1440 -e SCREEN_DEPTH=24 -e TZ=America/Chicago \
  ghcr.io/hjdhjd/prismcast:latest