Only 1 camera MMAL application can access the camera at any one time. That is why you can't use raspivid while raspimjpeg has the camera open. You can close the raspimjpeg connection temporarily (e.g. stop camera on web interface) in order to use raspivid but then all the other raspimjeg functionality is suspended.HaMaSch wrote: ↑Wed Jul 11, 2018 11:23 pmHi btidey,
thanks for your thoughts, especially for the hint to lower the framerate. This helps me lowering the cpu load when connecting from my pc. I was not aware that there are parameters possible.
Unfortunately it doesn't help me with my local Display. Calling cam_pic_new.php in the browser always pushes my cpu-load to 100%. Same with vlc
Only calling min.php with browser increases cpu-load only to 70-80%.
In all cases the image did not fit to the display, but I think I can adjust this when I've found the best way for the display.
Every browser and even vlc need an xserver for display and that costs performance. That's why I'd like to avoid an xserver.
Raspivid and omxplayer use the GPU of the RasPi directly and therefore need no xserver, but omxplayer sucks with this latency-issue and raspivid cannot open the camera device, because it's used by raspimjpeg.
I'd like to read more of your thoughts.
raspimjpeg is targetted at web use so doesn't have the direct live preview capability of raspivid.
It may be possible to add a direct preview option to raspimjpeg but this is quite a complex area as the MMAL connection set up is already quite complex. It will need a bit of time to research further. It is also complicated a bit in that I do all my raspberry development headless so don't have a natural environment for testing local screen preview.