Hardware Transcoding on Base Raspbian Image

sgruby · April 12, 2022, 10:46pm

I'm running Channels (latest server) on a Pi 4 and it runs well. I'm using a base Raspbian install (64 bit) and not the Channels image. If I turn on hardware transcoding, I get the following:

2022/04/12 15:25:05.771019 [HWE] Trying nvmpi: /home/pi/channels-dvr/2022.03.23.0209/ffmpeg-dl /home/pi/channels-dvr/2022.03.23.0209/ffmpeg-dl -hide_banner -nostats -loglevel warning -loglevel verbose -f lavfi -t 0.1 -i color=black:640x480 -f null -c:v h264_nvmpi -profile:v high -level 42 -b:v 400k -maxrate:v 600k -y /dev/null
/home/pi/channels-dvr/2022.03.23.0209/ffmpeg-dl: error while loading shared libraries: libnvmpi.so: cannot open shared object file: No such file or directory

It looks like the ffmpeg in chnannels-dvr already has the nvmpi encoder built in.

pi@dvr-internal:~/channels-dvr/latest $ ./ffmpeg -encoders | grep nv
 V..... h264_nvmpi           nvmpi H.264 encoder wrapper (codec h264)
 V..... hevc_nvmpi           nvmpi HEVC encoder wrapper (codec hevc)

I moved ffmpeg-dl and symlinked ffmpeg-dl to ffmpeg and the hardware transcoder seems to be working for live channels, but playing back recorded content in a browser gives me a green screen.

The log is showing:

2022/04/12 15:37:53.447233 [ENC] Encoder stopped for 10News at 5pm Sunday 2022-04-10-1700.mpg in /mnt/media/Channels/Streaming/file5609-ip10.0.1.62-4099321120/encoder-310-1380318048 after encoding 310 to 324
2022/04/12 15:37:53.448680 [ENC] Starting encoder for 10News at 5pm Sunday 2022-04-10-1700.mpg in /mnt/media/Channels/Streaming/file5609-ip10.0.1.62-4099321120/encoder-326-290827803 at 326 (347.587644) (encoder=h264_v4l2m2m, resolution=720, deinterlacer=linear, bitrate=1744, segment_size=0.01)
2022/04/12 15:37:53.463050 [HLS] ffmpeg: file5609-ip10.0.1.62:  [mpegts @ 0x2a011020] Dropped corrupted packet (stream = 1)
2022/04/12 15:37:53.463124 [HLS] ffmpeg: file5609-ip10.0.1.62:  [mpegts @ 0x2a011020] Dropped corrupted packet (stream = 2)
2022/04/12 15:37:53.759730 [HLS] ffmpeg: file5609-ip10.0.1.62:  [hls @ 0x2a039710] Non-monotonous DTS in output stream 0:0; previous: 31285891, current: 0; changing to 31285892. This may result in incorrect timestamps in the output file.
2022/04/12 15:37:54.558946 [HLS] ffmpeg: file5609-ip10.0.1.62:  [hls @ 0x2a039710] Non-monotonous DTS in output stream 0:0; previous: 31375981, current: 0; changing to 31375982. This may result in incorrect timestamps in the output file.
2022/04/12 15:37:55.220528 [HLS] ffmpeg: file5609-ip10.0.1.62:  [hls @ 0x2a039710] Non-monotonous DTS in output stream 0:0; previous: 31466071, current: 0; changing to 31466072. This may result in incorrect timestamps in the output file.
2022/04/12 15:37:55.776911 [HLS] ffmpeg: file5609-ip10.0.1.62:  [hls @ 0x2a039710] Non-monotonous DTS in output stream 0:0; previous: 31556161, current: 0; changing to 31556162. This may result in incorrect timestamps in the output file.

a) Any suggestions on what to install/change for the green image?
b) Can I install a package to get libnvmpi so that I don't have to muck with the install? If not, can the installer check to see if ffmpeg already has the encoder and just setup the symlink?

Thanks!

tmm1 · April 13, 2022, 12:33am

ffmpeg-dl is meant to fail. That version is for the jetson nano.

sgruby · April 13, 2022, 4:37am

Thanks! Transcoding works for live channels (when I removed my symlink), but still getting the green for recordings.

