Maybe it is caused by “(1)” in the path?
I found there is some unknown EXIF tag is causing problems for both the desktop uploader and the command tool. I used a workaround by using exiftool to remove most tags.
exiftool.exe -overwrite_original "-Exif:all=" -tagsfromfile `@ -DateTimeOriginal -CreateDate -ModifyDate -GPS:all -Make -Model "E:/Interval_20241111_164638(1)"
I have uploaded more samples. Excuse my head while I get a longer stick! And will need to work on improving the horizon, compass and GPS offset.
I am really impressed! What is your workflow? Taking 96 MP DNGs > Stitching > Exporting as JPEGs or DNGs? And then? How much work is necessary for post-processing the exports? What is there file size? Further sharpening needed? How did you batch process the images? What is the file size of the images you have uploaded?
It’s really stunning. Even this distant sign is readable: Mapillary.
Right now I am only using QooCam Studio to do all the processing/stitching from DNG to JPG. Each image is about 18MB and uploaded using the desktop uploader. I have submitted a ticket to Mapillary to see if they can fix the error so I don’t need to use ExifTool.
Most parts of the image is sharp, but I do notice edges of lens maybe not as sharp and I will look at other processing options.
How long do you estimate does it take in total to move say 1000 images from the camera to your desktop and stitch and export them as JPEGs?
Each DNG file is 183MB and it took QooCam Studio about 25 seconds to process and stitch to JPG. That’s going to take a long time (6 hours for 1000 images!). I am using an SSD so I can transfer between the camera and PC quickly.
Not sure what you mean. The camera has 128 GB internal storage and optional a SD-Card. How do you connect a SSD?
6 hours for 1000 images!
Oh, oh, I already have ~3000 images for a day long hike with effectively 9 secs interval.18 h only for exporting as JPEGs. Without any post-processing. Oh, oh
It is like a very fast USB drive that I can plug directly into the USB port on the camera and it will save to that. More specifically I am using an NVME to USB enclosure. The internal storage is still very fast at over 100MB/s but with my primary use of DNG, it will run out of storage very fast.
Yes it is a
I tried what can be done with the awfull looking JPG output of the camera and was suprised that it could be made looking much better. I increased saturation a little bit to much but it does not look bad. Here is the JPG Mapillary and here your DNG Mapillary
The DNG shows more details in shadows and highlights and it looks more, but not really sharp.
Here you can compare the raw DNG Mapillary with a sharpened JPG Mapillary.
Interesting, what tools do you use for your processing? I don’t mind the processing times if I can process the entire sequence without needing to go through one by one. Part of the softness seems to be the Mapillary compression especially zoomed out on a 4K monitor. It does look better if I use 360° Panorama Viewer Online.
You can see the differences without Mapillary compression too:
It’s a screenshot how it looks in ON1 Photo Raw.
Stitching and exporting with Insta360 Studio, in general with some overall corrections (brightness, black point or so). Then embedding the GPS positions with exiftool and finally some sharpening with ImageMagick. I go threw it one by one. But of course it could be automated with some programming too. Maybe later.
BTW How long takes it to export as JPG with QooCam Studio? Hopefully much faster than as DNG. DNG is really to slow for me.
Yes the difference is definitely there. I will look to incorporate sharpening into my workflow once I begin to put the camera into full use next month. Last thing I want to try is to remove my ugly self from all of these shots.
Nice, I didn’t think you could import images from this camera to Insta360 Studio. I gave it a try and attempted to import the unstitched JPG or DNG but it did not stitch them.
JPG to JPG is much faster, about 1.5s each.
You could import the JPGs for color correction and to pan around the view. I prefer the “live” preview to assess a correction.
For me standard settings for corrections were unsatisfying, so would not automate this task.
begin to put the camera into full use next month.
I am waiting. Curious about how it deals with very different lighting conditions.