DTS out of sync error #5784

Dvalin21 · 2023-03-21T07:43:19Z

Dvalin21
Mar 21, 2023

I keep getting the following errors. Not sure why. I was told that the time it shows not matching the server time has nothing to do with this error. Is there any tips or ideas on how I could fix this error?

2023-03-21 07:37:58.891252923 [2023-03-21 02:37:58] frigate.output 2023-03-21 07:38:41.949856686 [2023-03-21 02:38:41] watchdog.front_door 2023-03-21 07:38:41.949907782 [2023-03-21 02:38:41] watchdog.front_door 2023-03-21 07:38:42.048222882 [2023-03-21 02:38:42] frigate.video 2023-03-21 07:38:42.048304076 [2023-03-21 02:38:42] frigate.video 2023-03-21 07:38:52.052879222 [2023-03-21 02:38:52] watchdog.front_door 2023-03-21 07:38:52.052947291 [2023-03-21 02:38:52] watchdog.front_door 2023-03-21 07:38:52.053033614 [2023-03-21 02:38:52] ffmpeg.front_door.detect 2023-03-21 07:38:52.053111802 [2023-03-21 02:38:52] ffmpeg.front_door.detect 2023-03-21 07:38:52.053178037 [2023-03-21 02:38:52] ffmpeg.front_door.detect 2023-03-21 07:38:52.053247909 [2023-03-21 02:38:52] ffmpeg.front_door.detect 2023-03-21 07:38:52.053315236 [2023-03-21 02:38:52] ffmpeg.front_door.detect 2023-03-21 07:38:52.053378165 [2023-03-21 02:38:52] ffmpeg.front_door.detect 2023-03-21 07:38:52.053442526 [2023-03-21 02:38:52] ffmpeg.front_door.detect 2023-03-21 07:38:52.053502459 [2023-03-21 02:38:52] ffmpeg.front_door.detect 2023-03-21 07:38:52.053563865 [2023-03-21 02:38:52] ffmpeg.front_door.detect 2023-03-21 07:38:52.053623588 [2023-03-21 02:38:52] ffmpeg.front_door.detect 2023-03-21 07:38:52.053683131 [2023-03-21 02:38:52] ffmpeg.front_door.detect 2023-03-21 07:38:52.053761629 [2023-03-21 02:38:52] ffmpeg.front_door.detect 2023-03-21 07:38:52.053826722 [2023-03-21 02:38:52] ffmpeg.front_door.detect 2023-03-21 07:38:52.053888909 [2023-03-21 02:38:52] ffmpeg.front_door.detect 2023-03-21 07:38:52.053950065 [2023-03-21 02:38:52] ffmpeg.front_door.detect 2023-03-21 07:38:52.054011721 [2023-03-21 02:38:52] ffmpeg.front_door.detect 2023-03-21 07:38:52.054072727 [2023-03-21 02:38:52] ffmpeg.front_door.detect 2023-03-21 07:38:52.054132710 [2023-03-21 02:38:52] ffmpeg.front_door.detect WARNING : Unable to copy frame front_door1679384253.438862 to birdseye.
INFO : No frames received from front_door in 20 seconds. Exiting ffmpeg...
INFO : Waiting for ffmpeg to exit gracefully...
ERROR : front_door: Unable to read frames from ffmpeg process.
ERROR : front_door: ffmpeg process is not running. exiting capture thread...
ERROR : Ffmpeg process crashed unexpectedly for front_door.
ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
ERROR : [segment @ 0x55d6c83460c0] Non-monotonous DTS in output stream 0:0; previous: 3572844, current: 109568; changing to 3572845. This may result in incorrect timestamps in the output file.
ERROR : [segment @ 0x55d6c83460c0] Non-monotonous DTS in output stream 0:0; previous: 3572845, current: 110592; changing to 3572846. This may result in incorrect timestamps in the output file.
ERROR : [segment @ 0x55d6c83460c0] Non-monotonous DTS in output stream 0:0; previous: 3572846, current: 111616; changing to 3572847. This may result in incorrect timestamps in the output file.
ERROR : [segment @ 0x55d6c83460c0] Non-monotonous DTS in output stream 0:0; previous: 3572847, current: 112640; changing to 3572848. This may result in incorrect timestamps in the output file.
ERROR : [segment @ 0x55d6c83460c0] Non-monotonous DTS in output stream 0:0; previous: 3572848, current: 113664; changing to 3572849. This may result in incorrect timestamps in the output file.
ERROR : [segment @ 0x55d6c83460c0] Non-monotonous DTS in output stream 0:0; previous: 3572849, current: 114688; changing to 3572850. This may result in incorrect timestamps in the output file.
ERROR : [segment @ 0x55d6c83460c0] Non-monotonous DTS in output stream 0:0; previous: 3572850, current: 115712; changing to 3572851. This may result in incorrect timestamps in the output file.
ERROR : [segment @ 0x55d6c83460c0] Non-monotonous DTS in output stream 0:0; previous: 3572851, current: 116736; changing to 3572852. This may result in incorrect timestamps in the output file.
ERROR : [segment @ 0x55d6c83460c0] Non-monotonous DTS in output stream 0:0; previous: 3572852, current: 117760; changing to 3572853. This may result in incorrect timestamps in the output file.
ERROR : [segment @ 0x55d6c83460c0] Non-monotonous DTS in output stream 0:0; previous: 3572853, current: 118784; changing to 3572854. This may result in incorrect timestamps in the output file.
ERROR : [segment @ 0x55d6c83460c0] Non-monotonous DTS in output stream 0:0; previous: 3572854, current: 119808; changing to 3572855. This may result in incorrect timestamps in the output file.
ERROR : [segment @ 0x55d6c83460c0] Non-monotonous DTS in output stream 0:0; previous: 3572855, current: 120832; changing to 3572856. This may result in incorrect timestamps in the output file.
ERROR : [segment @ 0x55d6c83460c0] Non-monotonous DTS in output stream 0:0; previous: 3572856, current: 121856; changing to 3572857. This may result in incorrect timestamps in the output file.
ERROR : [segment @ 0x55d6c83460c0] Non-monotonous DTS in output stream 0:0; previous: 3572857, current: 122880; changing to 3572858. This may result in incorrect timestamps in the output file.
ERROR : [segment @ 0x55d6c83460c0] Non-monotonous DTS in output stream 0:0; previous: 3572858, current: 123904; changing to 3572859. This may result in incorrect timestamps in the output file.
ERROR : [segment @ 0x55d6c83460c0] Non-monotonous DTS in output stream 0:0; previous: 3572859, current: 124928; changing to 3572860. This may result in incorrect timestamps in the output file.
ERROR : [segment @ 0x55d6c83460c0] Non-monotonous DTS in output stream 0:0; previous: 3572860, current: 125952; changing to 3572861. This may result in incorrect timestamps in the output file.
ERROR : [segment @ 0x55d6c83460c0] Non-monotonous DTS in output stream 0:0; previous: 3572861, current: 126976; changing to 3572862. This may result in incorrect timestamps in the output file.