2022/04/12 21:35:34.824476 [ENC] Encoder stopped for LEGO Masters S01E01 Dream Park Theme Park 2020-02-05-2101.mpg in /mnt/media/Channels/Streaming/file2819-ip10.0.1.43-4095214785/encoder-161-68850967 after encoding 161 to 175
2022/04/12 21:35:34.825917 [ENC] Starting encoder for LEGO Masters S01E01 Dream Park Theme Park 2020-02-05-2101.mpg in /mnt/media/Channels/Streaming/file2819-ip10.0.1.43-4095214785/encoder-177-2750765008 at 177 (176.176000) (encoder=h264_v4l2m2m, resolution=720, deinterlacer=blend, bitrate=1744, segment_size=0.01)
2022/04/12 21:35:34.837321 [HLS] ffmpeg: file2819-ip10.0.1.43:  [mpegts @ 0x1495f020] Dropped corrupted packet (stream = 1)
2022/04/12 21:35:34.837411 [HLS] ffmpeg: file2819-ip10.0.1.43:  [mpegts @ 0x1495f020] Dropped corrupted packet (stream = 2)
2022/04/12 21:35:34.839663 [HLS] ffmpeg: file2819-ip10.0.1.43:  [mpegts @ 0x1495f020] Dropped corrupted packet (stream = 1)
2022/04/12 21:35:34.843186 [HLS] ffmpeg: file2819-ip10.0.1.43:      Last message repeated 1 times
2022/04/12 21:35:34.843268 [HLS] ffmpeg: file2819-ip10.0.1.43:  [mpegts @ 0x1495f020] Dropped corrupted packet (stream = 2)
2022/04/12 21:35:34.859160 [HLS] ffmpeg: file2819-ip10.0.1.43:  Error while decoding stream #0:2: Invalid data found when processing input
2022/04/12 21:35:34.859299 [HLS] ffmpeg: file2819-ip10.0.1.43:  Error while decoding stream #0:1: Invalid data found when processing input
2022/04/12 21:35:35.824310 [HLS] ffmpeg: file2819-ip10.0.1.43:  [hls @ 0x14982930] Non-monotonous DTS in output stream 0:0; previous: 15945713, current: 0; changing to 15945714. This may result in incorrect timestamps in the output file.
2022/04/12 21:35:36.317344 [HLS] ffmpeg: file2819-ip10.0.1.43:  [hls @ 0x14982930] Non-monotonous DTS in output stream 0:0; previous: 16035803, current: 0; changing to 16035804. This may result in incorrect timestamps in the output file.

Any suggestions?

Thanks!

tmm1 · April 15, 2022, 3:33pm

Probably has to do with the recording details. Could be interlacing or SD resolutions causing the issue.

sdust · April 15, 2022, 5:13pm

If you need to use transcoding you shouldn't be using RPi 4 . The hardware encoder really sucks. Do yourself a favor and buy something like Beelink GK Mini for about $200 and put Debian 11 on it.

sgruby · April 17, 2022, 3:35am

Thanks. I'll play around with the recordings and see which ones transcode.

sgruby · April 17, 2022, 3:37am

I had been running it on a Mac Mini, but decided to give it a try on a Pi. I rarely transcode and it runs great when not transcoding; software transcoding isn't awful for the little bit I use it, but if it supports hardware transcoding, why not use that?

sgruby · April 17, 2022, 6:06pm

I checked the "Old Transcoder" option and things are working much better. It appears to be using the hardware transcoder as the CPU load isn't that high. How long will the old transcoder option be around? I see that some of the ffmpeg flags are different for the old transcoder.

This seems to work for the apps both on my local network and via a VPN over cellular. It doesn't, however, seem to work with Safari on my LAN. It does work with Chrome on my LAN.

