Corrupted clip freezing FCP X during background rendering.

When I open a particular project, the background rendering starts up and gets to 35% where it then freezes the whole job.
Had to do a Force Quit.
This first occured during colour/exposure modifying, btw.
On start up of FCP I can review the video in the project window and see that a small part of one clip is corrupted, but as soon
as I open FCP (10.0.7) it attempts the backgound render before I can stop it, there-upon freezing.
Can the particular offending clip be successfully removed before I open FCP?
15" MBP with retina display, OSX 10.8.2
Thanks in advance.
Andrew

BenB
Thanks for that - "selected", but not "opened" I see.
Also, I reckon they should change the confusing menu item "Project Properties" to straight "Projects" Yes-No?
RussH
The particular clip would jump around - black frames-out of position frames -staccato playback.
As I said, this was after I'd tried colour adjustments that wouldn't render beyond a certain point.
Thanks for that lead to Pro Maintenace Tools. Does it work specifically with FCP X? Will check it out.
I do have the very handy Event Manager X.
Thanks all

Similar Messages

Background Rendering in FCP 10.2 is not working

Is anyone else having an issue with background rendering not working in the new FCP 10.2 version?
In fact even the render all function doesn't seem to be working properly since I upgraded. It only appears to be rendering small pieces at a time.
It won't render the whole project out like it's supposed too. Have to keep pressing the Control, Shift, R keys over and over to get it to completely render out the sequence.

Try turning off BG Rendering and turning it back on.
If you have multiple projects in a single library, try another existing project or create a test project; (add some clips with effects to get render bars). If they render, select the first project and choose Delete Computer Generated Project Files.
Russ

Any suggestions for re-rendering corrupt clips?

My current FCE project - 2 hours, 40 minutes - refuses to be exported to a QT, self-contained movie. I get a "General Error" message about 13% of the way through and I suspect currupt clips somewhere.
In the FCP forum on this topic there are suggestions to use a 'tool' to erase all renderings and then re-render to deal with corrupt clips. I see no such option in FCE. Does anyone know of one? Or what the workaround is?
Another suggestion to someone else with similar symptoms here - or in the FCP board - was to cut the sequence up and export it in sections. I tried that and was able to do it for one of three sections.
I have no idea how to find corrupt clips, if that's the key.
any help would be appreciated.
Thanks...
- Whitw

Find your render files on your media drive and trash them. Then re-render the sequence.

Background rendering when iMac is in standby mode

After I have imported a video file from my Sony HDR Z1 FCP X starts to render in background mode, when I am using the iMac all is fine but if I leave it overnight and the iMac "goes" to sleep" the rendering also stops. Is there a way to stop this so I can leave the machine to complete what it is doing before it goes to sleep?

When the machine is asleep, it is asleep, period.
If you want to give it time to finish rendering before it goes to sleep, open System Preferences->Energy Saver,
click on the "Schedule..." button and set a time for it to go to sleep.
Note: Depending on your mac and the content you are editing, you may not need background rendering at all. Many people prefer to leave background rendering off, and only render specific portions if the playback is not smooth (for instance if you have some effects on a given clip, that your mac cannot play well without rendering, you may want just to render that clip).

Help! FCP crashes during H.264 export!

Hi All,
I am using Final Cut Pro 6 and need to create a Quicktime movie file that is under 2 GB in size. The film is 2h 3m. The frame size should be 480x270 and 24fps. I am using H.264 as my compressor. To accomplish this, I am exporting from FCP using “Export with Quicktime Conversion”. I don’t know a whole lot about compression, so I have pretty much been experimenting. First I exported using the Bitrate setting as Automatic, but the file was over 5 GB. I then set the bitrate to restrict to 750kbps and the resulting file was 660 MB. However, I wanted to push it to right under 2 GB, for the best possible quality. I tried again with the bitrate restricted to 2000kbps. However, it takes so long to render on my computer (a few days each time), and happened to lose power during this render. So, since then, I have tried various times with these same settings, and every time FCP “Quits Unexpectedly.”
Since then I have tried various things to try to isolate the issue and determine what the problem is:
I have deleted all old render files, reset permissions and trashed preferences, and still FCP crashes during export.
I tried exporting a different piece of footage (30 second clip) with the same settings and it works great.
After breaking apart, rendering, seeing if it crashes, cutting that in half, rendering that, seeing if it crashes, etc., I've determined that the problem is happening in the last 15 minutes of the film.
I've been rendering with these attributes:
Compressor: H.264
480 x 270
2000kbps bitrate
AAC audio
I took that section of the film that was crashing on render and rendered just the audio and it worked fine. Then I rendered just the video and it crashes, so I've determined it is the video.
I tried rendering at a different bitrate with the H.264 codec and it still crashed during render again.
I also just rendered with two different other video compressors: ProRes 422 HQ and HDV 1080p24 and both rendered that section of the film fine.
This would leave me to believe that it is the H.264 codec at that one section of film crashing. Any idea why this might be, or how I can fix it?
Here are my conclusions:
-It occurs in the last 15min of the film
-Only occurs to video, not audio
-Only to H.264 codec
-Doesn't matter what the bitrate is at
-Deleting old render files doesn't fix it
-Trashing Prefs and resetting permissions doesn't fix it
-First noticed it after I tried rendering after my previous got killed due to a power loss in the house
If anyone has any input, I would greatly appreciate it! I have been dealing with this for weeks now and can't discover the problem. I am on my knees praying and begging because this whole film is caught up with this. I appreciate all and any suggestions! Thank you in advance and have a great day!

Thanks for the response!
I took the last 15 minutes, broke that into two 7-8 minute sections. Tried both and both crashed. Then took the first of those two sections (which I call 15/16 since it is the 15th section if the film is broken into 16 equal pieces) and cut that in half, so it was about 4 minutes long, and that crashed as well. The way the film was made is each scene is it's own sequence, and I then have all those into one full sequence (I'll reference that as TMUG-completed). That one sequence is then another sequence (TMUG-condensed), so I can then bump up all audio at once.
I have taken the sequence TMUG-completed, copied it, and pasted that into a new timeline, and rendered, but still got the crash. And all the render files have been removed as deep as they can go, going back to the individual scene render files.
Since each scene is it's own sequence, I can see that the problem is happening over multiple scenes.

Background rendering.

Hi, I've started using the trial version of Final Cut Pro X and have a question...
Background rendering is taking up LOADS of disk space.
Why isn't the rendering overwriting itself?
A 5 minute film shouldn't have to fill over 65GB of disk space, should it?
And, is it possible to delete a clip in iPhoto, that has been imported to
the project in Final Cut Pro X without it dissapering in the project as well?
Best regards,
Adam.

adji00 wrote:
And, is it possible to delete a clip in iPhoto, that has been imported to the project in Final Cut Pro X without it dissapering in the project as well?
As Tom said, this depends how you imported it. If you're not sure, select the clip and press Shift+Cmd+R to reveal the clip in Finder.
Depending how you imported the clip, the one you see here may be an alias (just a few bites in size). Right-click the clip in Finder and if you see the option to 'Show Original', the one you're lookinng at is indeed, an alias. Select 'Show Original' - it will probably be in an iPhoto folder.
If you don't see the option to 'Show Original', and the finder clip is more than just a few bites in size, then it's the original that FCP X is using and if deleted, will go offline in FCP X.
Andy

Clips freezing

I've begun making a movie via iMovie '08 and am having a problem with parts of clips freezing. It seems like every few clips, the clip freezes. I've been working on this for days and can't figure out what's going on. I go in, split the clip, delete the frozen part and continue on.
Anyone know where the problem may be? I'm using a new Sony hard drive mincam, had no trouble downloading the movies, etc.
Thanks!
susan

I am actually having the same problem. For what it's worth, it only does this when you play the project in iMovie. Once you export the project, it sews the clips together seamlessly and there is no "freeze" at the end of each separate clip during playback.
I'm not sure why it does this before rendering. My clips are tiny (file size and duration) and they reside locally on my Mac (with a 7200rpm hdd), so it's not likely this delay is caused by seek time to pull the data for the next clip.
We would appreciate some help if anybody has found a solution.

Background rendering? Oh REALLY? Who's Apple kidding?

One of the things I was looking most forward to, was - to quote the infamous Supermeet presentation: "Never ever have to wait for rending no more!"
It's just that, to my best knowledge, there really is absolutely NO background rendering going on NOR is it any different from the auto rendering we had in FCP 7. Just at bit more automatic, perhaps.
To me, the definition of af background task is something that continues while you continue your work. I'm positive that most people hear this in FCP X as in "so it will do the rendering in background, so you don't have to wait for it".
But wait........
- If it's a background process, while does it stop when we continue working ? That's no background task to me! Is it?
- If it's something so new, that it has to be accompaniet with "never have to wait no more", why is it almost 100% the same as we already had in FCP 7?
Two me, there seems to be only two very small differences:
- in FCP X you can set the time limit where in FCP 7 you had to stick to the, what, 15 minutes delay in this process starting automatically
- in FCP X you can pause the rendering temporarily just by doing anything in FCP X, where as in FCP 7 you had to click cancel to halt it
So the conclusion to is, that you most definately still have to wait for rendering, as you cannot finish you project before you completed the wait........
Background rending? Oh REALLY? Who's Apple kidding, anyway?

why is it almost 100% the same as we already had in FCP 7?
This is just incorrect. First, the technology in FCP is vastly superior to 7. The speed is substantially faster. It is not analogous in any meaningful sense to auto render. In addition, once render initiates, it does not actively have to be stopped by the user to continue working, nor does it have to be re-initiated. The process is seamless.
Indeed calling it background rendering is marketing hype and it is not in background in any true sense. However, it's relationship to what happens in 7 is zero. The two differences are minor. The real differences are in the processes ability to access new techology, using more RAM, more processor power, more graphics processing, and more modern OS technolgies. That's the real difference.

Importing Flip and iPhone clips into FCP

What is FCP's preferred video format?
I have a funky project consisting of clips from iPhone and a Flip Mino HD camera. When either of these are imported directly into FCP, they won't play without rendering, and any edit or trim "undoes" the render, forcing them to be rendered again... and again...
I'm guessing the best strategy is to convert them -- before importing -- to a format that FCP will like better and will play smoothly, without constant re-rendering.
So: what's the best format to convert them into, and what's the best tool for doing that pre-conversion?
Or am I wrong, and is there a way to handle these Flip and iPhone clips in FCP without pre-converting them?

Okay, that seemed to work. Thanks!
But now there's a new, odd problem: I can't add transitions! After dropping these new clips in the timeline, they play fine without rendering... but whenever I try to add a transition (dissolve, wipe, etc.) between clips, FCP changes the 1 second transition to a 3 frame transition. And there doesn't seem to be any way to change the duration - no matter what I do, it keeps changing back to one frame. Strangely, I can add the normal transition to the end of the sequence, but not between clips.
Am I missing something? Does the DVCPRO50 progressive format somehow prohibit modifications like transitions?
(And should I start this as a new topic?)

Export 1 clip to FCP bin

Is it possible to import a clip from the Cinema Tools database into FCP bin? It seems that FCP wants only to import a CT log, not directly from the CT database, so in order to bring in one clip into FCP (a clip which was already in the CT database) I had to manually edit a log so that it only showed the one clip and then use the FCP CT import log feature, which made a second copy of the clip in the CT db log, which seems kind of redundant and wasteful. Why can't I just bring in one clip (CT to FCP) without these complications?

