Error Sharing MOV clip as H.264

Hello
I am new to FCP and am running into a sharing issue. I have an MOV clip that I have imported into FCP and I am trying to share it as an H.264 file and I keep getting errors. I am able to share the clip using the "Video and Audio" mastering format with the codec as "Source - Apple ProRes 422" but the file size is huge. And it seems the only options in the "Publishing" formats are H.264 and this won't work. One error was "Video Rendering Error 60," but I think I got another un-named error as well.

Your suggestions would be appreciated. Also, where can I learn more about the real underlying issue here? I am guessing it has something to do with codecs and such but I don't know much about this.

Thanks!

Few standard things to try off the bat:

Hold Opt-Cmd while launching FCPX, when prompted delete preference files.
Select the Project, or the Library, and in the File menu, Delete Generated Media, and then select Render Files.

See if doing those two help.

BenB wrote: Few standard things to try off the bat:

Hold Opt-Cmd while launching FCPX, when prompted delete preference files.
Select the Project, or the Library, and in the File menu, Delete Generated Media, and then select Render Files.

See if doing those two help.

Hi,
Thanks for your reply. I tried your suggestion and then I tried to share as an H.264 file and I again got the "Video Rendering Error: 60" error. Any other thoughts? What does this error mean?

Thanks agin!

output as the foramt you can , then convert them to H.264....maybe it's not correctly, but sitll I want to post...

whitemax wrote: output as the foramt you can , then convert them to H.264....maybe it's not correctly, but sitll I want to post...

Can I use FCP to convert or do I need to use a different program? Thanks!

Any other thoughts? Thanks!

How long is your video?

Are you getting this error message somewhere during the sharing process, or immediately when you press Share?

- Ronny

ronny courtens wrote: How long is your video?

Are you getting this error message somewhere during the sharing process, or immediately when you press Share?

- Ronny

Thanks for your reply. The clip is 34 minutes long. If I open up the background tasks pane, I can see that the sharing task gets out to 95% and then stays there for several minutes and then it fails.

Thanks again!

Check this:

Open your Applications folder and select the FCP X program icon. Then press CMD+i to open the Info window.

In the Info window you see a checkbox to Prevent App Nap. Is this box checked?

- Ronny

ronny courtens wrote: Check this:

Open your Applications folder and select the FCP X program icon. Then press CMD+i to open the Info window.

In the Info window you see a checkbox to Prevent App Nap. Is this box checked?

- Ronny

Well, I found that the checkbox was not checked so I checked it and tried again and what I found now is that while I got the same error, there was actually a file that was written to the destination folder and it is playable. However I still got the error code. Any idea why? I am not sure if that was happening before but I am going to uncheck the box and see if I am in fact getting a file with the error.

I also opened the background tasks and watched the progress from the beginning and the % progresses pretty steadily from 0% up to 95%, then it hangs up. I can see that something is happening under the hood because my HD light will blink. This lasts for several minutes, then the error box pops up.

Thanks again for your help.

Troubleshooting should be done step by step and you have skipped one. You should have checked the box, then restart the computer and export again.

It absolutely does not make any sense to un-check the box, it must ALWAYS be checked.

- Ronny

ronny courtens wrote: Troubleshooting should be done step by step and you have skipped one. You should have checked the box, then restart the computer and export again.

It absolutely does not make any sense to un-check the box, it must ALWAYS be checked.

- Ronny

OK, that makes sense. So I restarted my computer and then tried the share again and this time it ran pretty quickly up to 99%, then stopped progressing. Then after a few minutes, I got the share error. But again, the file was written to the selected folder as an mp4 file and I can play it with Quicktime. Why do you think I am getting the share error and yet the file is still being created?

Thanks

You get this because you started sharing with App Napp enabled. If the file exports correctly now, everything will be OK from now on.

You only should worry about this if you get the same problem again when exporting a different file from a different Project. In that case, post back.

- Ronny

ronny courtens wrote: You get this because you started sharing with App Napp enabled. If the file exports correctly now, everything will be OK from now on.

You only should worry about this if you get the same problem again when exporting a different file from a different Project. In that case, post back.

- Ronny

OK, great, thanks!

Patrick Cox wrote: …then I tried to share as an H.264 file and I again got the "Video Rendering Error: 60" error. Any other thoughts? What does this error mean?…

btmk, apps trigger those errors but don't have their 'own', app-specific error codes; when you read the crash reports, on the first 'page' you'd read "error in thread #xyz", further on you can scroll to that specific thread and find those cryptical numbers...

-60 reads in human lingo as useful? For engineers. perhaps :lol:

me no coder, but it points into direction, somethings wrong with the drive you're saving to ...
so, aside following Ronny's excellent advice (he's the expert, not me!), I would check a few things there:
• what sort of drive? a LAN-drive/'server'/'home cloud'/'time capsule'/…
• format of drive is…? hfs/ntfs/fat?
• let the DiskUtitlity tool (Apps/Utilities) check your target drive ...

Karsten Schlüter wrote:

Patrick Cox wrote: …then I tried to share as an H.264 file and I again got the "Video Rendering Error: 60" error. Any other thoughts? What does this error mean?…

btmk, apps trigger those errors but don't have their 'own', app-specific error codes; when you read the crash reports, on the first 'page' you'd read "error in thread #xyz", further on you can scroll to that specific thread and find those cryptical numbers...

-60 reads in human lingo as

Code:

badMDBErr = -60, /*bad master directory block*/

useful? For engineers. perhaps :lol:

me no coder, but it points into direction, somethings wrong with the drive you're saving to ...
so, aside following Ronny's excellent advice (he's the expert, not me!), I would check a few things there:
• what sort of drive? a LAN-drive/'server'/'home cloud'/'time capsule'/…
• format of drive is…? hfs/ntfs/fat?
• let the DiskUtitlity tool (Apps/Utilities) check your target drive ...

Thanks for your reply. I am writing to a LaCie external Thunderbolt drive. It is formatted as "Mac OS Extended."

Patrick Cox wrote: ... I am writing to a LaCie external Thunderbolt drive. It is formatted as "Mac OS Extended."

so, item#3 in my list missing - run DiskUtility, to check/repair the drive ...