I just noticed you did your speed test while on your WiFi Likely you have far less bandwidth. Could you speed test on cell connection
It's crazy, stopped working again. I'm getting that timeout error
Will it play changing cellular to 8MB. Leaving delivery where it is. If so I’d leave it at 8 so it can use adaptive bit rate
No, just spinning again. Hopefully it'll connect if I just leave it
It just worked after about a minute. but was getting errors prior to that.
How about another screenshot of the latest logs
oops accidentally attached another note from desktop. please ignore
Does it matter if the app is on two phones?
Nothing really sticks out on the server side in the logs to me. I do know it’s not 2am tomorrow in Kansas City. So your server time click is wrong but I wouldn’t think that would cause this. What is your server running on?
No
Etc/UTC
Should i save it to something in the CST zone?
I don’t think it matters. I have mine to central so it’s easier to look at logs. I just tested my kc fox 4 at 8MB and it loads in 6sec.
2023/08/17 21:18:14.958369 [HLS] ffmpeg: ch4.1-dANY-b3e016ba56c7-1-hevc-aac-copy--7232-384-720-6-0--hardware-false-false-0.01-0: [hls @ 0x92c3ac0] Stream HEVC is not hvc1, you should use tag:v hvc1 to set it.
2023/08/17 21:18:34.160342 [HLS] Stopping transcoder session ch4.1-dANY-b3e016ba56c7 (out: 22.067911s, finished: false, first_seq: 1, last_seq: 21)
2023/08/17 21:18:34.167434 [ENC] Stopped encoder for ch4.1 in /home/rice/DVR/Streaming/ch4.1-dANY-b3e016ba56c7-2436431808/encoder-1-1059132197 after encoding 1 to 19
2023/08/17 21:18:34.177184 [TNR] Closed connection to 10804B89/2 for ch4.1 WDAF-DT
2023/08/17 21:18:34.178291 [SNR] Statistics for ch4.1 WDAF-DT: ss=100% snq=100% seq=100% bps=9424610,4484928-13937568 pps=807,384-1193
2023/08/17 21:18:34.178302 [SNR] Buffer statistics for ch4.1 WDAF-DT: buf=0% drop=0%
I would change deinterlacer to hardware and If it doesn’t improve I would submit diagnostics from the phone app from a cell connection and post back here that you submitted
1 Like
I guess it was set to hardware. I changed it to software and it's working again. Slow to load and have some buffering.
I meant on the server side. Your logs show your deinterlacer is on blend
1 Like
I appreciate all your help. Think I'll just leave it set on software. It seems to be working pretty good.
You should set your server OS/device to the correct timezone, then your Channels DVR server web UI will display the correct timezone. If running in a container, the timezone is set with an environment variable.
1 Like
I am using a Pi Hole as my DNS and do not have any problems except it blocked Fubo one time.