-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Config Support]: Only two of my cameras are working after trying to switch to intel from nvidia #4731
Comments
If you have a 12th gen processor you should be running QSV not VAAPI you may also be experiencing #3941 |
I think I may be experiencing that issue. I switched to QSV and now nothing is working.
Error Log:
|
Looks like it, in that case this will be fixed in 0.12 or you can run the docker image mentioned there which will work until 0.12 is released |
I got it working with the docker image listed in that thread. All my camera's except my h265 are recording now. I'm not quite sure how to write the config for a h264 detection stream and h265 recording stream. |
camera_name:
ffmpeg:
inputs:
- path: rtsp://main
roles:
- record
hwaccel_args: []
- path: rtsp://sub
roles:
- detect
hwaccel_args: qsv |
Front_Yard:
ffmpeg:
inputs:
- path: rtsp://[redacted]@192.168.40.23/cam/realmonitor?channel=1&subtype=1
roles:
- rtmp
- detect
hwaccel_args: qsv
- path: rtsp://admin:[redacted]@192.168.40.23/cam/realmonitor?channel=1&subtype=0 # <----- Add high res stream
roles:
- record
hwaccel_args: hevc_qsv
detect:
width: 640 # <---- update for your camera's resolution
height: 480 # <---- update for your camera's resolution I am not sure what I am doing wrong Log: [2022-12-18 15:40:41] watchdog.Front_Yard ERROR : Ffmpeg process crashed unexpectedly for Front_Yard.
[2022-12-18 15:40:41] watchdog.Front_Yard ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
[2022-12-18 15:40:41] ffmpeg.Front_Yard.detect ERROR : [NULL @ 0x563f615cb380] Unable to find a suitable output format for 'qsv'
[2022-12-18 15:40:41] ffmpeg.Front_Yard.detect ERROR : qsv: Invalid argument
[2022-12-18 15:40:41] ffmpeg.Front_Yard.record ERROR : [NULL @ 0x561b2bbb70c0] Unable to find a suitable output format for 'hevc_qsv'
[2022-12-18 15:40:41] ffmpeg.Front_Yard.record ERROR : hevc_qsv: Invalid argument
[2022-12-18 15:40:41] watchdog.Front_Yard INFO : Terminating the existing ffmpeg process...
[2022-12-18 15:40:41] watchdog.Front_Yard INFO : Waiting for ffmpeg to exit gracefully...
[2022-12-18 15:40:43] frigate.video ERROR : Front_Yard: Unable to read frames from ffmpeg process.
[2022-12-18 15:40:43] frigate.video ERROR : Front_Yard: ffmpeg process is not running. exiting capture thread... |
Update: fixed Front_Yard:
ffmpeg:
inputs:
- path: rtsp://[redacted]@192.168.40.23/cam/realmonitor?channel=1&subtype=1
roles:
- rtmp
- detect
hwaccel_args: -c:v h264_qsv
- path: rtsp://admin:[redacted]@192.168.40.23/cam/realmonitor?channel=1&subtype=0 # <----- Add high res stream
roles:
- record
hwaccel_args: -c:v hevc_qsv
detect:
width: 640 # <---- update for your camera's resolution
height: 480 # <---- update for your camera's resolution |
There's no reason to have hwaccel_args for your record role, there is no decoding being done (which is why I put |
It would give me errors if I did that for some reason. |
I do that without issues, would be interested in seeing the logs but it is not a big deal. I'll go ahead and close this. |
Describe the problem you are having
Hi! I tried switching from my nvidia encoding to intel. I have two cameras working. All of the cameras except one are using h264 encoding, the front yard camera is using 265 (thanks amcrest). They were all working on nvidia but now only the two doorbell cameras are working. I have a mix of amcrest and reolink cameras. I tried several different settings with no luck and now I am unsure of where to go next.
Version
0.11.1-2EADA21
Frigate config file
Relevant log output
Frigate stats
Operating system
UNRAID
Install method
Docker Compose
Coral version
CPU (no coral)
Any other information that may be helpful
Running a core i9-12900k processor
The text was updated successfully, but these errors were encountered: