It will be interesting to see if this camera has any features suitable for use in Mapillary Ricoh's new Theta X 360º camera features 2.55" touchscreen, interchangeable battery and Micro SD card slot: Digital Photography Review
Battery life Still image: Approx. 220 photos *6
That’s not much. But:
USB-C port on the side of the camera for keeping the device charged via a USB power bank without the need to swap batteries.
Great!
I wonder what the rate of the interval mode is. If it goes quicker than 1 pic every 2s. Would be great for bicycle applications.
Two image sizes are available to match the scene: 11K for a high-resolution bright-light indoor photography, and 5.5K to capture images easily and efficiently in other scenarios.
oddly specific information. So I guess they are using pixel-binning. This could be bad news for outdoor mapillary usage
Also, their use of Android sounds good.
I hope they do not take “still camera” too serious and are able to limit exposure time while in auto exposure mode. Or else, photography while moving would just smear everything.
Android is notoriously unsuitable for this because of limitations of their camera2 API.
Bad news: the minimum interval seems to be 6 seconds: Ricoh Theta X Review: NO STITCHING NEEDED for 5.7K 360 videos + 11k photos - 360 Rumors
Re: 6 seconds: I was afraid of that. So video and time lapse (if applicable) would be equivalent to previous 360 video. The higher pixel count and presumably processing power would only be useful for still spherical photos.
I found on-camera stitching very convenient, as one does not have to deal with software then.
Open source software in this area tends to not be so optimized and requires more manual labor.
Official sotware from both gopro and insta360 was always horrible. Heck, you cannot even download gopro’s stitching solution without that stupid Microsoft market account.
And you need that specific NVIDIA GPU which in turn have crappy closed source linux drivers.
Even worse, the mobile apps. The one for the Insta360 is full of US and Chinese spyware:
https://reports.exodus-privacy.eu.org/de/reports/com.arashivision.insta360akiko/latest/
Someone tested it and found 3s for 11K pics. Some improvement, but still too slow:
It seems possible to get 10fps 8K h.264 Video as a plugin developer:
So maybe the limit is the JPEG encoder?
8K is about 30 megapixels.
11K is about 60 megapixels.
So purely from a pixel-rate point of view, 11K might be 5fps…
Might be there’s another limit in the h.264 encoder.
Nevertheless 8K10 sound pretty attractive. Hope the video codec doesn’t impair the quality too much.
Update: the quality is very bad, lots of visible block artifacts: RICOH THETA 8K Video Tested For Developers. It's Great. - YouTube
Maybe they are doing much more than just saving the pic, because, even for 5.7K images, they claim 1.2 seconds per picture, whereas 30fps for basically the same sized video.
@MikeN, please add a tag “360° cameras”: 360° cameras - Mapillary Community Forum
Have used the 8K10 and 8K2 modes for a while now (after updating the firmware), and the resulting .mp4 files work fine with the mapiality_tools (2.10+), and most importantly the the overheating issues are almost non-existent when using these moves (at 25~30°C). 8K2 is fine for walking and the battery seems to usually last for over an hour, but while driving the camera needs to be set to 8K10.
A bit of a pity that there are no 11K2 mode. It is however odd that the App cannot download 8K pics/movies from the camera over WIFI. It is possible to fetch these using a USB-cable, but I found the process that inconvenient; much easier to just store everything on a large SD-cared (512GB) until one gets home, and can move the SD-card to a reader and use mapiality_tools directly process & upload the video.
The app can be used to configure the camera, when WiFi is on; but 8K have required the WiFI to be disabled, and this causes issue with the App. Using Bluetooth remote shutter button works fine though, but then you’d want to be able to hear or see the camera - and that can be problematic when the camera is mounted on a car…
Have had some issues with the camera suddenly dying when car mounted, and with battery and USB-charger connected; with only USB-charger connected things seems the camera seem more reliable. Regardless with any crash or sudden power loss the current clip is generally lost (0 bytes).
Thank you for sharing your experience @brunofilmklov! Sounds promising.
Here is are example of Theta X in 8K2 mode (probably), helmet mounted or on a double invisible-sick with a 200g counterweight*:
Maybe not the best the camera can do, so more of what you can expect while mapping a area.
(*) Google’s street view studio really don’t like wobbly GPS data in the videos, and if the camera i stable in the X/Y direction the GPS precision seems to be reasonably good, probably around 3m or less on a good/clear day. On day I think yd’ä have to be happy with ~10m. (Same issue with the Cellphone’s GPS & Theta V, if I walk with it in my hand then I’d lucky to get precision of 7~10m; but press the phone to the shoulder and that would improve to around ~3m.) I’m using a RICOH Theta Stick Tm-2 + Insta360 1.2m selfie-stick for ONE R/ONE X/ONE/EVO + 200g counterweight; (yes, the Insta360 stick is clearly not intended for this - the upper part not robust enough we connected to the bottom of the other stick, but it does help with stability and have surprisingly lasted more hen 6 months).
BTW, found out the hard way that the lens is very sensitive to rubbing, as I accidentally left the camera on a cardboard box while driving home - this rubbed a way the anti-glare coating, which was sufficient to cause significant blurring. The only “repair” offered by Richo seems to be to replace the camera, at about 50% of the cost for a new camera, so guess could have been worse.
Car-mounted, 8K10 mode, with [PULUZ Lens Guard PC Protective Lens Cover Case for Ricoh Theta SC2 / S/V Spherical Cameras Accessories Case Sticky Lens Protector] worked allot better then I had expected:
Yes, the Lens Guard is barely holding on the the lens mount, but better than risking a cracked lens. Not recommended in rain, or dew, as the lens can protector collect water and/or get covered with water droplets - with more or less unusable pictures as a result. Though driving in a light drizzle might not preclude getting useful footage, (though it likely voids the warranty - especially if USB-charge is connected…)
I don’t think the improvement in resolution would warrant a upgrade from the Theta V, but the workflow improvement and ability to record more or less for hours with only 5~10 second stops every 5~20 minutes**, instead of spending around 1/3 of the time downloading clips to the phone’s SD-card makes a huge difference - especial when walking with someone else is.
(**) If also uploading the clip to street view, the clip need to be shorter - up to ~7 seem to work fine; this is not an issue with mapillary_tools 2.10 that will automatically split the clip during upload (batches if 500 images).
Have used the camera with a large power bank and a cable with angled USB-connector; and while this works, with the older 3.x firmware the camera used to hang about once per day and require a forced hard reboot - and that clip was of course lost. The 4.x firmware seems more reliable; but now there are issues with user interface getting stuck, though at lest the normal power down works. So after acquiring a number of cheep replacement batteries and a few a double-battery-charger, I find stopping and swapping batteries more convenient, then dealing with the powerbank and cable combo.
Yes, you are correct in that there is difference in the image quality, as the 11K single photos seems to require about 11MB, and the extracted 8K video frames around 0.5~1.2MB.
Further we need to consider that Mapiallity currently have a fixed 2K max resolution for the projected image, so for now AFAIK there is a upper limit for the useful the camera resolution.
No, time lapse imagery is not natively supported anymore, but might be possible through a 3rd party plugin. (I believe there is a 3+ second startup time for taking a single photo, so yes you could probably approximate a 11K0.2 mode that way; however I believe a plugin-API have a bit more leeway in the frame and bit rate selection… Yes, Theta V used to have function, but not X. )
The bit rates for 8K2 and 8K10 seems to be adequate to me, given the limitations of the the camera form factor etc. I agree that the 8K resolution is a bit of a limitation OSM mapping, is it severely limits the ability to zoom in to read signs and get numbers and names. For the next major step in quality I think around 24~32K (and 6+ 4K cameras) are needed, and this implies a significant increase in physical size, storage space and cost. (And if I recall correctly, there are drone cameras that hit Mapiallity’s single image max size already…)
Usability of GPS is a more essential feature then anything else. High res and onboard stitching are nice but if the GPS isn’t straightforward and reliable then it isn’t a usable camera… the Insta360 X3 looks great on paper but the GPS implementation is so deeply bad that the camera is more or less useless as a tool for mapping if you value your time and sanity, so at the end of the day it isn’t a functional camera for mapping.