Timestamps and DTS warnings (ffmpeg)

[brandousov]

Which version are you using?

v0.14.0

Enhancement request

Our rtsp-simple-server only proxies private rtsp streams via hash-url's to mobile clients apps. Original RTSP streams are from Dahua and Hikvision IP cams.. the output of ffmpeg is:

$ ffmpeg -i "rtsp://10.0.0.201/cam/realmonitor?channel=1&subtype=1" -c copy -sn -f rtsp -muxdelay 0.1 "rtsp://***:8554/test" -hide_banner
Input #0, rtsp, from 'rtsp://10.0.0.201/cam/realmonitor?channel=1&subtype=1':
  Metadata:
    title           : Media Server
  Duration: N/A, start: 0.080000, bitrate: N/A
    Stream #0:0: Video: h264 (Main), yuvj420p(pc, progressive), 640x360, 100 tbr, 90k tbn, 180k tbc
Output #0, rtsp, to 'rtsp://***:8554/test':
  Metadata:
    title           : Media Server
    encoder         : Lavf58.45.100
    Stream #0:0: Video: h264 (Main), yuvj420p(pc, progressive), 640x360, q=2-31, 100 tbr, 90k tbn, 90k tbc
Stream mapping:
  Stream #0:0 -> #0:0 (copy)
Press [q] to stop, [?] for help
[rtsp @ 0000016f3cc75280] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
[rtsp @ 0000016f3cc75280] Non-monotonous DTS in output stream 0:0; previous: 0, current: 0; changing to 1. This may result in incorrect timestamps in the output file.

[aler9]

Hello, this has been already answered here #144 (comment)

[bluenviron-bot]

This discussion is being locked automatically because the last update was more than 2 years ago.

Do not use the content of this discussion as reference since it's probably outdated!

The official documentation is the only place in which you can find up-to-date answers.