merging projects

[nightflasher]

Didn't know how to get in touch with you, so I'm asking here:
Would you like to try to merge your code (maybe a plugin) into rubyfpv gs https://github.com/PetruSoroaga/RubyFPV/tree/main
So we (the tiny whoop fpv community) can have your system within the rubyfpv ecosystem?
Not implementing rubyfpv into the esp32, but let a radxa zero 3w receive the esp32 mjpeg stream?!

[RomanLut]

Currently, I’m swapping ESP32FPV and Ruby SD cards on my Raspberry Pi 2W GS. The hardware is fully compatible, including the GPIO joystick pinout.

In the future, I plan to create a dual-boot Raspberry Pi image where either the Ruby VRX app or the ESP32FPV VRX app will boot, depending on a GPIO switch.

Later on, I aim to develop a dual or triple boot image for the Radxa platform, allowing it to run ESP32FPV, Ruby, or OpenIPC.

As for integrating the ESP32FPV protocol into the Ruby VRX app, it would be too complex. It involves more than just handling the video stream—there are specific camera settings, telemetry, radio configuration, and relaying. Merging it into another project would significantly increase the coordination and development effort. A dual-boot solution would be much simpler.

I also recommend testing the project to see if it meets your needs. The advantage of ESP32FPV is the tiny all-in-one camera. However, if you can mount an OpenIPC camera on your UAV, it might be a better option. OpenIPC offers not just H264, but also better lenses and sensors. The best sensor for ESP32 is the OV5640 with a 12mm lens, but it's nowhere near the quality of the IMX335 in terms of sharpness and color accuracy.