Premiere Pro CC 2014 No Longer Remembers Which Order My Sequences Were Open

I often work with a dozen or more sequences inside a project. This was never a problem before, because I could have the ones I wanted to work on open and arranged in the Timeline Panel, save and exit, and when I returned to the project everything would be as I left it.
I've just installed the new 2014 version of the program, and now when I reload a project, it will load with a random selection of the existing sequences open, meaning I then have to reopen the ones I want and rearrange them. Every time.
Curiously, if I had two Timeline Panels running when I last quit, it will remember that, but not which sequence(s) were in the different panels.
Is there a known fix for this, or am I waiting on Adobe again?

Please everyone submit a bug report here to Adobe in hopes they will take action and not sit on this.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&loc=en
******BUG******
Concise problem statement:
Steps to reproduce bug:
1. Create multiple sequences in project A
2. Open a project B with only one sequence
3. Open project A brings up random sequences or only one sequence
Results: Sequence order in project is not remembered by Premiere after opening other projects
Expected results: Project should open the same sequences in the same order that were left open

Similar Messages

  • Premiere Pro CC 2014 crashing when trying to see a sequence

    This is the error message I keep receiving - 
    [/caravan/releases/2014.09/shared/adobe/MediaCore/Backend/Src/Sequence/PersistentGroupCont ainer.cpp-279]
    The only variant I've seen is when I try opening the same sequence in Premiere Pro CC, not 2014.
    I've tried importing in the exact sequence to a fresh new project and it drops the import altogether. Has anyone seen this happen across multiple versions of cleanly installed Premiere?

    Hi Cityroom,
    This might be helpful: https://forums.adobe.com/thread/1394068?tstart=0
    Thanks!
    Rameez

  • 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 2014.2 has been crashing within 10 minutes of opening a project. Usually when scrolling, but not always. What can I do?

    Sometimes it does it without scrolling, just on it's own. 
    PC. HP Z800 16 GB Ram Dual quad core Xeon  NVidia Quadro 3800 card.
    I started this project last week and went an entire day without a crash.  Since then the only major change to the computer was installing Quick Books 2015.
    Sometimes when I reopen PPRo after the crash, I get an error message that says Mercury GPU hardware not found, opening in software only mode, but that is maybe one time out of five.
    Any thoughts?

    Hi Chris,
    Chris Skrundz wrote:
    Sometimes it does it without scrolling, just on it's own.
    PC. HP Z800 16 GB Ram Dual quad core Xeon  NVidia Quadro 3800 card.
    I started this project last week and went an entire day without a crash.  Since then the only major change to the computer was installing Quick Books 2015.
    Sometimes when I reopen PPRo after the crash, I get an error message that says Mercury GPU hardware not found, opening in software only mode, but that is maybe one time out of five.
    Any thoughts?
    You may want to update your GPU drivers.
    Quick Books is less suspect, but you might try uninstalling it temporarily if updating GPU drivers does not help.
    Thanks,
    Kevin

  • Premiere pro cc 2014 just abruptly shut down and now will not open my project please help...

    I am trying to open a project file that just abruptly shut down - "serious error occurred" and now my project will not open at all.  I have no idea what to do other than start over completely!!  Multi cam mix with camera over 1 and 15 minutes of video - hoping my work is not lost forever.

    Yep that is what I had to do...Thank you for your help

  • 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 TickTime Crash FIX (in some cases)

    In my experience so far, Premiere Pro can return a TickTime.ccp error in several different situations. In some instances (too much Warp Stabilizer) just clicking okay a gazillion times is a usable workaround. In a case I had recently, Premiere Pro CC2014 crashed completely every time I tried opening the project file and all its autosaved versions. Here's a description of what I figured out to be the problem and how I solved it.
    My project file was created in CS6, then edited in CC2014 on a Mac, then Windows. After this the crashing started on both Mac and Windows version of Premiere Pro CC 2014.
    Symptoms:
    An error message pops up on opening project [..\..\src\TickTime.ccp-290]. Clicking okay brings up another more serious one about a Serious Error and PP needing to close. Then it dies.
    The problem:
    Somewhere between CS6 and CC2014, Adobe seems to have changed their XML file structure from using a comma as decimal separator to instead using a period. Somewhere within my project file, Premiere left one as a comma.
    My fix:
    1. Make a copy of your project file and change the extension from ".prproj" to ".gz"
    2. Use something like 7zip and extract the file, this should give you a new file with no extention.
    3. Edit this file in a text editor (I'd reccomend Notepad++ or TextWrangler, but Notepad and TextEdit will also do).
    4. Search for the term <PlaybackSpeed>. Most of your clips would have a numerical value of 1 directly after this, referring to a playback speed of 100%. Click Find Next a few times and look at the numbers following the selected bits. Anything that is not a multiple of 100 will be a decimal number, that should look like "0.5" or "1.2759984", (referring to speed values of 50% and 127.59984% respectively). If you see a comma, replace it with a full stop. My project had a value of "0,8845" I had to change it to "0.8845"
    5. Save the file, and using 7-Zip, compress it into a new gz file.
    6. Change the ".gz" extension to ".prproj" and you should be set to continue your edit.
    If you didn't change the speed of any of you clips, chances are this is not your problem.

    Hi Karel,
    Thanks very much for writing this up. I hope this helps others having this issue.
    Thanks,
    Kevin

  • Premiere pro cc 2014 update failed

    Couldn't move a project from desktop to laptop. Laptop showed premiere pro cc 2014 up to date. But when I tried opening project it said it was created on a newer version. Chat support said I should downoad an update from a link they provided. Tried installing but says Update Failed. Tried cc cleaner too. No luck.

    U44.. update error http://forums.adobe.com/thread/1289956 may help
    -more U44.. discussion http://forums.adobe.com/thread/1275963
    -http://helpx.adobe.com/creative-suite/kb/error-u44m1p7-installing-updates-ccm.html
    -http://helpx.adobe.com/creative-suite/kb/error-u44m1i210-installing-updates-ccm.html
    or
    Creative Cloud chat support (all Creative Cloud customer service issues)
    http://helpx.adobe.com/x-productkb/global/service-ccm.html

  • Audio-Problem with Adobe Premiere Pro CC 2014 by using long Clips in AVC-Intra Codec (4Gb Border)

    Hello
    We own a Panasonic camera (AJ-PX5000G) and we film in 1080p50 with the AVC-Intra100 Codec. When importing longer clips in Premiere Pro, the video is fully loaded, but the waveform of the sound ends at the Time Code 00:02:28:35.
    Sometimes the sound could be played after this Timecode but otherwise there is no audio. Even if we use the same clip several times we see that it works sometimes and sometimes not. It looks random.
    We also tried to import the Clips with Adobe Prelude directly from the P2-Card but there are the same problems.
    The Clips in 1080p50 AVC-Intra100 have a bitrate of 227Mbps. After 2 Minutes and 28 Seconds 4Gb are written on the P2-Card and the Camera starts a new picture file and 4 sound files..
    It looks like Adobe Premiere Pro has problems with the correct relation of the files that all get together to one clip.
    Is there anybody who can confirm this problem? Can anybody help me with this Premiere Problem?
    Dennis
    (Workstation:  Dell Precision T3600, Intel Xeon E5-1620 @ 3.60 GHz, 16 GB RAM, Windows 7 Professional 64-bit, Service Pack 1, Premiere Pro CC 2014.1 (Build 8.1.0)   )
    Mediainfo of the P2-Cards:
    General
    Complete name                            : \CONTENTS\VIDEO\0068T7.MXF
    Format                                   : MXF
    Format profile                           : OP-Atom
    Format settings                          : Closed / Complete
    File size                                : 3.92 GiB
    Duration                                 : 2mn 28s
    Overall bit rate                         : 227 Mbps
    Encoded date                             : 2014-10-15 13:33:41.000
    Writing application                      : Panasonic P2 2.0
    Writing library                          : Panasonic P2 2.0
    Video
    ID                                       : 2
    Format                                   : AVC
    Format/Info                              : Advanced Video Codec
    Format profile                           : High 4:2:[email protected]
    Format settings, CABAC                   : No
    Format settings, GOP                     : N=1
    Format settings, wrapping mode           : Clip
    Codec ID                                 : 0D01030102106002-0401020201323104
    Duration                                 : 2mn 28s
    Bit rate                                 : 227 Mbps
    Width                                    : 1 920 pixels
    Height                                   : 1 080 pixels
    Display aspect ratio                     : 16:9
    Frame rate                               : 50.000 fps
    Standard                                 : Component
    Color space                              : YUV
    Chroma subsampling                       : 4:2:2
    Bit depth                                : 10 bits
    Scan type                                : Progressive
    Bits/(Pixel*Frame)                       : 2.193
    Stream size                              : 3.92 GiB (100%)
    Color primaries                          : BT.709
    Transfer characteristics                 : BT.709
    Matrix coefficients                      : BT.709
    Mediainfo Audio-Datei P2-Card:
    General
    Complete name                            : \CONTENTS\AUDIO\0068T700.MXF
    Format                                   : MXF
    Format profile                           : OP-Atom
    Format settings                          : Closed / Complete
    File size                                : 13.6 MiB
    Duration                                 : 2mn 28s
    Overall bit rate mode                    : Constant
    Overall bit rate                         : 770 Kbps
    Encoded date                             : 2014-10-15 13:33:41.000
    Writing application                      : Panasonic P2 2.0
    Writing library                          : Panasonic P2 2.0
    Audio
    ID                                       : 3
    Format                                   : PCM
    Format settings, Endianness              : Little
    Format settings, wrapping mode           : Clip (AES)
    Codec ID                                 : 0D01030102060400
    Duration                                 : 2mn 28s
    Bit rate mode                            : Constant
    Bit rate                                 : 768 Kbps
    Channel(s)                               : 1 channel
    Sampling rate                            : 48.0 KHz
    Bit depth                                : 16 bits
    Stream size                              : 13.6 MiB (100%)

    Hi,
    we have the same problem!
    It is not possible to play audio with the AVC-Intra100 Codec fluently.
    Can anybody help?
    Thanks,
    Anja

  • Exporting to Media Encoder crashes Premiere Pro CC 2014

    Greetings,
    I am experiencing a problem with premiere off and on. Right now it is an on problem. When I am exporting from Premiere Pro CC (and CC 2014) it will intermittently crash Premiere. I have tried this with several different audio and video formats (AVI [Lagarith and uncompressed], WAV, H.264, MPG2, AAC, etc). At the moment, every time I go to export to queue it locks up and hangs on the "Preparing data for export..." Media Encoder Launches and then it just freezes. I get "Problem Even Name: AppHangB1" over and over. Sometimes a full restart will fix this temporarily and sometimes it goes away for a long while. I managed to get a few sequences exported and then it just kept freezing on every PP CC restart.
    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, H.264.mov from 7D, and H.264 .MOV from iPhone.
    All stock video plugins with a few third party audio plugs.
    This problem happens with and without third party plugs, but it happens that this project uses them.
    I have chatted with Adobe help twice about the matter and nothing has come of it. Log out, log in = same. Restart = same (sometimes), create new user account = same, and so on. The only thing I haven't done is completely re-install premiere, which seems a bit overkill. One of the reps said he would get back to me in a few days after he watched the issue via screen share. Never heard back.
    I get the sense that this has something to do with PProHeadless.exe not launching or not running properly. When the crash happens on a fresh restart of PP CC 2014 PProHeadless is not running. I can start PProHeadless and it will send sequence to media encoder. When I try to export another sequence from the same project it crashes and I see another instance of PProHeadless launched.
    Also, once the projects are exported to Media Encoder, I can encode them to any format with no problem. The problem is getting the sequences there!
    Is there anything that I am overlooking here?
    Thanks for the help!

    Hi
    Premiere pro cc 2014  8.0.1 (21) build
    Encoder CC 2014 8.0.1.48
    I use CC for Teams so it updates all the time.
    Again when I tried to use it today by letting premiere open it by sending an output into Queue it crashed both Encoder and Premiere.
    In order to shut down Encoder and Premiere I had to go into Task Manager and "End Process Tree" on everything adobe I could find because just ending Encoder did not work it would not close. I remembered that years ago when Premiere would crash we had to end a photoshop process. I found photoshop open even though it was not "alive" on my task bar. I had used it yesterday but had closed it. I also had to close dynamiclinkmanager.exe *32 as well as one of the three Adobe CDF Helper.exe*32. They popped back on but Encode closed and then I got a message that Premiere needed to close and did when I clicked the button to let it close.
    After all this I re-opened Encoder by itself and checked the Preferences finding that Import Sequences Natively option was again checked.
    By the way for me, "Launch AME manually, then drag the sequence from PPro's Project panel to AME's Queue (or to a preset in the Preset Browser). That uses a different code path than the File>Export>Media workflow." won't work most of the time because I do live events of panel interviews that may run 2 or more hours. I need to break them down to chapters for the web
    Also I know this isn't part of this problem but I and many others would still love dynamiclink to work to Encore because the DVD is not dead yet. The current work path is a drag.
    Looks like some programers and engineers have some work to do.
    Thanks
    Dennis
    My computer:
    Self built PC windows 7 Professional 64 bit Build 7601 SP 1 I use auto update so it is up to date.
    ASUS P6x58D Premium Motherboard
    Intel (R) Core i7 930 @ 2.80 Ghz
    Installed Memory  12 GB
    NVIDIA GeForce 9500 GT
    NVIDIA GeForce GTX 580
    2 Apple Monitors and a HP full HD Monitor
    With a BlackMagic Intensity Pro Capture Card

  • Adobe Premiere Pro CC 2014.2 (8.2) freezes up constantly on Mac OS X Yosemite

    After the latest update (no idea which one but the latest update) Premiere Pro cc just keeps freezing up constantly. There's no indication what brings it up but after different periods of time I just get the apple wheel and the entire program freezes up. I force quit and get the "sorry, a serious problem has occured", blabla. Sometimes it's in the middle of cutting a clip, sometimes it's while trimming. There isn't a single indication what causes it. At first I thought it was only because of using a multicam clip, but that's not the case anymore. I tried reducing memory to other apps, deleting preview files, deleting autosaves, turning off autosave altogether, deleting Adobe Premiere 8.0 preference file, changing permissions, basically everything in this post: Re: Adobe Premiere Pro CC keeps crashing... (Which now also seems totally neglected by Adobe).
    Believe me, there's hardly a thing I haven't tried.
    It's getting REALLY frustrating now and it's time something is done about this. Yes I know, "don't just say it's frustrating, explain the problem", but that fase has passed now. I'm paying for this product and it needs to work like it should.
    Also I know I'm not the only one who's having these problems.
    My specs are:
    OS X Yosemite 10.10.1
    MacBook Pro (Retina, Mid 2012)
    2,3 GHz Intel Core i7
    16 GB 1600 MHz DDR3
    NVIDIA GeForce GT 650M 1024 MB

    Hi JJ,
    JJ Millen wrote:
    It is not about the past times you may or may not have participated, but about the latest message from rob654 and my last messages in that thread (which are clearly not about Windows).
    One great reason to get a Mac only version of the post. It is never a good idea to post on a Windows post with Mac problems. And when threads get so long and unruly, the team can't focus on the actual issue so it doesn't get the attention it needs.
    Now that we have that sorted out...
    JJ Millen wrote:
    I checked that and it says 8.2.0. (65) build.
    Thanks for the verification. You are running Premiere Pro CC 2014.2 (8.2). It helps to have that absolutely clear.
    JJ Millen wrote:
    Here are all the checkpoints mentioned in that thread, applicable to my project:
    - Version 8.2.0;
    - My Creative Cloud says Premiere Pro is up-to-date;
    - Operating system is OS X Yosemite version 10.10.1 (14B25);
    Very well, did things operate any differently on Mac OS X 10.9.x? Or did you have the same problem?
    JJ Millen wrote:
    Type: MPEG Movie
    File Size: 4,0 GB
    Image Size: 1920 x 1080
    Frame Rate: 25,00
    Source Audio Format: 48000 Hz - 16 bit - Stereo
    Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
    Total Duration: 00:12:35:16
    Pixel Aspect Ratio: 1,0;
    So is this H.264? What is the camera that you are working with? DSLR?
    JJ Millen wrote:
    - I do not get any error messages, except for the "Sorry, a serious problem has occurred"-message after I have to force quit my Premiere because of the freeze;
    What kind of drives are the media files stored on?
    Are the permissions set correctly (as Read/Write) for the Mac HD and your media drives?
    Are the permissions set correctly for all the Adobe folders as I outlined in my blog?
    JJ Millen wrote:
    - The problem mostly occurs when cutting a clip with the razor tool, regardless of the kind of clip;
    When you import clips, are you using File > Import, or are you importing via the Media Browser?
    JJ Millen wrote:
    - Yes this has worked before, the problems started either after creating a submix (which I've deleted, without result) and/or after updating to a newer version of Premiere CC;
    Definitely do not update Premiere Pro or OS X when in the middle of a project. Wait until it's complete. If you did either or both of these things, you can cause your project to become corrupt. After your current project is wrapped, test with a brand new project.
    JJ Millen wrote:
    - The only software I run actively besides Premiere is Apple's Mail program, Safari and/or Chrome, sometimes Wire, sometimes Spotify;
    - I currently have no third-part effects or codecs installed in Premiere;
    - I installed the latest CUDA Mac Driver, version 6.5.37 (release date 01/14/2015);
    - The problem just happens while working in my sequence, not in any final output. I don't know what is meant by "previews", but I have the yellow bar indicator in my sequence, if that's info you need.
    I have heard of others having issues with OS X 10.10 and NVIDIA GPUs. My advice is to consider downgrading your OS if you continue to have issues. I believe I have avoided a lot of trouble by sticking to OS X 10.8.5.
    Previews AKA the Media Cache are your "render files." They can become corrupt, so it's a good idea to trash them when troubleshooting. You can locate them via your Preferences > Media. Click the Browse button.
    JJ Millen wrote:
    Okay I went through that menu (which I'm not eager to do, I prefer direct contact) and came across the CUDA setting inside the project settings. I've now enabled the "Mercury Playback Engine GPU Acceleration (CUDA)", which might help.
    So were you set to "Mercury Playback Engine Software Only" or "Mercury Playback Engine GPU Acceleration (OpenCL)" prior to changing it to "Mercury Playback Engine GPU Acceleration (CUDA)?
    JJ Millen wrote:
    Testing with a brand new project is not an option. I have a deadline for my current project and it's impossible to start from scratch. What I did try is start a new project and importing the existing one, which didn't help so far.
    I was just wondering if you experienced the same issues in a new project. Any project you update to a new version is suspect, in my opinion. In the future, try to avoid doing that. If your current project is corrupt, I could see why you are having certain issues.
    For what it's worth, we had another user that exhibited similar issues until they started with a brand new Premiere Pro CC 2014.2 (8.2) file.
    Since importing your 8.1 file to a new 8.2 project isn't working, make sure to triple check permissions on all the Adobe folders I laid out in my blog post: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)
    It's the #1 reason Mac users experience freezing and crashing. The other one I'd look at is that NVIDIA drivers are not working well with Yosemite. Finally, if you update a project across versions, it can become corrupt. Not much you can do about that except start a new project ASAP.
    Thanks,
    Kevin

  • Premiere Pro CC 2014.2 not stable on my system

    Mac OS 10.10.1
    I am having problems with Premiere Pro CC 2014.2 that make it almost unusable on my system. All other software, including AE, Audition, Prelude, Photoshop etc. working well.
    The symptoms, which are not specific to any one project - but seem to effect all equally - are:
    1) Intermittently, I loose the ability to play clips or the timeline. I can drag the playhead around, but nothing plays, nor does the viewer or program monitor change or update. I can't use the space bar for play, nor can I click the play button with the mouse.  Either action requires a re-start.
    2) Exiting the application, Premiere Pro will not completely shut down. It goes into some kind of limbo state. The only way to shut the application down is to use the Force Quit command from the Apple Menu. Once the application has been Forced to Quit, it will not restart until the computer has been restarted. It will just bounce up and down in the dock and never launch completely.  The only way to launch it again is to completely restart the computer. If the application has been force quit, when I shut the computer down, I get the spinning wheel for a very long time during the shut down process, but the computer does completely shut down on its own. After I restart, Premiere Pro starts up promptly.
    What I have done so far:
    Verified Disk Permissions
    Run Disk Warrior on all disks.
    Trashed Premiere Pro preferences
    Uninstalled the Premiere Pro app, and then re-installed a fresh download.
    My computer specs:
    And I am connected to 2 Thunderbolt Pegasus Raids for the media.
    Any help much appreciated.
    MtD

    Kevin Monahan wrote:
    Is your Mercury Playback Engine set to CUDA or OpenCL? Make sure it is in CUDA.
    Yes, it is.
    Does this happen with brand new projects, as well?
    Yes.
    Have you checked the permissions of all your Adobe folders? Are they set to Read Write?
    They were all set to read/write, I did the procedure as outlined in the link.
    Have you checked the permissions of your Mac HD and your media drives?
    Yes.
    If you create a new user with Admin privileges, does that work better?
    I have not tried this yet.
    If you disconnect your media drives do you see any improvement in stability?
    No.
    This problem does not, to me, seem to coincide with the either the OS upgrade or Software upgrade. It has begun to appear over the last week or so, and is occurring more and more often.
    Any help you can give appreciated.
    MtD

  • Premiere Pro CC 2014 freezes frequently and crashes

    Since upgrading from Premiere Pro CC to Premiere Pro CC 2014 my projects crash in regular intervals, which didn't happen before.
    All my settings and presets have been pulled across fine, but suddenly relatively slim projects get stuck during editing, rendering or exporting. The progress bar stops, the preview screen freezes and that's it. I can only radically crash the sucker. I did delete all preview files and it improved marginally... only that the time until it froze took a few minutes longer.
    I'm on 64bit high-end Windows 7 machine and have never had this problem with previous versions of Premiere Pro.
    Very frustrated.

    @bendubb37: I'm not the least bit defensive about complaints regarding the stability and general quality of the program. As a quality engineer on the Premiere Pro development team (not a member of the technical support team), I'm quite familiar with many if not most of the problems--both those that are legitimate bugs in our code and those that result from conflicts with OSes, hardware, codecs, other programs, etc. I genuinely appreciate having customers come to this forum to report issues they're having. Such reports sometimes help us identify bugs that we weren't aware of, and they always help us to prioritize bugs to fix based on which issues are biting the most customers and having the greatest impact on their productivity and satisfaction. And naturally I understand the frustration and anger of customers who are wrestling with one problem or another in the program.
    What I took issue with was cutco's derision of a perfectly valid troubleshooting step recommended by a technical support agent and his assertions that a) "This community is kind of useless" and b) "Adobe is absent." Cutco graciously acknowledged that he had let his frustration get the best of him.
    As to the oft-repeated claim that CC2014 is buggier and less stable than prior versions, I submit that it's a problematic claim to substantiate, at least based on anecdotal personal experience or taking the pulse of this forum & others. There's no question that some customers who enjoyed smooth sailing with an earlier version are experiencing problems with CC2014. But I know for a fact that this release included fixes for a significant number of bugs, including crashers, so many other customers who were having problems with earlier versions are now cruising along without a hitch (or at least without those old, fixed hitches). Alas, those people are not frequenting the forum to sing the praises of CC2014.
    My point here is simply that claims about the relative quality of one release versus others can be a distraction from the more important--and much more concrete--fact: a certain number of customers using CC2014 are having Problem X, which didn't happen in CC7.x. The more we can learn about Problem X--and the more clearly we can differentiate X from Y and Z, which may manifest similarly--the sooner we can nail down the cause.
    Don't get me wrong: there is an objective trajectory of a product's quality. Unfortunately, even when you have a large pool of data in front of you, the trajectory doesn't lend itself to quantification. You can't simply count the number of deferred bugs, for instance, because not all bugs are equal. You can't even go by the number of known crashers because some are extreme edge cases while others lurk in the path of mainstream workflows. That said, for people like me who spend our working lives trying to deliver the highest quality possible, the trajectory our program's quality is a common topic of discussion.

  • Importing Premiere Pro CC 2014 media into Avid MC8

    Hi guys,
    I've been having a problem using AAFs to move sequences from Premiere Pro CC 2014 to Avid Media Composer 8, long story short I'm working with a post company using Adobe for everything, but the editor is at a different facility and uses Avid. I've been testing a workflow to go between the two, I know how to use both programmes and relink media, but when I import the AAF i made in Premiere into Avid although the footage names are there and the sequence shows up in the correct order when i try to reconnect the offline media no matter what I try it just won't do it.
    Having googled it I found that this used to be an issue between Premiere CS6 and Avid 7, so is this still an issue that I have to find a way around? Or is there a simple fix that I haven't found?
    Thanks,
    Andy
    Also I forgot to note that the files we use are .MXF, which are unsupported by FCP7, meaning we can't go through Automatic Duck in there. Go figure.

    More hardware information might help someone give you an idea
    -Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
    or
    http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/

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

Maybe you are looking for