TOPIC:

Edited whole music video in 10.5.4, proxy, when switched back to original, latest edits were not reflected in original.
Just noticed it wasn not tracking 1 week ago, been trying different methods to resync to no avail.
The clips not tracking were shot with Red Komodo 6k raw
Other clips shot with Gh6, Gh5, and DVX200 seem to be working


2013 Mac Pro 128gb ram
Blackmagic Egpu
Qnap NAS

Normally this cannot happen -- IF using FCP-generated proxies. When R3D proxies are generated within FCP, the current state of the R3D RAW settings are "baked in" the proxies. If you afterward adjust the R3D color temp or ISO using the "Modify RED RAW Settings" button in the FCP Inspector's Info tab, that would make them out of sync with the proxy color state. When you try to do that, a warning dialog appears stating "REDCODE RAW Settings cannot be applied to transcoded media".

So the system is designed to prevent that. However -- IF you create proxies from R3D *external* to FCP, and the utility which generated those does not match the current R3D RAW settings, you might be able to link the proxies, edit them, then when you switch back to R3D original media in FCP, they might be out of sync. I've never tried that, this is just a guess.

Another possibility is if after you start editing, someone uses a RED utility like REDCINE-X PRO to adjust the color of the R3D files. FCP has no idea that happened, since those RAW color changes are not stored in the FCP library. That would put the REDRAW changes out of sync with the proxy color state.

The REDRAW color edits are stored in a .RMD "sidecar" file. So another way it can happen is if you get an updated set of R3D media, where (say) only one or two files were added. However in that update they sent you a new .RMD file which overwrote your existing .RMD file.

The .RMD file is actually an XML file. If you rename the extension to .XML you can see the file using TextEdit or other editing tools. It's best to use an XML-aware editing utility such as BBEdit: apps.apple.com/us/app/bbedit/id404009241?mt=12

If you have a Time Machine or other backup of your R3D files which includes the .RMD file, that backup .RMD can be compared to the current version using a "diff" utility such as Beyond Compare: www.scootersoftware.com/

Another possibility is it's a bug with a certain version of RED Apple Workflow or how FCP 10.5.4 interacts with that. The current version of RED Apple Workflow is version 20.0.0, dated 9-6-22: www.red.com/download/red-apple-workflow-installer

Thank you for your extensive response… I used FCPX to create the proxies, and did direct import from hard drive with Red files.
Are you suggesting using the Red utility instead?

No I would not suggest using the RED utility as a standard procedure. It might be necessary to use it in a contingency.

If you used FCP to create the proxies, in theory they should not get out of sync with the original R3D material. However I have only tested that on recent versions of FCP, MacOS and the RED Apple Workflow package. It's possible it wasn't as protected several years ago on the versions you are running.

There is no obvious way to inspect what version of RED Apple Workflow is installed. I emailed RED to ask them how to inspect and verify the installed version.

The fact the proxy/original color problem only happens with RED is understandable. R3D files are tricky to manage. Unlike a normal camera, each clip is a series of segment files inside a folder. They are not supposed to be renamed, although if you are extremely careful you get away with it, but it's risky. Have you ever renamed any of the R3D fles or folders on disk?

Unlike regular camera files, there are three separate methods of altering color on R3D files: (1) Via normal FCP color effects which stores those changes in the library, and (2) Via the RED RAW Settings tool in the FCP Inspector's Info tab, and (3) Via external RED utilities. For #2 and #3 those changes are stored in the on-disk RMD (RED Meta Data) file inside the folder for each clip. It is very easy if you are exchanging files or just project XMLs with a collaborator to get those out of sync.

BTW all media and FCP libraries should only be on disks formatted as MacOS Extended Journaled (HFS+) or APFS. Are any of your files or libraries on ExFAT or other types of storage?

Is it ALL RED clips that have this problem or only some of them? If it is only some of them, I suggest inspecting the creation date and last modified date of the RMD file for those clips. Also make a copy of that file and use a "diff" tool to compare it to the RMD file of a RED clip which does not show the problem. That might help determine if the RMD file has somehow been changed.

A possible clue would be doing a Finder search for all files having the RMD extension. What is the creation and last modified dates for those files? Do those dates jog any memory of actions on those clips on that date, such as getting new files or adjusting color with the RED RAW Settings or editing the same files with Premiere or Resolve? If the RAW settings were changed by some other app external to FCP, it doesn't know that and it cannot protect from this problem.