Premiere Pro CC 2014 seems to  Corrupt projects created with earlier versions

I have opened  in PPro CC 2014  projects created in PPro CS6  or PPro CC. Every time  PPro crashed and got the message " PPro Debug Event - PPro encountered a major problem and has stopped working" After that the project seemed corrupted and could not be opened even in earlier versions.
I get the following message
Première Pro Debug Event (Title of the window)
Premiere Pro has encountered an error
[c:\caravan\releases 2014.09\shared\adobe\mediacore\mediafoundation\api\incK... (can't read the res...)
Then there is a "continue" button if I hit this button I get the following window
Following a serious error PPro must shut down. The program will try to record your current project.
Has anyone encountered this problem?
I don't dare open any old project. help!

Hi there!
I´ve updated to latest version and then opened my project and got this error.
Then I found in a forum that I should delete the ADOBE folder in \my documents
I´ve deleted and then I could open the file again.
But the .MP4 and some other video files doesn´t open.
I saw that the 'Effect Presets and Custom Items.prfpset' file on \my documents\adobe\premiere Pro\8.0\Profile-myprofilename was causing the error.
I also saw in other forum that I should rename Adobe folder to old.adobe from \userfolder\appdata\roaming and \userfolder\appdata\local but this hasn´t solved the problem.
I tried also to reinstall Quicktime and K-Lite Codec Pack but the problem persists.
Have you found any solution??
Regards
Lucas

Similar Messages

  • 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

  • Save project created with trial version in Captivate 5.5 with license

    I have a project created with Captivate6 trial version. Now I have a license for Adobe Captivate5.5. The content of my project with Captivate6 will expire when the trial period is over and will not be accessible. I cannot open the .cptx file with Captivate5.5. How can I save my work from the trial Captivate6 to the licensed Captivate5.5? This is the last day of my trail version. Please help as soon as possible.

    Hello and welcome to the forum,
    I'm so sorry, but there is no backwards compatility beteen 5.5 and 6. You cannot copy slides, objects from 6 to  5.5. You can try to export what is available in the Library, some objects you will hopefully be able to reuse in 5.5. But the project will have to be recreated from scratch.
    Lilybiri

  • Persistent Premiere Pro CC 2014 error message: "This project contains a sequence that could not be opened..."

    I've been working on a project and everything was working fine. I close the program and reopened it an hour later. Now, I keep getting this error message: "This project contains a sequence that could not be opened. No sequence preview preset file or codec could be associated with this sequence type."
    I attempted to use one of the Adobe suggested solutions... opening a new project, clicking on the "Help" Tab and deactivating, but the tab doesn't have that option. I'm also a little afraid to uninstall and re-install premiere pro, the other suggestion, because I'm worried about losing my files.
    I would be grateful if anyone could help me.
    Thank you very much.

    Features and Sequence Presets missing | Adobe Premiere Pro CS6
    FAQ: Why are some codecs and sequence presets missing from my installation of Premiere Pro?
    What to do when you get a preview preset codec error in Adobe Premiere Pro CS6 | Val Gameiro, Writer, Director, Filmmake…
    if you try the project repair from Val's blog you will need to unzip the .prproj file to get access to the xml file.

  • Premiere Pro CC v7.0 - MP3s corrupted during import with "Write XMP ID to Files on Import"

    Premiere Pro CC v7.0 - original MP3s corrupted during import with default "Write XMP ID to Files on Import" option
    I have just started using a Trial version of Premiere.
    I have a folder full of corrupted MP3 files after attempting to import them into Premiere.
    After searching these forums I found that some other people have had corruption issues during import of media and it was related to the Preferences->Media->"Write XMP ID to Files on Import" option.
    I attempted to import additional MP3s (this time making backups first) with and without the Write XMP ID option, and have found that this is where the issue is.
    While the MP3 files still fail to be imported, the files are not corrupted in the process when the Write XMP ID option is unchecked.
    Writing to files that are being imported seems to me like unexpected behaviour for any software.
    Adobe please advise!
    Is there any way to recover my original MP3 collection?

    What exactly is wrong with them?

  • Downloaded Premiere Pro CC trial crashes as soon project opens with no error message

    I just downloaded Premiere Pro CC hoping to give it a try but haven't yet been able to because it crashes right after opening every time. I've uninstalled and reinstalled several times to no avail.

    PProCC Crash on Startup http://forums.adobe.com/message/5539903 may help

  • Can't open projects with Imovie 5 that were created with earlier version

    I can't open my Imovie projects that I created when using Mac OS 9.2 now that I'm using Tiger and Imovie 5.
    I'm not sure what version of Imovie I created them with. Do I need to find an earlier version and open them in the classic environment, or is there some way of converting or importing them?
    iBook G4   Mac OS X (10.4.2)  

    Theoretically iMovie 5 can convert old projects, but projects created in Mac OS 9.2 can be quite difficult, for OS 9 is very different than OS X. More about that here:
    http://discussions.apple.com/click.jspa?searchID=-1&messageID=1677339
    Your best option is to use the version of iMovie that you used originally to edit the project. If the projects are really old, that may require starting up your Mac in Mac OS 9 (instead of running iMovie in the Classic environment, which is Mac OS 9 running inside Mac OS X.)
    Your best solution may be to boot up in Mac OS 9 and use your old version of iMovie to export the project back to the camera, then boot into Mac OS X and import the tape into iMovie 5.
    If you don't have a camera, export to a Full Quality DV movie, then import that movie into iMovie 5.
    The camera will (probably) deliver the clips to iMovie 5 as clips, while the export to a Full Quality DV movie will not.
    By the way, to see which version of iMovie last edited the project, drop the project file on the TextEdit icon in the Dock. The version is shown at the top of the file.
    iMovie 2.1.2 was the first version to run in OS X, I believe. The last version to run in OS 9 had the same version number, unfortunately.
    If your Mac doesn't let you start up in Mac OS 9, then say more about exactly what happens when you try to convert the project. Do you get error messages? What are they?
    Karl

  • Where is a link to the Premiere Pro CC 2014.1 (8.1) update? - Can I get help with the ticktime.cpp-290 error?

    Ola to precisando do premiere versao 8.1 caravan consegue o link?
    Message was edited by: Kevin Monahan
    Reason: needed better title

    Hi Kevin,
    I posted about the same problem (TickTime.cpp-290 error) in another thread, but since you're asking here specific questions to resolve it, I'm answering it here.
    Re: Debug Event: [...\ ...\src\TickTime.cpp-290]
    What were you doing when this error started to occur?
              Nothing special I remember. The only thing I do recall, is:
              I was working with Premiere Pro (where the main project is), After Effects but rendering some PNG sequence, and Adobe Media Encoder. I sent from AE to AME a project to render. Configured 2 outputs (PNG & MP4). The same way I sent from PP a project to render and one error occured. Unfortunately I didn't write down the error, but it was like a path C://AME_64/something. But the AME queue updated and everything seemed OK. I close AME to be sure that the error wouldn't be the source of future error during rendering, and relaunched it. And at that time I couldn't open it. I got the error "Adobe Media Encoder has encountered an unexpected error and cannot continue". The only way I found to resolve this is to remove the directory /Users/%USERNAME%/My Documents/Adobe/Adobe Media Encoder/8.0/". The problem seems to appear when I save the queue. And since that time, Premiere do the TickTime.cpp-290 error.
              Another thing I noticed, don't know if it was there before, is, the AEP file in AME queue setttings displayed framerate as "25 / 29.97 / 30 / ...", a 2 digits number for the framerate. But suddenly (I thought first it was because of the Premiere Pro file being added to the queue, but no because it appended after without it), it was displayed as "25 000 / 29 970 / 30 000", a 5 digit number.
              After that, the TickTime.cpp-290 appeared. Sometimes when opening project, sometimes and resetting or changing the workspace (because it was messed up), sometimes when closing.
    Do you have iCloud installed?
              No.
    Is this a Premiere Pro CC 2014.0 or Premiere Pro CC 2014.1 project that was updated to Premiere Pro CC 2014.2? If so:
              It started long time ago a draft in CS6, but since I reopen the project, I saved new versions in Premiere Pro CC 2014.2 (not sure if I have other version like 2014.1 or 2014.0). Is there a way to know which 2014 version are my files? If I look into the XML I only saw Version="28"
    Do you have a copy that can be opened in an earlier version?
                  An old draft version in CS6. But that version has footage in different framerate and not all be interpreted at the timeline framerate.
    Do you get the same error in that earlier version?
                   No error here, the file opens properly.
                  Additional info: I tried to open the 2014.2 file on another computer (where PP 2014.2 is installed) and same problem (this computer is on Win7 64-bit)
    Did you use any unusual footage types in your project?
         I used MOV (Animation), MP4 (H264), and PNG sequence. The framerates of the footages are 24,25,30 and 60fps (but everything has been interpreted in 30fps)
    If you remove them, do you still get an error?
                  When I had the error, but not when I open the project file, I resave the file removing anything not interpreted in 30fps (because at that time I still had footage interpreted in their original framerate). I was able to work for some time, but now I can't open it anymore despite that.
    Was the fps interpretation changed in any of the clips?
         Since the error appeared, and because I saw in another thread that it could be related to footage of different framerate, my timeline is now in 30fps and all the footage have been interpreted in 30fps. Footage are MP4, MOV, PNG sequence in 24, 25, 30 & 60fps.
    If so, restore them to their original fps and see if you still get the error.
                  Unfortunately, since I can't open the project anymore, I can't test that.
    Did you use Warp Stabilizer?
              No.
    Do you have any browser plug-ins?
              What do you call browser plug-in in Premiere?
    Are there any third party plug-ins used?
              I have Magic Bullet Looks 2, and I'm using it on this project.
    If so, remove the effect from those clips and see if it improves the situation.
                  Unfortunately, since I can't open the project anymore, I can't test that.
    Some additional infos on my computer.
    I use Windows 8.1 (64-bit),  all Adobe softwares installed have the last update (for video apps, it's 2014.2)
    The language settings are configured in French, but Windows and CC apps are in English.
    If needed the 2014.2 project file is here:
    https://dl.dropboxusercontent.com/u/68413846/showreel19_30fps.prproj
    Thanks in advance to help us to resolve this weird bug.
    Christophe.

  • I'm having problem with exporting video from premiere pro cc 2014

    I'm using Adobe Premiere Pro CC 2014 and I'm having problem with exporting video.
    When I click Export and media, the window for exporting appears and it starts exporting video.
    But after a few minutes, it looks like it has completed exporting video and says there's a bug in exporting.
    It literally says it has a problem with compiling, but I don't know what the real problem is.
    I tried many things like restarting computer and Premire Pro but it's no use.
    But it works when I use Adobe Media Encoder CC 2014 for exporting video.
    If anyone knows any possibilities about why this problem happens, please let me know.

    I'm having a similar issue.  When I go to export my project, I add it to the render queue, set it up with the h.264 settings that I've used with countless past versions of the program, and then hit render.  Randomly, at some point in the process, the render just stops and the ETA just keeps climbing.  I actually had to save an XMF file of the CC 2014 project and bring it into the previous CC version of Premiere just to finish it.  Even a clean re-install of CC 2014 doesn't work.

  • Alle Tastenkürzel verloren in Premiere Pro CC 2014

    Ich habe ein eigenartiges Problem - bei Premiere Pro CC 2014 auf dem Mac (OS X Yosemite, aktuelle Version) funktionieren keine Tastenkürzel mehr - einschließlich Abspielen (Leertaste), Löschen (Rücktaste) oder Rückgängig (Command + Z). Einfach alles weg.
    Tastatur ist angeschlossen und funktioniert einwandfrei. Auch in z.B. After Effects ist alles in Ordnung.
    Wenn ich in die Tastenkürzel-Einstellungen gehe, sehe ich, dass keiner der Funktionen in der Liste ein Kürzel zugeordnet ist. Wenn ich es manuelle einstelle, funktioniert es wieder. Ich kann allerdings nicht sämtliche Funktionen manuell wiederherstellen...
    Wenn ich die Keyboard-Layout-Presets aus der Dropdown-Liste wähle (z.B. Adobe Premiere Pro CS6), bleibt die Liste der Befehle leider leer, es ändert sich nichts.
    Weiß jemand Rat?

    Lösche mal Deine Voreinstellungen:
    halte Shift+Alt beim starten von Premiere.
    Alternativ:
    Auf Mac findest Du die Voreinstellungen auch unter:
    UserFolder>Documents>Adobe>Premiere-Version>Versionsnummer.
    Falls der ordner versteckt ist:
    Access hidden user library files | Mac OS 10.7 and later

  • Upgrading Premiere Pro CC to Premiere Pro CC 2014 in the middle of a project

    Hi guys!
    I was working through a project with Premiere pro CC until I checked my creative cloud app and realised there was an update for the software, Premiere Pro CC 2014. I thought great, I'll download it straight away.
    It's a great bit of software and it does seem to be faster, however, whenever I play a sequence everything is fine and working as expected except the sequence monitor, which constantly freezes while trying to edit. Quitting the application and re-opening it is my only real solution so far as it's fine once I do this for a good couple of minutes until the sequence monitor freezes again
    I was wondering whether I could get any help with this problem? I am using Yosemite as my OS and I have read up on many issues that have come about with adobe applications since the launch of Apple's new OS update. Someone recommended going back to the older version of Premiere Pro CC, but I've done a serious amount of work on the newer version now so going back is out of the question really.
    I've spoken to quite a few people about the issue, like you do, and they are also a bit unclear of a solution. Some say its the graphics card. Some say I need to buy a new computer (I have an imac mid 2010 intel core i3). And most say to downgrade to mavericks again as adobe and Apple are still working on a solution for the near future.
    I was thinking of re-installing premiere pro cc 2014 altogether but I am a bit worried that work may go missing if I did?
    Any suggestions would be greatly appreciated!
    Tom

    There is this offer of a trial version FC Pro X with 30 day runtime:
    http://www.apple.com/final-cut-pro/trial/
    Too bad you didn't have a complete backup that could run the previous OS X
    and then you could resume using an earlier Final Cut Pro (10) or (7) since a
    clone would have been a means toward that position.
    http://www.apple.com/support/finalcutpro/
    http://www.apple.com/support/pro-apps/
    This appears to be another good reason to check out all the reasons why one
    would want or need to upgrade a working OS X version, since these kinds of
    events are known to happen as a direct result.
    Sorry to not have an answer to this, other than try & use the Trial version...
    Or see if someone at Apple sales/support can field your issue w/ an answer.
    Good luck & happy computing!

  • Premiere Pro CC 2014.2 Crashing while loading project...

    When trying to open Premiere project the program opens and looks like it will load and then crashes.
    If I create a new project Premiere opens and I can import footage but as soon as I try to play footage in the preview window or drop it in the timeline the program crashes as well.
    I am working on a Windows 7, 64-bit, i7, 8GB ram, 1TB multiple partitioned hard drive. My Graphics card is, Intel(R) HD Graphics 4600 - Driver Version: 9.18.10.3204
    My Error Log is:
    Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
    Faulting module name: MXF_SDK_4.4.33_vs10.dll, version: 4.4.33.0, time stamp: 0x534d772c
    Exception code: 0xc0000005
    Fault offset: 0x00000000000bdc55
    Faulting process id: 0x378c
    Faulting application start time: 0x01d02c3625e455c1
    Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
    Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\MXF_SDK_4.4.33_vs10.dll
    Report Id: b1b66e81-9829-11e4-95ce-c4346b64bc4f
    I can't figure out what the faulting module is.
    I just installed CC 2014.2 3 days ago. It all worked fine until yesterday when Premiere started crashing. I restarted the system - same issue. I uninstalled and reinstalled Premiere2014.2 - same issue. Premiere seems to be the only faulting application. Everything else (Ps, Ae, Lr, Id, Au, Ai) appears to still be working.
    My version of CS6 (Purchased before getting a creative cloud membership not downloaded through CC) is also still working properly.
    Thanks for the help.

    Update: I updated my Graphics Card Driver to a more recent version. Restarted computer and reopened Premiere and similar crash happened. I went through to get some more crashes and had different crash reports. The faulty module is not always the same.
    Problem Event Name:                        APPCRASH
      Application Name:                             Adobe Premiere Pro.exe
      Application Version:                           8.2.0.65
      Application Timestamp:                     5486db4a
      Fault Module Name:                          devenum.dll
      Fault Module Version:                        6.6.7600.16385
      Fault Module Timestamp:                  4a5bded7
      Exception Code:                                  c0000005
      Exception Offset:                                00000000000016a0
      OS Version:                                          6.1.7601.2.1.0.256.48
      Locale ID:                                             1033
      Additional Information 1:                  ec5a
      Additional Information 2:                  ec5adb2545b190cc19da7bdfa78d5bf1
      Additional Information 3:                  6e59
      Additional Information 4:  6e59168cf9de1a4a9616903b4a4ba1e1
    Problem Event Name:                          BEX64
      Application Name:                             Adobe Premiere Pro.exe
      Application Version:                           8.2.0.65
      Application Timestamp:                     5486db4a
      Fault Module Name:                          OpenCL.dll_unloaded
      Fault Module Version:                        0.0.0.0
      Fault Module Timestamp:                  50eb1a5b
      Exception Offset:                                000007fee84516a0
      Exception Code:                                  c0000005
      Exception Data:                                   0000000000000008
      OS Version:                                          6.1.7601.2.1.0.256.48
      Locale ID:                                             1033
      Additional Information 1:                  a527
      Additional Information 2:                  a527a6af76c2b04cfd1fc255c66e5364
      Additional Information 3:                  21c7
      Additional Information 4:                  21c71ffc516aa3806e495b8080bd51fe
    Both of those are different from the original posted report.
    I did have some success following these instructions.
    Premiere Pro CC 2014.1 has stopped working - Win 7 64 bit
    It appears I do not have a graphics card that is compatible with the mercury engine. I have had three successful tests and one crash since I selected Renderer: "Software only"
    I plan to upgrade to a Nvidia card or the supported Intel Iris Card.
    This seams to be the issue but I am hesitant to use CC 2014.2 for the time being because I don't know if it will crash randomly and CS6 is working fine. The second error code with "Fault Module Name: OpenCL.dll_unloaded" seems to be directly related to the graphics card and rendering processes. I will update as I learn more.
    Please comment with any suggestions or resolutions you have had.

  • Premiere Pro CC 2014 (8.0.1.21) crashes when opening or creating a project

    I just downloaded the trial for Premiere Pro CC (2014), and the program keeps crashing every time I open or create a new project. I can idle at the "Startup Screen" but as soon as I open a project the program closes without warning. I've re-installed all Adobe products I have, re-installed the Microsoft Visual C++ Redistributable 2012 and 2013 to get new MSVCR110.dll files (which seems to be the file causing the crash) but nothing is helping. I've also looked in every thread I've found on this forum and a lot of people seem to be having the same problem, but no one had got any answers for how to solve the problem.
    Anyone have a clue on what to do? According to others formatting the hard drives don't seem to solve the problem either.
    Here's the crash log:
    Problem signature:
      Problem Event Name: APPCRASH
      Application Name: Adobe Premiere Pro.exe
      Application Version: 8.0.1.21
      Application Timestamp: 53c7b17f
      Fault Module Name: MSVCR110.dll
      Fault Module Version: 11.0.51106.1
      Fault Module Timestamp: 5098826e
      Exception Code: 40000015
      Exception Offset: 00000000000740da
      OS Version: 6.1.7601.2.1.0.256.48
      Locale ID: 1053
      Additional Information 1: dac8
      Additional Information 2: dac844fabf0ae09d193ac750f70263ad
      Additional Information 3: 6e8b
      Additional Information 4: 6e8b89b059d1639bd5ba176e9f652c56
    I'm running a:
    Intel i7-3770K, not overclocked
    ATI Radeon 7850, not overclocked
    16gb RAM
    64-bit Windows 7 Professional with Service Pack 1

    Me too with this one have it randomly when just opening the same project and begining to edit
    had it happen about 4 times now.
    Latest update
    Microsoft Visual C++ Runtime Library
    Program C:\Program Fi...
    R6025
    - pure virtual function call
    [ok]
    Adobe Premiere Pro CC 2014.1 has stopped working
    roblem signature:
      Problem Event Name: APPCRASH
      Application Name: Adobe Premiere Pro.exe
      Application Version: 8.1.0.81
      Application Timestamp: 5426694c
      Fault Module Name: MSVCR110.dll
      Fault Module Version: 11.0.51106.1
      Fault Module Timestamp: 5098826e
      Exception Code: 40000015
      Exception Offset: 00000000000740da
      OS Version: 6.1.7601.2.1.0.256.1
      Locale ID: 2057
      Additional Information 1: a22a
      Additional Information 2: a22a26525c716a6a7fdf0a84944bf385
      Additional Information 3: 9245
      Additional Information 4: 9245cf38809b383bd6a86e3f052c9114
    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt

  • Premiere Pro CC 2014 keeps freezing when loading projects from Premiere Pro CC

    Hi everyone,
    I'm reporting this issue in case someone else would have the same problem.
    I just downloaded the 2014 version of Premiere Pro CC, and when I'm loading a project from Premiere Pro CC into CC2014 I have the software freezing and being unable to even play the loaded sequences. It seems that dynamic link is having trouble linking the CC and the CC2014 version of Premiere Pro.
    Until now the only solution I found was to kill the process of the software and start it again, after 8 times I got my sequence loaded alright, then sometimes it is freezing again, killing process, starting software again, and so on. Does anyone has the same problem ?
    I'm running a Windows 7 Ultimate PC with 12Go RAM dedicated only to Premiere Pro.
    Cheers,
    Vincent

    Hi Vincent,
    I feel your pain, you are not alone. Here are my machine specs and my very frustrating situation, if anyone has any idea as to how I should move forward, I would really appreciate the input/advice...
    iMac - 27" Late 2013
    Processor  3.4 GHz Intel Core i5
    Memory  12 GB 1067 MHz DDR3
    Graphics  NVIDIA GeForce GTX 780M 4096 MB
    Software  OS X 10.9.4 (13E28)
    I'm having similar issues that began when I installed Premiere Pro CC 2014, and actually got worse with the latest update/release. The majority of my projects worked fine at first, but the update last week ended that quickly. I did what I know I never should do and updated Adobe CC while completing a project on a deadline. I thought some of the fixes would help me complete the project sooner. Needless to say, the deadline has passed, my client is pissed enough to not pay me or hire me again and I'm stuck with an almost-there version that I can't export correctly because of this software. This is my problem, not Adobe's, but I didn't expect such a detrimental update to halt my operation.
    After doing some research, I found that some plugins could be the cause of some specific editing issues, mainly due to incorrect or inaccessible folders - who knows if its Dynamic Link, CC apps or 2014 apps. I concluded that my issue at the time was a plugin permissions issue on the Adobe "Preference" Folder, so I reset the permissions on the folder so that CC and 2014 apps would be able to access its contents without any problems. This was the wrong decision. For some reason, resetting this folders permissions also effected the main HDD, it's Kernel Text files and their respective permission. I could not boot my machine, just got the Apple and spinning wheel until I had to power down. I ended up on the phone with 3 different AppleCare reps who helped me at least be able to turn the machine back on and access my desktop/files, apps, etc. Outside of this, no one could offer anything other than "Uninstall the problematic application, reboot, reinstall, etc..." or "Backup your files and reimage the HDD." When I mentioned the recent CUDA driver update for my graphics card (NVIDIA GeForce GTX 780M 4096 MB now running CUDA Driver Version: 6.0.51), it was like they had never heard of graphics cards being used in their machines.
    Resetting permissions on Adobe Preference Folder...
    This is what I read would get the CC and 2014 apps communicating correctly so that they could utilize my plugins. There is a problem, I believe, in that their are TOO MANY locations where Adobe folders/components live. There are 3 "Preferences" folders that I found, and I don't know which effects what process, but the folder I changed permissions on clearly effects the operation of all of the CC & 2014 apps I had installed, as well as my HDD. Kernel Extensions and the entire system.
    Based on my perceived effects of the Preference folder, I needed to uninstall everything, run the Adobe CC Cleaner Tool, download/install just the 2014 releases and see if that resolved the issue. I'm not downloading CC apps, the 2014 releases should run fine on their own. I've yet to confirm this with Adobe, as what I've read has simply said to install the new release next to the CC apps, rather than on top of, as traditional update releases work. Anyway, one by one, I reinstalled the 14 apps that I use on a regular basis on a "clean" machine with no trace of previous Adobe apps.
    After reinstalling (without any plugins), I was at least able to open Premiere Pro from the Application folder and work for a few minutes before both Program and Source monitors froze and had to force quit the app. If I try to open the Project File by double clicking it in the Finder, SpeedGrade opens up instead of Premiere Pro - never seen that before. I also had to force quit to end that process and reopen in Premiere instead of SpeedGrade.
    So back to Premiere, if I do have success in opening a project in the right application, Premiere freezes - if not immediately, eventually it will just stop responding. The video clips, sequence segments and UI freeze, but the audio will keep playing until I force quit. When I force quit, Premiere Pro doesn't close entirely. The UI closes, but the process still runs. I've even force quit from Finder, force quit again from the Dock, Shut Down the machine, restarted and Premiere Pro will still be open, but "Not Responding", so I force quit again and open the project. Just now, I opened PP, made minor edits to a sequence, sent it to Media Encoder, exported, but the video I tested exported without audio. I force quite PP twice just before that and it is still running now, but again, it is "not responding".
    Ultimately, none of this works, nor have my attempts at resolving these many issues. One thing I know is that there is something VERY WRONG with either the latest release/update to 2014 apps, the Preference folder or the permissions that were changed.
    As I mentioned previously, and what I think is a major oversight by someone at Adobe, is that for some reason the permission changes to ONE Adobe folder also effected my entire system and Macintosh HD. Some Kernel Extension files went missing, which is never good and should not happen when resetting folder permissions, so I believe my issues are far greater than the faulty Adobe CC 2014 applications, and is the cause of many of my problems right now. If I can't get things sorted soon, I'm going to reimage my HDD and start from scratch. As much as I would like to avoid this, I really have no choice if I want to get back to work and not lose clients over inexplicable technology issues.
    If I find a solution, I will repost, but I think Adobe has to make some serious fixes on this release before anything is resolved entirely. I pay them monthly and rely on their software and platform to work without issue, which is foolish - I know, but I've used CC since it was introduced and it has work well enough until now.
    Is there anyone at Adobe that can offer some advice??

  • I am trying to open a previous completed project made on premiere pro CC 2014. i am getting a message that says the project was made on a newer version and cannot be opened on my new computer. However i made the older project on the same premiere pro CC 2

    I am trying to open a preciously completed project mad eon premiere pro CC 2014. I purchased a new computer and downloaded the same premiere pro cc 2014. However when i try to open my old project it says the project was made on a newer version and cannot open.
    that makes no sense...i downloaded the same version of premiere pro CC...help please!

    Hi,
    Seems that you don't have the most recent version installed right now. After launching Premiere Pro go to Help > Updates and check if any updates are available.
    Thanks,
    Rameez

Maybe you are looking for