Thank you
Depends on the event, but yes. Some of them are now using chunked mp4 files instead of regular ts segments and I'm not sure that Channels supports that yet
Is anyone getting 4k on the current St. John’s vs Butler game on espn+ FS1 ? It is in 4K on the TVE FS1. I’m only getting the 720. In the short time I’ve had the container going I’ve never seen it have a 4K feed.
Yes. 4K on both feeds.
I'm seeing 1080/60p for TVE and getting a Could not parse chunklist properly! error with the container.
EDIT: it was 1080/60p during the ads. It's 4k/30p during play.
Thank you, with that info I have relaunched the container adding max resolution uhd/hdr and 4k hdr is now working
The container documentation states default is uhd /sdr but I don’t think it is
If not set, UHD/SDR is the default.
Having a weird issue. I did a test recording for a 4k HDR game today but I have no episode art. Everything else works perfect. Any idea if I am doing something wrong? There isn't too much besides the standard stuff in the Custom channel setup
Not sure what I'm doing wrong, but I've got the channels coming in, but I can't get the guide data to populate. When I go into docker and look at the log, I can see the channels that have been created and the names/programs, but nothing ever populates in the channels guide; It just has generic 1hr blocks. I've attached some screen shots, any help would be appreciated.
Remove environment start_channel 300 and tell channels to ignore channel numbers from m3u and your guide will magically work.
I don't know if this has changed but I think you need ESPN_USER and ESPN_PASS for environmental so you can login.
They do state to look at your log file for the next information you need to do.
Anyone else having playback issue of the Fox Super Bowl Pregame stream on E+? I can't get the stream to play
Same here
Error: Invalid Playlist : SUBTITLES attribute MUST match the value of the GROUP-ID attribute of an EXT-X-MEDIA tag whose TYPE attribute is SUBTITLES.
at Object.INVALIDPLAYLIST (/app/node_modules/hls-parser/utils.js:44:9)
at /app/node_modules/hls-parser/parse.js:246:13
at Array.forEach (<anonymous>)
at matchTypes (/app/node_modules/hls-parser/parse.js:241:54)
at parseVariant (/app/node_modules/hls-parser/parse.js:281:3)
at parseMasterPlaylist (/app/node_modules/hls-parser/parse.js:327:23)
at semanticParse (/app/node_modules/hls-parser/parse.js:675:16)
at Object.parse (/app/node_modules/hls-parser/parse.js:702:20)
at new Playlist (/app/node_modules/dynamic-hls-proxy/dist/classes/playlist.js:42:26)
at Function.loadFromString (/app/node_modules/dynamic-hls-proxy/dist/classes/playlist.js:73:16)
Could not parse M3U8 properly!
yeah same thing here,, exact same message
Here's something else I notice. When I delete the tokens and whatnot, restart the container, i'm not being prompted to reauthorize but it's acting like I have....
The Fox Sports app itself logged in with the same information, plays just fine
I wonder if Fox made changes to support game related programming today. Remember, these shows are free to watch without a provider today.
Yeah it'd be about right for them to screw around with this stuff the day of the game. I was hoping to be able to record it in 4K today.
In addition, it looks like the login and logout of provider options have dissappeared from both the Fox and Fox sports apps.
That is by design they are diabling logins to provide free access to anybody.







