FCP freezes when rendering and exporting (HD)

2 x 2.66 dual core intel with 1 go 667 DDR2 FB-DIMM, ATY,RadeonX1900
Ok Got this project with green screen (conduit) and a motion template spiral title thing. When I tried to render the whole sequence it would freeze half way there. Then I rendered one cut at a time finally got it to be rendered the I try to save as quicktime movie as is and when it's at 90% its freezes.
Recently I upgraded but didn't do anythigne mush different then usall. Help me got a bunch of other green screen to do.

Read up on setting up 'Virtual Clusters' in compressor. This works extraordinarily well with an 8core Mac Pro.
No real benefit within FCP, but within Compressor, the thing screams.
x

Similar Messages

  • Adobe Premiere CC Crashes When Rendering and Exporting

    Even with a simple sequence. Files are .mts from a GH2 camera. I never had this issues before with Premiere Pro.
    Error report:
    Process:         Adobe Premiere Pro CC [458]
    Path:            /Applications/Adobe Premiere Pro CC/Adobe Premiere Pro CC.app/Contents/MacOS/Adobe Premiere Pro CC
    Identifier:      com.adobe.AdobePremierePro
    Version:         7.2.0 (7.2.0)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [166]
    User ID:         501
    Date/Time:       2013-12-15 11:35:18.870 -0800
    OS Version:      Mac OS X 10.8.5 (12F45)
    Report Version:  10
    Interval Since Last Report:          151219 sec
    Crashes Since Last Report:           12
    Per-App Interval Since Last Report:  1430 sec
    Per-App Crashes Since Last Report:   1
    Anonymous UUID:                      FECDFAEE-2196-A4B1-9E85-BEEF74626DBD
    Crashed Thread:  26  Dispatch queue: com.apple.root.default-priority
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x000000009def0488
    VM Regions Near 0x9def0488:
    -->
        __TEXT                 0000000100000000-0000000100003000 [   12K] r-x/rwx SM=COW  /Applications/Adobe Premiere Pro CC/Adobe Premiere Pro CC.app/Contents/MacOS/Adobe Premiere Pro CC
    [Please don't post full crash logs to the user forums.]
    Message edited by Jim Simon

    Just that one project, or any project?  Can you create new projects?

  • General error in FCP re: rendering and export  after Quicktime 7.5.5 update

    Hi
    My FCP 6.0.4 rendering and export to Compressor no longer works after an update to Quicktime 7.5.5.
    Rendering fails after a few seconds "General Error!" pops up. Exporting to Compressor, after setting it compressing, Compressor after a few seconds fails. (audio is processed) My current work around is exporting a sequence using Quicktime conversion (time consuming) and then opening in Compressor.
    I've done the usual, deleting prefs, new sequences and projects, even saving movs in different codecs.
    (been using H.264)
    My sequences are all custom sizes but tests using presets also fail.
    Any ideas anyone?
    And I was so happy the Quicktime upgrade could play sequence movs recorded months earlier that until now I couldn't play properly due to previous Quicktime upgrades!
    Apple gives with one hand and takes with the other....

    Hi There,
    Thanks for your reply on this.
    Well basically since I'm using content already in the H.254 codec (eg: a trailer off the internet, or the downsizing of HD footage) i'm just exporting to a codec that didn't have to be rendered and gave quality results. I used motion jpeg B as an export codec because it was quick (although HD space hungry) with no drop in quality. The resulting exports could be imported into a custom sequence (720 x 405) as square pixel aspect ratio files. Overlapping the canvas with other windows (eg: viewer) meant I could play a clip (with dropped frames) but not have to render it. I selected the H.264 codec as the sequence codec because I've found other codecs introduce darkening or lightening or blurring or other undesirable artefacts when exported to Compressor. H.264 used in the sequence settings exported through Compressor would give resulting m2v's as sharp and contrast accurate as the source file.
    That was until the recent 7.5.5 Quicktime update where attempts to do the same things I did before result in "General Error!" coming up after a few seconds of play or rendering.
    Traditional DV codecs are "blurry" in my opinion, especially when coping with web content or conversion of HD downloads.
    If you can suggest an editing codec that works best with FCP that is quick, doesn't introduce blurring or general degrading of the image I'd be happy to try it out. I typically downsize HD content from the web for DVD playback, so it's usually in a H.264 codec already. So i would need a codec for export from Quicktime that would work best with a codec in FCP. That doesn't alter picture quality when compressed to m2v in Compressor.
    Thanks!

  • FCP 5.0.4 freezes when rendering or converting to quicktime on my macbookpr

    FCP 5.0.4 freezes when rendering or converting to quicktime on my intel macbookpro. It really is very bothersome because I can't complete projects without rendering. I recently was just told that we should not download any updates at all for any appliction unless it is absolutely neccessary. Is there any truth to this. Would I be better off doing a complete erase and install to get rid of all updates that I have installed. My mac book is a 2.4 ghz with 2 gigs of ram, 200 gb hd, and 512 of vram. Help! My dead line is approaching.

    What you've heard about Academic versions is correct. They are not upgradable.
    If you want to run a version of FCP that is compatible, you have two options.
    1. purchase a used PPC computer (G4/G5) and run your version of FCP 5 on it.
    or
    2. purchase a version of FCP designed to work on intel processors (v5.1 or higher).
    #2 can be satisfied by purchasing a used version of 5.1 (full retail install) on ebay. Alternatively, if you qualify for academic pricing, FCS3 can be had for around $900 rather than the $1300 for the retail version.
    On another subject, the MacBook is hardly the ideal editing platform no matter what version of FCP you are running ...
    x

  • Premiere Pro CC - Playback issues, rendering and export

    Adobe Premiere Pro CC 7.2.2
    Computer: HP Elite Book
    OS: Window 7 Professional
    RAM: 8GB
    Intel I7 Processor
    64 Bit Operating System
    Intel HD Graphics Card
    250 GB Computer, 39.2 GB Free
    Hello all -
    I am trying to edit, render, and export a video for play on YouTube.  The source is a Camtasia Studio 8 Screen capture with a 1080P High Defintion PTZ camera that is hooked up to the computer as the "webcam".  We recorded the screen, used Camtasia to produce and edit, and saved it as a .MOV
    I then transferred the .MOV to my computer and opened Premiere Pro CC.  I have been watching a lot of YouTube videos and have a read a lot of threads, so I decided that a simple edit job would be the easiest and fastest.  I have attempted this 3 times now, each try has been a failure.
    Attempt 1:
    Opened a new project.  Imported my video.  Dropped it into a sequence.  Added an opening and closing title card, plus lower third captions to video, and added transitions.  Playback was choppy, so I read that it needed to be rendered.  I rendered the sequence (it took most of the evening).  When I went to play it back, I just got footage that said "Media pending" in 7 different languages.
    Attempt 2:  I decided not to render, just export.  Followed the steps above, but instead of rendering, and exported it.  I exported as media file, chose the TechSmith Capture Codec, and .AVI as the format.  Let it do it's thing.  The result was very fuzzy, plus the audio was about 10 seconds out of sync from the video.
    Attempt 3:  I didn't get very far here, because when I started playback to check my audio syncing, my computer started flipping between Premiere and my desktop, just swtiching back and forth.
    Any help here, suggestions, would be very much appreciated.  I need to post this video for work as soon as I can.
    Adobe Premiere Pro CC 7.2.2
    Computer: HP Elite Book
    OS: Window 7 Professional
    RAM: 8GB
    Intel I7 Processor
    64 Bit Operating System
    Intel HD Graphics Card
    250 GB Computer, 39.2 GB Free

    Camtasia http://forums.adobe.com/thread/836800 may help
    -and Lagarith Codec http://forums.adobe.com/thread/1287577
    -and http://forums.adobe.com/thread/775288
    -and http://forums.adobe.com/thread/453044
    -and http://forums.adobe.com/message/3202148

  • HELP: Premiere Pro CC not using all CPU and RAM during rendering and export

    Hello,
    I am using Premiere Pro CC on a Windows 7. My timeline is quite simple with two videos, one with the movie (mpeg) and the other with the subtitles (avi).
    When I render the sequence in PP or export, the rendering time is way too slow and it only uses around 15-20% of the CPU and 3 GB of RAM.
    My hardware config is :
    - CPU : i7-4770k 3.50Ghz
    - RAM : 8 GB
    - Disk : 2 x 3 TB SATA (no raid)
    RAM is not the bottleneck, neither the disk access.
    I have tried rendering and exporting the same project on an iMac (with an i5 2.7 Ghz and 4 GB RAM and only 1 disk) and the result is 4x faster !!!
    The CPU usage is close to 100% as well as RAM usage.
    So how come PP uses all resources availble on an iMac and not on a Windows 7 ?
    Is there any known bug or software bottleneck on Windows 7 ?
    My machine is brand new and nothing much installed besides Adobe products.
    Any help is very much appreciated.
    Thanks,

    I just rendered out a a 2 minute sequence with about 100 clips in it and Colorista effects on everything to the Vimeo 1080 H264 preset. It took about 5 minutes to render straight from Premiere, it used all the recourses it could, my CPU was running at near %100, same with my ram and GPU, I was happy.
    Then I did another render with Red Giant Denoiser and it now wants to take 30 mins and it is only using about %20 of the recourses available. My problem isn't that its taking longer with Denoiser but that its not using all of my computers CPU and GPU.
    Im rendering at maximum render quality and bit dept to H264 (Im happy to wait the extra time), if I try to use VRB 2 it encodes 1 pass at a time and wants to take up to 40 minutes.
    I would appreciate some advice on this.
    Premiere Pro CC 2013
    2.6 GHz Intel Core i7
    NVIDIA GeForce GT 750M 2048 MB (CUDA GPU enabled in Premiere)
    16 GB 1600 MHz DDR3
    OS X 10.9.4 (13E28)

  • Very slow Rendering and Exporting

    Hello,
    I switched to Premiere CS6 from FCP 7 after FCPX came out and haven't looked back. In a lot of ways, it's much better for certain tasks.
    In others, it's not. Initially playing back "red-lined" content worked fine and i was able to view the edit before I committed to render/export.
    Now, I see every 10 frames or so and it skips and stutters. Rendering and exporting times have spiked dramatically over the past month
    for some unknown reason. I have a small prod company and we're using Mac Pro's (8-Core) with min of 16GBs of RAM in each.
    I know there are 101 factors that go into export time, I'm just wondering if anyone if encountering the same issues.
    I just pieced together a 10-min video in FCP7, all ProRes files with minimal cutting and it exported in 2.5 minutes.
    The same project on Premiere was telling me 3 hours. I don't get it.
    Can anyone shed any light on this?
    Thanks
    Dan

    Rendering times are not decided purely on the length of the video.
    The type of effects you have added have more impact.
    Also you cannot always trust the estimated time you are given.
    Have you let it render for about an hour to see whether the estimate drops dramatically?

  • Lightroom 2.6 freezes when trying to export images

    I have been using LR successfully on a Windows XP machine for several years and using version 2.6 for the past several weeks . As of a few days ago, LR would freeze when trying to export images. The export functions of 'Export with Previous' and 'Export with Preset' seem to work without crashing LR but most of my exporting needs me the ability to adjust the export settings. Any advise?

    I would guess LR only goes by drive-letter so if you've kept that the same it should be ok.  Look for something else.
    I would look in your Lightroom Preferences files to see if there is any drive letter that no longer exists.
    On Vista/Win7 my LR prefs file is in:
    C:\Users\[user name]\AppData\Roaming\Adobe\Lightroom\Preferences
    XP has something similar under C:\Documents and Settings\Local Settings (or Application Data)
    If you open that file in a simple text-editor like NotePad then about halfway down (at least in mine) there are some export-related things that include the drive-letter and path on your hard-drive to various folders.  You can find it by searching for:
    AgMRUPopupList_AgExport_destinationFolderPathPrefix
    Look through those and see if any of the drive-letters or paths are wrong and look around for other paths.  The paths will contain
    or
    instead of \ because the low-level language routines LR is written with need it that way so if you change anything, keep the number of slashes consistent.
    It could very well be that there is nothing wrong with any of the paths, so another approach would be to rename or move your preferences file to see if LR will recreate it with defaults for everything, and see if that clears up the lockups. 
    Whether you decided to edit or rename your preferences file, please make a backup copy so you can put it back in case something even worse happens and you need it back.

  • TS1398 my problem is my iphone 4s is connected to the internet(wi-fi) with full signal strength but freezes when browsing and says "Cannot Open Page, Safari could not open page because the server stopped responding".

    my problem is my iphone 4s is connected to wi-fi with full signal(3 bars) strength but freezes when browsing and says
    "Cannot Open Page"
    "Safari could not open page because the server stopped responding"
    I already reset the iphone to its factory settings and erase all contents but still the browsing speed freezes or not searching at all. Sometimes it will work and fast but then the problem uccors every now and then. Iv'e been using iphone 4 for two years and I still have it and works fine compared to this IPHONE 4S.

    Settings → scroll down to Safari → in Safari settings, I selected both Clear History and Clear Cookies and Data.
    IF that does not work -
    Restart or reset your iPhone, iPad, or iPod touch - Apple Support
    Finally - if problem still present -
    Go to Settings>General>Reset
         Reset the network settings - you will need to add the password of your home WiFi in your phone once more
    The device should turn itself off & back on then go into Settings>Wifi and join your network

  • FCP Freezes When Exporting to Flash Video (FLV)

    Final Cut Pro 7.0.2 freezes when exporting to Flash Video (FLV). The resulting FLV file contains only a few seconds of the exported video. A 2009 Apple Support notice offers this re. FCP 6 and CS3 Flash Video Encoder...
    ===
    Final Cut Pro: May quit unexpectedly when exporting to Flash
    Last Modified: February 13, 2009
    Article: TS2593
    Symptoms
    Final Cut Pro may quit unexpectedly when you export using QuickTime Conversion if you choose Flash Video (FLV) from the Format menu.
    Products Affected
    Final Cut Pro 6.x, Adobe Creative Suite 3 Flash Video Encoder
    Resolution
    This can happen if you use the Adobe Creative Suite 3 Flash Video Encoder and Final Cut Pro together. This issue does not occur with the Flash Video Encoder in Adobe Creative Suite 4. To work around the issue:
    Choose File > Export > QuickTime Movie.
    Be sure to enable Make Movie Self-Contained.
    Open the exported movie in QuickTime Player.
    Export the movie to Flash from QuickTime Player.
    ===
    I just installed CS5, so I would think I shouldn't be bothered with an older, problematic Flash Video Encoder. I don't think I should have to convert an MOV file to an FLV file using QuickTime Reader or anything else. Why doesn't it export correctly out of FCPro 7.0.2?

    oh well.

  • Premiere freezes when rendering in timeline (exporting is working fine). After crash, project seems corrupted.

    OK... I'm using the latest PP CC with Windows 7 64-bit on an iMac.
    I recently formatted my hard drive and reinstalled Premiere, and since then I've been unable to render in timeline (pressing enter). I can still export media without rendering, and it all works perfectly, but when I try to render it always freezes and I have to force quit program.
    In addition to this problem, when I try to re-open the project I was working on it says "This project contained a sequence that could not be opened. No sequence preview preset file or codec could be associated with this sequence type".
    I've read some threads on this, and I'm able to make a new project and import the sequences from the corrupted project onto it, but I don't want to have to do this every time! Is there any way to fix these problems?
    Thank you.

    Hi,
    The error message that you have given occurs mainly when Premiere Pro is not activated properly or even sometimes when Creative Cloud Desktop app is not updated or you are not signed in.
    To troubleshoot, first make sure your Creative Cloud Desktop app is updated and you are signed in. Next launch Premiere Pro and sign out and sign back in to Premiere. Next try to open your particular project.
    In case you still get the same error, check your hosts file (hosts file location: C:\Windows\System32\drivers\etc).
    Let me know the outcome.
    Thanks!
    Sarthak

  • Slow renders and exports.

    Jello,
    I have a standard config, 2x2.8 Ghz Quad-Core Intel Xeon.
    It has only 2 GB of RAM.
    I am editing HDV 1080p footage for output of the same encoding.
    It recently dawned on me that my render and export processes might be significantly expedited by an increase in my RAM.
    Yes, no? Why, why not?
    Glad to answer any questions, just want to make sure I make the right move.
    RAM cheap, but it ain't that cheap.
    Out,
    -the apple video dude

    I have the same Mac Pro with 10GB RAM but I'm also disappointed. I'm rendering VOB files (ie only the audio needs fixing) and it's taking looong. The activity monitor says the processor is only using 9%.
    However, when I use MPEG Streamclip for conversions I see that the activity monitor shows how it is using real raw power, unlike FCP.

  • PE2 hangs with Windows 7 when creating and exporting files

    My computer running WinXP just broke down on me for the 2nd time in 7 years, so I finally decided to upgrade. I put it off because I was afraid of windows 7 having compatibility issues with my old software, and now I'm having trouble with Premiere Elements 2. After it opens up I can cancel and exit but if I try to create a file it stops responding. The tutorial opens up as if there's no problem and it plays on the timeline like normal. When I tried to export that sample video the computer hung for a long time before letting me change the output settings. The file rendered at a normal speed, and the exported video looks fine. Since then I've transferred my old files and have no problem working with them or importing new media to an existing file. It's just creating and exporting that causes problems. I'm using Windows 7 home premium, 64 bit.

    Have you tried right-clicking the application icon and setting it to run in XP compatibility mode?
    If not you could install a Virtual Machine to run using your existing XP Licence. Or upgrade your W7 to Professional/Ultimate that includes Virtual XP Mode.
    Cheers,
    Neale
    Insanity is hereditary, you get it from your children

  • Muse freezes when attempting to Export to HTML...

    Hello,
    I'm currently working on a photographer's website, with over 1000 pages. Every time I try and export to html the program freezes when at about 78% completed exporting. It also happens when I try to publish to the businesscatalyst temporary site.
    Anyone know, or have a guess at the problem?
    Thanks!

    Sorry for the slow reply. Thank you for sending your file. (I was on vacation for a few days.)
    At ~1.5Gb and 978 pages, yours is the largest .muse file I've seen to date.
    Muse is currently not a great tool for the site you're creating. The shear size of your site is beyond what Muse can work with in a single .muse file.
    Your site is best suited to a Content Management System where a small set of template pages are married with a database of items, products, or in your case, animal species. Unfortunately, I'm not aware of any Content Management Systems that provide a no coding WYSIWYG solution to website creation. I'm confident Muse will eventually grow to enable database-drive website creation without coding, but we're not there yet.
    If using a CMS and a developer and/or coding a site is not an option, then you could get to the end result I think you're looking for with the current Muse, but it will be labor intensive to create and maintain.
    The basic idea would be to view your website as a set of smaller microsites (all hosted under the same domain name yourbiz.com). Each microsite would be uploaded to a separate directory/folder on your hosting. Perhaps there would be a folder (and thus a .muse file) for birds-a-d and another for birds-e-h, etc. You would manually create URL hyperlinks to link from a top-level microsite with the home page and major category navigation pages to specific pages within the microsites. And manually create URL links from the microsites back to the top-level microsite.
    Strictly speaking there is no specific page count, image count or other complexity limit within Muse. But as the total size and complexity of a .muse file increases, the performance of Muse will degrade. Targeting a page count of 50-100 pages per .muse file (assuming low to moderate complexity per page, as you currently have) should provide reasonable performance and room for growth in each .muse file.
    We're actively working on major changes that will eliminate some of the memory constraints Muse currently has and enable us to take alternative approaches to improving performance of large sites. But it will be some time before the fruits of our labors result in Muse being the best tool for creating and maintaining a website like yours.

  • INDD CS5.5 freezes when trying to export IDML

    Hi there,
    For a couple of days I'm trying to Export a 23.2MB INDD file in IDML, but after a few seconds it freezes:
    Adobe InDisign CS5.5 has stopped working
    A problem caused the program to stop working correctly.
    Windows will close the program and notify you if a solution is
    available.
    I have INDD 7.5.1 running on Windows 7; 64bit.
    Any suggestions?

    I have tried to break up the file and export two pages a time, but in vain.
    Create a new document and go to the Pages panel and choose Move Pages and move your pages to the new document.
    See if that clears it up. If not, try a single page. If it works, when you can narrow to the problem.
    Is there a possibility to cut and past INDD CS5.5 to INDD CS4 ?
    Actually, yes. Select the page elements in CS5 and Export to a Snippet (in fact, you might even be able to drag and drop to CS4...).

Maybe you are looking for