Bugs in Premiere Pro CC 2014 (8.0)

I'm going to file bug reports but just wanted to see if anyone else is having these problems...
• setting poster frames - whenever I set a poster frame the chosen frame doesn't stick
• video & audio preview folder location - I have my scratch disk folders all set to my RAID, but every time I quit & reopen a project the preview folder location changes to inside the folder where my project files are. this is highly frustrating bc I save my projects in a dropbox folder for backup, and now dropbox is always trying to sync my preview file folders as well. changing the location in project settings has no effect after a quit & reopen.
• project manager - I recently opened a Trimmed project that was created in PPro CC (7.X), the project used to open fine but now in PPro CC 2014 (8.0) the Trimmed project has various problems, clips not lining up, or missing or having black frames. I opened the original (non-Trimmed) project in PPro CC 2014 (8.0) and everything was fine, then I used project manager in 8.0 and the resulting Trimmed project had the same problems as the one created previous to 8.0
anyone else?

The project was very large. Connected to 5 TB of media on a server, not local, or ext. hd. I needed to "trim" the sequences to make them manageable to put on an Ext HD and mail around the world to different bureaus of our media company. I opened the project manager and trimmed the first sequence and it worked fine. All subsequent sequences ended in the same error. "Unknown error, please save and re-try." I tried changing the settings of the "trim" and nothing worked. I tried several different computer, still didn't work. I tried saving the trimmed sequences to different HD's, servers, local desktops, etc. Nothing worked. Same Unknown Error. I think it might have to do with audio that is in the sequence that is not being used in conjunction with the associated video. But, that is crazy. All sequences include this type of editing. But, the first sequence that worked didn't. SO, maybe that is it.
Please fix this problem because I still need to trim these sequences and I'm on a deadline of December 1, 2014!
Thank you,
Ben Dyer

Similar Messages

Bug in premiere pro cc 2014.1 (81)

Hello everyone,
there is a bug in Premiere Pro 2014.1 (81) - when you want to replase klip from bin or from sourse monitor on klip in your timeline (and speed of your clip on timeline is not 100%, it is set to 50% , or 60% - it is not matter) it happends, but it replaced not from moment, that you are deside (with your IN button), it replaced from the another point of the video. It happends only if your klip on timeline is not set on 100% speed (then it is on 100% speed - everything is work perfect). In previus build (AP 2014.0.1 (21)) all work perfect in any case .
Maybe someone faced a similar problem and knows its solution ?
Best regards , Alex

More information needed for someone to help... please click below and provide the requested information
-Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
Exactly what is INSIDE the video you are editing?
Codec & Format information, with 2 links inside for you to read http://forums.adobe.com/thread/1270588
Report back with the codec details of your file, use the programs below... A screen shot works well to SHOW people what you are doing
https://forums.adobe.com/thread/1070933 for screen shot instructions
Free programs to get file information for PC/Mac http://mediaarea.net/en/MediaInfo/Download

Re-interpreted footage metadata is lost when moving Premiere Pro CC 2014 project file to different computer

Hi guys,
I believe this is just a bug in Premiere Pro CC 2014 (and other versions in the past), but I wanted to make sure it was on the PP team's plate for the next update, since it's detrimental to a workflow that include more than one computer or more than one editor on a project.
My team shoots a lot of footage in slow-motion (for instance, 59.94 for 23.976). Premiere's process to conform this footage is great. Modify -> Interpret Footage -> Assume this frame rate: "23.976".
Unfortunately, when we move this project file to another system, even if we are using a hard-drive that is synced to have the exact same source media files with the exact same file structure, we lose the footage interpretation metadata. Premiere Pro CC thinks this footage is 59.94 again, and our sequences are in shambles. All clips where the interpretation metadata is lost have "zebra pin stripes" on them wherever they exist in our sequences.
We have to manually re-interpret the footage, and then sometimes manually re-select in and out points. This is a work-around that enables us to push forward, but it's a barrier that makes collaborative editing extremely challenging and opens up rampant possibility for error. It's hard to locate every clip we need to re-interpret in some of our more complex projects, and even harder to avoid re-interpreting the wrong clips.
Looking forward to a resolution to this problem.
Daniel Lichtenberg
[ad/link removed by moderator]

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

