Full metatags example.
We are trying to map the IMU data we are getting from blackmagic ursa 17k rushes that we are getting as EXRs. But there are no examples of HOW imu should be entered.
This is a pretty constant issue because I have no control over how the post houses pack metadata for VFX pulls and I've had issues before just trying to map lens info that was there but not working when I tried to map it in my custom metatags.
SO can we get a full example of every possible metadata entry to help map things?
For example we have:
{exr.braw.motion.acceleration.x 0.0897826}
{exr.braw.motion.acceleration.y 9.69771}
{exr.braw.motion.acceleration.z 0.68534}
{exr.braw.motion.gyroscope.x 0.00399474}
{exr.braw.motion.gyroscope.y 0.00585895}
{exr.braw.motion.gyroscope.z -0.0098537}
But zero references to how that data should be mapped in metatags, just documentation that it can be done.
Hello Toby,
All the supported tags you can use (such as frameRate, squeeze, focal, position, orientation etc..) are in the example metatags.xml file that ships with PFTrack, but it looks like you've got some raw IMU data from an accelerometer and gyroscope that cannot be mapped directly using the existing metatags.
Raw IMU data needs to be converted into position and orientation values that PFTrack can understand. This involves integrating the high frequency data from the IMU over time using calibration information specific to your device such as noise, bias, offset, drift and camera-relative orientations.
PFTrack can read the position and orientation values for ARRI and RED cameras, or from EXIF data generated by DJI drones because these devices have already integrated the raw IMU data using their camera-specific calibration before writing their media files. It looks like the Blackmagic RAW SDK (or the conversion to EXR) is just passing through the raw data, so we'd need a dedicated Blackmagic IMU importer to support this in PFTrack.
There may be some more information available in your EXRs or original BRAW file, but you'd also need all the original high frequency IMU samples for accurate results (rather than just one sample per frame) because IMUs for navigation typically operate at several hundred Hz.
If you can post a download link to your data then we can take a look and see what's possible. We are planning on looking further at the Blackmagic SDK, although there's no timeframe on that currently.