[Jeremy Garchow]

Are there any files that start with a period? Those are the hidden files.

[Jeremy Garchow]

You can simply update from the App Store. Should be good!

[Jeremy Garchow]

[Erick Puentes] ” I have a feeling this is close to the solution but for some reason, the Google universe doesn’t seem to have another option/solution to fix this type of file error.
“

It’s easy to list hidden files in terminal.

Open Terminal.

Type “cd” and then hit the space bar.

Now drag the folder that contains the errant dv file to the terminal. This should list out the directory.

Now hit return. This will change Terminal to the folder that contains the dv file.

Now type “ls -a”

what does it list?

[Jeremy Garchow]

[Erick Puentes] “How is it that FCPX can play it, yet not export it out.”

Some sort of corruption.

Can you duplicate the clip on the Finder level? That may shake loose permission errors.

If that doesn’t work, you should try and “Get Info” on the file and turn off all permissions.

[Jeremy Garchow]

Are these separate system wavs, or wavs from R3D?

If R3D, I’d suggest sending an AAF to Logic Pro with X2Pro.

[Jeremy Garchow]

Sweet!

Chalk it up as a win, and celebrate the victory.

[Jeremy Garchow]

Do the thumbs work in Finder?

[Jeremy Garchow]

Try to optimize the file in FCPX, then import the optimized file and has that. Delete the dv file completely out of the library.

You can also try Compressor (or Motion) to make a new version.

[Jeremy Garchow]

To add to the add, there are other processes that use optical flow like stabilization. Be sure to check if any clips have that turned on.

Sometimes you have to re add the clip to the timeline to shake loose the failed processing, but this is a rare occurence.

[Jeremy Garchow]

That is to say, without a bug, like remove silent audio actually removes all the audio.

I never use that feature so I’m not sure how well it works or not.