Premiere Pro Unresponsive after queuing to Media Encoder

In the current version of Premiere Pro (8.1.0), every time a send a sequence to the Media Encoder, Premiere becomes unresponsive. But not in a spinning beach ball of death fashion. It's like the UI is non responsive, with some very strange behavior. For example, when I try to quit and save, the save dialogue just sits there until I have to force quit the application.
Any thoughts? This is extremely annoying!

Exact same problem here, plus exports are slow
Specs
latest CC
OSX 10.9.2
3.4GHz Core i7
32Gb 1600MHz DDR3
GTX 680MX GPU
4TB Thunderbolt GRAID, footage/project files
3TB USB3 Seagate for cache
1TB Apple for system

Similar Messages

  • Premiere Pro freezes after exporting with Media Encoder

    So I'm running the latest version of CC.
    Mac Pro, OSX 10.9.2, 8-Core Xeon, 24GB RAM, ATI Radeon HD 5870 1GB
    I've got a very simple and straight forward timeline. After sending "Exporting Media" via queue to Media Encoder, everything exports fine. But after returning to Premiere, it has become impossibly slow--practically frozen. No crash, no error message, just takes about 60 seconds for any clicks to register. I click save project, and the saving progress bar does not visibly progress, yet it seems to actually successfully save the project, because closing and launching premiere, the file is saved up-to-date just fine.
    So for the past few days, I've been saving --> export/queue timeline --> quit premiere --> allow queue to complete --> then relaunch premiere... Of course, this is only a temporary work around.
    Now, if I "Export" the media only without queueing in Encoder, it does fine and premiere remains stable and normal.
    Ideas?

    Exact same problem here, plus exports are slow
    Specs
    latest CC
    OSX 10.9.2
    3.4GHz Core i7
    32Gb 1600MHz DDR3
    GTX 680MX GPU
    4TB Thunderbolt GRAID, footage/project files
    3TB USB3 Seagate for cache
    1TB Apple for system

  • We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason. Anyone else got that too with Premiere Pro CC and the new Media encoder? Thanks! bedrijfsfilm Companyfilms

    We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason. Anyone else got that too with Premiere Pro CC and the new Media encoder?

    We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason
    Anyone else got that too with Premiere Pro CC and the new Media encoder?
    Lack of detailed info makes your question impossible for anyone to answer you!
    eg. ...."Doctor it hurts...anyone else got something that hurts?" 

  • Premiere Pro CS4 Export fails with Media Encoder CS4 "Encoding Failed"," Could Not Read From Source.

    There has never been a history of Adobe CS3 installation on the brand new MAC Pro I am using prior to installing Master Collection CS4, despite other posts claiming that chief cause of this issue is a previous CS3, Beta or trial installations of previous versions. I simply had a straightforward installation of CS4 and have had trouble since day 1.
    I have uninstalled and reinstalled Master CS4 three times, two times with the action script cleaner for CS4. I tried changing Adobe Cache folder locations to alternative drives. I ran shift start many times to correct any inconsistencies and corrected for permissions using disk utilities repeatedly. All updates have been installed and I am still getting the same error when exporting my timeline to Media Encoder CS4, be it a large High Definition project or a small one consisting of few stills.
    No matter what presets I chose, the job appears as one of the items in the render qeuee of Media Encoder CS4 and sits there with the status WAITING until i hit Start Queue. When I do, it still says WAITING under Status and at the bottom corner of the window it reads : Loading "project name.prproj" and after an average of about 6 minutes, a yellow caution sign appears. No render whatsoever takes place. When I click on the yellow caution sign, it reads a log of all errors in connection with each job, including the ones that have gone before it. Here is one:
    Start of the Error Paste
    - Source File:/users/myname/Library/Caches/TemporaryItems/test.prproj
    - Output File:/ users/my name/Documetns/Adobe/Premiere Pro/4.0/Sequence 01.mov
    - Preset used :NTSC DV
    - Video:
    - Audio:
    - Bitrate:
    0 Encoding Time: 00:33:01
    Sat Mar 21 17:12:25 2009 : Encoding failed
    Could not read from the source. Please check if it has moved or been deleted.
    END OF ERROR Paste
    Please any gurus out there know how to troubleshoot this damn thing on Mac, I really appreciate it. I have not yet encountered any posts of Mac owners with no previous CS3 installation having this issue. I am in the middle of 3 projects with tight deadlines and need your urgent help. THANK YOU!

    Hello There,
    I resolved the issue through a simple process of elimination. So simple in fact I wonder how I missed it. Since there has been no history of prior CS3 installation on this machine and every conceivable trick was applied to resolve the problem (refer to my original post earlier in the thread) ending in frustration, the problem had to reside in a factor or series of factors that were only present in this machine. Of the two remaining causes different in compare to other machines, I had to look into the possibility of any hardware and/or software conflicts. After all, this very same installation works perfectly fine on my colleague's Apple Macbook Pro and several Windows machines.
    It turns out that I had installed Pro Tools on this machine that comes with all kinds of optional plug-ins in the so called ignition pack. One of these optional plug-ins is called IZOTOPE (three varieties include Spectron, Trash and another one that escapes my mind). They were all lite version licenses that would automatically pop up on their own when you would start a program where they had been residing. One such program where an association existed was indeed the Premiere. An annoying dialogue box directing you to buy the full version when you would start the premiere would refuse to go away. Sometimes it would even start on its own culminating in a a permanent dialogue box.
    The cause of the problem was right before my eyes and I had overlooked it. Once uninstalled using IZOTOPE clean uninstaller on step 4, the problem was resolved. Projects are now loading very fast into the AME and encoding begins in earnest. I have never had any issues ever since.
    Long story short, if you have any plug-ins specially the ones that are loading upon the start of any program or the ones that reside inside the premiere or the ones that start on their own independently, they could be one of the highly probable causes of this error. I have seen other similar posts complaining of plug in folders inside premiere that needed to be moved to resolve the issue for instance the ones that needed to be moved to AE folders. If you are a plug-in admirer, I would suggest to look into them seriously.
    On the side note, many combination and causes may lead to the same error. I am not claiming that this is the solution for everyone.
    It must also be noted that I applied the trick of creating a shortcut of Premiere (and naming it exactly as such) and dropped it into the Adobe Dynamic LInk folder (even though this was suggested for windows)and have changed the adobe Cache locations to an alternative folder on a separate drive. I haven't been able to establish conclusively if the latter steps are also essential in fixing the error on MAC but I can confirm that since the latter steps were taken before the uninstalling of Izotope plug-ins and i still had issues, probably uninstalling those plug ins or finding a way to move them to a place where they don't interfere (if you absolutely need to keep them) is the one essential step that solved the problem.
    Hope this helps.

  • Premiere Pro not Exporting to Adobe Media Encoder

    Never had this problem before on a Mac. Now using a Windows 7 Machine.
    Intel Xeon CPU E5-2630 v3 @2.40 (2 processors)
    64 GB Ram
    Nividia Quadro K4200 v. 2.1.2
    Trying to export a Premiere Pro sequence to Media Encoder for encoding. Nothing pops up in AME. And if I try to add the sequence from within AME, doesn't work either. Exporting directly from Premiere DOES work though. Any ideas?

    This was my first video in Premiere Pro CS4.
    Information Hard Disk #1 :
    Manufacturer :
    Seagate
    Model :
    ST3500418AS
    Serial Number :
    5VMFTSYR
    Revision (Firmware) :
    CC38
    Family :
    Seagate Barracuda 7200.12 family
    Serial ATA :
    Yes
    Serial ATA Version :
    2.0  -  (SATA-300)
    Support :
    ATA8-ACS
    Size :
    500GB
    Solid State Disk (SSD) :
    No
    Speed :
    7200 rpm
    Cache :
    16 384KB
    Information Hard Disk #2 :
    Model :
    MAXTOR STM3320620AS
    Serial Number :
    6QF4Z8WZ
    Revision (Firmware) :
    3.AAE
    Family :
    Seagate Maxtor DiamondMax 21
    Serial ATA :
    Yes
    Serial ATA Version :
    1.0  -  (SATA-150)
    Support :
    ATA/ATAPI-7
    Size :
    320GB
    Cache :
    16 384KB
    ECC Size :
    4
    Multiple Sector :
    16
    Thanks for your reply

  • Exporting from Premiere Pro.  Takes forever for Media Encoder to start.

    When I exported a timeline out of PrePro to the Media Encoder and press "Start Queue" it took it over 19 minutes before it began rendering.  Is this normal?

    Morning all
    Fair point John.
    Webshark2000, the orignal poster of this topic, has got Vista 64bit, so he can make use of the more memory.
    I understand that memory use for  CS4 is:
    Premiere -  2gigs
    Encore - 2gigs
    Media Encoder - 1 gig
    + Windows and other apps you may have running!
    So if you don't have around 5 - 6 gigs ram, Windows will be doing ALOT of paging! Thus slowing the system and render times down.
    64Bit and tons of ram -  is the way forward. It rocks with it!
    Hope that helps - Shaun

  • Premiere Pro CC 2014 update and Media Encoder update fail to install

    Hi -
    I've been updating my CC applications. But PP CC 2014 and media Encoder say: "UPDATE FAILED". Naturally I cannot get through to Abobe. Does anyone have a suggestion?
    Harry

    Hi Harry,
    Sorry, chat and phone support are closed on weekends for the video queue. We only have general support open on weekends. It's been this way for years. Sorry if that caused some inconvenience.
    I hope you have solved your issue. If on Mac, you can update NVIDIA drivers in the NVIDIA control panel in System Preferences. AMD GPUs are merely updated when you update OS X.
    Also, please check out the doc that was recommended: Installation failed. Error U44M1P7 | Updates
    If you are still having trouble, contact us Monday through Friday 7AM-7PM PST here: Contact Customer Care
    If you can't get your issue solved, send me a PM and I'll try and help.
    BTW, I am not sure why your post is marked as correct. I do have that ability but did not do that. Sorry for that.
    Thanks,
    Kevin

  • Premiere Pro CC not queuing exports into Media Encoder CC

    I try to make this simple...
    standard export from PP CC to ME CC
    File -> export -> media, then hit queue.
    Media encoder opens and just sits there. Left it for hours to see if anything would ever happen, and nothing ever did.
    I've restarted the programs and machine dozens of times and that does nothing.
    I can still export from PP CC.
    I have no CS6 products left on my box.
    I also tried to open the project from Media Encoder and load the sequence that way with no luck.
    Thanks for the help!
    On a Mac Pro
    Premiere version 7.0.1
    Media Encoder version 7.0.1.58
    Adobe Creative Cloud for Teams Member (so it's licenced and updated to the fullest)

    rforgaard wrote:
    I had this exact same problem, and I figured out the solution in my case.  I know the original problem report is ancient, but there are recent replies, so I am adding my solution here.  I spent untold hours figuring this out, so hopefully this will save someone else some time.
    There can be other causes to this problem, I'm sure.  I'm just telling you about what fixed this problem for me.
    Just to clarify, here is the symptom: Running Windows 8.1.  Standard export from Premiere Pro CC 2014.2 to Media Encoder CC 2014.2, using File -> Export -> click Queue.  Media Encoder opens and just sits there.  Premiere Pro is hung and has to be forcibly terminated.
    I spent countless hours on this.  I thought I had messed up my computer's configuration somehow, so (believe it or not) I re-installed Windows on a freshly formatted hard disk, re-installed Creative Suite, same problem.  (I can't believe I wasted all that time; I feel like a dummy.)
    I finally narrowed it down to a very simple test case with a very tiny one-clip sequence that is less than one second long.  Same problem.
    It turned out to be a problem in the Premiere Pro project file itself.  I suspect that a small file corruption somehow snuck into the project file, that was completely invisible.  In that clip in my project, if I removed the "Vocal Enhancer" effect, the problem with exporting to Media Encoder went away.  If I then re-added the very same "Vocal Enhancer" effect, the problem was still gone.  It must be some small corruption in the ".prproj" file that went away when I removed the "Vocal Enhancer" effect and re-added it again.
    NOTE: I DON'T think that there is some kind of bug with the "Vocal Enhancer" effect.  I don't think this problem has anything to do with "Vocal Enhancer" per se.  It is just some kind of small generic corruption in the project file.  When Premiere Pro tries to export that sequence to Media Encoder, the problem occurs.  It was just a coincidence in my case that removing and re-adding the "Vocal Enhancer" effect made the problem go away.
    BOTTOM LINE: If you find that you have this bug where Premiere Pro hangs when exporting to the Media Encoder queue, try the following: Create a brand new project with a single clip in it, and export it to the Media Encoder queue.  If that works, you know that it is not a problem with Premiere Pro in general; it's a problem in your specific project file.  Once you've made this determination, make a copy of your original project file, and remove clips from the project until the problem goes away.  Keep narrowing it down until you find the clip(s) that are the issue.  Then, try removing and re-adding any effects on those clips, or even removing and re-adding the clips themselves, to fix the problem.  Eventually, by removing and re-adding a specific effect or clip to your project, the problem will vanish (hopefully).  It's just a matter of narrowing down which half of your project the problem occurs in, then which half of that half, etc., until you have it narrowed down to one clip or group of clips that need to be removed and re-added.
    Having said all this, it is a bug that ideally should be fixed so someone else doesn't spend untold hours trying to figure out the problem.  To that end, I create a tiny ZIP file that just has project file and the single media clip needed to reproduce the problem, along with a small description "READ ME.txt" file that explains the very simple steps to reproduce the problem.  I have submitted this as a bug report to Adobe using their official online bug report form at www.adobe.com/cfusion/mmform/index.cfm?name=wishform along with a link to the ZIP file so they can download and reproduce the problem.
    If anyone else is curious about reproducing this same bug, you can also download the small ZIP file if you want to.  I guarantee it doesn't have any viruses or anything - it's just two small files to reproduce the problem.  To download the ZIP file containing that project file, media file, and "READ ME.txt" file, you can get it at www.forgaard.com/files/PremiereProBug.zip.
    I hope this saves someone some time.  This one sucked up a zillion hours of me chasing apparitions.
    I was having a problem with exporting a sequence to AME.  PPro would freeze and I would have to force the program to close.  This was on a project where I was just running out a bunch of interview clips for the director to look at.  One of them had a audio effect (DeHummer) on it, and it was the one that was giving me troubles.  I selected the audio and right clicked then "Render and Replace" then it would export to AME with no issue.  Thank you for your well written response to this thread.  While it may not have fixed the OP's issue, it did help with mine....
    Thanks,
    Phil

  • Premiere Pro CC hanging on export media

    Hello,
    I've a project shot on P2 cards with a couple of MP3 audio tracks. Never been a problem before. Went to export media (Queue to Media Encoder) and as it's processing the request the application stops responding.  (also realized at this time the auto-save wasn't so I lost 2hrs work)
    After recreating and saving - same issue - hang on export media
    Updated to Premiere Pro CC 2014 - managed to get to Media Encoder and then it failed with an unspecified H.264 error (I'm trying to save to the H.264 YouTube 720p 29.97 compression) When I tried again, it hung up on the export process as originally happening.
    Trashed preferences (of both versions of PPCC) - tried again - same results
    Removed MP3s and tried again - same results
    Went back to Premiere Pro CC and opened another project shot with a Canon 7D and was able to export media.
    I've done at least ten projects with my Panasonic Camera's and the P2 workflow in Premiere Pro CC and have not had any problems.
    Any suggestions on how to troubleshoot further would be greatly appreciated.
    Mark
    MacPro

    OK, So to be more specific it's hanging when I send it to Media Encoder Queue. I was just able to just do a direct export.
    I found the article on permissions and that was not the issue.
    I've made no changes to hardware and have done three projects with the same codecs, type footage, duration (1 hour range) with no problems.

  • Both After Effects & Adobe Media Encode CC giving are not letting me export.

    Dear All,
    Both After Effects & Adobe Media Encode CC giving are not letting me export movies.
    Some times they will, but after one file both programs give me the following error messages.
    After effects:
    “[file path and name].mov. An output module failed. The file may be damaged or corrupted. (-1610153464)"
    AME:
    "Can't read from source."
    I've went through the forum and found threads & pages discussing the problem.
    E.g.
    http://blogs.adobe.com/aftereffects/2013/08/solutions-for-problems-with-quicktime-files-in -after-effects-cc-12-0-because-of-conflict-with-dvcprohdvideoout-quicktime-component.html
    http://forums.adobe.com/thread/1252092
    After following all the tips and suggestions (from deinstalling quicktime components & audio components to completely reinstalling CC) I'm still experiencing the problems.
    Which leaves me in a bit of a squeeze. I need to export over 144 movies in the coming 2 days and the only way to do this is to quit and open media encoder (or AE) after each single export.
    Not really an option.
    Both problems have the process Adobe QT sever in common, I took this from the console:
    9/26/13 1:02:44.517 PM com.apple.launchd.peruser.501[171]: ([0x0-0x42042].com.adobe.Adobe QT32 Server.application[331]) Job appears to have crashed: Segmentation fault: 11
    9/26/13 1:02:44.672 PM ReportCrash[354]: Saved crash report for Adobe QT32 Server[331] version 7.0.1 (7.0.1.0) to /Users/martijn/Library/Logs/DiagnosticReports/Adobe QT32 Server_2013-09-26-130244_martijns-MacBook-Pro-2.crash
    System information:
    Retina MacBook Pro (Mid 2012) (16gb ram)
    Mac OS X 10.8.5 (12F37)
    Running Adobe CC (for teams), all apps are up-to-date.
    I don't no why Adobe puts out such a buggy piece of software (I know it has to with Apple's poor 32bit quicktime implimentation, but hey, this was known information no?).
    Upgrading to CC has given our office nothing but problems.
    Hope someone can help to find a work around until Adobe realeases a proper update and solves this problem once and for all.
    All help is much appreciated.
    Kind regards,
    Martijn

    Hello Tim,
    Thanks for the really quick response!
    Regarding the crash log: it doesn't reference com.apple.audio.CoreAudio (though it did before, so I followed all the steps in your blog post before I posted to this forum).
    I've uploaded the crashlog to:
    http://martijnlambada.com/TMP/AdobeQT32servercrash.zip
    If you want to inspect it. It mentions the DXV codec (which I also uninstalled), but the crash keeps occuring. Also I need to export to DXV since it's the only codec the d3 media
    server accepts (http://d3technologies.com).
    I followed all the steps in the troubleshooting steps.
    Codecs used: I've tried everything from animation to Apple ProRes (including: h264/motion jpeg/uncompressed). With all codecs the Adobe QT32 server keeps crashing (though I can't always reproduce).
    Export destination: Internal SSD (same as where the OS is installed on) + External raid (via firewire & thunderbolt) + external HD via usb 3.0 (tried everything).
    When does the problem start: Really hard to specify, sometimes a day without crashes, sometimes every export for days on end. Sometime after restarting (tried logging out, restarting, switching off and on the computer). With other programs running and with out. Now checking every process active when exporting, and comparing log files.
    Can you export to other formats: See question 1, sometimes I can, sometimes not.
    When you launch AE and/or AME, is QT32 Server running? At what point does it stop running?  Still runing when I open the program. It crashes when exporting (ofter after finishing the first export).
    What component files are in your Library/QuickTime folder?: Currently the folowing:
    AppleAVCIntraCodec
    AppleHDVCodec.component
    AppleIntermediateCodec.component
    AppleMPEG2Codec.component
    AppleProResCodec.component
    DesktopVideoOut.component
    DVCPROHDCodec.component
    DVCPROHDMuxer.component
    DVCPROHDVideoDigitizer.component
    DVCPROHDVideoOutput.component
    DVCPROHDVideoOutputClock.component
    FCP Uncompressed 422.component
    iChatTheaterPreview.component
    IMXCodec.component
    LiveType.component
    Hope this helps.
    Cheers,
    Martijn

  • 2009 & 2010 MacPro upgrading for today´s Video-editing (Premiere Pro CS6 & After Effects)

    I have now two  MacPro´s: MacPro4,1 (Early 2009/Nehalem) and MacPro5,1 (Early 2010/Nehalem) and I was wondering how to get the best of them for video-editing with Premiere Pro and After Effects (CS6 or later CC) for todays standards.
    The specs of the machines:
    MacPro5,1
    Early 2010 Nehalem
    (http://www.everymac.com/systems/apple/mac_pro/specs/mac-pro-quad-core-2.8-mid-2010-nehalem -specs.html)
    2.8GHz     Quad-core Xeon W3530 (256k level 2 cache, 8 MB of "fully shared" level 3 cache)
    32GB RAM "1066 MHz DDR3 ECC SDRAM" (PC3-8500) modules (4 x 8GB)
    ATI Radeon HD 5770 with 1 GB of GDDR5 memory is installed in a double-wide, 16-lane PCI Express 2.0 graphics slot.
    single 1 TB (7200 RPM, 32 MB cache) Serial ATA 3Gb/s hard drive.
    + I have added a 480GB SSD-drive via PCIe (http://eshop.macsales.com/shop/SSD/PCIe/OWC/Mercury_Accelsior/RAID )
    The 480GB PCIe SSD-drive is now the boot-drive and gets writes over 500MB/s and reads over 600MB/s testing with "BlackMagic Speed Test"-application. The 480GB SSD-drive that is connected via PCIe-card has also two eSATA ports on it. How could I take advantage of them? Is this just a bottleneck, what would you think. Would I get the same results if I had just Samsung 840 SSD installed with adapter-device to the internal drive bay 2.5" SATAII connections?
    What about the graphic card?
    What would you suggest to do for the setup to maximize it´s potential (For now it´s working fine)? Would it be good idea ome 7200rpm hard-drives for media and cache storage or do I need that or can I see significant improvements over it since there is still 3 3,5" internal hard drive bays with SATA II connections (and the two eSATA ports).
    MacPro4,1
    (Early 2009/ Nehalem)
    (http://www.everymac.com/systems/apple/mac_pro/specs/mac-pro-eight-core-2.66-early-2009-neh alem-specs.html)
    - 8-cores: powered by two2.66 GHz Quad Core 45-nm Xeon X5550 (Nehalem) processors with a dedicated 256k of level 2 cache for each core and 8 MB of "fully shared" level 3 cacheper processor.
    - 34GB 1066 MHz DDR3 ECC SDRAM
    -NVIDIA GeForce GT 120 with 512 MB of GDDR3
    A lot like the MacPro5,1 but does have a bit different graphic cards and more memory and cores.
    Any ideas?

    jsssi wrote:
    What about the graphic card?
    What would you suggest to do for the setup to maximize it´s potential (For now it´s working fine)? Would it be good idea ome 7200rpm hard-drives for media and cache storage or do I need that or can I see significant improvements over it since there is still 3 3,5" internal hard drive bays with SATA II connections (and the two eSATA ports).
    First and foremost: keep an eye on that 480G PCI-E SSD that you dumped a lot of money into.  Those OWC drives aren't known for their robustness or reliability (OWC folks will argue with that statement.  Ignore them).  Since OS and apps are easy to re-install, it may not be a big deal.  But don't put any of your projects on it, even though it's a fairly quick device.
    Second, start adding SATA drives to the other 3 bays.  Fill them up with the biggest drives you feel comfortable buying.  Make one of them a 10k RPM drive for your scratch space.  The others can be 7200RPM drives; since you're limited to SATA2, there's not much use in trying to crank serious disk bandwidth through the system.
    Video cards.  Get rid of those OEM garbage cards.  Drop them into a chipper/shredder, in fact.  Contact this guy about getting flashed nVidia cards that will work in both Macs, and will help with Pr and Ae.  Dave can sell you a flashed GTX780 that will boot (with grey Apple screen) and run in the Mac just fine.  And it'll outperform anything Apple has ever sold for those Mac Pros.

  • I need to reinstall my computer, how do I deal with Premiere pro and After effects?

    Hello,
    As my question states I need to reinstall my computer (laptop) and I'm not quite sure on how to deal with Premiere pro and After effects.
    I am thinking that I need to do some sort of backup and save my projects and footage on a sepparate drive.
    If I reinstall my computer, install my creative suit production premium, and move back all of my projects and footage, won't I have to re-link every single clip?
    I am currently workning on several different projects and having to re-link everything is something I don't even want to think about, that would take me days if not weeks.
    Another option on my mind would be to use Creative cloud. I do have the free version but I have never used it even once before and I'm not quite sure what the purpose of the cloud is and if this is a way to use it.
    I have no idea how to go about this computer reinstalation without either loosing tons of work or having to re-link every single clip used.
    I am videoediting only as a hobby so I have no experience working with other people and sharing projects or the like, wich is my understanding of what the cloud is for.
    Any and all help would be grealty appreciated, I know this is probably really easy but ever since i got my Suit I haven't reinstalled, upgraded och changed my computer so I am just clueless as to how to go about this.
    I have Creative suit production premium, I also have the free Creative cloud.
    It is only Premiere pro and After effects that I am using and am worried about.
    Thank you for any help.
    -Lisa Kajupank
    (and oh, I just notice my name - umustbejoking - I think I just wrote that cause they wouldn't let me use anything else, saying it was already taken. So nevermind that haha.)
    Message was edited by: umustbejoking

    If the computer's running Mac OS X, move the cursor to the very top of the computer's screen, click on Store, and choose Authorize this Computer.
    If the computer's running Windows, press the Alt and S keys and choose Authorize this Computer, or click here, follow the instructions, click on Store in the menu bar, and choose Authorize this Computer.
    (84620)

  • Nikon D7000 .MOV files in Premiere Pro and After Effects CS5.5

    I recently upgraded from Production Premium CS5 to CS5.5. Initially Nikon D7000 .MOV files used in previous CS5 Premiere Pro project would not play well in CS5.5. Now .MOV files do work in both PP and AE CS5.5. Here are the steps I followed. Not recommending you follow my steps exactly, just providing info for those that are interested.
    1.       Launch Premiere Pro CS5.5 and open previous PP CS5 project, convert project to CS5.5 and rename project file as not to replace previous CS5 project file.
    a.       At this point .MOV files do not play in new project or in AE CS5.5
    b.      Close Premiere Pro and After Effect if still running.
    2.       Using Adobe Bridge CS5.5, batch rename;
    a.       Make copies of original files to new folder location while renaming file extension from .MOV to .mpg
    b.      Let Adobe Bridge finish creating all new thumbnail previews.
    c.       Leave Bridge running in background.
    3.       Launch Premiere Pro CS5.5, let Premiere finish recreating thumbnail previews if needed.
    a.       Attempt to preview existing .MOV file in project. It worked for me.
    b.      Attempt to play sequence containing .MOV files. It worked for me.
    c.       Attempt to play or modify sequence .MOV files in AE CS5.5 via Dynamic Link within Premiere. It worked for me.
    d.      Close Premiere Pro project and AE projects if open.
    4.       Create new Premiere Pro project and sequence
    a.       Import a different Nikon D7000 .MOV file not previously used or renamed.
    b.      Attempt to play this newly imported .MOV file. This worked for me as well.
    c.       The new, previously un-renamed .MOV file also worked in AE CS5.5 for me.
    I will perform additional tests but at the moment Nikon D7000 .MOV files are working for me in CS5.5 after initially performing a batch rename in Bridge CS5.5 from .MOV to .mpg and letting Bridge create preview files. Even .MOV files not renamed now work.
    An example of Nikon D7000 footage edited with Adobe Premiere Pro CS5.5, After Effects CS5.5, and Sound Booth CS5 can be seen on my blog, http://stevelandonsmyth.typepad.com/steve-landon-smyths-blog/2011/07/my-first-hd -video-shoot-with-nikon-d7000.html
    My system: MacBook Pro 17" 2.3 GHz i7 quad core, 8GB RAM, 500MB SSD
    Message was edited by: Steve Landon-Smyth

    Hello,
    I see 2 post in this thread from Todd that say they are working on a fix and it should be out soon.  One is from July, the other from August.  It is now Sept 7th and I still see no patches or fixes for any bugs.  I spent 400 dollars on an upgrade, but is this upgrade going to be supported?
    This is making me rethink upgrading to the .5's in the future.
    It is a minor bug to most, but in that sense it should be an easy quick fix. Am I wrong? Is this really a complicated issue?
    I apologize if this comes off like a rant, but thats kinda what it is.  It is not hard to batch rename files, but its a pain to have to relink all those files in PP.

  • Error code U44M1P34 when trying to update Premiere Pro and After Effects- tried everything, nothing works

    I am out of ideas here. I had several program installed for months with no issues. Every update was fine. I haven't moved any installations or changed configurations, etc. I have probably a dozen CC apps installed or more.
    Then out of nowhere, I start getting an error U44M1P34 when trying to update Premiere Pro. After Effects updates give me a similar error.
    1. Tried uninstalling these apps, then restarting, then installing again, but no luck. It tells me that installation was successful, but an update failed.
    2. I tried clearing all temp files, etc. No luck.
    3. I uninstalled EVERYTHING Adobe related on my computer. Restarted. Ran the Cleaner tool as admin. Restarted. Installed Creative Cloud then tried to install Premiere Pro. Same problem.
    So after all that, including putting my work on hold so I can uninstall everything from my machine and try all this junk, it still gives me an error. I can't update those two programs, and maybe more(hard to say since some programs haven't had updates since this started, so it might be worse than just those two).
    I was able to install programs like Fireworks and Muse without issue since these problems started.
    I've pretty much read every post of every thread where this error message is at. I've looked at my log files, but don't see anything fatal(please tell me what I'm supposed to be looking for as the instructions given are vague at best).
    I just need to get this stuff installed and updated. Any ideas? Since I've literally removed Adobe's presence from my computer, then started from scratch, what else is there to try? I haven't moved ANYTHING to another drive or partition. Everything is in the same place it was since 10 months ago when I started CC.
    I'm running Windows 8.1 Update 1 64-bit. 16GB RAM, hundreds of GB of HD space remaining. Geforce GTX760m (also have the Intel 4600 integrated graphics, for whatever that's worth).
    I've run both PP and AE  just fine, and they even run fine without the update. But I WANT to update them.
    Ideas or thoughts are appreciated. Thanks.
    Brent

    Well, the Adobe rep hasn't called me yet.
    The good news though is that it's no longer an issue. Since the 2014 versions of the Adobe CC apps were released today, I was able to install/update just fine. So it was something with the previous update that was broken, or something like that.
    FWIW, the new 2014 editions are fantastic so far. Some great improvements that I'm happy with. I just wonder whether this update issue will rear it's ugly head again with a later revision?
    Time will tell. Thanks for the help regardless!
    Brent

  • How much does Premiere Pro and After Effects rely on the hard drive it's installed on?

    This may be a really dumb question, but how much does Premiere Pro and After Effects rely on the hard drive it's installed on if all your video files, assets, disk cache, etc are on different drives than the one the program itself is installed on?
    The reason I am asking is that I currently have a "relatively" slow Sata II SSD for my C drive that has just my OS (windows 7 64bit) and programs (adobe editing programs, no games) installed on it and nothing else. All of the files used in my projects are saved on either a very fast Sata III SSD or a slower HDD depending on what the files are. For example, disk cache on the Sata III, stills on the HDD.
    Being cyber monday I have the opportunity to buy another very fast Sata III SSD to replace my current Sata II SSD C Drive (just OS and programs). Both synthetic and real world benchmarks show a near double in performance. I just want to know if anyone thinks the upgrade is even worth it because for all I know there won't be any increase in performance since no videos, still, cach, etc will be stored on the C Drive.
    The alternative is to get a second monitor because I currently only use one 21" monitor.
    I suppose another alternative would be to not buy anything on the cyber monday deals and just save money for something else.
    Any advice or input would be greatly appreciated. Thanks!

    Thanks Alex! I think you are right about not being able to notice the difference between the SSDs. I ended up finding a deal to get about $80 off a great monitor that I've been looking at for a while and decided to pull the trigger on it. I thought about it and realized that there have already been a bunch of times where I want to watch a tutorial on youtube and follow allong in AE or PrePro, but have to keep switching windows. I also frequently want to have my video preview on a separate monitor so I can have a taller timeline window. This monitor will help a lot with that. Thanks again for your help!

Maybe you are looking for