Requesting Ricoh to Open Source HDRI Plugin for better App Integration and Community Development

I’m working on an iPad/iPhone app that will interface with the Ricoh Theta camera. It’s being developed to aid people that have to capture data on film sets. The idea behind it is that even people without much technical knowledge would be able to operate it and be confident that they’ve captured everything that’s needed.
One of the things we need to capture is an HDRI. Right now we’re focussing on using the Theta Z1, and the ability of it to shoot bracketed exposures so quickly is amazing. But this is where it gets interesting.
Transferring the individual exposures over WiFi to the iPad takes quite a bit of time, even more so if we’d use DNG files (it takes too long). So when I discovered the HDRI plugin developed by Ricoh themselves (a colleague of mine developed the initial idea in the form of the Authydra plugin), I thought that it would be great if we could use that instead and do the processing on the Theta itself.
But then I quickly realized that I needed some extra ways of controlling the HDRI plugin from the iPad. And this is where my request comes in.

It would be wonderful if there was a way to build upon what Ricoh has created. So, then I thought, wouldn’t it be great if Ricoh could open source their plugins? Right now, my interest is only in the HDRI plugin, but why not make all plugins available? I think it would benefit this community a great deal, as they could serve as perfect examples to take ideas from and develop even more plugins. And in my case, I could add the few things I would need to the HDRI plugin, to make it suitable to control from our iPad app.

Also, while the source code for our app won’t be available, the app itself will be free on the App Store, once it’s released. So in that sense we would be giving back to the community as well.

I really hope the Ricoh will consider this as I think it could jumpstart plugin development quite a bit.

Thank you.
With regards,
Marijn Eken

1 Like

Is no one else interested in this? I can hardly believe it.

Also, I’d be very grateful if Ricoh could respond. But it looks like I need to start looking at other solutions.

Cheers,
Marijn

You may be able to use this project as a base to modify. You may be able to work with the developer. Try open an issue and see if the developer responds.

The developer of that particular plugin, Kasper, happens to be my direct colleague. So getting in touch with him is not a problem. :wink:

In fact, we discussed this particular idea and he agreed that it would be great if Ricoh open sourced their plugins, since he struggled with getting his plugin to function properly (mainly due to memory limitations). The developers at Ricoh seem to have done a great job with programming their HDRI plugin that it’s too bad that Kasper, or I can’t benefit from their knowledge. Ricoh probably knows their device best and knows some best practices for sure.

Would it be an idea otherwise to ask Ricoh for some more example material, or documentation on best practices, instead of fully working plugin code? If the issue is intellectual property, then maybe that could be alleviated that way?

Cheers,
Marijn

I will include this information in the agenda we have with a RICOH manager. Is the memory limitation problem encountered during the merge process where multiple frames are combined into one?

As the Authydra plugin was built before the availability of the Z1 _burstOption, it likely does not have this implemented.

Is there a limitation of the existing _burstOption settings?

Or, is the problem in identifying when the burst is over and then freeing up memory for the merge process?