@tmm1 I submitted diags incase it helps you
Tried 2023.02.12.2353 on the server I haven't lost Fox 6002 on and same old error
[ERR] Failed to start stream for ch6002: TVE: platform response: 403 Forbidden
Logs have been submitted as 3fd8e8e1-02a5-4f50-93db-5b2bb65fdefc
1 Like
Non 4k should work now with new build v2023.02.13.0011
EOF Issue for 4k confirmed on linux dvrs. Mac DVRs working.
1 Like
Yep working here on my Mac Mini. Strong work. Thanks!
Can anyone confirm on Windows?
Works on Mac and ATV now. Audio only two channels but picture is 4k around 15mb.
1 Like
Same here. 4k picture, 2 channel audio on my ATV 4k and Windows 10 server. Well done everyone.
1 Like
This is just for info, on Sinology, 4k isn't working with the following error. Non 4k works. This doesn't impact me. But it may impact others.
2023/02/12 19:36:51.634320 [TNR] Opened connection to TVE-ATTOTT for ch6002 WTTG
2023/02/12 19:36:51.653203 [HLS] ffmpeg: tve-ffmpeg-fox: https protocol not found, recompile FFmpeg with openssl, gnutls or securetransport enabled.
2023/02/12 19:36:51.653255 [HLS] ffmpeg: tve-ffmpeg-fox: https://foxvideo.global.ssl.fastly.net/haw/mcl-haw-uhd-a/index.m3u8?ad_env=1&cdn=fa&hdnts=exp%3D1676248706~acl%3D%2F*~hmac%3D63c3b98f2f983cf1ef2dd1b889ecd972fa1e2023aeca3e697ed85f977c3e994c: Protocol not found
2023/02/12 19:36:51.653267 [HLS] ffmpeg: tve-ffmpeg-fox: Did you mean file:https://foxvideo.global.ssl.fastly.net/haw/mcl-haw-uhd-a/index.m3u8?ad_env=1&cdn=fa&hdnts=exp%3D1676248706~acl%3D%2F*~hmac%3D63c3b98f2f983cf1ef2dd1b889ecd972fa1e2023aeca3e697ed85f977c3e994c?
2023/02/12 19:36:51.657153 [ERR] Error during stream TVE-ATTOTT ch6002 WTTG: exit status 1
Same here on Synology with 4k. Non-4k working fine.
Log is filled with these
2023/02/12 16:38:04.734892 [HLS] ffmpeg: tve-ffmpeg-fox: [tcp @ 0x8d789c0] Failed to resolve hostname foxvideo.global.ssl.fastly.net: Name or service not known
2023/02/12 16:38:04.735136 [HLS] ffmpeg: tve-ffmpeg-fox: http://foxvideo.global.ssl.fastly.net/haw/mcl-haw-uhd-a/index.m3u8?ad_env=1&cdn=fa&hdnts=exp%3D1676248747~acl%3D%2F*~hmac%3D953565c08d9669506aa97cefbde3a209d09e1fabf364fd374dd4d20b0e368f99: Input/output error
2023/02/12 16:38:04.738961 [ERR] Error during stream TVE-Comcast_SSO ch6002 KTXL: exit status 1
v2023.02.13.0025
Logs have been submitted as f6fd3163-6bcb-4d62-8fd3-b166c346e0f9
@tmm1 I just tried your new build, still get EOF.
2023/02/12 19:44:00.030854 [ERR] Error during stream TVE-Cox ch6002 WVBT: signal: segmentation fault (core dumped)
2023/02/12 19:44:00.030871 [TNR] Closed connection to TVE-Cox for ch6002 WVBT
1 Like
Sorry no easy fix for 4K feed on Linux DVRs
1 Like
I remotely updated the server on Windows and it seems to be working with the 4k box checked! Not sure how to test to see if it is recording in 4k from my tablet away from home. Great to see that it is actually recording regardless.
Edit.
I was able to get the first 90 minutes of the game recorded in 720p. It looks like it is working in 4k from the two minute warning onwards.
Great Job Developers working great on my Windows Server.
I would have loved to try it too but I lost my Fox channel after one of the updates earlier today. It is no longer in my DirecTV lineup. Once my DVR is idle, I will upgrade to the latest and then try to get it back by unchecking the local channels option and enable it again.
Anyway, it seems that you got Fox TVE 4K working in Channels. Fantastic! 
1 Like
Depends on the source too. A football game vs a concert vs a movie ect. Upmixing two channel for crowd noise isn't that much of a trade off. I would choose the HDR for football for sure.
1 Like
I take it that this "hack" for the Super Bowl, won't carry over to any other Fox "4K" production? It will take the Docker EPlusTV method moving forward? Is that due to the Super Bowl being open to everyone with no need for credentials?
1 Like
Free access vs 4K feeds are separate concerns. Work to integrate 4K support is ongoing.
7 Likes
Does this address the Linux issue for the future or was that not an fmp4 problem?