Flicker footage in Premiere Pro CC 2014.2. Tested on different computers. When waiting for fixes this bug?

Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different. Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
It can occur even in the parts without filters !!! But no all time.
ver 2014.2 - win 7 - intel i7-4770 - gtx 770 - flicker!
ver 2014.2 - win 7 - intel i7-4770 - Intel HD Graphics 4600 - flicker!
ver 2014.2 - win 7 - intel i7-2700K - quadro 2000 - flicker!
MERCURY PLAYBACK ENGINE work fine! But still flickering in preview and render.
When waiting for fixes this bug?

Hi Aleksey,
Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different.
Have you tried with the Mercury Playback Engine set to "Software Only?" More info please: FAQ: What information should I provide when asking a question on this forum?
Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
Is this a brand new project or one you updated from an earlier version? What kind of footage are you exporting? Which preset are you using?
When waiting for fixes this bug?
If I can repeat the case here with the same hardware, GPU, and drivers, that would be easier to fix the bug. Currently, I cannot recreate the bug. If you or anyone else can provide me with steps to recreate the bug, that would help immensely. It sounds like this will be the difficult thing.
Thanks,
Kevin

Bug in Premiere Pro 2014.1

Hello everyone,
there is a bug in Premiere Pro 2014.1 (81) - when you want to replase klip from bin or from sourse monitor on klip in your timeline (and speed of your clip on timeline is not 100%, it is set to 50% , or 60% - it is not matter) it happends, but it replaced not from moment, that you are deside (with your IN button), it replaced from the another point of the video. It happends only if your klip on timeline is not set on 100% speed (then it is on 100% speed - everything is work perfect). In previus build (AP 2014.0.1 (21)) all work perfect in any case .
Maybe someone faced a similar problem and knows its solution ?
Best regards , Alex

Anyone from Adobe care to offer some insight as it's something that is reportedly fixed?

What is the problem with Adobe Creative Cloud Premiere Pro CC 2014, why it freezes often?

I Purchased the Adobe Creative Productive Premium Suite CS5 in early 2010 and I was very satisfied with it all this time, I can say that I never had a problem while using any of the Production Premium applications. Few weeks ago, I asked Mr. Philip Bloom about a technical issue regarding the best method to use a 50 FPS clip with a 23.976 FPS project, and I got his kind help but he recommended me too that I should upgrade to the latest Adobe Cloud CC 2014 which has many new features added to the different programs. I took his kind advice and downloaded a trial version of all the Adobe Cloud CC programs which I use for my filmmaking business.
Today is the 20th day of my trial period and I have 10 days left to take the decision of continuing with CC 2014 or not. The past 20 trial days were not very pleasant. I want you to share with me the following details which I'll list them as bullet points and I would appreciate diagnosing the problem if you can and suggest a solution for it to re-try the Adobe Cloud CC 2014 for the 10 remaining days with no further problems.
I used to have the Gigabyte graphics card GTX 470 for about 4 years and it malfunctioned last year and I replaced it with a humble Geoforce GT 610 card, but it worked fine with the Adobe Suite CS5 programs.
My system configuration is Intel Core I7 950@ 3.07GHz , installed memory 12 GB. , Windows 7 Ultimate, 64 bit Service pack 1, 3 hard drives 1TB. each (one of them is dedicated for Adobe asset files and the editing work)
For the first 2 or 3 days I used mainly the Premiere Pro CC 2014 establishing short projects for a max. of 5 minutes each and it was working normal. But, later, as soon as I started to build a project which reached about 24 minutes of length and I began to edit those before I add more clips to the timeline, unfortunately, the PrPro CC 2014 started to freeze on any of the frames every time I try to edit normally as I used to do with the CS5, so, I had to wait for 2 or 3 minutes every time it freezes, then it works for seconds then freezes again!! and during the 20 days mentioned above it crashed once.
The movie files of my project are the Nikon's .Mov files and the editing work which I performed included effects such as Color correction (levels) color correction (fast) color correction (Auto) sharpen effect, and stabilizing effect.
I installed the Magic Bullets Suite trial version, and the Neat Video trial version, aiming to purchase either the DeNoiser or the Neat Video (but I tried their effects without saving them to the project).
I used to export parts/ or whole project before finalizing the editing process to be able to monitor on a TV screen (mp4 file format) some of the changes I made in PrPro before being freezed.
Based on my previous 5 years experience using the CS5 Suite I have a strong trust in Adobe, I never thought the problem was in the PrPro application, but rationally I thought it was the graphic card (GT610), and accordingly I purchased yesterday a new Zotac Geoforce GTX 770 (listed by Adobe as an approved card) and I installed it and checked that it is running fine and I checked the processor temperature which was within the normal level.
Only today, I began to think that it might be something wrong with the Adobe Cloud CC 2014 ( a bug or something) and as a result of searching on the internet I could see lot of users since 2014 who were having freezes and crashes with the CC and the CC 2014 versions. That was a shock for me, could it be that until Feb. 2015 the same severe problem still occurs???
Sorry for any inconvenience, looking forward to seeing a solution for that serious problem.