blakeblackshear · 2023-03-21T11:30:25Z

blakeblackshear
Mar 21, 2023
Maintainer

I think you have cutoff the log. The actual ffmpeg error will be the very last line of ffmpeg output. All ffmpeg messages are reported as an ERROR status when it crashes even if those messages were just informational.

12 replies

Dvalin21 Mar 28, 2023
Author

I see. Frigate is telling ffmpeg to exit because it stops receiving frames. There isn't an error message because it didn't actually crash or exit unexpectedly. It was intentionally stopped. Does it start back up ok?

I had time to search today on this issue. Do the presets by chance include the following ffmpeg setting -use_wallclock_as_timestamps 1 and if not, how can I set it for my cameras? I got the solution from the following link. Its a little old https://video.stackexchange.com/questions/24462/timestamps-are-unset-in-a-packet-for-stream-0-this-is-deprecated-and-will-stop

NickM-27 Mar 28, 2023
Collaborator Sponsor

The default presets do use that except rtsp-restream and rtsp-restream-low-latency

Dvalin21 Mar 28, 2023
Author

The default presets do use that except rtsp-restream and rtsp-restream-low-latency

Is it possible add this to rtsp-restream? or would it matter at all?

NickM-27 Mar 28, 2023
Collaborator Sponsor

You can always just switch back to the normal preset, or you could define args manually.

raeserfisk May 14, 2024

