Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Loosing r3d Gyro data after trimming

Ivars Svarcs

Member
Joined
Nov 24, 2020
Messages
23
Reaction score
7
Points
3
Today pulling out archive files realised that all trimmed files has lost the Gyro data (Komodo r3d to be specific).
Is it true that REDCINE-X PRO after trimming cuts out and does not include the gyro data in trimmed file?

If so, then why? Or am I missing some checkbox that must be selected?
 
Seams odd, have not checked for Komodo but for dsmc2 the gyro data is written into each frame as I remember.
 
Do your R3D Trims have the RMD sidecar file included with the image file?

If the gyro data is saved in the RMD sidecar file, not the actual image file, you'd have to make sure you select 'Save RMD Sidecar' in the 'R3D Trim/Setup' drop down menu in the 'Export' settings.

There's also a 'Automatically Save RMD Files' check-box in the 'General' section of the 'Edit/Preferences' menu.

Edit - Of course, if the RMD file is there with the R3D Trim and you still don't have the gyro data, then that is odd. Just checking the obvious stuff first.
 
Last edited:
Do your R3D Trims have the RMD sidecar file included with the image file?

If the gyro data is saved in the RMD sidecar file, not the actual image file, you'd have to make sure you select 'Save RMD Sidecar' in the 'R3D Trim/Setup' drop down menu in the 'Export' settings.

There's also a 'Automatically Save RMD Files' check-box in the 'General' section of the 'Edit/Preferences' menu.

Edit - Of course, if the RMD file is there with the R3D Trim and you still don't have the gyro data, then that is odd. Just checking the obvious stuff first.

Thank you Björn and Les for your replies.

Komodo 1.7.5
REDCINE-X Pro 61.1.2
Freshly reinstalled macOS 14. Sonoma

On exported trim file via File --> Export --> RED Trim --> SETUP ( i have selected Save RMD sidecar, Save Camera audio, Ignore Frame Rate Override) --> rest is as it was in default.

Automatically save RMD in general is also enabled.

Would be great if someone could try to reproduce the steps and share their findings?
 
I contacted RED support and Sean suggested to use Reline in terminal to check if the file after trimming has still the gyro data:
redline --i [Drag your R3D clip to the terminal window to auto-populate the file path, minus the brackets] --printMeta 5

After performing these steps i could see that trimmed file still has similar data to source file only less of it, so data indeed should still be there.
However Gyroflow does not see the movement data in the trimmed file.

Seems that Gyroflow does not read the gyro from trimmed file and is probably sone read issue.
I have contacted the Gyroflow Dev channel to see if this phenomena can be addressed.
 
If anyone is interested..
sadly seems I was right

After discussing this with our colleagues and further testing, the aux data like IMU/Gyro cannot be recreated into the new R3D trim files. You can verify this with REDLINE –printMeta 7 command to see IMU/Gyro on Raptor and Komodo clip lose aux data when R3D trimming. The only solution would be to keep the entire R3D if you need the aux data or extract the metadata into a sidecar file before doing the trim.
 
Thanks for getting that figured out, surprised it hasn't been mentioned before.

The ability to keep the Gyro metadata in an R3D Trim should definitely be included in the list of future RCX updates, if it isn't already.
 
I agree.
I thought that Trimming r3D purpose was to get the same RAW unaltered file only shorter.
 
I'll vote for this as well. This was something I notice a month or so ago.
 
"To Whom It May Concern"
Good news, since I last communicated with you. We are pursuing saving the Gyro Data in a later version of RCXP. I was told it may not be soon but our software team is working on it.
 
Has this been resolved? Just encountered the same issue myself after editing down 3TB of R3D footage and trying to stabilise the trimmed clips in Gyroflow. Was hoping there was a work around for future edits.
 
Back
Top