ChannelsDVR in Tesla

[rickpaquin]

I've been playing my video recordings in the web browser of my Tesla for years. During the past month it now will only play about a minute or so of a recorded program, and then stop.

Live programming, streaming from my antenna at home streams perfectly with no issues. It's only the recorded programs that stop playing after about a minute.

My recorded video's play fine on ALL other equipment, whether it be in a web browser or the app so I fail to see where there's anything wrong with my server. And since the live video runs continually without issues in the car's browser, I fail to see where it's a buffer or bandwidth issue. I'm stumped. None of my recordings will play more than a minute in the Tesla browser, but live video is fine. What could possibly be wrong?

[Shaggylive]

have you tried changing the Playback Quality, or Client Buffer?
channels does handle streaming recordings and hdhr differently.

[rickpaquin]

I did try increasing the client buffer, but that had no effect. Other services from my NAS stream fine. I haven’t changed anything such as quality or streaming rate but perhaps I’m hitting a browser limit of some sort. I’ll see if I can reduce the streaming quality and see what happens.

[Shaggylive]

I know starlink has been making changes to its throughput, perhaps they are throttling certain protocols, but not sure how cdvr would differ from others your using.
any difference h264 or h265?

[Rice]

I am seeing this as well. It’s very strange, on live content fps hovers around 60fps but recorded content runs up to 500fps plus. When the stream fails it still shows transcoding. So frustrating.

Live stream pic;

Recorded content stream:

Recorded content stream when it fails:

@maddox diagnostic log submitted under baeb161a-9ef0-4d88-8386-cfeb43dc8766

@Shaggylive

I know starlink has been making changes to its throughput, perhaps they are throttling certain protocols,

Teslas don’t use Starlink, they use regular cell tower data. Verizon I believe.

[Shaggylive]

@Rice

Teslas don’t use Starlink, they use regular cell tower data. Verizon I believe.

you know I didn't really think so, but wouldn't surprise me if changes they made for the birds were also made for the cars. just throwing stuff to see what sticks, until an expert can weight in

[maddox]

@Rice

It’s very strange, on live content fps hovers around 60fps but recorded content runs up to 500fps plus

you can't transcode live tv faster than...it happens. what you're seeing is completely normal.

[rickpaquin]

Rice seems to be duplicating my issue as well. Live TV streaming is fine. But for recorded video I also see streaming rates above 66 fps and after a minute or so it just stops.

Logically it would seem something changed with the browser, except I load Emby and stream video through that browser with no issue. I hope we can get ChannelsDVR working again. I don't like Emby. Tesla uses AT+T but since it streams Live TV with no issues, that would rule out the browser or internet throughput. Makes no sense.

[chDVRuser]

For testing purposes,
clear the DVR server streaming cache,

delete the video index for one of your recordings
Delete the recordings FILE# folder in your server Metadata directory

and try playing that recording.

You can always rebuild the video index for a recording.

[rickpaquin]

I cleared the cache and as to the video index. I'm recording new video's all them time. Doesn't matter what video I choose to playback, it's the same result, but only on the Tesla browser. Other browsers stream recorded video fine. And in the logs, it shows corruption.