Video encodings are so much fun to get right (I've dealt with video encodings for years, but not on the level that the Channels team has.)

eric · April 17, 2022, 10:11pm

Can you describe in what way the behavior is better with the "Old Transcoder". It's very surprising you would see a difference in performance. It's actually using the same ffmpeg for both (and should be using basically the same parameters). The difference is in how we process the output from ffmpeg to make the Adaptive Bitrate functionality work.

sgruby · April 18, 2022, 2:07pm

Hi @Eric ,

With the old transcoder and hardware transcoder, the iPad client plays any recorded show or live program I throw at it. With the new transcoder, I get a green screen. The audio plays fine, just no video. This is on my LAN (same behavior using a VPN over cellular).

Here's the log from a live session with the new transcoder.

2022/04/18 07:05:20.698557 [TNR] Opened connection to 1080AC73/2 for ch10.1 KGTV-HD
2022/04/18 07:05:20.699848 [HLS] Starting live stream for channel 10.1 from 10.0.1.43 (bitrate=0)
2022/04/18 07:05:21.478271 [HLS] Probed live stream in 778.172939ms: mpeg2video 1280x720 progressive 4156651bps
2022/04/18 07:05:23.129862 [HLS] Session ch10.1-dANY-ip10.0.1.43 started in 2.756623054s
2022/04/18 07:05:23.138622 [ENC] Starting encoder for ch10.1 in /mnt/media/Channels/Streaming/ch10.1-dANY-ip10.0.1.43-481589250/encoder-1-1367552483 at 1 (1.430467) (encoder=h264_v4l2m2m, resolution=576, deinterlacer=blend, bitrate=808, segment_size=0.01)
2022/04/18 07:05:23.856214 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 200814, current: 0; changing to 200815. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:24.792982 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 262375, current: 0; changing to 262376. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:25.912183 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 352465, current: 0; changing to 352466. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:25.929700 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 355468, current: 0; changing to 355469. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:26.860916 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 445558, current: 0; changing to 445559. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:27.850179 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 535648, current: 0; changing to 535649. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:28.822634 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 625738, current: 0; changing to 625739. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:29.917935 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 714327, current: 0; changing to 714328. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:30.899338 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 804417, current: 0; changing to 804418. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:30.909335 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 805918, current: 0; changing to 805919. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:31.851319 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 896008, current: 0; changing to 896009. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:32.655686 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 986098, current: 0; changing to 986099. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:33.437489 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 1062675, current: 0; changing to 1062676. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:34.442781 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 1134747, current: 0; changing to 1134748. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:35.240493 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 1211323, current: 0; changing to 1211324. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:36.159158 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 1280392, current: 0; changing to 1280393. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:36.929196 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 1370482, current: 0; changing to 1370483. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:36.947894 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 1373485, current: 0; changing to 1373486. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:38.559309 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 1441053, current: 0; changing to 1441054. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:38.942536 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 1504116, current: 0; changing to 1504117. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:39.441844 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 1585197, current: 0; changing to 1585198. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:40.155414 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 1664776, current: 0; changing to 1664777. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:40.958291 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 1735347, current: 0; changing to 1735348. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:42.364181 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 1802914, current: 0; changing to 1802915. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:42.796520 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-1-h264-aac-copy--808-96-576-0-0--blend-false-false-0.01:  [hls @ 0x37cd3210] Non-monotonous DTS in output stream 0:0; previous: 1870482, current: 0; changing to 1870483. This may result in incorrect timestamps in the output file.
2022/04/18 07:05:43.247516 [HLS] Stopping transcoder session ch10.1-dANY-ip10.0.1.43 (out: 22.718411s, finished: false)
2022/04/18 07:05:43.266650 [ENC] Stopped encoder for ch10.1 in /mnt/media/Channels/Streaming/ch10.1-dANY-ip10.0.1.43-481589250/encoder-1-1367552483 after encoding 1 to 20
2022/04/18 07:05:43.267118 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-remux:  [mpegts @ 0x22b32dd0] Dropped corrupted packet (stream = 1)
2022/04/18 07:05:43.267192 [HLS] ffmpeg: ch10.1-dANY-ip10.0.1.43-remux:  [mpegts @ 0x22b32dd0] Dropped corrupted packet (stream = 2)
2022/04/18 07:05:43.272952 [TNR] Closed connection to 1080AC73/2 for ch10.1 KGTV-HD
2022/04/18 07:05:43.273060 [SNR] Statistics for ch10.1 KGTV-HD: ss=100% snq=100% seq=90%,0%-100% bps=5565483,0-7765152 pps=476,0-665

Here's a log for the new transcoder with a recording:

2022/04/18 07:06:44.216180 [ENC] Starting encoder for 10News at 5pm Sunday 2022-04-17-1700.mpg in /mnt/media/Channels/Streaming/file5635-ip10.0.1.43-2624342286/encoder-0-4117534692 at 0 (0.000000) (encoder=h264_v4l2m2m, resolution=576, deinterlacer=blend, bitrate=808, segment_size=0.01)
2022/04/18 07:06:44.230439 [HLS] ffmpeg: file5635-ip10.0.1.43:  [mpegts @ 0x25ad8060] Dropped corrupted packet (stream = 1)
2022/04/18 07:06:44.230525 [HLS] ffmpeg: file5635-ip10.0.1.43:  [mpegts @ 0x25ad8060] Dropped corrupted packet (stream = 2)
2022/04/18 07:06:44.999238 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 125499, current: 0; changing to 125500. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:45.579134 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 215589, current: 0; changing to 215590. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:45.647175 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 217090, current: 0; changing to 217091. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:46.128375 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 307180, current: 0; changing to 307181. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:46.651472 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 397270, current: 0; changing to 397271. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:46.651700 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 398772, current: 0; changing to 398773. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:47.049384 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 487360, current: 0; changing to 487361. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:47.489430 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 560934, current: 0; changing to 560935. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:47.962281 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 649522, current: 0; changing to 649523. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:48.448347 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 739612, current: 0; changing to 739613. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:48.448427 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 741114, current: 0; changing to 741115. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:48.942229 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 831204, current: 0; changing to 831205. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:48.942363 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 832705, current: 0; changing to 832706. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:49.578264 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 922795, current: 0; changing to 922796. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:49.578406 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 924297, current: 0; changing to 924298. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:49.788997 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 973846, current: 0; changing to 973847. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:50.040607 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 1015888, current: 0; changing to 1015889. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:50.040749 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 1017390, current: 0; changing to 1017391. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:50.642944 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 1107480, current: 0; changing to 1107481. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:50.659719 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 1110483, current: 0; changing to 1110484. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:50.974948 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 1187059, current: 0; changing to 1187060. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:51.413834 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 1262134, current: 0; changing to 1262135. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:51.906625 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 1352224, current: 0; changing to 1352225. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:51.958068 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 1353726, current: 0; changing to 1353727. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:52.302079 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 1424296, current: 0; changing to 1424297. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:52.645915 [HLS] ffmpeg: file5635-ip10.0.1.43:  [hls @ 0x25afab90] Non-monotonous DTS in output stream 0:0; previous: 1490362, current: 0; changing to 1490363. This may result in incorrect timestamps in the output file.
2022/04/18 07:06:53.133194 [ENC] Stopped encoder for 10News at 5pm Sunday 2022-04-17-1700.mpg in /mnt/media/Channels/Streaming/file5635-ip10.0.1.43-2624342286/encoder-0-4117534692 after encoding 0 to 11

Please let me know what additional information you need or what else you'd like me to try.

Thanks!

eric · April 18, 2022, 10:09pm

Could we get you to try to stream with both the old and new transcoder and then submit diagnostics from the app?

sgruby · April 19, 2022, 4:48am

Done!

sgruby · October 19, 2022, 2:54pm

Any update on this? Any chance the "Old Streaming System" can remain between restarts? I tried to watch a show yesterday when I wasn't home and forgot about this setting.

Thanks!

clknight · December 5, 2022, 5:05am

Wanted to +1 this. The only thing I would add is that viewing transcoded streams in browser is fine; it’s only on iOS clients that I get green-screen transcodes. Not a huge deal since I do most of my watching at home without transcoding but would still be nice if everything worked. Please let me know if logs or other info would be helpful. Thanks!

ChrisAndLaura · January 6, 2023, 6:49pm

+1 here too, same symptoms and same workaround by using the "Old Streaming System" option.

eric · January 6, 2023, 10:56pm

Are you using the Channels DVR image or something else?

We're trying to reproduce the issues using the Channels DVR image and are having trouble reproducing the issue.

tmm1 · January 7, 2023, 12:23am

We've isolated this issue to the 5.15 PI kernel upgrade and are looking for a fix.

tmm1 · January 7, 2023, 5:16pm

Please try this build:

enodev · January 8, 2023, 3:39am

After updating to v2023.01.07.1206, I still have to enable "Old Streaming System" for it to work on the iPhone Channels app using the hardware transcoder. Without Old Streaming System, the video stream never starts (it used to play audio with a green screen.) The software transcoder does work without enabling Old Streaming System.

I also get the same results using the Channels web viewer.

Pi 4 is running this kernel:

> uname -r
5.15.84-v8+

sgruby · January 8, 2023, 5:46am

My initial test using the web viewer seems to be working! ( 5.15.32-v8+). I'll try again tomorrow when I'm outside my home network over my VPN.

Thanks!