Hello Ashraf,
Sorry you didn't get any help on this post. In the future, please contact Adobe Support for 1-1 assistance on issues like this: Contact Customer Care
Thanks,
Kevin

How to work on the same project on two machines at the same time and also exchange progress seamlessly using Adobe Premiere Pro CC 2014?

We are working on a film project on Adobe Premiere Pro CC 2014. Two editors are working on the same film project (same pproj file ) on two machines. As a result the bin structure and the file structure is exactly the same. We even bought two licenses for the respective machines to make matters simple (at least we thought it would).
Now when we share a sequence between the two machines, every time we have to import and re-link media. Also each sequence import comes with its own set of files, which are actually already present in the project. Basically the new sequences are looking to re-link the media to the original/ source files only and are completely ignoring the file structure present in the project.
In all editing softwares, timeline/ sequence sharing is a very common practise when working on multiple machines. Why is it so tedious in CC 2014? Every time we share a sequence between the two machines the media gets doubled and tripled in the project. As a result the project file size is increasing perpetually. Already Premiere CC 2014 is extremely laggy and slow, and this stupid bug is making it more difficult for us to finish our work on time.
Has anybody ever faced this issue? How do we solve it? We are willing to try out any workflow that you can suggest.

Concurrently working on the same project it requires a specific implementation in all editing programs like Avid's Unity/ ISIS shared storage. That's what you are simply not considering. none of your issues would be any problem if your projects resided on a commonly accessed server or something like that. Check respective hardware solutions.
Mylenium

After upgrading to Premiere Pro CC 2014, I can't change the render preview location

Ever since I downloaded Premiere Pro CC 2014, I cannot re-route my render preview files. I have two internal hard drives and I need the files to go to my secondary one. With CC, it did this just fine, but since I've upgraded to 2014, it will not do it. I've set it the same way I did before in Preferences/Media, then set the Media Cache Files and Media Cache Database to the new hard drive. It's eating all my hard drive space and I cannot render or export a large sequence. Is there a trick to this I'm missing that has changed?

Thanks Neil! I'm actually wondering how to change where the preview files go. I've attached two screen grabs. Right now my media cache is going to my SATA drive (my smaller of my two internal hard drives and the drive where Premiere Pro is located.) I want to re-route my render files to go to my Macintosh HD drive which is much larger and gives me more breathing room. I could do that before but since I've upgraded to 2014, even though I have it set in preferences, it STILL goes to my SATA drive. So annoying! I'm wondering if I'm doing something wrong or if it's a bug. I'm still running Mountain Lion (getting ready to finally upgrade, I've just been needing to backup my computer), could this be the reason? Any ideas? Thanks so much for the help!

Can't Move Audio Clips in Timeline After Expanding to View Waveforms (Premiere Pro CC 2014.2)

So, this seems to be a bit of a weird one, and I'd be pretty stoked if it ended up being something silly that I'm doing wrong, but I can't for the life of me figure out what that might be.
As the title suggests, I can't use the mouse to move some audio clips in a timeline once I expand the track to view the waveforms. This appears to only happen with independent audio clips (WAV. AIFF, MP3, etc), and not with clips attached to video. Also, it's worth noting that I don't have track keyframes turned on. I was hoping that was it, but it wasn't.
So, what happens is this:
1) I drag an audio clip down to the timeline (I can drag it onto an existing track, or drag to the bottom of the sequence and create a new track. Neither option seems to get a different result.).
2) So long as the track isn't expanded and the waveform isn't visible, I can move the clip left, right, or up and down to a different track.
3) As soon as I expand the track to view the waveform this functionality goes out the window. When this issue happens I can use the keyboard to nudge left and right, but that's about all the movement I have.
4) It's almost as though the track becomes corrupt. The lanes for the track don't redraw properly, and the track is pretty much unusable. I can't put anything into it, and I can't take anything out. All I can do is delete the track and start again.
Complicating issues is that this doesn't always happen, but instead is one of those "vast majority of the time" issues. I can't see any rhyme or reason for why it works or doesn't. I seem to do the exact same thing, but occasionally get different results. It doesn't matter what type of file I'm using (WAV, AIFF, etc), and this only happens with independent audio clips.
Once again, I don't have track keyframing turned on when this happens. Believe me, I wish that was it.
I have already filed a couple of bug reports about this over the last month or so, but haven't heard anything yet. I was wondering if anyone else was having the same issue, and if so, whether they had any workarounds.
Mandatory system info:
Windows 7 Professional SP1 (64-Bit)
Intel i7-3820
32GB RAM
Nvidia GTX 980 (350.12)
Premiere Pro CC 2014.2

Update:
I was just looking to post a screenshot of the timeline when I discovered something interesting. As soon as I use the vertical scroll bar to the right of the sequence, the tracks start to work again. Close off the waveform and the clip goes haywire. Move the scroll bar a tiny bit (or a lot), and suddenly the clip starts working.
Pretty bizarre.
The good news is that for the time being that could be a workaround, though it would be great for this to not happen at all.

Premiere Pro CC 2014 and Media Encoder CC 2014 not completing encode.

This is a project that I have been successfully encoding in short segments until now. Now when encoding, session runs about 10-15 minutes and then ends without error messages.
Removing effects and changing to Mercury PB Engine SW did not help.
Also tried disabling metadata as suggested in another forum.
When CUDA used, logged as "Encoding failed." When Mercury SW used, logged as "File Successfully Encoded" even though video file is only 6 KB with no content.
Premiere Pro Build 8.1.0 (81)
Media Encoder Build 8.1.0.122
Windows 7 Professional
Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
8 GB RAM
NVIDIA GeForce GT 610 (9.18.13.3788)

I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out.

Premiere Pro CC 2014 and Media Encoder CC 2014 Crashing constantly

Running out of options and ideas...
Symptom: Every time I work on any project in Premiere Pro CC 2014 or try to render out in Premiere Pro CC 2014 or Media Encoder CC 2014, the software crashes after 2-3 minutes of use/rendering when the GPU is enabled in Premiere/Media Encoder, or after 5-10 minutes of use/rendering in software only mode. The crash is a software crash, Windows continues to run fine.
I have tried all the standard list of steps that adobe reps post on threads like these - clearing media cache, software only on render, new project, etc. https://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-windows.html
Windows event is not that helpful to me:
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff5ecb4de40
Faulting process id: 0x1dc8
Faulting application start time: 0x01d04a503cd82df2
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: unknown
Report Id: cacdfbab-b717-11e4-826d-8863dfc268bc
Faulting package full name:
Faulting package-relative application ID:
I have wiped adobe off the machine and reinstalled - same problem. I have tried projects that crash the machine on other machines and it works fine.
The machine is new, clean install and runs everything else great - 3ds max, high res games, scientific computing - max memory use, etc.
Spec:
5K iMac running bootcamp and Windows 8.1
Intel Core i7-4790K @ 4.0 GHz
32 GB ram
1TB SSD
AMD Radeon R9 M295X 4GB GDDR5
I have used this bootcamp/imac configuration for 5+ years on 3-4 machines and everything has always just worked great. Guess it was my time for a problem, but I'm open to new ideas to try...
Finally - I hope someone from Adobe reads this. I have spent 2 nights on the phone with support. The first night I got an over confident answer that it's a gpu driver issue, just go with software only (no luck - same crashes and different drivers aren't solving the problem). Tonight I was hung up on "by accident" as the agent looked up my video card after waiting 15 minutes to talk to someone, only to be hung up on a second time while on hold after calling back and waiting 20 minutes (because I assume the Adobe call center closed). No message to say so, just hung up on. An overall very disappointing experience.
Thanks in advance to anyone with ideas on things to try,
Cheers!

