Premiere Pro CC Export Crash and Freeze

So basically, i recorded in 4k 24p on my Panasonic GH4 and some 1080 60 clips and am editing in a 4k premiere pro cc timeline. All the clips are .MOV files. Whenever i go to export my 3 1/2 minute video straight out of Premiere pro or even the Media encoder it stops at about 3%  or whenever the export starts to hit the video files and the encoding time raises higher and higher and higher until the export just freezes. I'm exporting it out as an h.264 file 4096x2160 at 24fps. Vbr pass 2 times, at a bitrate of 25mbps. Earlier this past week i exported out about 30 seconds of the video at a random point of time in the video and it exported out fine, i just wanted to see how it compressed and how the footage would look like on vimeo. Now even if i try to export really any clip in the timeline individually it just freezes up like i said. I've been doing LOTS(4 days worth) of different troubleshooting and have not found a solution and im pretty upset. My computer is fast enough for sure, i have exported out a few different 4k tests and videos fine a few weeks back. Im running windows 7 16gb of ram, 8 cores, i7 processor and my graphics card is fine. Could you help me out?

One more thing. A BIG problem like this crashes - it´s up to Adobe to work it out with Apple or who every other vendor causing the problem (if there is a third part fault).
Adobe have to solve the problems together with the third part vendor, then com back to us multi million dollars worth of users with a easy quick fix. Do it!

