Closed alsimms closed 1 year ago
NickM-27
commented
1 year ago Please read the docs, you are using the restream but not using preset-rtsp-restream for the input_args. This is one of the primary reasons separate args are recommended - to avoid stuttering in recordings https://docs.frigate.video/configuration/restream#reduce-connections-to-camera
alsimms
commented
1 year ago Hi Nick,
Thank you for your prompt reply. My mistake, I have added the preset-rtsp-restream to input_args to all main streams and substreams but the issue still remains after testing again. It is also my understanding that under the current config, rtc2go is the only connection to the cameras and frigate is pulling from 8554 on local host. There is nothing else connecting to the cameras.
The config portion in question now looks like this.
cameras:
tapodeck: # <------ Name the camera
motion:
mask:
- 0,188,494,35,796,34,955,54,1280,139,1280,0,0,0
- 499,663,581,614,558,440,523,371,457,326,298,331,181,371,192,586,227,630
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/tapodeck_sub # <----- The stream you want to use for detection
input_args: preset-rtsp-restream
roles:
- detect
- path: rtsp://127.0.0.1:8554/tapodeck # <----- The stream you want to use for recording
input_args: preset-rtsp-restream
roles:
- record
live:
stream_name: tapodeck_sub
tapofront: # <------ Name the camera
motion:
mask:
- 1280,0,1280,313,1214,265,1220,216,1259,147,1252,60,1187,38,1078,34,982,61,801,63,760,125,279,131,151,141,0,73,0,0
- 1106,720,954,496,778,408,412,410,339,529,344,720
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/tapofront_sub # <----- The stream you want to use for detection
input_args: preset-rtsp-restream
roles:
- detect
- path: rtsp://127.0.0.1:8554/tapofront # <----- The stream you want to use for recording
input_args: preset-rtsp-restream
roles:
- record
live:
stream_name: tapofront_sub
taposwing: # <------ Name the camera
motion:
mask:
- 587,40,981,48,1280,74,1280,0,605,0,508,0,358,0,363,41
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/taposwing_sub # <----- The stream you want to use for detection
input_args: preset-rtsp-restream
roles:
- detect
- path: rtsp://127.0.0.1:8554/taposwing # <----- The stream you want to use for recording
input_args: preset-rtsp-restream
roles:
- record
live:
stream_name: taposwing_sub
garage: # <------ Name the camera
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/garage # <----- The stream you want to use for detection
input_args: preset-rtsp-restream
roles:
- detect
- record
live:
stream_name: garage
roofcam: # <------ Name the camera
motion:
mask:
- 617,0,482,149,343,187,369,324,809,406,1135,377,1160,0
- 0,585,0,633,78,634,212,509,276,412,368,307,280,125,193,105,153,102,97,118,76,143,0,158,0,227
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/roofcam # <----- The stream you want to use for detection
input_args: preset-rtsp-restream
roles:
- detect
- record
live:
stream_name: roofcamto be clear, new recordings after making the change and restarting frigate still have the stuttering?
I would suggest using preset-vaapi instead of qsv
alsimms
commented
1 year ago Yes, after restarting they do still stutter. I will try your recommendation and get back you in a few. Thank you once more !
alsimms
commented
1 year ago Sorry Nick,
I made the changes you suggested but after restarting and testing with preset-vaapi the pauses and catch ups became more pronounced.
NickM-27
commented
1 year ago okay, then I'd suggest trying to put ffmpeg: in front of all the go2rtc streams
alsimms
commented
1 year ago All Right Boss,
You got it, give a few and I will get it done ! :rofl:
alsimms
commented
1 year ago Do I need to add quotes like the one below it? - "ffmpeg:tapofront#audio=aac" or is it fine without them?
I tested as is below and still have the issue, no error on log.
go2rtc:
streams:
tapofront:
- ffmpeg:rtsp://xxx.xxx.xxx.xxx/stream1
- "ffmpeg:tapofront#audio=aac"
tapofront_sub:
- ffmpeg:rtsp://xxx.xxx.xxx.xxx/stream2
tapodeck:
- ffmpeg:rtsp://xxx.xxx.xxx.xxx/stream1
- "ffmpeg:tapodeck#audio=aac"
tapodeck_sub:
- ffmpeg:rtsp://xxx.xxx.xxx.xxx/stream2
taposwing:
- ffmpeg:rtsp://xxx.xxx.xxx.xxx/stream1
- "ffmpeg:taposwing#audio=aac"
taposwing_sub:
- ffmpeg:rtsp://xxx.xxx.xxx.xxx/stream2
garage:
- ffmpeg:rtsp://xxx.xxx.xxx.xxx:554/h264
roofcam:
- ffmpeg:rtsp://xxx.xxx.xxx.xxx:9554/roofcamYeah I'd suggest adding quotes. If that doesn't work then I don't know what it would be other than camera iframe issues but I don't believe that's configurable on tapos
alsimms
commented
1 year ago Nick,
That did not resolved it either. I think you are correct in your thinking about iframes or -use_wallclock_as_timestamps which has been discussed a lot with Reo cams. This has been my suspicion all along. Most people resolved these same issues by adding...
-f
live_flvto their configs but I do not think that applies in my case as Reo cams have a link with FLV and mine does not. Regardless, I appreciate your super duper help. The project is lucky to have you ! You would be an asset in any organization. I wish you nothing but the best!
See you later alligator !
NickM-27
commented
1 year ago Feel free to leave this open, some others may have ideas to help
Describe the problem you are having
First off my hat's off to all the devs, contributors and testers that work and support this incredible project.
My issue is related to stutter in all recordings no matter from which camera it comes from. Playing video from camera directly plays fine. Playing video using live webrtc plays fine with no stutter. I have searched here and found some custom settings but these are mostly for reo cams and when I tried, it complained about invalid options and settings being used.
Everything words perfect as expected, it is just the recording portion that needs help. Thanks in advance.
Frigate is running on an 8400T cpu with 6 cores, 16 GB ram and 512GB m.2 msata 512GB.
Docker compose
ffprobe output from camera.
Version
0.12.1-367d724
Frigate config file
Relevant log output
Frigate stats
Operating system
Debian
Install method
Docker Compose
Coral version
M.2
Any other information that may be helpful
No response