[HW Accel Support]: Dis-coloration on part of cams images (v14 - intel iGPU) #13146
Replies: 4 comments 9 replies
-
|
See the FAQ, Usage question 15. Auto-detection of your |
Beta Was this translation helpful? Give feedback.
-
|
I just noticed you have Axis cameras. For some reason they don't report the resolution correctly, even when you define it in your camera's stream URL. Your camera is set up in portrait orientation, so perhaps you could try But in the end, go2rtc is the best solution. https://docs.frigate.video/configuration/live/ |
Beta Was this translation helpful? Give feedback.
-
|
great- thanks, i was taking portrait vs landscape into account when i was manually defining the resolutions in config.yaml - but will look in this direction (as well as will move to using go2rtc) and update this thread. |
Beta Was this translation helpful? Give feedback.
-
|
This was the right move (moving to using go2rtc and re-streaming), No more artifacts, and plus everything else is working better and smoother (including a tad better frame rate on birdseye) one new issue im having though (after switching to go2rtc) - on the live view page (ie when i click one of the 10x cams from the main page) - about 90% of the time i just get a spinning wheel and no live view comes up (some times it does work though, but rarely). im Guessing this is related to one of the three video players that frigate is automatically choosing - if that is the case, how can i change / over-ride this? (ie video for all cams Comes up instantly and great frame rate if I go to the debug view or motion Tuner or the settings page where you at change your masks)
Im seeing the same issue on 2x differen win11 PCs, and im testing with FF 129.0 and chrome 129 (have cleard cache, and tried incognito on both). Dev-View seems to show it waiting on something like: (while im getting the spinning wheel): I have added this (made no effect): i do have docker allowing these ports through (is all local network, same 10.6.6.x subnet): this is a sample of how my config now looks: i will post my full config So that others can compare it to my original config above as it may be helpful. |
Beta Was this translation helpful? Give feedback.
-
|
i also tried specifying the width / height and still getting discolor (while using go2rtc) - this is on 14.1-dev. (see image pls, vlc shows same url as correct res):
|
Beta Was this translation helpful? Give feedback.
-
|
Frigate defaults to use MSE first, since it's usually the most well supported in a browser without additional configuration. If it's not able to load the MSE data from your stream within 3 seconds, it tries WebRTC (if you've defined So it looks like MSE and WebRTC is failing (assuming you still have There are a few things you can try:
|
Beta Was this translation helpful? Give feedback.
-
|
I found this (mentioning Axis cameras) that may be helpful: https://gardinal.net/understanding-the-keyframe-interval/ |
Beta Was this translation helpful? Give feedback.
-
|
ok thank you- (btw- yes you can adjust i-frame interval on axis cams, they call it GOP , or dynamic GOP you can also disable "ZipStream", which is their h264/265 compression booster thing- you can change these options globally via the cameras webGUI, as well as change these options right in the RTSP URL being requested for that specific stream, on Axis cameras.). one final question in re-guards to the discoloration im seeing- Does it impact anything outside of the live view in the web GUI? IE does it cause issues for the detection Algorithms or detection image pipeline flow? (i ask as i dont use the live-view of the webGUI much at all, so if thats the only thing being effected i can live with that). |
Beta Was this translation helpful? Give feedback.
-
|
Oh, great - that's nice to know about Axis cameras. Thanks!
No - the artifacts are only a visual distortion when using the jsmpeg player specifically. Nothing else in frigate is affected. |
Beta Was this translation helpful? Give feedback.
-
|
in closing this issue- 2 things were helpful (thanks to @hawkeye217 for this): 1- moving my frigate cameras rtsp inputs to using go2rtc and restream to frigate (instead of ffmpeg directly). 2- i still see artifacts (only in the frigate webGUI's live view) - and only on the 3x or so "portrait view" cameras i have - however this is due to an issue on the cameras side (im using axis cameras). (see the replies and discussion above for more details). here is my frigate config NOW after moving my cams to using go2rtc (can contrast this wil my full config in the opening post): |
Beta Was this translation helpful? Give feedback.
-
|
Happy to help! I would be interested to see if changing your GOP value and/or increasing your frame rate makes your live views use MSE rather than falling back to jsmpeg. Because your |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
its only in the webGUI live pages i see this Dis-coloration / shape occur (ie not in recorded videos, nor on home assistant frigate cards which stream the cameras). it only seems to occur when the webGUI is live updating one of the cameras (i think due to motion occuring) - All of my cams are Axis and current gen, ie p3265-xx (or some are one gen behind, such as p3245-xx). all cams are local, eth hardwired, and on the same ip subnet as frigate.
(this actually is Not that big of an issue, i dont use the live-view page that much - but i Wanted to bring it up in case it might be causing other issues in my frigate setup)
i do recall Prior discussions where this type of issue would occur if you specify the wrong resolution in your config file, however I was manually specifying the resolution (and verified it was correct with VLC of the same urls) - and issue still occurred. I read that frigate since version 13 can auto detect the resolution, so I removed the resolution definitions, and the issue still persists.
this is a Optiplex micro (i5-9500T) only runs Docker and Frigate + portainer (thats it) - Coral is a pcie one
(thank you for your time , help, and for FRIGATE ITSELF!! ITS AMAZING!!)
Versions:
its easier to see than describe:
video of issue:
(note in stats below, i had just restarted a few min prior to this sys info image below, but this is how the stats generally look):
Hardware Info from Frigate:
Version
0.14.0-da913d8
Frigate config file
docker-compose file or Docker CLI command
Relevant log output
FFprobe output from your camera
Operating system
Other Linux
Install method
Docker Compose
Network connection
Wired
Camera make and model
axis p3265-lve
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions