Update to Premiere 5.5 is a joke

After installing all 3 disks and seeing that the install was complete,
I checked the W7 desktop for changes. Same old icons and they
launch all 5.0 program versions.
The only real reason was to get rid of that junky Soundbooth and get an updated Audition.
So Adobe doesn't update the desktop icons? I have to fish around for them and then kill off the old ones? That seems kind of primative. After finding the 5.5 Premiere icon and launching the program, I now discover that the 5.0 projects now have to be "converted". After converting one, it no longer works.
Plus it no longer recognizes my Black Magic Desgin interface - so I guess I have to rip out and reinstall that too.
Thanks for nothing Adobe.

Anyone have any thoughts on whether or not a "Clean Install" is good idea?
Right now I have CS4 and CS5 in edit station.  (putting CS4 back in along with CS5 gave me .mpeg HDV previews in Bridge which I need.)  So updating/grading to my CS5.5 Master Suite will add to the drive.  Things are working well now, don't want to upset the cart.
RG

Similar Messages

  • Problem update Adobe Premiere Pro CC(2014)

    Hello,
    when I try to update Adobe Premiere Pro CC 2014 the system give me this error "Unable to extract the downloaded files. To download please selected try again. (U44M1L210)
    Nicolò

    We can't know anything. You have not provided any system info or the detailed error report from the "Learn more/ More info" link.
    Mylenium

  • I can't update my Premiere Pro CC 2014 8.01 Version to 8.1 on my mac...???

    I try to update my Premiere 8.01 to 8.1 on my Mac Pro Workstation with 10.8.5 OSX. Creative Cloud only install the 8.01 version.
    I tried to uninstall and reinstall with updates but it will alway only give me the 8.01 version and not the new one...???
    Does anybody have the same problems or any ideas?
    Best regards
    Florian.

    Hi Florian,
    Please sign out of Creative Cloud, then sign back in: http://helpx.adobe.com/x-productkb/policy-pricing/activation-deactivation-products.html#ac tivate-how-to
    Thanks,
    Kevin

  • Cannot Install the Raw 7.3 update for Premiere Elements 11 and photoshop Elements

    I get an error message when I try to update the  Raw 7.3 update for Premiere Elements 11 and photoshop Elements. It says to run support adviser which I did, but it says that it could not detect any problems.
    Thanks,
    Ron

    The next step will be to review the installation logs for the cause of the installation failure.  You can find details on how to locate and interpret your installation logs at Troubleshoot with install logs | CS5, CS5.5, CS6 - http://helpx.adobe.com/creative-suite/kb/troubleshoot-install-logs-cs5-cs5.html.

  • I bought the pkg. of Photoshop & Premiere Elements 10 in 2012.  I now want to update to  Premiere Elements 13 without updating Photoshop.  Can I do this?  Will you please tell me the steps I need to take?

    I purchased Photoshop and Premiere Elements 10 as a package in 2012.  I now want to update the Premiere to the 13 edition, without updating Photoshop.  Can I do this?  Will you please tell me the steps I need to take?

    Just buy version Premiere Elements 13.
    Even if you don't get the "upgrade" price, you can probably find it for about that cost on sites like Amazon.com.
    You can keep Photo Elements 13 if you'd like. The only downside is that Premiere Elements 13 and Photo Elements 10 won't share the same Organizer catalog. Otherwise, they'll get along just fine.

  • My PC works OK with dowload, but when I try to make an update for Premiere Elements 9, it says "An error occured during download, quit and retry later"

    My PC works OK with dowload, but when I try to make an update for Premiere Elements 9, it says "An error occured during download, quit and retry later" - What can I do ?

    try a manual update,  http://www.adobe.com/downloads/updates/

  • I just updated to Premiere Pro CC 2014 and it can't start up

    I just updated to Premiere Pro CC 2014, and now I am seeing an error message saying it cannot find any capable play modules. I updated the driver for my graphics card (Firepro), and tried running as administrator with no change. I am running amd fire pro control center which doesn't have the speed settings that is suggested for this problem. For some reason, the original Premiere Pro CC can still open (luckily). I looked up this problem on the on the support page, and it is listed, but when I click the link it redirects me to the start of the troubleshooting questions. I hope there is an answer to let me use the latest version of Premiere!
    [moving to Premiere Pro... JTS]

    Same here! Screen shot attached. I'm running the latest MBP with max specs. Anybody there @ Adobe.......?
    ***UPDATE*** - it's pretty easy to fix yourself. Just follow these helpful instruction on Creative Cow: Re: CC 2014 startup issues : Adobe Premiere Pro

  • Have the problem to export media use the queue after the latest update of Premiere and Media encoder?

    After update the Premiere CC 2014 and Encoder CC 2014, I couldn't export the movie use the Queue function?
    There always had a unknown error stop the process. (Compile error?)

    You need to fix that first.
    Export and preview in the Media Encoder and watch when it stops.
    There you need to fix the timeline.
    Start a new project to see if you can use AME.

  • Updated to Premiere CC 2014, now I can't export. Error - unknown error.

    Hello -
    I recently updated my Premiere Pro to the 2014 version. I opened my project in the new 2014 release and kept editing, but now when I want to export I can't. It fails every time at the beginning of the export and then gives me "Error - unknown error"
    I've tried copying the sequence into a new sequence AND a new project. I've tried exporting with all different settings, to no avail. I have cleared the media cache and the preview files just in case. Cannot fix this! Need to export for a client so any help would be appreciated.
    Basic doc-style sequence - some AE comps for Titles, some images with the ken burns effect, and 2 video tracks. Shot 720p and trying to export for 720p. 
    help!
    Thanks

    Hi,
    Does this error come up as soon as you start the export procedure.
    Did you try to export it through the Media Encoder?
    Thank You
    Arjun

  • After ther last update for Premiere CC, when I export to MEdia Encoder, it freezes

    Can I roll back the last update for premiere? Our system became unstable after the last update, Media Encoder won't work now, it freezes.

    JUST FOR MAC USERS - Some 10.9.x links
    -next link says After Effects, but check YOUR permissions !!!
    -http://blogs.adobe.com/aftereffects/2014/06/permissions-mac-os-start-adobe-applications.ht ml
    -Mac 10.9.4 and OpenCL issue https://forums.adobe.com/thread/1514717
    Some 10.9.3 links that may still help
    -Mac 10.9.3 workaround https://forums.adobe.com/thread/1489922
    -more Mac 10.9.3 https://forums.adobe.com/thread/1491469
    -and https://forums.adobe.com/thread/1507936
    And some other Mac links
    http://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-mac.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

  • AME 2014 Export Error. Sequences not updating from Premiere.

    It seems that queuing sequences from Premiere Pro to AME via Ctrl+M is forever broken as that causes Premiere to hang and crash on the "Export Media" dialog box. This has been broken for several months. I have talked to developers with no resolution to this. Because of this, I now can only export projects by dragging sequences over to AME from Premiere. This has worked fine until a few days ago.
    What happens now is that AME gets part way through encoding a video and then hangs and fails encoding. I get the super helpful
    12/19/2014 03:25:14 PM : Encoding Failed
    Export Error
    Error compiling movie.
    Unknown error.
    I have created new sequences with the same media, removed 3rd party audio plugins, moved all the footage over to a different drive, tried to encoded to a different format like AVI, and I have tried setting the encode to save on several drives. It always fails at the same point. It seems hang and fail on clips that I created in AE, which are rendered using PhotoJPEG .MOV. I tried rendering the clip where AME fails using a different AVI container, but it ended up failing in the same spot.
    The strangest thing is that when I disable the clips in Premiere and dragged tried rendering, it hangs on the same clip as if it wasn't disabled! I have also deleted the clips from the timeline and they still show up in the preview window in AME and it hangs on them and then fails!
    Here are my system specs:
    Premiere Pro CC (up to date)
    Win 7 64bit (up to date)
    i7 970
    24GB Ram
    NVIDIA 470GTX (driver up to date)
    3 x 1.5TB internal
    4TB internal
    3TB internal
    12TB RAID 5 via USB 3.0
    USB 2.0 and 3.0 drives
    FireWire audio device (M-AUDIO FireWire1814)... although, I am not using it for playback. It is connected.
    Footage is from C100 H.264 .MTS, PhotoJPEG .MOV from AE, JPG Stills, simple titles made in Premiere Pro, color mattes, and .WAV audio clips
    All stock video effects and transitions.
    Thanks for your help.
    Mark Mapes
    Adobe Media Encoder (AME)

    I tried a re-install of PP and AME, moving all assets to another machine and encoding, enabling and disabling "Import sees natively" in AME, enabling and disabling Mercury in PP and AME, and I got the same result. AME fails encoding with a "error compiling movie" error. Same result when I tried to export from PP.
    The only thing that worked was re-rendering all the clips that I created in AE using a different codec (was MOV PhotoJPEG and I re-rendered to Lagarith AVI). This seemed to work. When it would fail in AME it would hang on a frame for several minutes before giving me the sheep sound. The original MOV PhotoJPEG clips from PP played fine in the sequences and in media players. No drama, no glitches.
    Not sure why AME wan't updating the sequences from PP. The fix for that was launching AME with Shift held down to clear preferences. Also I made sure I saved in PP before I dragged over to AME for encoding.
    Hopefully this will help someone else along their journey. Thanks for looking!

  • Error installing update in Premiere Pro CC 2014.2, error code U44M1I210

    Tried several times to update Premiere Pro CC 2014.2 with the same error code U44M1I210. Tired to contact customer but their site is down.

    Got the same Error. Previous I worked with a GTX 760, and was hoping to get it fixed with using a GTX 780 6GB. But just as you, didn't solve the Problem.
    Usually I got the Problem solved, with exiting Premiere, restarting it, reset my Workspace. Then the Problem of having the bugged Workspace was gone. And also the Problem of the missing Video Tracks.
    At the moment I started on a new Project. Pretty simple, with only a 21 second DV footage. And here I was switching tabs with my Browser, came back to the Project, and the Video Tracks were gone. I saved, closed Premiere, restated and the Video Tracks are still  missing.
    So I made a new Sequence, voilá the Video Tracks are there. Thus I need to copy and paste the Tracks onto the new Sequence.
    But that is not really a solution!
    I was on the Phone with Adobe, and on Chat, but they couldn't help me. They suggested to get a Tesla or Quadro Card, or at least a GPU that got confirmed as working on their page. I did that, but obviously, that is not the issue.

  • Red Giant Trapcode plugins no longer work after updating to Premiere Pro CC 2014.1 (v8.1)

    I'm not sure why but after updating Premiere Pro CC to 2014.1 none of my previously installed Trapcode plugins work. I tried uninstalling Trapcode and then re-installing the latest Trapcode update (12.1.6) but it didn't fix the problem. I'm also running Windows 8.1.
    I checked the plugin loading log file (\AppData\Roaming\Adobe\Premiere Pro\8.0\Plugin Loading.log) and noticed all the Trapcode plugins had the message "The plugin is marked as Ignore, so it will not be loaded."
    So to fix it, I had to manually modify the registry and change "Ignore"=dword:00000001 to "Ignore"=dword:00000000 for most instances of my Red Giant plugins. Everything works now.
    Here's all the ones I had to modify:
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\3DStroke.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\HairLines.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\LightFactoryLERender-64.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\LightFactorySpectactularRender-64.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\RadiumGlow.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\RadiumGlowEdge.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\RadiumGlowLite.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\RGCornerPin.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\RGReflection.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\RGSGrowBounds.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\RGShadow.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\Screen Text.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\Shine.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\Smooth Tiler.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\Starglow.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\Text Grid.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\Text Hacker.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\Text Matrix.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\Text Spiral.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\ToonIt Blacklight Edges.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\ToonIt Goth.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\ToonIt Heat Vision.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\ToonIt Outlines Only.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\ToonIt Roto Toon.aex]
    "Ignore"=dword:00000000
    [HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\TypeOn.aex]
    "Ignore"=dword:00000000
    -Pete

    First ... have you checked that these are all updated to work with the CC versions? I'd check with the makers of each plugin, the software has MANY differences.
    Next ... if say you removed all but one, do any of them work? It might be worthwhile to remove them from the folder, then add one by one until you find one that is crashing things. That would at least get you part way forward.
    And ... you might list which ones you have, in what versions. Folks around here might be able to help just seeing that.
    Neil

  • Updated to Premiere CC 2014 - Now getting Startup Error - Could not find any capable video play modules

    I have a late 2013 MacBook Pro Retina with NVIDIA GeForce GT 750M 2048 MB.
    Ever since the Premiere CC 2014 update, on launch, I get this error right after it shows "ExporterQuickTimeHost.bundle" loading (I tried removing this, but it still did it, so I don't think it has anything to do with the QuickTime plugin):
    Adobe Premiere Pro Startup  Error
    Adobe Premiere Pro could not find any capable video play modules. Please update your video display drivers and start again.
    I never got this in the CC version. I have the latest CUDA driver: version 6.0.46  &  GPU Driver: version 8.26.21 310.40.35f08
    The computer is unusable for about 4-5 mins after this happens until it all clears up. This whole process takes up 7-8 mins!
    This same thing also happens with Prelude CC 2014.
    If anyone knows what's going on I would be very grateful.
    Thanks, Maz

    I found a solution that worked for me. Seems to be a permissions problem. Here's the solution I found (found it here: CC 2014 startup issues : Adobe Premiere Pro):
    In the finder menu click and hold on the GO menu. Hold the option button and the User library will show up. Click the User Library.
    In that folder go to preferences and find the adobe folder.
    Right click on adobe folder and click get info.
    In the Sharing & Permissions section there should be three names.
    All should say Read & Write next to them.
    Unlock the lock, switch them all to read and write.
    Then click on the little gear directly under the names or to to the left of the lock and in the pulldown click on "apply to enclosed items.
    Then lock the lock again.
    Now go to your OS Hardrive and click on Users, your user name, Documents.
    Find the adobe folder there.
    Right click on adobe folder and click get info.
    In the Sharing & Permissions section there should be three names.
    All should say Read & Write next to them.
    Unlock the lock, switch them all to read and write.
    Then click on the little gear directly under the names or to to the left of the lock and in the pulldown click on "apply to enclosed items.
    The lock the lock again.
    Wait 1 minute. Then launch Premiere.
    This fixed it for me.

  • Updated to Premiere CC 2014 and AE CC 2014 and now have blue lines/blue imprints of windows and crashes after 5 minutes of use or on start up

    iMac - 27 ", late 2012
    Processor  3.4 GHz Intel Core i7
    Memory  32 GB 1600 MHz DDR3
    Graphics  NVIDIA GeForce GTX 680MX 2048 MB
    Software  OS X 10.9.4 (13E28)
    After I updated from CS6 to CC 2014, my screen started to display blue lines and/or a blue imprint of a previously closed window, and Premiere CC 2014 and AE CC 2014 began crashing after about five minutes of use. Also, an error message popped up telling me to update my CUDA driver. I took the iMac into Apple and after updating the CUDA driver in store with an Apple associate, the error message went away. They were concerned about the blue lines, and after 3 days of hardware testing, they determined that the screen was not failing, the hardware was in great shape and the lines and crashing must be a software related issue. I took the computer home, uninstalled and reinstalled AE using the appropriate installer, and rebooted. Then I uninstalled and reinstalled Premiere using the Premiere installer and rebooted again. During the second restart a blue imprint of the Google Chrome window I had had open before the reboot was imprinted over the welcome/password screen. I typed in my password, opened up the Premiere project I'd been working on and immediately, the always dramatic message "A serious issue as occurred..." popped up. I tried opening it again, saved a new recovery copy and started to work on the project. Five minute later it froze up and I had to force quit. This happened two more times, both roughly after five minutes of use....back to square one.
    Obviously, this is seriously hurting my workflow. Any advice you could give would be greatly appreciated!

    ... a blue imprint of the Google Chrome window I had had open before the reboot was imprinted over the welcome/password screen.
    The apple guys said this wasn't a hardware error? I don't know software errors to save imprints throughout a restart. If I were to live dangerously and assume anything it would be that you got a failing graphics processor.
    Ever tried cloning your boot drive and then doing a complete wipe and re-install of OS and CC?

Maybe you are looking for