Exporting large file premiere keeps crashing

I am exporting the 26 minute file as a h264 1080p 25 with a VBR 1 pass (only because it seems to usually crash with a 2 pass) and have reduced the Target Bitrate to 32 with a maximum nitrate of 40. estimated file sizes 6036 MB. its too large for what i want, as i will need to be able to put it in vimeo, so i wanted highest possible quality before i turn it into a file for web...
Anyway i haven't even be able to get past the first base as yet. I have made three attempts to export at the high quality, and when i come back to it 2and half hours later!!! the file is corrupt.
Any suggestions would be most welcome....
thanks in advance
Leola

I don't think I understand the question... you say crashing, but do you mean the program quits, or that it produces a corrupt file?
http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/
Also, More information needed for someone to help... please click below and provide the requested information
-Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840

Similar Messages

  • Aperture is exporting large file size e.g. original image is 18.2MB and the exported version (TFF 16 Bit) is 47.9MB, any ideas please

    Aperture is exporting large file size e.g. original image is 18.2MB and the exported version (TFF 16 Bit) is 47.9MB, any ideas please

    Raws, even if not compressed, Sould be smaller than a 24-bit Tiff, since they have only one bitplane. My T3i shoots 14 bit 18MP raws and has a raw file size of 24.5 MB*. An uncompressed Tiff should have a size of 18 MP x 3 bytes per pixel or 54 MB.
    *There must be some lossless compression going on since 18 MP times 1.75 bytes per pixel is 31.5MB for uncompressed raw.

  • How do I export a file and keep the aspect ratio intact?

    I'm exporting an edited scene from an external hard drive to a macbook but the video on the laptop is anamorphic (squished) compared to the original file on the hard drive.  How do I export the file and keep the aspect ratio intact?

    Please give the exact specs of your project. If the material is anamorphic, aspect ratio display is a function of the playback device. What is it?

  • Timecode.cpp-1014, premiere keeps crashing?

    Hello,
    I am using Adobe Premiere Pro CS 6.01. I have been working on a project hassle-free for about 2 weeks now. The other day, after I have been working in Encore (I did NOT link the PPro Project, but rather I exported the video files first), suddenly my Premiere Pro project keeps crashing. Every time I open the project, as soon as all media has loaded, it has a Timecode.cpp-1014 error. Strangely, I am not capturing any footage (from what I have read about this error). Here is a screen shot of this error:
    It always pops up twice like that. Then, once I click continue, it has this error:
    and then Premiere Pro closes.
    I also notice the red "x" in the bottom right corner of the screen, and before I close Premiere, I click it and it pops up saying, "An input violation has occurred!"
    My sequence settings are: AVC-Intra 100 1080i 60Hz, 29.97 frames/second, 1920 x 1080 square pixels, upper fields first, 30fps drop-frame Timecode.
    In my project, I have the above footage (AVCHD, from a Canon Vixia Hf G10), footage from my iPhone 4s, linked audio from Audition, and linked animations from After Effects.
    My computer has the following specs:
    Intel i7-2600 @ 3.40GHz
    Windows 7 Home Premium
    16BM Ram
    3TB Hard drive space, on 2 hard drives'
    ATI Radeon HD 5700 Series, 1024MB
    750-watt power supply, Cooler Master GX750W
    Any advice/help would be much appreciated!
    Zack

    I'm working on a feature length doc (I have footage from over 100 shoot days), and I'm having similar problems that seem to center around a "master project" I'm importing projects into.  I create a project for each shoot date where I will log/sync footage from that day, but then also sometimes I play around and edit footage together (into squences saved with that day's project).  I'm creating the "master project" by importing the 100+ daily project files, so I can retain the keywords I've assigned and the bin structure.  The goal is to be able to search through my footage in the master project by using (among other things) keywords and logging info, and begin editing my scenes together using footage from over the 100 days.
    Unfortunately this master project crashes all the time... it's blatantly unuseable.  I should note that some of the already-edited-scenes are were edited in Final Cut, and imported as squences (i.e. FCP XML).
    Either Premiere can't handle all the linking that's going on, or it can't handle that amount of footage... either way I don't know what to do.

  • Exporting Large Files for Web Use

    Most of my images are around 3000x2000 in filesize and between 10MB and 15MB. They are for use on the web so I don't want them to be too large (in MB's.)
    What is the best option:
    - keep original size and lower the quality-setting from 100% to -let's say- between 75% and 90%
    - Resize them -let's say- to half size.
    The large files have more pixels but are lower quality, or the resized files are higher quality but have less pixels - what is the best?

    You don't need to but it is advisable as scaling always makes images soft.
    You have to scale to display an image on a monitor as a monitor is a very
    low resolution device. Luckily you can do the sharpening straight in the
    export dialog and you don't really need to think about it. Sharpen for
    screen at standard setting is usually just fine. So try using the following
    settings in the export dialog:
    File settings: jpeg, quality 75, Color Space sRGB
    Image Sizing: resize to fit long edge, 800 pixels
    Output sharpening: Sharpen for screen, amount Standard
    Metadata: Minimize embedded metadata (preserves your copyright info
    but omits all the edit and
    camera info)
    Then play
    around with the sharpening amount and compare the exports to see what
    you prefer. There is very little difference between High and Standard.

  • Exporting large file in QT

    I am trying to export a 55 min. sequence in Pro Res 422 to a QT self contained file in the same format and I keep
    getting the "error-out of memory" pop up.
    I tried to render out the sequence first, but I get the same message.
    This is strange as I have done this operation before without problems on a different project.
    Not sure what to try next. Any suggestions would be appreciated as always.
    thanks
    MP

    Thanks for the responses. I do have a good number of stills, but they are in RGB. And 55 min. of ProRes IS a large file, but it all is going into an empty 1TB external drive, so there is plenty of space there.
    Now, this is a 55 min. doc that is subtitled. So, I'm thinking that the subtitling may make it render heavy.
    I suspect that the problem is in the amount of rendering because I get the same message when I try to render the sequence before exporting it out onto a QT file.
    So, this is where I go dark because I'm not really a computer techie. How is the rendering achieved? I thought that the system used HD space when it ran out of RAM.
    My sequence is made up of 3 different segments from 3 different original sequence files. Would it help if I bring in all 3 sequences as nested files?
    mp

  • Need help exporting large file to bitmap format

    I have a large file that I need to export to a bitmap format and I am experiencing unknown "IMer" errors, memory and file size limitations.
    The file contains only one artboard of size around 8000 pixels by 6000 pixels. I can successfully export as a png at 72dpi giving me a 100% image of my AI file. However I need to export an image at 200% of the AI file. If I export as a png at 144dpi to achieve this I get the following error(s)
    "The operation cannot complete because of an unknown error (IMer)" or "Could not complete this operation. The rasterised image exceeded the maximum bounds for savung to the png format"
    I have tried exporting as tiff, bmp and jpeg but all give "not enough memory"  or "dimensions out of range" errors.
    Does anyone know the limitations with AI for saving large files to bitmap format?
    Does anyone have a workaround I could try?

    You could try printing to Adobe Postscript files.
    This will actually save a .ps file and you can scale it to 200% when doing so. You'll need to "print" for every image change.
    Then open a Photoshop document at your final size (16000x12000 pixels) and place or drag the .ps files into the Photoshop document.
    I just tested this and it seems to work fine here. But, of course, I don't have your art, so complexity of objects might factor in and I'm not seeing that here.
    And you are aware that Photoshop won't allow you to save a png at those dimension either, right? The image is too large for PNG. Perhaps you could explain why you specifically need a png that large???

  • Export large files and maintaining high dpi

    My export default is set to 300 dpi, but it continually exports at 250 dpi -- how can I fix this?  I have very large files, but sometimes when I upload to Photoshop they show at 72 dpi.  Something is off.

    Where do you set the export default? There is no Export default, afaik. You can define export presets, to pick from. Which export prset will be applied, depends on how you export.
    If you export using the Media Browser - drag from the Aperture window, the Preview will be exported.
    If you export an Image Version (File -> Export -> Version), the selected Export preset (in the File chooser) will be used.
    If you export a Master (File -> Export -> Master),no export peresets apply, the original master image file will be exported.
    If you export to an external Editor, the settings in the Preferences -> Export apply.
    So how do you export and "upload to Photoshop to get so surprising results?
    Regards
    Léonie

  • Export large file

    Is there a way to export a large file containing approximately 250,000 rows to excel or a csv file? If not, is there another tool that can be used?
    Pany

    spool filename.csv
    There are a number of ways to do this. You can use "set colsep ," but that leaves lost of spaces between columns which most people don't like; or you can concatenate columns to get using "col1||','||col2....".
    On the ask tom website if you search around there is a pl sql program which will generate a csv for an arbitraty statement.

  • Is there a system preference menu somewhere that is blocks exporting large files?

    Why won't iphoto 8 allow me to share large files?  Are there system preferences set that I can't find?
    I am trying to burn a DVD, and don't want to downgrade the image quality.  It is set to moderate, and the place of choice is greyed out. 
    Thanks!

    As a test launch iPhoto with the Option key held down and create a new, test library.  Import some of the large photos and test to see if the same problem persists. Does it?
    To get the original large photos out of your current library Command (right) - click  on a thumbnail and select Show Original File from the Contextual menu.
    You'll be taken to the original file in the Finder  so you can COPY it to the Desktop to use in the test library.
    OT

  • My Premiere keeps crashing every time I click export.

    I'm using a Macbook Pro Retina with Mountain Lion.  This just started happening today after I started using new footage in a project.  The footage is H264 Mov and Mp4.  However, I have mixed codecs before with no problems.

    The link below is about OSX, but it may give you some ideas
    http://helpx.adobe.com/creative-cloud/kb/ame-premiere-crash-launch-export.html

  • Premiere Pro CC exporting a file has  started crashing my computer of if it completes gives me an audio only MP4

    Read somewhere that a possible solution would be to delete all "Preview" files.  Does this sound logical? Where are these located?

    I have a similar problem. I mostly use XDCam and quicktime H264 footage. The problem arises when I try to adjust the LKFS level with the LKFS radar plugin. I loop the piece of audio so that the radar reaches an average and that easy enough. But every once in a while the level start going down by themselves during the playback loop and it won't stop going down until I stop playback, click elsewhere in the timeline and start again. Once I have done this everuthing falls back to normal.

  • Adobe Premiere keeps crashing upon start up and in the middle of edits.

    I have been through some technical assistance with your team. But it seems I've found more on the forums in relation
    to my computer and what I need to make sure is up to date and yadda yadda.
    I open my project and it will crash consistently, annoyingly. It seems to happen with an AVI file.
    Here's the video specs
    Here's my hardware.
    I'm up to date on almost everything else. Any tips for me to keep this app running and actually functional?
    Thanks,
    Jeremy
    (CC customer)

    I have read through quite a bit of all of this info. I don't necessarily want to buy anything extra unless I absolutely have to.
    It's a strange camera that's for sure, Emerson has no website or support online. I will see if I can find a disc or possibly
    just plug the camera into this computer and see if it gives me the CODEC. What about GSPOT?
    Is this specifically what's crashing my Premiere? I have yet to try anything without that AVI/MJPEG file yet. It seems that
    it handles the 264 just fine, it's the silly MJPEG that's kicking my butt. I read that it may have been corrupted
    somewhere along the way. If that's true do I need to just scrap the file?

  • Best compression for exporting large files from iMovie for use in iDVD?

    I have a doco that I've made as separate projects too slow to make it all in one project - which I then exported as Quicktime .mov files. When I assembled the .mov files in iDVD I ended up with 4.7GB of material which iDVD flipped out on and crashed.
    What would be the best compression to apply to the large .mov files but reduce the overall file sizes by say 10%
    Its sometimes taking up to 6 hours to render each project average total screentime per project is about 70 minutes and each project file size ranges from 1 to 6GB...
    I feel like I'm a little out of my depth on this one!
    Any suggestions for this dilemma?
    Thanks
    Tony

    When I assembled the .mov files in iDVD I ended up with 4.7GB of material which iDVD flipped out on and crashed... Any suggestions for this dilemma?
    Not sure if your 4.7GB reference is for the source files or the resulting "muxed" MPEG2/PCM encoded content. In any case a single layer DVD is limited to 4.7 GBs of total content. To be safe, this usually means you are limited to 4.2 to 4.3 GB of encoded movie and/or slideshow content depending on how many and what type of menus you are creating created. Thus, if you are encoding for a single-layer DVD and your project encoded content exceeds the capacity of your DVD, then this would likely explain your problem.
    If your project size reference is for the source content being added to your iDVD project, then it is totally irrelevant and you need to concentrate on the total duration of your iDVD and the method of encoding instead of file size. Basically, for a single-layer DVD, only about 60 minutes content can be encoded using the "Best Performance" encode option, 90 minutes using the "High Quality" setting, or 2 hours in the "Professional Quality" encode mode. Thus, if your content duration exceeds the capacity of your encoding mode here, it would likely explain your problem.
    In either case, the solution would be to either burn to higher capacity optical media/higher capacity encoding mode or burn your content to multiple DVDs as individual projects at the current media capacity/encoding mode.

  • Premiere keeps crashing

    Over the last few days, my Premiere Pro (CS6 Creative Cloud) has crashed nearly 30 times.
    It's crashing seems completely unrelated to anything I'm doing as earlier I left my iMac alone for a few minutes and when i returned it had crashed.
    I'm using a brand new iMac and have no idea why this keeps happening.
    I'm still in the first month of my CC contract and I'm wondering if its worth cancelling because it's really inconvenient.
    Anyone else having similar problems?
    When I was using the trail version I had an issue where it would crash every time I tried to export but now it's happening far more frequently and at seemingly random points.
    Thanks
    Spencer

    Yes, I don't know Tweetdeck but to get back to 'standard' configuration you should disable, (shut them down so they don't show up in the even temporarily, 3rd party apps that may be needing resources on a constant basis, beyond major packages like Adobe. I've even found that I encountered more crashes than I was expecting when I was running Chrome at the same time as Pr. A good rule of thumb is to try and keep your editing suite 'stand alone' (I know, it's never really only running itself), while using it. I don't run mail, browsers, or anything but Adobe's apps and underlying untilities when running Pr. I have a second machine for my 'office' activity. If I have to fireup Dropbox or a browser, I close the project at the very least, but usually close Pr for the time being. Activity monitor is what I use to check on these processes. I get rid of Chrome, Dropbox, Rosetta Stone Daemon, and especially any Microsoft processes, since they often are old from people running old versions of Office or even Entourage.
    Thanks about the info on the keying software.  Since I moved to Pr last year,  I've not done any keying, so was unfamiliar with whether that was Adobe native or not. BCC for example, on FCP, was "native' to the package but still third party licensed so they were not built by Apple internal teams. Sony Vegas gives away New Blue, but it's buggy as heck, even though it's supposedly 'Vegas recommended', and not buildt by Vegas teams. It's more likely that any third party apps shipped with the core product have been significantly tested by the manufacturer, but that's not always the case.
    One last thing that is worth a thought. I have found that crashes seem to occur more often after I've gone a long period of time using sleep mode. I often sleep my editing computer throughout the day, and sometimes even overnight. I've gone as long as 30 days in sleep mode, but found that after a crash, if I reboot the machine, that the next crash is usually a long way away, like weeks. Might be about clearing caches that are only cleared on machine reboot.  It seems to make a difference in my setup, and that's an experience over multiple machines, over multiple months.

Maybe you are looking for