QT proxies gone wild

[Michael Wilson]

I have some weird proxies showing up and some r3ds missing _m proxies on a red drive. Shot 4k 2:1 23.98

Regenerating the proxies via Redalert fixes the problem. I have a couple hundred clips to regenerate though. Seems to be about every other R3D file did something like this.

Clipfinder didn't like most of the files on this drive and wouldn't bring the proxies into FCP.

I believe this is what it named the _F proxy on one R3D file.
FE9055CB-C5EB-4F42-B32F-58C44EE6003C-422-000000D6E940B494

Has anyone ever seen this? How can I avoid this? Its going to take some time to regenerate these proxies.

[Bruce Ingram]

I've never seen that, sounds like it may be an in-camera issue. You may try reinstalling the firmware.

In the meantime you can batch create the proxies using REDrushes.

[NateWeaver]

Sounds like the drive as a whole is corrupted.

[Michael Wilson]

after further investigation it seems that the proxies got corrupted after dumping to the server from the on set back up drives. Footage and proxies on the drives are fine. The footage on the server got messed up somewhere in the transfer.