Charles Crossan

Results 218 comments of Charles Crossan

So, it looks like the call to `xioctl` on line 334 of `v4l2uvc.c` is a wrapper for `IOCTL_VIDEO` which, according to https://www.kernel.org/doc/html/v4.9/media/uapi/v4l/func-ioctl.html both returns a `0` or `-1`, _and_ sets...

I GOT IT TO WORK! Had to do some code-hacking (see https://github.com/crossan007/mjpg-streamer/commit/a1380b1cf010c78389994502e94d8441026c7b97). By hard-coding to JPEG, I can run the GStreamer pipeline: ``` gst-launch-1.0 videotestsrc ! "video/x-raw, width=640, height=480, fps=30/1"...

By using `avenc_mjpeg` in GStreamer to encode the jpeg (rather than letting mjpeg_streamer handle the raw YUYV stream), my raspberry pi processor usage is significantly down. The Gstreamer pipeline here...

To add some fun context; I'm using this to "combine" two different webcams from my 3D printer into one stream that OctoPrint can use. ![image](https://user-images.githubusercontent.com/11679900/112759559-894e4400-8fc1-11eb-95ab-b8eed6418dc1.png)

@tombo9999 try building mjpg-streamer from my commit: https://github.com/crossan007/mjpg-streamer/commit/a1380b1cf010c78389994502e94d8441026c7b97 That basically "hard codes" the parser to use `V4L2_PIX_FMT_JPEG` instead of the format the the v4l2loopback device is "claiming to have". It's...

@christianrodher I'm afraid I'm not sure how to reduce CPU consumption. I was experiencing this issue as well. I kind of gave up on this project, since the CPU usage...

If I recall correctly, the "high consuming" piece here was the MJPEG encoding - maybe that GStreamer wasn't able to utilize hardware acceleration, or that the device I was using...

I'm working out using ESPHome on a TTGO T-BEAM for an idea I have to create a C component that extends the ESP API over a LoRA Mesh (bringing in...

Yes - this would be nice! Also sort of related to #2033 - where I may type a "generic title" (like coffee) into the consume / purchase / inventory workflow...

Raoul Snyman took a shot at fixing this a while back, but unfortunately we haven't yet incorporated his changes to the build process: https://github.com/rsnyman/churchcrm-crm/tree/docker-deployment