Similar Messages

  • Premiere Pro 2014 is crashing and freezing and I have to use force quit to get it to shut down.

    Premiere Pro 2014 is crashing every day. i am running Premiere Pro 2014 on a 2013 imac with 3.4 GHz Intel Core i5 with 16  GB RAM. Playback on premiere continually freezes and the program crashes. Or the playback will start to freeze and then I save and close the project file/program, but the program will not close and I have to force quit. This is extremely frustrating. Premiere Pro CC was super stable and I rarely if ever had a problem. I have changed my permissions to give myself read/write. I have created a new project file in 2014 and then imported all my sequences from my updated project file but none of these strategies have worked. I am considering creating a new project file and going back to working solely in CC because I am on a deadline and troubleshooting this issue is taking up so much time.

    I have had to force quit PP CC four times today. The fourth was when it crashed while trying to reopen it. I have had exactly the same problems as described above. I have no solutions to offer. I will go through a week of constant Premiere Pro bugs and poor performance then experience a period that seems too good to be true only to end up having a day like today. I can't believe that they call this a professional editing suite. It just wastes so much of my time pissing around trying to fix things and managing all the extra render and preview files it makes each time I have to save a new copy of a project which usually results in renaming it. It gets confusing after a while. Really not happy with this and have begun to learn Avid so as soon as this project is done, PP will be history.

  • Adobe Premiere Pro CC Keeps crashing and freezing my MBP

    Hi all, Im really at a loss as to what is causing this...Premiere Pro CC randomly freezes. It can happen at any given time and seems to be getting more persistent! When this happens the only thing I am able to do is power down my computer and restart it
    Here are my details.
    2014 Mac Book Pro
    2.3 GHz Intel Core i7
    16GB DDR3 RAM
    500GB Internal SSD - Programes are stored here.
    4TB External Thunderbolt HD (8TB Mirrored) - Media files are kept here.
    Im using Premiere Pro CC Version 7.2.2
    Mainly editing AVCHD files, but often a combo of AVCHD/ProRes/H.264
    I have just recently cleared my Cache in Premiere. Didn't help.Would be great if anyone has any more suggestions, let me know if you need more info from me!
    Cheers!
    Rob T

    I am on Windows, but have a few saved Mac discussions that may help (or, may not... but free to read)
    Mac and Root User http://forums.adobe.com/thread/879931
    -and http://forums.adobe.com/thread/940869?tstart=0
    Mac & nVidia Driver http://forums.adobe.com/thread/1075592
    -and http://www.nvidia.com/object/mac-driver-archive.html
    Mac Retina Bug http://forums.adobe.com/thread/1159632
    Troubleshooting guide for Mac freeze
    http://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-mac.html
    http://blogs.adobe.com/aftereffects/2011/02/troubleshooting-quicktime-errors-with-after-ef fects.html
    External speakers stop playback http://forums.adobe.com/thread/1370072?tstart=0
    OSX Crash http://helpx.adobe.com/creative-cloud/kb/ame-premiere-crash-launch-export.html

  • Adobe Premiere Pro is constantly crashing and freezing

    I'm a new user to adobe and I've used their free trials in the past for cs6, but this latest version of Premiere Pro keeps crashing while I'm in the middle of projects. I really don't know what the problem is. Is there something I need to update?

    Macbook Pro 13" 2013
    OS Mavericks
    8gb RAM
    Processor  2.5 GHz Intel Core i5
    Graphics  Intel HD Graphics 4000 1024 MB
    I forget what it said specifically, but the error message said something along the lines of
    "There was a serious problem with Premiere pro and it needs to shut down immediately. It will try to save your current session"

  • Premiere Pro CC 2014 Crashing and Bogging Down on Documentary Film Project

    We have been working in Premiere on this documentary film for months.
    As we reach completion it is beginning to really bog down and crash a lot.
    Equipment is
    iMac 27 inch 3.5 GHz Intel Core i7 Late 2013 Model
    Apple Cinema HD Display
    32 GB 1600 Mhz DDR3 RAM
    NVIDIA GeForce GTX 780M 4096 MB Graphics Card
    1TB internal SSD Drive
    We are running Premiere Pro CC 2014.0.1 and have remained there because we don't want to upgrade the software in the middle of the project.
    The media is all on the external drive. It's a USB 3.0 connection. There is quite a lot of footage that we are working with.
    We do have some After Effects comps that are linked in the project and we have exported the ones that are complete as QuickTimes to try to stop that from bogging us down.
    Any advice on how we can manage this crashing and freezing problem would be much appreciated.
    We don't have the cash to upgrade the computer and it has been working pretty well for us so far.
    Here are things we have done:
    Made a smaller timeline because we were working on one that was the entire movie.
    Turned off the secondary monitor and unplugged it.
    We are looking at moving the render cache off the external drive to a thunderbolt drive, but I'm concerned that this may take a long time.
    Any recommendations would be greatly appreciated.

    Splitting up the read/write items is rather a key to getting smoother operation out of PrPro. Either that or putting things on a large RAID-0/5, this sort of thing is covered over on the
    Tweaker's Page ...
    http://ppbm7.com/index.php/tweakers-page
    And I highly recommend you take a look. Their info isn't just "we think ... " ... but the results of many many carefully crafted test sequences run on many machines with all sorts of hardware bits & pieces. You can also register, download the PBM test and run it on your own machine. It takes only a little while to do so, and with the logger app that's included and posting the results back to them, you can get a very good breakdown on where your machine is doing ok ... and where any choke points are occurring.
    I think this would be good for you right now ... you need to get stuff done, not guess & try things.
    Neil

  • Premiere Pro CC 2014 crash and crash, and crash....

    Kevin and all you other Premiere Pro CC people out there.
    How long before Adobe will solve the problem of Premiere Pro crashing over and over again.
    I guess there is no one reading this that could tell me "it works for me".
    So Kevin (staff),
    Here is the 36-line-report you requested from me.
    For your information. Premiere Pro CC 2014_2 and back paddling to 8.0, they all crash.
    Most crashes are freeze on timeline. Thats is, nothing moves, sometime the music track
    just keep going and you can't stop it, so you have to hard quit.
    My power: Mac Pro 2014, 6 core, dubble graphic card, 64 GB memory, 1 TB SS storage
    This is my latest report:
    Process:               Adobe Premiere Pro CC 2014 [717]
    Path:                  /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
    Identifier:            com.adobe.AdobePremierePro
    Version:               8.0.0 (8.0.0)
    Code Type:             X86-64 (Native)
    Parent Process:        ??? [1]
    Responsible:           Adobe Premiere Pro CC 2014 [717]
    User ID:               501
    Date/Time:             2015-04-03 14:55:56.729 +0900
    OS Version:            Mac OS X 10.10.2 (14C1514)
    Report Version:        11
    Anonymous UUID:        3C4BE865-15A1-83C0-2A8F-247384EECB0D
    Time Awake Since Boot: 19000 seconds
    Crashed Thread:        0  Dispatch queue: com.apple.main-thread
    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes:       KERN_INVALID_ADDRESS at 0x00000000000000c0
    VM Regions Near 0xc0:
    -->
        __TEXT                 0000000100000000-0000000100003000 [   12K] r-x/rwx SM=COW  /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   com.apple.CoreText             0x00007fff8c98db95 TLine::~TLine() + 243
    1   com.apple.CoreFoundation       0x00007fff9105ca9e CFRelease + 526
    2   com.apple.HIToolbox           0x00007fff8d5a0944 TCoreTextLineInfo::~TCoreTextLineInfo() + 34
    3   com.apple.HIToolbox           0x00007fff8d5a0913 TLayoutInfo::Clear() + 51
    4   com.apple.HIToolbox           0x00007fff8d5a078f TCoreTextEngine::Invalidate() + 49
    5   com.apple.HIToolbox           0x00007fff8d59d0a8 TCoreTextEngine::Init(void const*, THIThemeTextInfo const*) + 92
    6   com.apple.HIToolbox           0x00007fff8d59cf00 TThemeTextCache::Create(void const*, THIThemeTextInfo const*) + 460
    7   com.apple.HIToolbox           0x00007fff8d59c8bf DataEngine::GetTextDimensions(void const*, double, HIThemeTextInfo*, double*, double*, double*) + 259
    8   com.apple.HIToolbox           0x00007fff8d59c785 HIThemeGetTextDimensions + 185
    9   com.apple.HIToolbox           0x00007fff8d5e124e HIStandardMenuView::MeasureItemTextWidth(__CFString const*, TextLayout*, __CTFont const*) + 122
    10  com.apple.HIToolbox           0x00007fff8d5e0a3f HIStandardMenuView::GetItemWidth(float, TextLayout*, unsigned char*) + 719
    11  com.apple.HIToolbox           0x00007fff8d5dde02 HIStandardMenuView::GetOptimalSizeSelf(CGSize*, float*) + 878
    12  com.apple.HIToolbox           0x00007fff8d5dda1c HIView::SendGetOptimalBounds(CGRect*, float*, CGSize*) + 416
    13  com.apple.HIToolbox           0x00007fff8d5dd84f HIView::GetOptimalSize(CGSize*, float*, CGSize*) + 45
    14  com.apple.HIToolbox           0x00007fff8d5dd755 HandleCalculateMenuSize(OpaqueEventRef*) + 154
    15  com.apple.HIToolbox           0x00007fff8d58213a MenuData::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 358
    16  com.apple.HIToolbox           0x00007fff8d58098c DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1260
    17  com.apple.HIToolbox           0x00007fff8d57fdce SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 386
    18  com.apple.HIToolbox           0x00007fff8d57fc42 SendEventToEventTargetWithOptions + 43
    19  com.apple.HIToolbox           0x00007fff8d5dd4e4 _CalcMenuSizeOnDevice(MenuData*, unsigned short, unsigned int, CGRect const*, unsigned int) + 763
    20  com.apple.HIToolbox           0x00007fff8d5e1bad GetInitialMenuRect(MenuSelectData*, MenuData*, unsigned char, Point, unsigned short, Rect*, unsigned int*, CGPoint*) + 261
    21  com.apple.HIToolbox           0x00007fff8d5f6f32 GetCurrentMenuRect(MenuSelectData*, unsigned int*, CGPoint*) + 110
    22  com.apple.HIToolbox           0x00007fff8d605890 DrawTheMenu(MenuSelectData*, __CFArray**, unsigned char, unsigned char*) + 582
    23  com.apple.HIToolbox           0x00007fff8d60548c MenuChanged(MenuSelectData*, unsigned char, unsigned char) + 356
    24  com.apple.HIToolbox           0x00007fff8d5f1e36 TrackMenuCommon(MenuSelectData&, unsigned char*) + 1211
    25  com.apple.HIToolbox           0x00007fff8d604fb1 MenuSelectCore(MenuData*, Point, double, unsigned int, OpaqueMenuRef**, unsigned short*) + 510
    26  com.apple.HIToolbox           0x00007fff8d604c5e _HandleMenuSelection2 + 446
    27  com.apple.AppKit               0x00007fff9191b8be _NSHandleCarbonMenuEvent + 277
    28  com.apple.AppKit               0x00007fff917b72f0 _DPSNextEvent + 1843
    29  com.apple.AppKit               0x00007fff917b6730 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 194
    30  com.apple.AppKit               0x00007fff917aa593 -[NSApplication run] + 594
    31  com.adobe.Frontend.framework   0x00000001000c948d FE::MacApplication::RunSelf() + 45
    32  com.adobe.Frontend.framework   0x0000000100047cca FE::Application::Run(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 4058
    33  com.adobe.Frontend.framework   0x00000001000cad44 FE::AppMain(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 276
    34  com.adobe.Frontend.framework   0x00000001000d1f25 FE::Run(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 581
    35  com.adobe.AdobePremierePro     0x00000001000018ac main + 508
    36  com.adobe.AdobePremierePro     0x00000001000016a4 start + 52

    Hi,
    Sorry to hear about the experience. Can you please try this:
    Go to the following locations:
    Location 1: When in Finder, click on Go > Go to Folder > ~/Library/Application Support/Adobe
    Location 2: Go > Go to Folder > ~/Library/Preferences/Adobe
    Location 3: Documents > Adobe
    In all the locations, rename the 'Adobe' folders to 'OldAdobe'
    Launch Premiere, accept the License Agreement and see if it works.
    Note: You will lose your customized workspaces and keyboard shortcuts. Wait for Premiere to generate the media cache the first time you launch the project.
    Also i would suggest you to make this change if the playback issue continues and see if it works better:
    Under File > Project settings > General, change the Video renderer to Mercury Playback Engine software only. Click OK and select "Delete Previews"
    Thanks,
    Rameez

  • Premiere Pro CC continuous crash and extremely slow renders on a new Mac Pro.

    Hello,
    recently we changed our editing machines with the new Mac Pro with this configuration:
    - CPU 3,5 GHz 6 core Intel Xeon E5
    - 32 GB RAM
    - 2x AMD FirePro D700 6 GB
    we work on a server connected to the Mac Pro in Dual Ethernet configuration.
    The rendering of a sequence at 1920x1080 with 3 video tracks (video footage converted at ProRes 422 LT, a title on a linked After Effects Comp and a PSD graphic overlay of a small logo) of the length of about 3 minutes it takes about 4 hour... when it doesn't crash.
    When it crash, usually when i simply scroll the timeline, i receive an error message very long (if you want I can send you a rtf file about it, it's too long to paste it here).
    These are my system information:
    - Premiere Pro CC 8.2.0 (65)
    - I've installed every updates available at this time
    - OS X Yosemite 10.10.2
    Thank you very much in advance, and sorry for my bad english.

    Thanks Andrea for your assistance in reporting that additional information. You have come across an intermittent bug which has been reported by other users with no reliable repro steps for us to follow in house. So it appears to be mainly system specific, but we're not even sure which sorts of systems demonstrate it yet.
    One other thing to try is clearing your media cache files (from preferences > media panel). In the meantime,e the best thing to do is make sure you submit those crash logs to adobe whenever you get them. This helps us identify common thread among various users who may be experiencing the same problem. Also, if you have time, please file a bug report describing the steps that caused the issue in your case: http://adobe.ly/ReportBug
    Please be as specific as possible when describing your steps. Without a repeatable case, a bug like this is very, very difficult to fix. Thanks again for your support.
    To work around the sloe render for AE comp problem, please try right clicking on the comp in the timeline and then choose the "Render and Replace" command to transcode it out to a more easily handled format. This should help a lot with your performance slowness, and you will still have the ability to restore the original comp files if needed.

  • AMD Radeon HD 6750M Premiere Pro CC2014.2 crashes and no hardware accleration 2011 MBP

    I have a fresh install of 10.9.5 and Premiere Pro CC 2014.2 Everytime I move a video into my workspace it crashes. Log shows [CL_INVALID_OPERATION] : OpenCL Error : Failed to retrieve device information! Invalid enumerated value! For video and rendering playback options, the software option is the only choice. 512GB VRAM on AMD and Intel HD Graphics 3000 512 MB. This is a late 2011 15" Macbook Pro.

    Hi Jason,
    Sorry you're having a tough time.
    For video and rendering playback options, the software option is the only choice. 512GB VRAM on AMD and Intel HD Graphics 3000 512 MB. This is a late 2011 15" Macbook Pro.
    Right. You need 768 MB VRAM for hardware acceleration for the Mercury Playback Engine. In speaking with engineering and researching past posts, your GPU is underpowered and you will probably continue to experience performance issues and unexpected behavior with current versions of Premiere Pro.
    It is recommended to roll back to Premiere Pro CC.1 (7.1) and to avoid certain effects listed in this post: Performance crippled by 7.2 update - GPU Acceleration. See the recommendations from QE engineer, Peter Garaway.
    It might be time to begin looking at updating your hardware in order to take full advantage of your Creative Cloud subscription. We have an outstanding hardware forum should you need advice on upgrading your computer.
    Thanks,
    Kevin

  • Premiere Pro CC14 delayed playback and freezing

    I've recently upgraded to CC14 (Mac) and editing in Premiere Pro has become so frustrating. About 1 minute into editing, playback is delayed or completely stops (only audio continues) and rendering takes forever. Has anyone else had this issue with PProCC14? I am pulling my hair out!!!

    First two things to check are permissions and prefs.
    Prefs: go to Documents/Adobe/Premiere Pro/8.0 and rename the folder "<username>-Profile." When you launch PPro, all new prefs will be written.
    Permissions: fixing permissions problem that impedes start of Adobe applications | After Effects region of interest

  • Why Do Both Photoshop CS5 (64 Bit) and Premiere Pro (64 Bit) Crash on Start up.

    Both Photoshop CS5 (64 Bit) and Premiere Pro (64 Bit) Crash on Start up. 32 bit version of Photoshop works fine.
    Here is the problem signature when they crash.
    Problem signature:
      Problem Event Name:          APPCRASH
      Application Name:          Photoshop.exe
      Application Version:          12.0.0.0
      Application Timestamp:          4bbc5b10
      Fault Module Name:          CoolType.dll
      Fault Module Version:          5.7.82.7602
      Fault Module Timestamp:          4b980c97
      Exception Code:          c0000005
      Exception Offset:          0000000000073a92
      OS Version:          6.1.7601.2.1.0.256.48
      Locale ID:          1033
      Additional Information 1:          7c82
      Additional Information 2:          7c821a1fc13b00b508d1bb6ee7ecaf44
      Additional Information 3:          019c
      Additional Information 4:          019cb6db15489631b8a43faf27e30830
    Problem signature:
      Problem Event Name:          APPCRASH
      Application Name:          Adobe Premiere Pro.exe
      Application Version:          5.0.3.0
      Application Timestamp:          4ce382d1
      Fault Module Name:          CoolType.dll
      Fault Module Version:          5.7.82.7449
      Fault Module Timestamp:          4b7b1af3
      Exception Code:          c0000005
      Exception Offset:          00000000000739ea
      OS Version:          6.1.7601.2.1.0.256.48
      Locale ID:          1033
      Additional Information 1:          889a
      Additional Information 2:          889afed61eb6ddf1c1c3419adc6026b6
      Additional Information 3:          8235
      Additional Information 4:          823549a371dff618695395cc0a8514ee
    Both are referencing cooltype.dll. I ran Font Doctor on all system and non-system fonts and found no errors. Booted without Extensis Suitcase loading. Nothing works. All 32 bit programs work fine. Any clues would be appreciated.

    It does not necessarily mean a "corrupt" font, but can be a font that PrPro, and PS, cannot handle.
    Though I have read that changes have been made, Open Office's DejaVu font would crash PrPro's Titler - every time. There are quite a few others. Font Dr, and similar utilities, will not see the font(s) as corrupt, but they are so poorly designed, that PrPro and PS cannot deal with them.
    Though it can be a long, drawn out process, one can often zero in on the problem font(s), with a little work. This is accomplished by first defining the "System Fonts," and not touching them. Then, uninstall half of the remaining fonts, and testing PrPro and PS. If they launch fine, you know that somewhere in that list of fonts, the problem exists. If there is still a failure to launch, chances are good that the problem font(s) reside in that half, that are still installed. Note: because the problem still exists, does not guarantee that there are NOT problem fonts in that uninstalled group, so keep that in mind.
    Repeat the proces, by uninstalling half of the remaining fonts and testing.
    If necessary, repeat by removing half of the now remaining fonts and testing.
    When you get to a point, where you are no longer getting problems, reinstall fonts, in small groups, testing in between. The smaller the groups, the easier it will be to pinpoint the problem font(s).
    Keep notes on which fonts you are uninstalling and reinstalling, until you narrow it down to the problem font(s).
    I would start by uninstalling any "free fonts," and then commercial, 3rd party fonts. A lot of free fonts are just poorly designed, and can cause issues, though they might work fine in some other programs.
    I use a font manager, so that I only have ~ 350 fonts installed at one time, and then dynamically install fonts, as needed for Projects. That keeps my machine clean, and if, upon installation, I get a crash/hang, I know that at least one font in that Set is causing it. This helps, as my workstation has ~ 19,000 fonts on it, and some are free fonts, and many are from 3rd parties. Some are also very, very old.
    Good luck,
    Hunt
    PS - one common cause for hangs on loading PrPro can be from VST's, used in Audio-editing. If you also have a lot of VST's, you could have two issues with two separate programs, i..e. PS hanging on fonts, and PrPro hanging on VST's. The results would be the same, but the causes could be different. That leads to even more work. For PrPro, also see this ARTICLE. If you get PS launching, but PrPro is still not functioning, drop by the PrPro Forum, and someone can help you there.

  • I work with Premiere Pro on a mac and export quicktime movies to be played on pc's or mac's

    I work with Premiere Pro on a mac and export quicktime movies to be played on pc's or mac's. When I export a qt from Premiere with audio it will not play on a pc only a mac. After extensive research I have narrowed down the problem to this: if you use the inspector in quicktime it looks like this
    DV, 720 x 480 (640 x 480), Millions
    16-bit Integer (Little Endian), Stereo (L R), 48.000 kHz
    I have to run it thru AE to make it look like this....then it plays
    DV, 720 x 480 (640 x 480), Millions
    16-bit Integer (Big Endian), Stereo, 48.000 kHz
    SOOOO the problem is the Little/Big Endian. I googled that and it looks like a file/bit structure....anyone know how/why to change it in Premiere? Because everytime I make a movie in Prem I have to drag the sequence into AE and render it there so the sounds works.....
    thanks

    Two questions:
    1. What CODEC are you choosing when exporting on the Mac?
    2. Do you have any Blackmagic hardware/software installed?
    Cheers
    Eddie
    PremiereProPedia   (
    RSS feed)
    - Over 300 frequently answered questions
    - Over 250 free tutorials
    - Maintained by editors like
    you
    Forum FAQ

  • Why remove .flv export from Premiere Pro CC 2014? And what's a good workaround?

    Why remove .flv export from Premiere Pro CC 2014? And what's a good workaround?

    OK, so you want to put it on your own web page. That's fine as long as you know how to create a web page.
    The next thing you have to decide is how big do you want the video to appear on the web page. Many people just post on YouTube and then embed the video into their web page. That way, the video can take advantage of all of the various sizes that YouTube provides.
    In any case, I suggest that you use H.264. But the data rate depends on the size of the file. If you are going to display it in HD, then you probably want to start at about 20Mb/s and go up or down from there. The required data rate depends on what you find acceptable, and that depends on the amount of movement in the video. For example, a talking head next to a white board explaining something requires a lot less bits to represent the image because less changes are taking place from frame to frame. If you use 10Mb/s for that, you might find 20Mb/s or more is required to make you happy if you shot a football game from the sidelines.
    I generally use settings that look like this image. If you have any questions as to why I choose these settings, feel free to ask.

  • When I run the program Adobe Premiere Pro CC I at once freezes the computer completely and to make it work I have to restart his, what do I do?

    When I run the program Adobe Premiere Pro CC I at once freezes the computer completely and to make it work I have to restart his, what do I do?

    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
    •What is your exact brand/model graphics adapter (ATI or nVidia or ???)
    •What is your exact graphics adapter driver version?
    •Have you gone to the vendor web site to check for a newer driver?
    •For Windows, do NOT rely on Windows Update to have current driver information
    •-you need to go direct to the vendor web site and check updates for yourself
    •nVidia Driver Downloads http://www.nvidia.com/Download/index.aspx?lang=en-us
    •ATI Driver Autodetect http://support.amd.com/en-us/download/auto-detect-tool

  • Premiere Pro CC 2014 crashes when loading project file

    Hi guys, any help on this is much appreciated as I have a job due in 18 hours and I'm in big trouble if I can't fix this.
    I've been editing a project in Adobe Premiere Pro CC 2014 (updated to the latest version) and when I tried to access the same file today it is giving me the error message:
    'Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project.'
    I had saved other version files and they all seem to be working properly so I know it's not my HD that is corrupt. In fact my suspicion is that it has something to do with a blur effect i'm using. The only problem is, I can't even access the file to delete the effect as the project file won't open.
    Information about my computer:
    I am using a Macbook Pro
    OS X version 10.9.4
    2.6 Ghz Intel Core i5
    Memory 16 GB, 1600 MHz DDR3
    Any suggestions/comments would be appreciated.

    Guys I solved my own problem - thought I'd share with you how in case anyone else is having this problem -
    I came across this thread
    Premiere Pro CC error message and crash
    which had the suggestion -
    "Do tou have after effects installed? If yes, please try to import the main sequence into it and then export it as premier pro project from file/export ootion and then try to open that in premiere pro."
    This didn't work for me too but I did try and import my existing project into a new project and copy all the files over. Works fine now.
    I don't know if I will have the same issue again tomorrow so I'm going to render out a super high res video before I close premiere just in case

  • Premiere Pro 2.0 crashes - Avi deleted

    Hello,
    Today I Had to insert a Time Code in film that belonged to a project made with Premiere Pro 1.5. I Installed PPro 2.0. I opened the project and i was able to insert the TC and Export it to a Quicktime File. But right after the export, Premiere Pro 2.0 crashed. It appeared the message "Premiere has found an unexpected error. We will try to save your project". After a while the program shut down. I rebooted the computer, and when i restarted the program i found out that not only my project file had dissappeared, but also the Avi's Captured from tapes. I recovered the project from a previous autosave but most of the clips are offline. The most surprising thing is that checking the scratch disk, it has the same Gb occupied than it had before the "deletion" of the avis. So, I suppose they are still there but a cannot read them. Is that correct? How Can I retrieve them?
    Thanks in advance for your responses,
    Salvador Savarese
    Buenos Aires, Argentina

    I'm with Bill in that I've never seen Premiere delete either a project file or actual media, even after an error like that.  Chances are more than likely the reported problem is partly due to operator error.
    For example, clips being offline isn't the same as actual media being deleted from the hard drive.  My very strong suspicion is that you have a case of the former, not the latter.  If that's the case, then it's also very likely your original project is still on the hard drive, right where you left it, even if it doesn't appear in the recent projects list upon startup of Premiere.

Maybe you are looking for

  • HT1338 cd or dvd are not detected

    no cd or dvd are detected it just spins and is ejected

  • Timestamplockingpolicy - ClassCastException

    In our workshop, we are using Toplink latest version. I am trying to use TimestampLockingPolicy on a DB2 database table. The attribute is lastUpdatedAt which is java.sql.Timestamp. When I am running the application, I am getting ClassCastException in

  • How do I discontinue a Elments 11 trial?

    I keep receiving e-mail from Adobe telling me that time is running out for my trial of Adobe Elements 11.  Although I purchased and installed Photoshop Elements11, it is not my intention of adopting Elements 11 for home use because I almost never do

  • Access webservices through SSL

    HI! I want to access webservices through SSL. I could config the SOA suite to connect to (for example) Enterprise Manager Console through SSL (https://localhost:4443/em), but when I want to try to access a webservice through SSL (https://bonus4:4443/

  • Can my website be saved?

    My computer crashed and everything had to be reinstalled. I lost everything from the hard drive. I can access my website on-line, but when I go to iWeb none of my documents are there. I have tried dragging the site pages that are stored on iDisk, but