Skip to content
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

New Adapter: dual fish eyes #1288

Open
truongsinh opened this issue Apr 12, 2024 · 4 comments
Open

New Adapter: dual fish eyes #1288

truongsinh opened this issue Apr 12, 2024 · 4 comments
Labels

Comments

@truongsinh
Copy link

truongsinh commented Apr 12, 2024

Describe the feature

Insta360 and Gear 360 save their raw image as dual fish eye texture. I have Insta360 and can provide some of their video/picture for reference. Insta360 provide studio app on Mac and Windows with different stitch strategy, but I think we can just get 1 to work first, and can improve later.

Alternatives you've considered

Manually convert all Insta360 image and video to equirectangular

Additional context

Stitching options from Insta360 studio

Screenshot 2024-04-12 at 12 20 02 AM

Prior art: https://github.com/acalcutt/Gear360_html5_viewer

No response

@jtoppine
Copy link

jtoppine commented Apr 12, 2024

Just adding that Ricoh Theta Z1 (one of the most popular "pro" cameras for specifically stills) raw images are also dual fisheye, DNG. (JPG's are equirectangular, and raw images contain an embedded full size preview or "thumbnail" image, which is confusingly equirectangular unlike the dual fisheye main content). I can provide Ricoh files if needed.

Having PSV support this projection would be interesting, as it would simplify workflows which do not, or can not use the manufacturer's software (eg. on linux, or web servers with transcoding capabilities). One could edit/resize/adjust the files directly in generic raw software and serve direct to PSV, without the Ricoh apps or compatible stitching suites.

@mistic100
Copy link
Owner

yes please share some examples

@jtoppine
Copy link

Not trying to hijack OP's feature request here; if I understood correctly this is identical feature/usecase, just a different camera. I have no experience with Insta360 cameras or files, but I imagine they use similar approach. Anyway:

Here is a set of two sample files from Ricoh Theta Z1. Even one raw file from the camera is too large for github, so sharing via dropbox: https://www.dropbox.com/scl/fi/5vx0ood4avhckgy3zlvwd/psv_ricoh_theta_z1_samplefiles.zip?rlkey=pkwjjmpcpq9cdxolk4p8resg0&dl=0

Two sample files, for both:

  • raw file direct from camera (dual fisheye raw data + equirectangular preview)
  • jpg file direct from camera (equirectangular, which of course works well with PSV already)
  • dual fisheye jpg made from the raw file with darktable (unfortunately, I'm unsure how to retain or create the proper panorama projection metadata so that a theoretical dual fisheye -compatible viewer could detect the image as such and be able to view it properly)
  • exif metadata from the raw file as text, as reported by exiftool, for convenience

Here's how I imagine the workflow to go if PSV would support dual fisheye projection:

  1. users store/upload raw files to a web server
  2. server processes the raw file with some parameters/adjustments, and converts it to a browser compatible format. this would naturally be dual fisheye as that's what the raw is
  3. (server app would probably need to insert the proper projection related EXIF tags, or otherwise let PSV know it is indeed a dual fisheye projection image)
  4. PSV is used to view the processed files

@truongsinh
Copy link
Author

truongsinh commented Apr 22, 2024

Not trying to hijack OP's feature request here; if I understood correctly this is identical feature/usecase, just a different camera. I have no experience with Insta360 cameras or files, but I imagine they use similar approach. Anyway:

Correct, same format, just different cam :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants