Rendered Clips Become Unrendered

I have been getting a lot of "Out of Memory" errors in FCP lately... Mainly with one particular project. I have the latest version installed, by the way.
My entire timeline (all footage in ProRes 444 LT) will render out--all but one clip. When I try to render it, I get the error. I will close other sequences and other applications. Sometimes this will fix the problem, sometimes not.
However, the crazy thing is that FCP has also started discarding my rendered files. It will happen when I load my project, having previously rendered all the clips. It wil also happen after rendering... I will render one clip, and after the process is complete, 10 other rendered clips will become unrendered.
Any ideas why this could be happening?

Perhaps because you are editing in a non-existant format? There is no ProRes 444 LT. There is ProRes4444 and there is ProRes 422 LT    My guess you are working in ProRes422 LT (more commonly designated as ProResLT around here)
Remove the proplematic clip from the project. It is likely corrupted. Does the program work as expected now? If yes and you need that material in the story, recapture/ reimport it from your backup. If you don't have a backup version, recut the project without it.
If the program is still misbehaving, shut down FCP and delete the FCP Preference files. (Digital Rebellion has a nifty little app -  FCS REMOVER - that will do this for you)
After you delete the pref files, the next time you start the program you will need to set things like the scratch disk locations.
Does FCP work as advertised now?
x

Similar Messages

  • Send Clip To Motion, becomes Unrendered Footage

    I sent my clip to Motion now in my FCP project the footage has become unrendered I have quit and restarted FCP and no luck, anyone know what the problem could be?

    If you want to continue with that method you should...
    use more that one video track, alternate each clip in an AB fashion, drag out the handles, then send.
    btw. so sorry for your second place finish
    o| TOnyTOny |o

  • Rendered clip playback problem

    Here's the problem: When I play back a rendered clip it freezes up on my NTSC monitor. In the viewer in Final Cut, it becomes a jumbled mess... lots of gray blocks... very pixely. It doesn't seem to matter what kind of clip it is; Motion file, still pic, etc.... The first time it did it, I deleted my render files for that project, shut everything down and started back up. Everything worked fine... for a while. The problem came back and nothing seems to be helping this time.
    I'm running a Dual-core 2.3GHz PowerPC G5 with Final Cut Studio 2. Any help would be appriciated.
    I hope I made a little bit of sense... at this point my brain is fried from trying to figure this thing out. I'm getting close to my project deadline.
    Thanks

    Thanks for the quick response. You've helped me figure out part of it.
    I'm editing on a DV NTSC timeline (footage is from a DVX100A). I just checked and the MOTION clip I used was saved in HD... so that explains that. The other types of clips that I'm having problems with are a still pic that has a little bit of keyframed motion to it (created in FINAL CUT) and some shots that I've slowed down. I've never had any problems with these before. Could the HD clip be affecting these as well?

  • PE8 - No audio in rendered clip

    I'm getting no audio after rendering, but do have sound before rendering. I've checked all the settings I know to check!
    The PE8 audio hardware preference is set to 'Premiere Elements WDM Sound'. Is this a device that should show up in Device Manager? If so it isn't there. No problems with sound on any video except for PE8 rendered clips. I'd appreciate some help.
    System:
    Win7 Pro, 64-bit
    ATI Radeon HD5850, Catalyst 10.2 driver
    ASUS P6T motherboard
    6 GB DDR3
    Core i7 950 (stock clock)
    BTW, PE8 bombs from time to time for no apparent reason. I gather from reading other posts that nobody else is having this problem? Ha! Also have Cyberlink PowerDirector but it rarely crashes. Sorry, had to get some gigs in.
    Thanks,
    Justin-H

    As far as PowerDirector goes, I have an older version (think it is 10, but cannot recall clearly), and it has actually crashed more than my PrE 4. Now, in all fairness, I use it to handle some really odd CODEC files, and basically convert with it, for editing in PrPro. My observations do not reflect either the newer versions, do not compare with PrE 8, and also include some very difficult footage. Still, it goes down about 1:5 sessions, while PrE 4 has only "hung it up" twice, and at least one was OE on my part, while the other was definitely a resource issue, as I did not utilize my own tips in this ARTICLE.
    Just some personal observations and not a controlled test,
    Hunt

  • Rendering clips

    I have made several movie/slideshows and have never had any problems. All of a sudden, after my children have been using it, I can not successfully make a movie with photographs. I started to create a new movie, and when I went to save it, it says that it is rendering clips. Usually it only takes a few seconds to render, but now it does nothing... just states that it is rendering clips. Can anyone help? Thanks!

    iMovie looks in your "Pictures" folder for the photos. When you use iMovie's photo browser it only presents the "thumbnail views" (very small reference copies of the originals).
    First when you render your project iMovie then uses the original photos to create the finished movie.
    You should have a folder in your Pictures folder called "iPhoto Library", this contains sub folders. At least one named with the year, inside that, one with the month, then one with the day. Further sub folders contain the "Originals" and "Thumbs". If any of these folders are renamed, moved or otherwise tampered with, iMovie (and iPhoto) will not be able to find the material it needs to do the job.

  • IMovie 10.0 contains glitch. Clips become tinted red when imported.

    Just throwing it out there. You are not alone. It was reported to Apple that some imported clips become tinted red in the newest version. A news article. If you would like to help, does anyone have a work around. I must finish an editing project and I've tried everything. After the first few clips, the rest are red. Tried restarting, quiting and reopening, every setting.

    I just found the solution for others experienceing this. It seems it happens most with .mov files. I changed to a mp4 by changing the file extension but iMovie still turned it red. The way I found is to convert it using SmartConverter in the app store for OSX to the iPad option.

  • Clips become partly invisible

    I'm having this strange problem with iMovie HD:
    Everytime I put clips into the clips sequence the last seconds of the clips become invisible. When put back into the clip viewing panel these last seconds become visible again.
    Sounds familiair to anyone?
    I'm using Snow Leopard. Does this have anything to do with it?

    Hi
    No not familiar - see if anything in my list helps
    *Not knowing the origin to Your problem - General approach when in trouble is as follows.*
    • Free space on internal (start-up) hard disk if it is less than 10Gb should rather have 25Gb
    • Delete iMovie pref file - or rather start a new user/account - log into this and re-try
    iMovie pref file resides.
    Mac Hard Disk (start-up HD)/Users/"Your account"/Library/Preferences
    and is named. *com.apple.iMovie.plist *
    While iMovie is NOT RUNNING - move this file out to desk-top.
    Now restart iMovie.
    • Hard disk is untidy. Repair Permissions, Repair Hard disk (Apple Disc Util tool)
    • Garageband-fix. Start it, Play a note and Close it. Re-try (Corrects an audio problem that hinders iMovie)
    • Screen must be set to Million-colors
    • Third party plug-ins that doesn't work OK (not relevant for iMovie’08 or 09)
    iMovie updated ?
    QuickTime updated ?
    Mac OS version ?
    • Program miss-match. iMovie 5.0.2, up to Mac OS X.4.11 AND QuickTime 7.4.1 - is OK
    • Program miss-match. iMovie 6.0.3 or 6.0.4, Mac OS X.4.11 AND QuickTime 7.4.1 - is OK (might work under Leopard)
    • Program miss-match. iMovie’08 v. 7.0.1, Mac OS X.4.11 AND QuickTime 7.4.1 - is OK (might work under Leopard)
    From LKN 1935. (in this case = iMovie HD (5), I tried it all, but nothing worked.
    Your answer (above) has been helpfull insofar as all the different trials led to the conclusion that
    there was something wrong with my iMovie software. I therefore threw everything away and reinstalled
    iMovie from the HD. After that the exportation of DV videos (there has not been any problem with HDV videos)
    to my Sony camcorders worked properly as it did before.
    Lennart Thelander
    I run "Cache Out X", clear out all caches and restarts the Mac.
    Yours Bengt W

  • When importing rendered clips from davinci into premiere they look darker and more contrasty.

    After importing the graded and rendered clips from davinci into premiere pro cc they look darker and more contrasty. I've checked the exported files from DaVinci and they look totally fine if you play them with any media player, but when I import them in Premiere Pro CC, they appear darker and way more contrasty than I've graded them in Resolve. Anyone have a solution for that?
    Thanks!
    Andrew

    This is a long-standing and complicated issue.  To start with, different media players interpret footage differently.  You can hope for the best, but there can be no expectation that footage in one player will look the same in another.  Ridiculous, but true.  The situation is further aggravated by different display cards and different monitors, and no prevailing standards of how color and levels are interpreted.
    In your specific case, you need to look at the waveforms, in Resolve and in PPro.  It sounds as if the blacks are being crushed in PPro, which could mean you're monitoring them at 64 in Resolve, but they're being output at 0 or remapped to 0 in PP.   This may also relate to whether you've monitoring with data or video levels in Resolve. 
    Is there a setting in PPro which covers how values are mapped, as data or video?  I think so, but just can't recall....  Anybody?  Staff?

  • Modified Files on FCPX... Random files in event folder(that I used to make a multicam clip) become modified and unusable. Is there anything i can do to prevent this?

    Since I upgraded to Mavericks, every time I create a multicam clip on FCPX, random files(that were used to make the multicam clip) become modified and unusable(in High Quality). Is there anything I can do to prevent this?
    I've tried transcoding, creating proxy media, creating optimized media, plus I've tried none of the above. Thing is, no matter what I do, it still happens(to random files) "after" I make the multicam clip. Is there a setting or something that was accidentally enabled by me or the upgrade?
    BTW: Everything seems to work fine when 'playback' is set to proxy. The problem is when I'm ready to export and switch 'playback' to High Quality.

    I had this same issue! But fixed it by going into the finder, finding the event, and delted the files out of the "High Quality Media." My project then refreshed to normal and no red modified file slides. The cool part: I din't even shut fcpx down to mess with the files in the finder. It all worked like a charm.
    Good luck!

  • Adding Dissolves in FCP after importing rendered clips from Color

    Hi,
    I'm editing a 4 minute sequence. I sent my edit to color, graded them accordingly, sent it back to FCP. I'm trying to add some cross dissolves between clips, but for some reason it is not allowing me to do so. Anyone come across this ?
    Trying not to get in depth into the problem, the reason I didn't add the dissolves pre-color grading, is that some clips have their speed reduced. The clips that had their speed reduced weren't being properly recognized in color. So, I had to remove the dissolves, bring back the clips speed to 100% and then send it to color for grading, send it back to FCP, reduce the speed of the rendered clip. Except, now I can't add the dissolves. As a matter of fact, I can't add any dissolves on any rendered clip, except for Fades.

    Specifying the addition and duration of "handles" is offered in the "Project Settings" tab of the Setup Room. The default value is one second.
    The reason that you cannot stretch the trims on the exported rendered footage is that it is new independent media with no relationship to your original source clip. I should add that handles can affect the computed time offsets of certain types of COLOR operations, which will throw those effects out of sync.
    jPo
    Message was edited by: JP Owens

  • Audio sync drifting in rendered clips

    I'm using Premiere Pro CS5.5 on a PC running Windows 7, 2.80GHz Intel Core i7 CPU, 6GB RAM, 64-bit OS.
    I am working on an interview I shot with 2 Canon DSLRs, a 500D and a Rebel T3i, using audio captured with an M-Audio Microtrack II. The audio was edited down in Premiere then rendered out and handed over to a third party to be cleaned up in Pro Tools. The length of the edited interview is just short of 4 minutes.
    When I preview in my Premiere timeline the audio is synced but when I render out the clip the audio drifts so that it starts already out of sync by a frame or two and by the end it's clearly off by a lot. I'm not sure how to proceed since the audio looks more or less perfect in my timeline.
    I'm really hoping somebody has some suggestions as this project deadline is tomorrow, I'm supposed to be just making minor fixes at this point but suddenly I'm dealing with an issue that has totally broken nearly half my video.
    Thanks

    I'm definitely working with a mess of a project. Frame rates is actually one of the things I'm looking into and there are a number of discrepencies in settings between, raw footage (30fps from the 500d & 29.9 from the rebel), sequence (29.9fps) and export settings (59.9fps). Unfortunately in the overall project I'm working with video from a number of sources so I'm starting with a number of different frame rates (in other sequences I have captured video game footage that is 60fps too). I'm still going to try and match them up as best I can and hope it helps. I'm just worried that the destination for these rendered clips is a pre-existing After Effects project where all the comps are 59.9fps, if I try to change those and that causes problems I could be looking at a pretty huge set back right before my deadline.
    To add a little more detail, the problem seems to be getting progressively worse. In early renders there was no sign of an issue, then yesterday during a review we noticed it was slightly off so I thought i fixed it did a render last night and when I checked it this morning it was as I described in the first post. I have at least 3 or 4 early renders where the problem was either not there or so slight it's hard to notice. The really weird thing I've discovered, if I put the rendered clip back in premiere it syncs up, but if I play it in quicktime or use it in After Effects (the next step in my workflow) it doesn't. Guess that could still have to do with frame rates. We'll see.
    Thanks for the tip

  • Rendered clips turned out to be not render after premiere pro update

    Hello guys,
    I was using the old version of premiere pro for quite awhile, then my colleague told me to update it to the lastest to fix any bugs that exist.
    so I updated my premiere pro to version 4.2.1.
    After the update, I realised all the rendered files became not render. the timelines were all red and the program did not prompt for the rendered clips when I open the projects. For what I know, the rendered clips are still in the folder 'Adobe Premiere Pro Preview Files.'
    I am really desperate for help as the amount of clips rendered is really a lot. I appreciate any help, thanks so much.

    Welcome to the forum.
    It sounds like the update might have separated the Render files from the Project's links.
    Now, remember that Rendering is only necessary for the smoothest playback. You only have to Render, where you are working with critical aspects, like Keyframing Motion/Scale, or adding Effects. I complete many Projects, and never bother to Render, as I can see playback at a high enough level to do my editing. OTOH, there are often tiny segments, that might get Rendered many dozens of times - usually where Keyframing was done.
    One can use the WAB (Work Area Bar) to just Render a small segment of the Timeline.
    Now, why your existing Render files became un-Linked, I do not know that answer.
    Good luck,
    Hunt

  • Clips always unrendered and offline when project is loaded

    Having a weird problem at the moment that seems to make no sense at all, so any help would be vastly appriciated. Currently have a project where everytime it is loaded up all the footage with effects on, or with titles, says media offline, despite the clips still being avaible and accesible within the program. However, when any variable is clicked in the Effect Control panal on a clip, for example the clip's Scale, the clip comes back, but unrendered. When I say click on any of the variables I don't mean change any of them, just the simple act of clicking on the number 100 next to Scale brings the clip back. Bizzarre to say the least! Obviously this is starting to get very annoying, as the act of clicking on every clip's Scale and rendering before any new work can be done on the project is getting very tiresome...
    Any help?

    Are you perhaps experiencing this issue?: FAQ:Why are my clips showing as "Media Offline"?
    Cheers
    Eddie

  • Unwanted strobe effect showing on rendered clips - Adobe CC 2014

    I'll try and describe the issue as best as possible - I haven't been able to find any similar issues by googling or on forums.
    As a bit of information about the project it's adobe CC 2014 with a mix of c100, c300, Gopro and various other footage so a mix of .MTS, .MXS and Mp4 files. All stored and edited from external hardrive via USB 3.
    I started out by having red frames appear when I scrubbed through footage on the timeline, and then they appeared in the actual exported file - which from googling seemed to an issue with media encoder not being able to render the source clip properly.
    As part of the fix which seemed to work to get rid of the red frames I moved the media cache files from their default location users>library>applicationsupoprt>adobe>common to a render folder which I created on the external hardrive. To be specific I manually deleted media cache and media cache files then created the folder on the external drive and directed adobe to put the files there. That got rid of the red frames but a few days and a different project later I started getting a strobe like effect where every other frame on a few (seemingly random) clips is black, except for the top left corner which shows the image in part. When the footage is unrendered (red on timeline) it plays back fine. When it's rendered the strobe effect happens everytime on playback and with export. All clips it happens to are c300 clips, but there are plenty of c300 clips in the timeline it doesn't happen to. All clips have the same effects on them.
    I've made all clips offline, and reconnected media. I've uninstalled and reinstalled adobe CC desktop and all apps about 3 times and used Adobe cleaner to get rid of files then reinstalled. Nothing seems to work. I have noticed that even though the media cache files are redirected to the external drive now, it still creates a media cache folder in the default location and puts some render files there. Perhaps it's something to do with these duplicate render files???
    Hope that makes some sense.
    Anyone else had this happen?
    Any help/advice would be much appreciated. It's for a TVC and needs to be delivered next week.

    Thanks Simon, I think you're right.
    I seem to have narowed ig down to being a combination of the 'warp stabilisation' effect plus a vignette (made from black video and 'circle' effect). 
    Whenever these effects are both on, and the clips are rendered I get the strobe effect, but if one or the other is off I don't anymore.
    At least I can export the edit with warp stabilisation effect, and then add the vignette to the exported clip - not ideal but a work around.
    Hope it get's fixed soon.

  • How to reduce re-rendering clips in Premiere Elements 12

    Each time I restart a Project in Premiere Elements 12 the timeline indicates that I need to re-render the clips. Is there away to avoid excess rendering? Thanks.

    don_
    Your question is a long standing issue that seemed to have peaked around Premiere Elements 8.0/8.0.1 and seems to be independent of computer operating system, scratch disk locations, and QuickTime versions among other things. And Adobe has not come out with an explanation to date as far as I have ever seen.
    But, let me make sure that I am interpreting your question correctly.
    Are you saying that, after you save/close a project whose Timeline had been rendered for preview purposes, the re-opened project presents with an orange line over the Timeline content with the implication that you are looking at an unrendered Timeline? If that is the case, please read on.
    I will dig out the unabridged version of what I have written about this in the past. But, for now, the abridged version.
    1. Although the color indicator implies that the Timeline content is "unrendered", that is, you are not getting the best possible preview of what you are seeing in the Edit Mode monitor preview, the preview files that were originally generated are alive and well in their hard drive save location. Best guess is that the link between the preview files and the project are getting broken and are not repairable, short of rendering the Timeline content again if absolutely necessary for preview purposes.
    2. In the re-opened project, rendering again to turn the orange line to green (best possible preview) can be done for the whole of the afflicted content or selectively (just segment) by setting the WorkArea Bar gray tabs to span just the area to be rendered.
    3. My philosophy on this is to move on or re-render all or part if indicated. You have rendered the area previously and should know what that is going to look like...unless of course you make changes in the re-opened project.
    This one has an unforgetable history going back several versions and apparently surfacing again in the present and still without the whys.
    Please review and let us know if I have targeted you question.
    Thanks.
    ATR

Maybe you are looking for