It's the field labeled Channel Selector

thanks, but didn't change anything.
Sorry if this has already been addressed in the forum. I looked through it and couldn't find a direct reference if this is possible, so any help is greatly appreciated.
I'm wondering if there's any support or workaround for NVIDIA gpus? Has anyone gotten PrismCast to use NVIDIA NVENC for hardware encoding? I have a 2080 super I'd like to use with PrismCast, nvidia-smi sees the card inside the container, but ENC stays at 0%. Is intel /dev/dri VAAPI the only acceleration path?
Yes, based on the fact that we're using a custom version of Xvfb from the selkies-project. If you can figure out how to make that work with your hardware, we should be able to add it.
Thanks for the confirmation and quick response!
I'll tinker around and see what I can come up with. Will keep you posted!
I'm not sure if selecting nbc.com or cnbc.com as the stream source (instead of stream.directv.com/guide) will work?
If it's fed through Chrome instead of a direct feed to Channels DVR, it might work.
I tried changing the stream source to cnbc.com and it wouldn't make a difference. The channel would still open in Directv.
I did a lot of work this morning, switching from docker to native windows installation and back. I have Prismcast mostly working with more really strange behavior. Now, instead of every Prismcast channel tuning to MS NOW, Prismcast will replace the TVE channels I have with Prismcast's (weird, right?) So what I've done is disabled those channels in Prismcast and the TVE channels return to my guide. Now Prismcast channels with Directv as stream source will tune correctly.
Is your installation Windows, Mac, Linux? Using Docker? Which Chrome version?
Running it on a M4 Mac Mini.
Everything is up to date (using brew to install/manage all but Chrome)
Chrome v150.0.7871.47
Thanks. My initial install was on an M1 Mac. It worked but struggled. Very slow.
An amd64 container on an arm64 Mac? -- that's not recommended for anything that requires more than modest processing power.
He ( @rayellio77 ) "had" it originally on an M1 Mac running natively.
He's been talking about moving it to a new Windows PC which sounds like what he did this morning.
Not sure if docker on Windows is going to be more problematic than just running it on Windows.
My Beelink N100 mini PC runs windows 11 and I run the Windows version Channels DVR on it as well as SLM, Plex and my Macrium Sitemanager. I looked at Windows Docker and it sounded like a cluge so I enabled Hyper-V and Installed Ubuntu Server as a VM. Then Docker, Portainer, FastChannels, and Uptime Kuma. This is a nice clean way to run Docker. It's amazing how little CPU the system uses with the only time I see high CPU is during commercial skipping, Windows Update and Virus scans and even then everything is responsive.
I started playing with this, and when I click on the Add Channel nothing happens. Any idea why that would be?
Any way to increase the browser timeout Im trying to add a custom channel https://www.newsmaxtv.com using my tv provider login etc All that works BUT they seem to show a 15-30 second add before the stream starts so it seems to kick me out before it starts etc.Not a big deal as its NOT a high use channel for me yet BUT asking now
No.
Works for me using Brave, Edge and Firefox.
Is your PrismCast setup and working.
This is correct. I moved from the Mac a month or so ago to a Beelink EQi12. All was running fine until I foolishly let Windows update. Had to downgrade Chrome. Like I said, Prismcast is running fine albeit with strange behavior.
I've seen the same thing, local Fox has always been unreliable but I can't see why.
It was the browser version. Thanks!
I've seen the same thing, local Fox has always been unreliable but I can't see why.
Glad to hear I'm not the only one.
I even enabled PrismCast Debug logging (http://192.168.1.9:5589/debug) and still can't figure out why it selects the Fox News channel instead of my Local Fox at Fox One (https://www.fox.com/live/channels). I can see it selecting Fox News in Chrome when I try to play my Local Fox more than 50% of the time.
There's a setting for "idle timeout," but I don't know if it's the right one to adjust for your issue.