I have, possibly, the same problem with a Tapo camera that sporadically gives me this error (but when it does it's like 2000 of em..). I am using the rtsp-restream - what would I write to just add "-copytb 1" on top of the rtsp-restream-preset?

mrplow · 2023-03-21T17:56:59Z

mrplow
Mar 21, 2023

I didn't want to hijack this issue but I'm seeing the same thing on 12beta10 using my 3 reolink cameras.

I thought my issue was due to the crappy reolink firmware, but I'm seeing a pattern in the logs. Switching to the rtsp stream resolves the issues in the logs - but the reolink rtsp implementation is terrible and regularly has corrupted output, so I'm sticking with the http stream and ignoring the errors.
I'm seeing the Non-monotonous DTS in output stream ... This may result in incorrect timestamps in the output file. errors for all 3 cameras every 84 minutes like clockwork.

frigate.log
go2rtc.log

1 reply

NickM-27 Mar 21, 2023
Collaborator Sponsor

This is due to bad reolink realisation and expected. You should contact reolink support and ask for firmware which does not have broken RTSP

mrplow · 2023-03-21T18:03:54Z

mrplow
Mar 21, 2023

Broken to the point where all 3 cameras are failing at the same time every 84 min? Seems pretty coincidental. I will bug reolink anyways, can't hurt. Also, I'm using the http stream, not rtsp.

3 replies

NickM-27 Mar 21, 2023
Collaborator Sponsor

yes of course, because their timestamp implementation is incorrect. I've spent a lot of time with the dev of go2rtc at the packet level analyzing and looking at different reolink cameras and basically none of them follow the RTSP / HTTP-FLV protocol correctly

Also, I'm using the http stream, not rtsp.

right, because rtsp is broken. Support has had firmware for all my reolink cameras that fixed these visual rtsp issues

NickM-27 Mar 21, 2023
Collaborator Sponsor

Here is an example of how reolink does not comply with the protocol:

https://github.com/AlexxIT/go2rtc/blob/3002d5f4f1e4056581732227c436f5ecc5b4848c/pkg/httpflv/httpflv.go#L72-L80

	// Normal software sends:
	// 1. Video/audio flag in header
	// 2. MetaData as first tag (with video/audio codec info)
	// 3. Video/audio headers in 2nd and 3rd tag

	// Reolink camera sends:
	// 1. Empty video/audio flag
	// 2. MedaData without stereo key for AAC
	// 3. Audio header after Video keyframe tag

Morphy99 Dec 10, 2023

Hi Nick, couple of questions if you don't mind:

Are you saying there is a firmware that fixes these issues?

Could they cause a memory leak in the Frigate container?

twister36 · 2023-12-21T18:02:25Z

twister36
Dec 21, 2023

@NickM-27 - So is this error related to the restream? I too was getting, but most things worked, so I hate to say ignored it. However going through my system to clean it up I too see these errors...

I only use restream for my other processes (HA primary) to use the restream

1 reply

superdong69 Mar 30, 2024

Anyone ever get this fixed?

Dvalin21 · 2024-04-03T06:56:35Z

Dvalin21
Apr 3, 2024
Author

Anyone ever get this fixed?

No, still happens, but from what I can tell, it doesn't hinder the performance.

0 replies

kankadev · 2024-05-11T09:28:20Z

kankadev
May 11, 2024

Have the same issues.

And I very often have this error message [concat @ 0x5797654c9a40] No files to concat. Then I can't download the event clip in my script which listens to MQTT frigate topic. Frigate answers with error code 500. When I try to debug hours later, the relevant clip is downloadable then.

Is this problem related to the error messages you are familiar with or not? Otherwise I would open a new ticket.

Here's my last full log:
frigate_log.txt

Here's my config:

mqtt:
  host: 192.168.0.111
  user: mosq
  password: test
  port: 1883
  topic_prefix: frigate
  client_id: frigate

ffmpeg:
  hwaccel_args: preset-vaapi
  output_args:
   record: preset-record-generic-audio-aac

detectors:
  coral:
    type: edgetpu
    device: usb

objects:
  track:
    - person
    - dog
    - cat
    - car
  #filters:
    #person:
      #min_area: 400 #5000
      #max_area: 100000

cameras:
  # Tapo C200 - Studio
  inside_studio:
    ffmpeg:
      inputs:
        # High Resolution Stream
        - path: rtsp://camera:mysecret@192.168.0.100/stream1
          roles:
            - record
        # Low Resolution Stream
        - path: rtsp://camera:mysecret@192.168.0.100/stream2
          roles:
            - detect
    detect:
      width: 640
      height: 360
      fps: 15
    record:
      enabled: True
      events:
        retain:
          default: 30
          mode: all

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

DTS out of sync error #5784

{{title}}

Replies: 6 comments 17 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

DTS out of sync error #5784

Replies: 6 comments · 17 replies

blakeblackshear Mar 21, 2023 Maintainer

Dvalin21 Mar 28, 2023 Author

NickM-27 Mar 28, 2023 Collaborator Sponsor

Dvalin21 Mar 28, 2023 Author

NickM-27 Mar 28, 2023 Collaborator Sponsor

NickM-27 Mar 21, 2023 Collaborator Sponsor

NickM-27 Mar 21, 2023 Collaborator Sponsor

NickM-27 Mar 21, 2023 Collaborator Sponsor

Dvalin21 Apr 3, 2024 Author

Replies: 6 comments 17 replies

blakeblackshear
Mar 21, 2023
Maintainer

Dvalin21 Mar 28, 2023
Author

NickM-27 Mar 28, 2023
Collaborator Sponsor

Dvalin21 Mar 28, 2023
Author

NickM-27 Mar 28, 2023
Collaborator Sponsor

NickM-27 Mar 21, 2023
Collaborator Sponsor

NickM-27 Mar 21, 2023
Collaborator Sponsor

NickM-27 Mar 21, 2023
Collaborator Sponsor

Dvalin21
Apr 3, 2024
Author