[Motion-user] Gray glitching but only one of of two identical cameras

[Barry M. <bar...@gm...>]

Hi!


I’m not sure how to describe the problem which makes looking up 
potential solutions difficult.


I am using a Raspberry Pi 4, 4 GB version. Its GPU is set at 128 MB; get 
into the 512 MB range and it won’t boot, which is ‘correct’ for the 4’s. 
Task Manager shows CPU Usage shows 35-45%. Memory Usage currently 284 MB 
of 3775 MB. I have not noticed either spiking when my problem occurs.


Motion version is Git-28b7cb2a4297c78b9c08c9ce29a648aeb22120d0 per the 
Help option. And running *sh git-commit-version.sh* I get 
Git-ad7e243fcaee500f67297305d9235556fb4270b9 .

*sh version.sh* gave ‘trunkREVUNKNOWN’ - not at all helpful! Umm, my 
notes start last February.


Have two identical USB cameras: SVPro SV-USBFHD06H-BL36 (Appears to be 
the same as the ELP version). One behaves, only glitching maybe once 
every few hours just to get some attention while it’s twin can glitch 
two or three times in a minute. Seems the glitching is definitely more 
active the brighter the outdoors. There are various glitches. One is a 
solid gray overlay such as when a camera is not found except can be just 
the very bottom portion of the picture, to bottom quarter to half to 
almost the entire display. With this glitch I extremely rarely see 
through, so 100% opaque where the glitch portion is – I see the 
remainder of the picture.


Other types of glitches are like a coloured lens was placed over the 
camera for a split second: pink, light blue, dark blue, green…. Usually 
a slight tearing/shifting: top stays in place, bottom is ‘moved’ – 
generally to the left.


lsusb gives 32e4:9422 but nothing in the descriptor field.


Tried plugging both cameras to the USB 2 ports, both are currently in 
the USB 3 ports (figured higher speed and maybe current); also tried one 
in USB 2, the other USB 3….


What seems odd is the camera acting up is camera1.conf while 
cameraa2.conf which is basically a copy with a few descriptor changes 
works fine – rarely glitches.


I originally had the framerate set to 15; decreasing to 5 didn’t seem to 
make any difference. The resolution is currently 1280x720. Increasing to 
1920x1080 didn’t seem to make any difference. Running at 800x600 (4:3) – 
seemed about the same as far as glitching was concerned.


I had read in I think an Raspberry Pi forum to try blacklisting the 
sound option:

edit //etc/modprobe.d/blacklist.conf/

add entry: /blacklist snd-usb-audio/

Mine is ////etc/modprobe.d/raspi-blacklist.conf/ and underscored vs. the 
post’s hyphenated so altered; didn’t make any difference other than 
/lsmod/no longer listing/loading.



Apologies for the long post but trying to give as much information as 
possible.


Barry