I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out.

Premiere Pro CC 2014 and Medie Encoder CC 2014 problem

Hello there,
Every time that I am willing to export my project my Premiere Pro CC 2014 stop responding all together. I tried the short cut (Commend+M) or going through the Manu bar. the result is the same, Premiere Pro CC 2014 just freezes and does not respond to anything till I force quit it and restart it allover again. I tried exporting from Premiere Pro it self, without using Media Encoder, but the problem remains the same.
I am using the new Mac Pro. I heard Adobe Premiere Pro is experiencing problems with the New Mac Pro. Is that true? Or is there other issue?
Thank you and looking forward to hear back,
Maruf

I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out.

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

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

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

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.

Premiere Pro CC 2014 crash when I Click and Drag

Hi All, I have a problem with Premiere CC 2014 that is driving me crazy!
The issue is as follows:
If I try to drag a clip, sequence, effect or transition anywhere within the premiere, it will crash - with "Sorry, a serious error has occurred" message. The program will crash, quit and the saved recovery project is usually healthy (luckily!). BUT, as soon as I've re-started the program, and reloaded the project - or any project for that matter - the problem persists. As soon as I click and drag, Premiere crashes!
In order to 'reset' this, I have to restart my machine. Once I have done so, I can continue editing as normal for a while (not long, perhaps up to an hour, or so) but eventually, it WILL crash again. I've not been able to work out what I have to do in order to trigger this - it seems random. But once it's happened, only restarting my computer will resolve it - and then only temporarily.
Here are all the facts:
The crash ONLY happens when I drag something... This can include moving a clip on the timeline, dragging a clip form the source viewer or project window, dragging an effect or transition.
The crash happens after I have clicked, as soon as I start to move my mouse.
I CAN click and drag to extend in and out points on the timeline, and I can do 'insert' edit using the button on the source monitor. No crash here.
The footage plays fine.
I am trying this on a CLEAN OS X install, with only Adobe packages installed, to eliminate any potential of interference from other programs. There are no third party plugins or drivers installed. No user data installed either (preferences, photos, documents, etc) - as fresh as it comes!
I am not running Time Machine in the BG
My system is: Macbook Pro 2011, 16GB Ram, 1tb SSD, OS X Yosemite 10.10.1. Intel Graphics card, so no option to turn on or off hardware acceleration. It is set to software only.
I have tested this with projects and footage on an external drive, as well as internal, same issue.
I noticed the issue had started on, or around 25-27th November 2014.
Interestingly, I have noticed that once this crash has occurred in Premiere, a similar problem will occur in After Effects as soon as I drag a file or layer... doesn't matter what the layer is. The crash seems less elegant here, I don't get an error message, it just freezes and I have to 'force quit'. Again, the problem persists until the machine is restarted.
I have been using my macbook and premiere pro cc 2014 on Mavericks for a long time, and had no problems - so I know it should work fine! The only things that changed were an update to Yosemite, I started using Time Machine to make regular backups, I installed a few new fonts and any CC updates that happened in the background... I can rule out most of these because of my fresh install, with no user data, fonts plugins or time machine to confuse matters... It must be an Adobe bug with Yosemite!
Any ideas?
Thanks so much in advance!!

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

Bugs in Premiere Pro CC 2014 (8.0)

Similar Messages

Maybe you are looking for