Feature Request: Camera tethering with real-time parameter controls

[myki-jim]

I would like to discuss adding camera tethering functionality to RapidRAW. Before implementing, I'd like to get your feedback on the approach.

Proposed Features:

1. Real-time camera parameter display (ISO, aperture, shutter speed, white balance, exposure compensation, focus mode, etc.)
2. Camera parameter controls (change settings from the UI)
3. Auto-import captured photos into the editor
4. Folder monitoring for new captured files

Implementation Approach:

• Use libgphoto2 Rust bindings for camera communication (already in use locally)
• Add Tauri commands for: get_config_choices, set_config_value
• React context for global camera state management
• File system monitoring using notify crate

Questions:

1. Are you open to adding this feature?
2. Would you prefer I add toast notifications (requires sonner dependency) or use a different notification approach?
3. Should this be a separate panel or integrated into existing UI?
4. Any specific requirements or limitations I should be aware of?

I have tested with Canon EOS series and can submit PRs for review. I will do more test with more cameras before submitting.

[CyberTimon]

Hey @myki-jim,

Thanks for writing this up. Tethering would be a very valuable feature for RapidRAW, so I'm open to adding it.

Here are my thoughts on your plan:

UI:
I think it should be a new panel in the right-hand sidebar that only appears when a camera is detected. This keeps the UI clean for users who aren't using the feature. For consistency, please reuse the existing UI components for dropdowns and buttons so it matches the look and feel of the other panels. The current design in the screenshot feels a bit out of place.

Technical Side:
My main concern is cross-platform stability. It's critical that adding libgphoto2 as a dependency doesn't introduce compilation failures on Windows, macOS, or Linux in our CI pipeline. We'll need to be very careful with the build configuration to ensure it remains stable for all platforms.
Also, how do you plan to implement the photo transfer so it appears in the editor? And is Live View part of the initial plan, or something for later? How are we gonna support more cameras? (For example I can only test it with my Sony A7III)

Testing:
I have no personal experience with tethering, so I can't effectively test all the use cases. I'll have to rely on your judgment for that. When you open a draft PR, a simple testing checklist in the description would be helpful for me to follow.

This would be a solid addition - let me know when you have a draft PR up for review :)

Kind regards,
Timon

[myki-jim]

Hi @CyberTimon ,

Thanks for your feedback! I've already considered most of the points you mentioned. Here's my current progress:

Done

• UI/UX: Added to the right sidebar, the cam panel only appears when a camera is detected, keeping the UI clean
• Component Reuse: Using the existing Dropdown component for consistent look and feel
• Photo Transfer: Implemented two methods:
  • Software capture (click Capture button in the UI)
  • Camera button capture (press camera shutter, auto-download)
  • Photos appear in the editor automatically after capture
• Folder Monitoring: Using notify (new dependence) crate to watch the download folder, new photos load automatically

A Few Questions

1. Live View: Abuot this I planning to add this as a follow-up feature, I want to ensure basic capture is stable first
2. Camera Support: Only tested on Canon EOS RP (macOS Sequoia, Apple Silicon) so far, I'll do more test with different camera and OS. libgphoto2 should theoretically support Sony A7III, and i will test it later.

Currently Improving

• Feature Flag: I'm considering make gphoto2 dependencies to optional to ensure CI won't break

Test Checklist

I've prepared a 160-item test checklist covering:

• Cross-platform builds (macOS/Windows/Linux)
• Unit tests, smoke tests(in case the new feat break the original function), functional tests
• Camera compatibility tests

⚠️ Known Issue

I've noticed intermittent slow downloads (5-10 seconds) after capture, which may causes the second capture to block. Reconnecting the camera seems to resolve it, but I haven't identified the root cause yet. I'm still investigating this issue.

Does this direction look good to you?

Also, I'll attach some screenshots showing the current UI...

Without camera

After Connecting

After shot (Automatic upload)

Part of some test cases

Best regards,
Jimmy