Lens Data

[Tim Wilkinson]

Has anyone figured out how the lens data is accessed in the metadata?
Just got our camera back from red and a client would really like to access this info.

 

[Tim Wilkinson]

Bump

 

[Curran Giddens]

Don't think there is any program that can access the lens data at the moment.

 

[Mark Stock]

So is it in the meta data?

 

[Stuart English]

Lens Data

So is it in the meta data?

For sure.

 

[Brandon Kraemer]

For sure.

Great! So how do we extract it? My 3D compositors want to know.

 

[Curran Giddens]

Someone should make a plugin for RedCine-X....

I'm pretty sure that RED uses the Cooke /i Technology.

http://www.cookeoptics.com/cooke.nsf/products/itech.html

Best bet is either Pixel Farm or Avid. Does Avid support R3D natively?

http://www.cookeoptics.com/cooke.nsf/downloads/Avid_and_Cooke_i_Technology.pdf

 

[Tim Wilkinson]

So is there a way to access that meta data?

 

[Colin Hubick]

any answer on this??

 

[Shane Betts]

For sure.

I love this! Oh, it's in there for sure. You can't get at it or use it, but it's in there. Honest.

 

[Frank Mirbach]

Any news here ?

 

[Matt Fleming]

This was a huge draw for me on buying a RED but while all the components seem to be in place, there is currently no way to access the lens metadata apart form seeing it in the monitor. I would FLIP with convulsions of joy to hear otherwise. The lack of info or feedback from RED on this topic is frustrating.

 

[Matt Fleming]

one of many dead-end posts regarding this topic:
http://reduser.net/forum/showthread.php?t=47750

 

[Gavin Greenwalt]

If you throw a Nuke "ViewMetadata" node onto it is it available? I'm looking at an r3d file but I don't think there was iData being recorded and there is no empty metadata field for focal length or focus.

 

[Matt Fleming]

Hi Gavin,

I'd do just about anything short of getting naked on the internet (no ones wants to see that anyway) to see accessable lens i-data from .r3d files. I'd pay money for it! I'd be more than happy to shoot and send you test files if you could get this to work in Nuke or any other pipeline. Please feel free to contact me...

Same goes for some/any feedback from RED about the topic.

Best,
-Matt

 

[Paul Leeming]

Matt, the info has to be in there already, you just have to reverse engineer the R3D file to pull it out.

Here's a couple of interesting tidbits I pulled from an R3D that I know I shot with my Canon Birger mount (which passes lens data to the camera).

1. Proof that the Red One Mysterium-X sensor really IS the same as the Epic S35 sensor

2. Actual Birger mount information is captured in the metadata stream, right down to the mount's serial number!

With all that in there, I'm positive the lens data (when captured) is in there. You just need to find the relevant pointers and figure out the best way to consistently extract them on a per-frame basis.

HTH

Paul

 

[Matt Fleming]

Thanks Paul, appreciate that. Yeah, it has been confirmed by Jim, Deanan, and others that the data is actually in there.

...figure out the best way to consistently extract them on a per-frame basis.

And therein lies the problem.

 

[Gavin Greenwalt]

I took a look at some r3ds but it looks like the Metadata is no longer in ASCII, which is quite the shame because I can identify frame starts easily enough and with the correct offsets would be trivial to spit out a CSV file.

Nuke also doesn't see it. Maybe someone with the R3D SDK can write a CSV metadata writer?

 

[Chris Swinbanks]

Missing metadata

Missing metadata

I presume that no-one's found a fix for this...??
I have the latest Redcine-X (windows), and test clips I've just shot with Birger/Canon show "0" in the metadata tags, yet its there in the monitor.
And I can also see the "Birger library" comments in a file in a hex-editor... so I know it must be in there as other have said....

 

[Matt Fleming]

Chris,

The data is for sure in the r3d files. For some rerason, RED is not allowing us access to the data. We've been told that access will come in the next "big" , non-beta of the SDK.