2026/06/22 04:00:56.363004 [HLS] Starting transcoder for file24940-87eee5ebbecd at 9m39s from 195.252.231.69 (encoder=h264_vaapi, resolution=, deinterlacer=hardware, bitrate=4000)
2026/06/22 04:00:56.376915 [HLS] ffmpeg: file24940-87eee5ebbecd:  [mpegts @ 0xb8a7c40] Packet corrupt (stream = 1, dts = 8038547425), dropping it.
2026/06/22 04:00:56.376973 [HLS] ffmpeg: file24940-87eee5ebbecd:  [mpegts @ 0xb8a7c40] Packet corrupt (stream = 2, dts = 8038564705), dropping it.
2026/06/22 04:00:56.378690 [HLS] ffmpeg: file24940-87eee5ebbecd:  [mpegts @ 0xb8a7c40] Packet corrupt (stream = 2, dts = 8038564705), dropping it.
2026/06/22 04:00:56.378881 [HLS] ffmpeg: file24940-87eee5ebbecd:  [mpegts @ 0xb8a7c40] Packet corrupt (stream = 2, dts = 8038564705), dropping it.
2026/06/22 04:00:56.378962 [HLS] ffmpeg: file24940-87eee5ebbecd:  [mpegts @ 0xb8a7c40] Packet corrupt (stream = 2, dts = 8038564705), dropping it.
2026/06/22 04:00:57.870702 [HLS] Stopping transcoder for file24940-87eee5ebbecd after seek to 9m40s (out=408.666ms, finished=false)
2026/06/22 04:00:57.901254 [HLS] Starting transcoder for file24940-87eee5ebbecd at 9m40s from 195.252.231.69 (encoder=h264_vaapi, resolution=, deinterlacer=hardware, bitrate=4000)
2026/06/22 04:00:57.916139 [HLS] ffmpeg: file24940-87eee5ebbecd:  [mpegts @ 0xb920c40] Packet corrupt (stream = 1, dts = 8038547425), dropping it.
2026/06/22 04:00:57.916193 [HLS] ffmpeg: file24940-87eee5ebbecd:  [mpegts @ 0xb920c40] Packet corrupt (stream = 2, dts = 8038564705), dropping it.
2026/06/22 04:00:57.918147 [HLS] ffmpeg: file24940-87eee5ebbecd:  [mpegts @ 0xb920c40] Packet corrupt (stream = 2, dts = 8038564705), dropping it.
2026/06/22 04:00:57.918341 [HLS] ffmpeg: file24940-87eee5ebbecd:  [mpegts @ 0xb920c40] Packet corrupt (stream = 2, dts = 8038564705), dropping it.
2026/06/22 04:00:57.918423 [HLS] ffmpeg: file24940-87eee5ebbecd:  [mpegts @ 0xb920c40] Packet corrupt (stream = 2, dts = 8038564705), dropping it.
2026/06/22 04:00:58.090855 [HLS] Stopping transcoder session file24940-87eee5ebbecd (view: 9m40s, out: 1µs, finished: false)
2026/06/22 04:04:42.937162 [ENC] Starting encoder for CBS Evening News 2026-06-20-2329.mpg in /share/Multimedia/Channels DVR/Streaming/sessions/file24940-87eee5ebbecd-2377532593/encoder-501-1574192635 at 501 (574.959871) (encoder=h264_vaapi, codec=h264, acodec=aac, resolution=720, deinterlacer=hardware, bitrate=2744, segment_size=0.01)
2026/06/22 04:04:42.950972 [HLS] ffmpeg: file24940-87eee5ebbecd:  [mpegts @ 0xc199cc0] Packet corrupt (stream = 1, dts = 8038547425), dropping it.
2026/06/22 04:04:42.951041 [HLS] ffmpeg: file24940-87eee5ebbecd:  [mpegts @ 0xc199cc0] Packet corrupt (stream = 2, dts = 8038564705), dropping it.
2026/06/22 04:04:42.953110 [HLS] ffmpeg: file24940-87eee5ebbecd:  [mpegts @ 0xc199cc0] Packet corrupt (stream = 2, dts = 8038564705), dropping it.
2026/06/22 04:04:42.953305 [HLS] ffmpeg: file24940-87eee5ebbecd:  [mpegts @ 0xc199cc0] Packet corrupt (stream = 2, dts = 8038564705), dropping it.
2026/06/22 04:04:42.953390 [HLS] ffmpeg: file24940-87eee5ebbecd:  [mpegts @ 0xc199cc0] Packet corrupt (stream = 2, dts = 8038564705), dropping it.
2026/06/22 04:09:03.924505 [HLS] Stopping inactive session file24940-87eee5ebbecd
2026/06/22 04:09:03.947898 [ENC] Stopped encoder for CBS Evening News 2026-06-20-2329.mpg in /share/Multimedia/Channels DVR/Streaming/sessions/file24940-87eee5ebbecd-2377532593/encoder-501-1574192635 after encoding 501 to 974

[chDVRuser]

So you deleted the video index for recorded file 24940 Metadata/24940 after clearing the streaming cache and before trying to play the recording?

It looks like it's transcoding using adaptive bitrate (bitrate=4000 then bitrate=2744)

[rickpaquin]

Yes. I've actually been watching ChannelsDVR video's in the Tesla browser for years. I don't mess with the server settings at all. Pretty sure this happened after one of the Tesla update, but why do Emby recordings play? And I checked the Emby transcoding settings and it has no upper limit set. That seems to indicate throughput is fine and the browser can handle the higher streaming rate.