As far as CPU, the system is running high at 85% and most of that usage is from the mjpg_streamer process. I tried changing the resolution and surprisingly didn’t find a change in CPU usage so opted to keep it. The advantage of changing the settings in the boot config file is every time you unplug the camera the process dies, and when it starts it will use this setting (there is a background process called “webcam” that handles this). This can be done by ssh to your machine or shut the machine down and edit the file on your computer after putting in the SD card.
#SONY PS3 EYE CAMERA OCTO PRINT UPDATE#
You can update settings in /boot/octopi.txt so these are used by default. The “-q 50″ controls quality of the result compression. The important parameters above is the “-f 1” which says do one frame per second (I’m not looking for high quality video – I just want to see if print has lifted and get a feel of progress). I use the following options to run the streamer. Building the stream is a much more efficient if your camera is newer and has support for MJPG – otherwise you’re using YUYV encoding and the Pi has to do a lot of extra work. This software is distributed with the OctoPi build, no extra install required. This tool takes content from your web camera and creates a web video stream. The way OctoPrint integrates with a camera is by pulling into its page a video stream from mjpg_streamer (a web server running on a different port). But an older camera you have (or $5 Playstation Eye camera) is worth a try right? No way, CPU will be too high, you won’t have enough USB ports, system will run too hot, will cause printing to pause … or will it? Disclaimer: I know the Raspberry Pi camera using the camera interface is “the way to go”.