Premiere Pro 2014.2 jumbling open Sequence tabs

It appears I'm not the only one experiencing frequent crashes. As incredibly soul crushingly annoying as they are, their disruptive impact is multiplied by my open sequence tabs being... randomized... when I re-open the project. A normal SAVE and OPEN is NOT SAVING my sequence tabs accurately.
So if I've got 20 of my most important sequence tabs open. And the program crashes (or even if I just save and close it properly) when I open it up again, I've got to close the wrong sequence tabs and open the correct sequence tabs to get back to the workspace I had before the crash.
...the frequent crashes, I mean.
My editing progress has ground to a crawl.
If Adobe would like a proper bug report on this, could someone please direct me to bug reporting? The page was down before, and I don't know if it is up, or where to find it.

I too have the same problem. It is very annoying considering I manage dozens of projects daily and it takes a damn good memory to remember wich sequence I was working on cause some of my projects contain many sequences with many versions of an edit.
I work on a PC station
HP Z820 with dual quad cpu Xeon processors
64g RAM
Quadro 4000
SSD Raid system drives
A hint to what might be happening is that every time I close the application, I get a crash window that tell me that Premiere Pro as stopped working. So basically it is not finalizing the shut down and this could very well be the problem.

Similar Messages

  • "Adobe Premiere Pro 2014.1 has stopped working" Open Project Error

    Hey, everyone.
    I recently tried to re-open a project file that I created earlier today. As soon as it loads, the familiar "Adobe Premiere Pro 2014.1 has stopped working" window comes up.
    I created a new project file and it seemed to work fine. When I first started this project, I was having trouble using a ".m2ts" AVCHD movie file (PPro would crash in a similar manner), so I used Media Encoder to change it to a ".mov" Quicktime file. Seemed to work fine after I did that. This new issue only arose once I tried to re-open the project file after shutting down the computer.
    Got any suggestions?
    -Ross

    Correction - I converted the ".m2ts" file to an ".mp4" file, not an ".mov" file.

  • File menu can't open Premiere Pro 2014

    I have a Premiere Pro 2014 on a Windows 8.1 Pro, both are all up to date.
    When I try to access the file menu, the program crashes and you have to do a power cycle to get it up and running again.
    If force the program to be run in Windows 7 mode it will work without crashing when opening the file menu, but it will take 4 times as long to open.
    However if you run the program as administrator it will work just fine in Windows 8 mode, but not as the local user and not as a logged in administrator, you have to "Run As" administrator to make it work.
    Does anyone have any idear what the issue could be.

    Hi appman,
    Premiere pro runs fine on an admin account and not as a standard user. It requires proper permissions that are available being an admin on the computer and hence on a standard user you can run into these kind of problems,
    Thank You
    Arjun

  • Premiere Pro 2014.2 crashes as soon as I try to do anything. Any ideas?

    Hi there,
    My employer just leased a new system for me. Up until last week I had PP 2014 installed and everything ran without issues. Since the new system and installing the latest version of Premiere Pro 2014.2 I can no longer work on anything.
    The software will stay open if I start it up and don't do anything. I can even open a project and it will still work. The problem occurs when I try to do something i.e. import a file, open a sequence, rename a title, etc.
    Can someone help? If so, please let me know if you need more info from me (see system info below). Thanks.
    Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)
    Language: English (Regional Setting: English)
    System Manufacturer: Hewlett-Packard
    System Model: HP Z230 Tower Workstation
    BIOS: Default System BIOS
    Processor: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (8 CPUs), ~3.6GHz
    Memory: 16384MB RAM
    Available OS Memory: 16070MB RAM
    Card name: Intel(R) HD Graphics 4600
    Manufacturer: Intel Corporation
    Chip type: Intel(R) HD Graphics Family
    DAC type: Internal
    Display Memory: 1696 MB
    Dedicated Memory: 64 MB
    Shared Memory: 1632 MB
    Current Mode: 1920 x 1080 (32 bit) (60Hz)

    I just something and it seems to be working so far. I found this on a few sites. Will this affect what I can do with the latest version of Premiere? Should I leave it this way? Thanks in advance.
    In the Video Rendering And Playback section, select the appropriate renderer: Mercury Playback Engine GPU Acceleration or Mercury Playback Engine Software Only. 

  • After I purchased the creative cloud, I receive an error message when trying to use premier pro cc 2014.  It states "Adobe Premiere Pro 2014.2 has stopped working.  A problem has caused it to stop working.  Windows will close the program and notify you of

    After I purchased the creative cloud, I receive an error message when trying to use premier pro cc 2014.  It states "Adobe Premiere Pro 2014.2 has stopped working.  A problem has caused it to stop working.  Windows will close the program and notify you of a solution."  When I used the trial I never received this message.  Now after purchasing it I receive this error each time I open PP and am unable to use. it.  Any ideas or support to fix this issue?

    What does the detailed crash report say?
    And have you updated your video card drivers from the GPU maker's website? (most crashes on launch are due to bugs in out of date video card drivers)

  • My Program and Source Monitor Stopped Working: Premiere Pro 2014

    Heres how it all started.
    I got an error which said I didn't have the correct video modules, then came the ugly face of BSOD. I restarted, tried again, same result. I did a system restore with Windows, reinstalled Windows 8.1, reinstalled all of my plugins and Adobe CC programs, and when I opened my project was completely scrambled. Uninstalled all Adobe software, ran CC Cleaner, reinstalled. This got the audio in my videos to work but now there's only a white screen on my my Source and Program monitor when I try to play my timeline. I did another system restore on Windows, went to my laptop manufacturers website and updated my bios, graphics driver, and processor. Also reinstalled windows updates, and my Adobe software, I've tried CC Cleaner before each install, tried going back to the previous version of Premiere and still nothing in my source or Program monitors.
    MSI GE70
    Intel Core i7 4700MQ Processor
    NVidia GeForce GTX 765M / 2GB GDDE5
    12 GB Memory
    using .MTS footage from a Canon C100
    Premiere Pro 2014.2
    Things I've tried from other threads:
    -I read that there might be a problem with the .MTS files so I've also tried starting a new project with .MOV files and h.264 and still nothing.
    -I tried going into the project settings and choose "render with software", still nothing.
    -I tried emptying media cache files under C://users/my user/app data/roaming/Adobe/common.....you guessed it, NOTHING.
    -I tried using my daughters "Frozen" magic wand we bought her for Christmas to fix the problem with icy magic like Elsa did in the movie.......surprisingly, still nothing.
    Any other ideas out there?

    Hi,
    Do you have Dual Graphics Adapters? You can check that under Device Manager > Display Adapters.
    If yes, Disable Intel Graphics and see if it helps.
    Have you tried to Trash the Preferences?
    Rename the 8.0 folder to trash the preferences: <drive>\Users\<username>\AppData\Roaming\Adobe\Adobe Premiere Pro\
    Thanks,
    Rameez

  • Premiere Pro CC crashes in opening a project file

    I am using Premiere Pro CC since 1.5 years now. No big problems so far but now suddenly a strange one in opening a project file.
    Several other project files open up as usual, but the last one I've been working on, suddenly crashes in the middle of loading the media files.  An error message like this appears:
    "Premiere Pro has encountered an error. [c:\ppro772\releases\2013.10\shared\adobe\mediacore\mediafoundation\api\inc\ " (and the rest of the path I'm not able to see, it's cut.)
    I have installed the latest version of the graphics driver today. I have installed Premiere Pro 2014 some time ago but didn't really use it yet. I already tried to open the project in 2014 with no success.
    Now I just found out that I can open the project from the one-before-the-last autosave file! Thereafter I saved the project with a different name, but trying to re-open it resulted again in the same error!!
    Any idea what the problem could be and what might help?

    BUt that's a different error.
    I am getting this one aswell.
    [c:\ppro772\releases\2013.10\shared\adobe\mediacore\mediafoundation\api\inc
    Please fix it.
    I really want my Premiere Pro to work :\

  • Premiere pro 2014 cross fades don't get saved or load as saved audio drops???

    For no apparent reason premiere pro 2014 will not save cross fades...  it saves them but wont load them
    Audio is dropping out ....
    I was given a project to make some changes to and every time I open it I need to recreate the cross fades and then export it and then check it and then recreate the cross fades that didn't export and then hope for the best!!
    this is so unstable and there seems to be no apparent reason
    any help would be magnificent

    Hi Vince,
    vince_email wrote:
    ...The only things that changed were an update to Yosemite, I started using Time Machine to make regular backups...
    Please check this blog post. Updating from Time Machine can cause this issue: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later).
    Thanks,
    Kevin

  • What is the best PC laptop to use with Premiere Pro 2014?

    I'm excited that I get to buy a NEW LAPTOP!!!
    I'm editing a documentary with tons of footage.  I'll use external SSD drive for files.
    What is the best PC laptop to get for editing movies on Premiere Pro 2014?
    I can spend up to $1500
    Thanks SO MUCH for your help!!!!

    premiere will run fine with the 7200rpm hdd. while editing, if your hdd/ssd isn't fast enough it will stutter and skip as it cant feed the data fast enough to premiere. thats with high bitrate footage, if you are using low bitrate footage the 7200rpm might work ok to hold your footage too. odds are that external samsung ssd will be fast enough to hold the media, project cache and any preview files. you shouldn't need another external hdd for export/render.
    the ssd for internal will let windows boot faster and let programs open and close faster. once windows is loaded and programs are opened, they load into ram. there is little to be gained after that for ssd/hdd speeds while using most programs.

  • "The project was saved in a newer version of premiere pro and cannot be opened in this version." - Except it wasn't!

    Last night I saved a project I've been working on for a couple of days. It's been fine all along. Today, when I went to open it, it's no longer listed in the recently opened files on startup and i get this message:
    "The project was saved in a newer version of premiere pro and cannot be opened in this version."
    Except it wasn't! I use Premiere CC and it's been fine all along. I can no longer open it at all...
    Any thoughts? Very frustrating!

    One more item.   In using PP CC2014 for the first time with this project, I have run into multiple issues making this project very frustrating.  When adding a sequence to the master sequence, I have to render the audio each time in order to see all of the audio waves. You have to keep doing this over and over, even though you've already rendered a sequence already.
    I am getting error messages when rendering the project saying there are issues compiling the movie.  Getting same type error message if I try to export.  I narrowed it down to two sequences keeping the program from rendering without the error messages.  They each had a tiff file.  I deleted them and they rendered.  Not sure what this issue was with these particular files since I have other tiff files in the project.  Once the rendering of all sequences was done, all the individual sequences were closed and the master was the only one open.  I didn't close them.  So now to edit any of the sequences I have to go back and open them.
    The only thing this project has in it are titles created in PP, a few graphics, mostly tiff tiles and some jpeg and the dissolve effect.  That's it.  Seems like they should have done more with this version before putting it out there.  Maybe that's why there are two separate applications for PP?  Who knows.  I will be uninstalling PP CC2014 when this project is complete.

  • 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.

  • Premiere Pro 2014 MultiCam forgets cut points when rendering (Adobe please help!!)

    I have started using multi-cam and notice that almost always when using multi-cam the rendered results are incorrect - with many camera selections forgotten or flipped to exact opposite!
    Very frustrating - especially since you discover after render!!
    Many times when I select Camera A at some point and then later go to beginning of sequence - many of the selections have been reversed with reversal again at clip transitions - resulting in exact opposite of what I selected or random changes. Locking the tracks does not prevent this. It seems to be overriding my choices based on some program logic!!
    This is with latest Premiere Pro 2014.1 {8.1 build)
    Useless feature if you cannot get it to render your selections but rather random selection
    Wish there was a manual! And not just incomplete video tutorials that are teaser for some associate's paid training (of unknown value).
    Or at least quick forum / support response from Adobe representatives so I can be productive with the tooling.
    Another week of no answers and I will have to recreate in FCP X where multi cam seems to work fine.
    Not the best for brand loyalty, eh?
    Please help

    I'm thinking it might be operator error on this one.  Here's a process that works every time.
    1. Create a sequence matching the specs of your footage.
    2. Add your clips.
    3. Sync manually.
    4. Create a second sequence matching the first.
    5. Nest the first sequence into the second.
    6. Right click on that nested sequence and choose Multi-Camera>Enable
    7. Turn on the Multi-camera view in the Program Monitor.
    8. Play the sequence in real time, switch angles using keyboard shortcuts.  If you make a mistake, leave it for later.
    9. When you're done with the first pass in real time, go back to the normal view in the Program Monitor.
    10. Move through the sequence a second time, cut by cut, tweaking as necessary with the Rolling Edit tool (shortcut N).
    On a side note, 2014.2 is actually the current version.  You should update.

  • Premiere Pro 2014 Cross Fades don't save and or load and saved audio drops???

    For no apparent reason premiere pro 2014 will not save cross fades...  it saves them but wont load them
    Audio is dropping out ....
    I was given a project to make some changes to and every time I open it I need to recreate the cross fades and then export it and then check it and then recreate the cross fades that didn't export and then hope for the best!!
    this is so unstable and there seems to be no apparent reason
    any help would be magnificent

    Hi Vince,
    vince_email wrote:
    ...The only things that changed were an update to Yosemite, I started using Time Machine to make regular backups...
    Please check this blog post. Updating from Time Machine can cause this issue: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later).
    Thanks,
    Kevin

  • The project was saved in a newer version of Premiere Pro and cannot be opened in this version

    I edited a project on CC on one computer and saved it on my external. My friend took the same project to edit it on her computer under her own name and licence. Both of us recently upgraded to CC. But the same project that worked a few hours back on Premiere Pro CC, does not work now also on Premiere Pro CC and I received a message saying: The project was saved in a newer version of premiere pro and cannot be opened in this version." Can you please help us.?
    Message was edited by: Kevin Monahan
    Reason: Your title was too long.

    Hi alexxxkid,
    You should be able to import the xml into an earlier version.
    Backward compatibility has never been there with Premiere and it is always recommended not to update in the middle of a project.
    As far as the crash is concerned, please tell me more about it so that i can help you to the best of my knowledge.
    Thanks,
    Rameez

  • Failure to import fcp7 project's xml into Premiere Pro 2014.  Details below.  Why is it crashing? Any thoughts?

    Here are the details of my problem:
    Premiere Pro 2014 (up to date)
    Mac book Pro OSX Yosemite 10.10.1 with 2.8 GHz Intel Core i7 processor
    Source footage includes a variation of codecs as follows: H.264 in a .mov container, 1920 x 1080 Apple Pro Res 422, Linear PCM
    There are no error messages, the import into Premiere Pro 2014 begins normally but the "progress bar" never starts and then after about 10 seconds a blank white box appears followed by the pinwheel.
    When the problem occurred I was trying to import a fcp7 project's xml file into Premiere Pro.
    I emailed Adobe Support Tech the fcp7 xml file and it crashed his computer, however, I was able to successfully import one clip from fcp7  (an Apple ProRes 422, Linear PCM, duration 1 minute) from the fcp 7 project into Premiere Pro, but not the whole project or the bare essentials (the cut itself).
    I am not running other software
    Do you have any third-party effects or codecs installed?  Not that I know of...
    Tell us about your computer hardware. Be especially certain to tell us about third-party I/O hardware (e.g., AJA, Matrox, Blackmagic, MOTU). ??????
    I am using Mercury Playback Engine GPU Acceleration
    The problem only happen when I try to import the FCP7 xml project file into Premiere Pro

    Hi Lynn,
    Have you inspected the XML file for any anomalies? That might be a way to see if any third party effects were used.
    Thanks,
    Kevin

Maybe you are looking for