[Roundtripping is so not on my feature list...]
Out of FCPX, simply Share > Export Movie as ProRes, any "flavor" (even Proxy should have adequate bandwidth for excellent results.) [Don't confuse proxy media in FCPX with ProRes 422 Proxy which is a full resolution format that has a bandwidth of approximately 45Mbps for 1080/30p video. Proxy media in FCPX is ProRes 422 but 1/4 resolution (i.e., 1080 video is downconverted to 960x540.)]
You can drop the video into Motion (set your project to accommodate the length of the clip, or all the clips you need), do your thing, then Share > Export out of Motion and bring the video back into FCPX.
The way I figure it, the difference between the "new way" for Motion 5 and the old roundtripping is maybe one extra rendering.
With Motion 5, you don't need the video from FCPX. You design your effect and as soon as you save it, it's available in FCPX. There is a placeholder provided (with the exception of generator templates, for which they are simply not necessary.) If you need a "reference", you can export a still and load it into the placeholder while you design, then delete it when your finished.
The way Motion 5 and FCPX work together is so much better and more efficient than the old way of FCPStudio roundtripping.

Final cut pro x freezing while trying to background render. Won't budge.

Final cut pro x and my brand new computer is freezing while trying to background render. Help!!!

I can't give any specific advice but try these general FCP X trouble-shooting suggestions.
Use this free app to trash the preferences. This should be the first thing you try when any problems occur.
http://www.digitalrebellion.com/prefman/
2. Open Disk Utility and Repair Permissions.
3. Trash FCP X using this free app and reinstall it.
http://www.digitalrebellion.com/fcsremover/
If these 3 measures don't work, create a new User Account (Admin) in System Preferences and try running FCP X from that as it sometimes works miracles.

IDVD quits unexpectedly during menu rendering. I have burned a similar project before and it worked just fine. Suggestions?

I have iDVD for iLife'11. Every time I try to burn my current project, iDVD unexpectedly quits around the same time during the rendering menus process. My macbook pro is practically brand new, and I have succesfully burned a very similar (and larger) project before with no problems. Does anyone know how to fix this issue?

Hi
My first thoughts
• free space on start-up (Mac OS) hard disk - less than 25Gb (not probably on a new Mac Book Pro)
• corrupted iDVD Pref file - trash it and re-start iDVD. (Or even better - start a new User Account and log into this and re-try - this forces Your Mac to do lot's of new error free pref files.
• corrupted project - Start a brand new one - Don't use old problematic one
• jumping from iDVD back to movie editor - results in iDVD BUG. Start a new iDVD project - or trash movie in iDVD and clean Media Assetts. Then re-try.
Yours speculating. Bengt W

Message: The following clip encountered an error during import and is still referencing media on the camera:

I am getting this message when I try to import files from Canon C100: The following clip encountered an error during import and is still referencing media on the camera:
These are AVCHD files and it seems to be happening randomly. With different clips as I try to import...happening both with regular importing and with Create Optimized Media...
It just started happening yesterday-never had this problem before and have uploaded countless times with this camera and system. THanks.

Update: OK, I just tried to import the footage into another hard drive (an internal hard drive) and it seems to be going fine now. Maybe something is corrupted on the external hard drive I was importing into...wierd.

Stalling:Error in background rendering so switching to foreground rendering after 0 frames completed

Our facility is running AE CS6 ver 11.0.0.378 on 8 core Mac Pros with 32 Gb ram running OSX10.6.8
using Thinkbox Deadline 5.2 for distributed rendering to other 8 Core Mac Pros with 32 Gb ram.
The issue is that we are in crunch mode trying to deliver 4K comps (soon to be 8k comps) and we are experience substantial
delays 10-20 minutes after the AERENDER starts, but before it starts doing any fruitful rendering.
We are reading from and writing to Quicktime movie files (which normally works just fine for us) and thus the entire frame range needs
to get computed on a single host.
The symptom is that many comp jobs (but not all) stall for a while with no apparent actibity before spitting this messgage, but then happily
and swiftly complete each frame in a second or less with no errors:
0: STDOUT: PROGRESS:   There is an error in background rendering so switching to foreground rendering after 0 frames completed out of total 576 frames.
0: STDOUT: PROGRESS: 00001 (1): 20 Min, 16 Sec
0: STDOUT: PROGRESS: 00002 (2): 1 Seconds
0: STDOUT: PROGRESS: 00003 (3): 0 Seconds
0: STDOUT: PROGRESS: 00004 (4): 1 Seconds
0: STDOUT: PROGRESS: 00005 (5): 2 Seconds
0: STDOUT: PROGRESS: 00006 (6): 1 Seconds
Given that the delay, seems to be related to the number of frames (350 frames creates a 10 min stall and 576 frames creates a 20 minute stall), it seems like it's trying to do something for every frame in background mode, before it gives up and does them quickly
in foreground mode. During this time, there doesn't seem to be any signficant CPU or Network or IO activity. I looked for command line args that might force AERENDER to foreground mode, but didn't find anything.
Here's what the digested submission args look like.
0: INFO: Startup Directory: "/Applications/Adobe After Effects CS6"
0: INFO: Process Priority: BelowNormal
0: INFO: Process Affinity: default
0: INFO: Process is now running
0: STDOUT: PROGRESS: 12/6/12 10:37:54 AM PST: Starting composition sc20_assem_R_v57 .
0: STDOUT: PROGRESS: Render Settings: Best Settings
0: STDOUT: PROGRESS: Quality: Best
0: STDOUT: PROGRESS: Resolution: Full
0: STDOUT: PROGRESS: Size: 1200 x 860
0: STDOUT: PROGRESS: Proxy Use: Use No Proxies
0: STDOUT: PROGRESS: Effects: Current Settings
0: STDOUT: PROGRESS: Disk Cache: Read Only
0: STDOUT: PROGRESS: Color Depth: Current Settings
0: STDOUT: PROGRESS: Frame Blending: On for Checked Layers
0: STDOUT: PROGRESS: Field Render: Off
0: STDOUT: PROGRESS: Pulldown: Off
0: STDOUT: PROGRESS: Motion Blur: On for Checked Layers
0: STDOUT: PROGRESS:
0: STDOUT: PROGRESS: Solos: Current Settings
0: STDOUT: PROGRESS: Time Span: Custom
0: STDOUT: PROGRESS: Start: 00001
0: STDOUT: PROGRESS: End: 00576
0: STDOUT: PROGRESS: Duration: 00576
0: STDOUT: PROGRESS: Frame Rate: 23.976 (comp)
0: STDOUT: PROGRESS: Guide Layers: All Off
0: STDOUT: PROGRESS: Skip Existing Files: Off
0: STDOUT: PROGRESS:
0: STDOUT: PROGRESS: Output Module: APR_422HQ - Millions
0: STDOUT: PROGRESS: Output To: /Volumes/Renders/Scenes/20/sc20_assem_R_v57_r1_2k.mov
0: STDOUT: PROGRESS: Format: QuickTime
0: STDOUT: PROGRESS: Output Info: Apple ProRes 422 (HQ)
0: STDOUT: PROGRESS: Output Info: Spatial Quality = 100
0: STDOUT: PROGRESS: Include: Project Link
0: STDOUT: PROGRESS: Output Audio: Off
0: STDOUT: PROGRESS: Channels: RGB
0: STDOUT: PROGRESS: Depth: Millions of Colors
0: STDOUT: PROGRESS: Color: Premultiplied
0: STDOUT: PROGRESS: Resize: -
0: STDOUT: PROGRESS: Crop: -
0: STDOUT: PROGRESS: Final Size: 1200 x 860
0: STDOUT: PROGRESS: Profile: -
0: STDOUT: PROGRESS: Embed Profile:
0: STDOUT: PROGRESS:
0: STDOUT: PROGRESS: Post-Render Action: None
We're under the gun to get this production delivered, and these delays are killing us. I worry when we switch to 8K comps
that the "fruitless delay time" will just get longer.
I'm currently trying to correlate the plug-in assortments in effect for the shots that exhibit this behaviour. Clearly in "foreground mode" the machines are capable of rendering the shot quickly.   We've speculated, that posibly some plugins may be GPU or OpenGL accelerated (these machines have ATI Radeon HD 5770 cards) despite the fact that AERENDER probably doesn't require special graphics cards).
Anyone have any ideas, especially if there is some way for force the foreground mode from the start?
Regards,
Jay Production IT Support.

Just to follow up, Our compositing supervisor was still convinced that running with MP was the way to go, so I worked
with him to run some benchmarks on medium and heavy shots that we determinied would trigger the issue in -MP mode.
The test scene was about 50 frames in length, and we ran it on the same hosts with -MP on and -MP off, and also ran a
version of bundled frames (10 frames per host/task) and another where we did all 50 frames on a single host (with and without MP).
Interestingly, in every scenerio of these 4 cases, the version with -MP on, was 2-15% faster (despite the 10-11 minute delay at the start in MP mode).
His conclusion was it's still faster with -MP mode ON, and requested that I continue to explore for patches or theories how we might get around the delay.
Have read links:
http://forums.creativecow.net/thread/2/1025525
http://helpx.adobe.com/content/help/en/after-effects/using/memory-storage1.html
Regards,
-Jay-

What is background rendering? Should I use it?

Sorry for the probably very basic question, but I recently started using Premiere Elements 8 (was using 3 before) and I am not totally clear on the purpose of background rendering even though I have read the faq's and Adobe help descriptions of it.
Is it just for viewing the clips once they are in the movie? Or does it actually affect the final product? Do I need to wait for background rendering to complete or do it by pressing entere before I watch a clip that I have just placed into the sceneline or timeline? Just would like to know what the general purpose of this is and whether I should use it.
(Right now I am working with some old Motion Jpeg files which I have convereted to DV-AVI, but later I plan to use mostly mts files from my camcorder.)
Thanks in advance for your help.

Tech_Savvy,
Good explanation on Rendering.
Some folk do it constantly for that smooth playback. Personally, I will only Render small sections (by setting the WAB), when I am working on Keyframes, of custom animations and Transitions. These, I want to see as smoothly as playback will allow.
The drawback to Background Rendering is that it does take resources. On a fast computer, the user might never even know that it's going on. With a slower computer, the GUI will seem to hang, while this Background Rendering is going on, and any change will trigger it. I do not have PrE 8, but would turn this off, even on my very fast workstation, and manually Render, just the sections I need to preview, when I need to do so. That's just me.
Going back many years, Pinnacle added this feature to Studio. It caused so many problems, though I have to admit that computers were a lot slower then. Most users could do nothing in the program, while the Timeline was being Rendered. Everyone, who I knew, turned it off and never looked back.
Thanks for the inclusion,
Hunt

Corrupted clip freezing FCP X during background rendering.

Similar Messages

Maybe you are looking for