CONCLUSIONS
In the beginning, my goal was simply to migrate the Raspivid stereo functionalities onto a pi5. As the pi5 no longer supported the Raspicam apps, I used PiCamera and Python to accomplish these tasks: those being stereo video, stereo photos and stereo time-lapse movies. All of which are encapsulated in Python.
All three Python apps work 100% of the time when directly called from the command line, ie python3 video.py
The big issues is that in an app environment, these scripts must be called via an intermediary, such as NodeJS or PHP. Unfortunately, these Python scripts only run half the time they're called from an app, via intermediary code. This code will be used on a physical device and users won't be useing command lines, they'll be using buttons via a web interface. Therefore I have a problem. Scripts that work when called directly by the developer and scripts that work half the time via intermediary.
This brings me back to inquiring about a native Libcamera camera 3D SBS type parameter mentioned in the Official Raspicam Software docs. While I'm proud see all three Python scripts accomplish their associated tasks, it would appear they cannot be used in a real-world environment, ie on on hardware consumer product.
I know there has been some work with "synching" multi-cameras together done by the Pi-Team. If this "synching" approach is to be the equivalent of a native 3D SBS, then this means we're back to Python and back to intermediaries.
If there the any members of the PI Team still watching this thread, please me know if there is any news related to these subjects
MrV
In the beginning, my goal was simply to migrate the Raspivid stereo functionalities onto a pi5. As the pi5 no longer supported the Raspicam apps, I used PiCamera and Python to accomplish these tasks: those being stereo video, stereo photos and stereo time-lapse movies. All of which are encapsulated in Python.
All three Python apps work 100% of the time when directly called from the command line, ie python3 video.py
The big issues is that in an app environment, these scripts must be called via an intermediary, such as NodeJS or PHP. Unfortunately, these Python scripts only run half the time they're called from an app, via intermediary code. This code will be used on a physical device and users won't be useing command lines, they'll be using buttons via a web interface. Therefore I have a problem. Scripts that work when called directly by the developer and scripts that work half the time via intermediary.
This brings me back to inquiring about a native Libcamera camera 3D SBS type parameter mentioned in the Official Raspicam Software docs. While I'm proud see all three Python scripts accomplish their associated tasks, it would appear they cannot be used in a real-world environment, ie on on hardware consumer product.
I know there has been some work with "synching" multi-cameras together done by the Pi-Team. If this "synching" approach is to be the equivalent of a native 3D SBS, then this means we're back to Python and back to intermediaries.
If there the any members of the PI Team still watching this thread, please me know if there is any news related to these subjects
MrV
Statistics: Posted by MRV — Fri Nov 15, 2024 10:10 am