-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial implementation of camera-controller app #37835
Initial implementation of camera-controller app #37835
Conversation
PR #37835: Size comparison from b205837 to be616c7 Full report (58 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
PR #37835: Size comparison from b205837 to c1b95fd Full report (74 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
@yufengwangca, wondering if we can link to the same sources from chip-tool (for the base part) in the camera-controller BUILD.gn file instead of making a copy of the sources in the camera-controller app. |
If you compare the source code of these two example apps, you'll find significant differences. Chip-tool is much more complex, and I have removed a lot of code that is not relevant to the camera. And we have not add any camera specific features yet, and that will make sharing code even harder. |
This is the initial implementation of camera-controller app running on a Linux platform.
In a typical setup, the Camera Controller app manages a CameraDevice app running on a Raspberry Pi. The CameraDevice captures and encodes the video feed before streaming it through a WebRTC track, while the CameraController receives this video stream and displays it, creating a complete end-to-end camera solution.
Note: The initial version is inherited from chip-tool, with no camera-related features added.
Testing
Build is validated by CI
Pairing Camera device app from Camera Controller