Fox @ 4k HDR

I did it on my Windows MINIPC attached to my TV have no Clue about ATV4K.

Thanks. I'll try that.

Latest prerelease should let you access fox (without 4K). We're working on a hotfix for 4K support.

1 Like

Didn't work for me.
Still getting [ERR] Failed to start stream for ch6002: TVE: platform response: 403 Forbidden
Toggled Experimental TVE locals and lost Fox channel 6002.

Logs have been submitted as a267f711-dbca-410c-a203-c85542580dd0

Trying to individually rescan channel 6002 shows this error
InvalidAccessTokenKeyId: Invalid AccessToken Key Id (403)

The FOX Sports APP keeps changing 720 HD then Sometimes 1080i then 2160 Drove me nuts went to 112.1 ATSC 3.0 better sound and Steady Picture.

New prerelease should fix 4K feed

Might work if you didn't lose channel 6002.
I lost mine and a rescan still gets error InvalidAccessTokenKeyId: Invalid AccessToken Key Id (403)

Logs have been submitted as bad20181-ada0-4ffb-ac2d-32fbbc876aea

EOF warning.

@tmm1 me too. (eof)

@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?

Working on both servers, got ch 6002 back.

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