Premiere Pro CC 2014 on Mac and AMD Firepro 7000

Hi,
Just got a new Mac Pro...
Processor 3.5 GHz 6-Core Intel Xeon E5, Memory 32 GB 1867 MHz DDR3 ECC, Graphics AMD FirePro D700 6144 MB X 2, OS X 10.9.4. Machine looks like a kettle whiteout a spout, but other than that, fantastic!
Set it up via TimeMachine backup from old machine (iMac 27''). Have to say that I'm not seeing a great difference in performance in Premiere? The old iMac have just 1gig of GPU, the new machine has 12gig. The only notable difference is that in the render bar above the timeline, what used to go red in need of rendering, is now yellow. But, anything complex (lots of effects or stacked video) looks like it needs rendering - judder, pixelated. I realise I could render whole timeline, but I work on events videos, sometimes timelines up to 2.5 hours.
Most footage I work in tends to be AVCHD from Sony's and I do realise that can be an issue but I was looking for a revelation in my editing experience - not there.
So what am I missing here? Having ported over from the old machine, is Premiere not optimised for this machine? Looked to see if I could re-install via Creative Cloud, don't seem to able to.
Any wisdom would be greatly received.
Nick

So the source, scratch, and exports are all being written/read via the USB caddy? It's a single drive? Or do you have mulitple caddies and drives? Spinning drive or SSD in the caddy?
Yes all being written to caddy. Double Inatek Caddy, only 1 drive being used - spinning drives not SSD's I'm afraid.
I wouldn't concern yourself too much with the displays you're using as far as speed is concerned. Storage, yes. Getting Tbolt2 RAID arrays will help, specially if you pack them full of SSDs. But nevermind that for now.
One day that will be the plan, have to get by for now.
Did you also restore from TM your user directory? Or did you create an entirely new user on your Mac Pro and start from scratch? My suspicion is that something may have gotten transferred over during the TM restore, and it's not playing nice.
Yes, restored User Directory too - am indeed thinking that was a bad idea - take note anyone reading this, there is an option not to.
Hm. That's not what the yellow bar means. Since you're using MPE in hardware mode, it means one or several of the following:
The source media’s codec is computationally difficult (such as AVCHD). As mentioned above, only very few simple codecs don’t get a yellow bar; these include DV and DVCPRO.
The settings of the clip (e.g., pixel aspect ratio, frame rate, field settings) don’t match the settings for the sequence.
A CUDA-accelerated video effect or transition has been applied to the clip. (A CUDA-accelerated video transition only causes a yellow bar over the duration of the transition.)
(per Todd's write-up from a few years ago)
I guess it will be the AVCHD. Thanks for link, better understanding now. Didn't see them very often on the old machine.
Given that you're editing AVCHD, it's likely the first bullet. When I edit AVCHD I see the same thing: a yellow bar. But playback is silky smooth (I have the 8-core version of the same machine).
So after reading your last post have had a play and setting up a new project on the internal 1TB SSD everything is indeed fine and I do now see a major difference.
Set up another new project on external drive and it was "OK", certainly better than existing project but better result working from the internal. That was my mistake, to open an existing project from an external drive and expect to see a major difference!
I had hoped that the external spinners would perform well enough via USB3, but obviously not. Future plan is to work off internal SSD and archive to externals when finished. I know it's still not ideal but i am gradually making my life easier. Happy to say I have the Mac for the job now just need to sort out storage.
Thanks Jason, you have helped by making think straight. It's taken a while to be able to afford the new Mac but that is obviously just part of the story. Still a Premiere man through and through!
ps. will try and edit the Subject line - get rid of that extra zero!

Similar Messages

Since installing Premiere Pro CC 2014 upgrade, Mac Pro jumpy video and freezes constantly

Since installing Premiere Pro CC 2014 upgrade, Mac Pro jumpy video and freezes constantly. Worked perfectly before. Anyone else finding these issues? I'm running a quad core Mac Pro, so it's definitely not the hardware.

I've maxed out the memory assignment, but this isn't a memory problem per se.
It looks like certain Premiere Pro conditions are associated with a huge increase in kernel_task memory, zeroing out any available free memory. In my case it seems to be associated with effects applied to titles or jpgs or imported psd (Photoshop) files.
Program restart pulls kernel memory back to the 1.3gb normal size.
Here's where I am at startup:
Within three minutes:

Adobe Premiere Pro CC 2014 keeps lagging and crashing

My Adobe Premiere Pro CC 2014 keeps lagging and crashing to a point where I cannot do my job. When I open my premiere file, I can work on my timeline for maybe two or three minutes before it lags, freezes, and then finally crashes. I'm at a loss of what exactly is causing my problem because I edit primarily H.264 files and my sequences are not complex in any sense of the word. I've been dealing with this for days and I cannot seem to find a solution. If anyone has any advice please let me know because I am desperate. Thank you.
Specs:
Model Name: Mac Pro
Model Identifier: MacPro6,1
Processor Name: Quad-Core Intel Xeon E5
Processor Speed: 3.7 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 10 MB
Memory: 16 GB
Boot ROM Version: MP61.0116.B05
SMC Version (system): 2.20f18
Illumination Version: 1.4a6

Hi Dana,
Can you go to File-Project Settings-General and change the video renderer to Software Only Mode.
Check if that works or not.
Are you using any third party plug-in's for Premiere Pro?
Thank You
Arjun

Premiere Pro CC 2014 playback freezing and crashing with new iMac i7

Using Premiere Pro CC 2014 and having constant playback freezing and software crashes on a brand new iMac i7.
Here are the specs:
iMac i7 4.0GHz 5k Retina
32 GB Ram
AMD Radeon R9 M295X 4GB graphics card
512GB Solid State Drive
I was on chat yesterday with an Adobe tech. Although playback/render settings show the OpenCL option to utilize the AMD graphics card for processing, I was advised to switch to "Software Only" as that card is not supported yet. I had to re-render my 45 minute documentary (which doesn't appear to be any faster than it was on my old 2011 iMac by the way) and it still has the same issues.
So frustrating? Anyone else experiencing this? Any advice? I hope I didn't just buy this "super machine" in vein.
Thanks,
Jason

Hi All,
Taking some tips from Kevin Monahan. If you haven't already gone through this list please do so.
Sign out from Creative Cloud, restart Premiere Pro, then sign in
Update any GPU drivers
Trash preferences
Ensure Adobe preference files are set to read/write
Delete media cache
Remove plug-ins
If you have AMD GPUs, make sure CUDA is not installed
Repair permissions
In Sequence Settings > Video Previews, change the codec to one that matches your footage
Disconnect any third party hardware
If you have a CUDA GPU, ensure that the Mercury Playback Engine is set to CUDA, not OpenCL
Disable App Nap
Reboot
Best,
Peter Garaway
Adobe
Premiere Pro

Premiere Pro CC 2014 QuickTime Audio and Video Syncing problem

Hi everyone,
I am having and issue when I import QuickTime video into Premiere Pro CC 2014. I've just started doing some editing so I am very new to all of this. I recorded video in Photo Booth on my mac. I exported the file to a .mov file and imported it in to Premiere. When I play the file in premiere everything is fine up until halfway through the video. The video starts to play faster than the audio and everything is off. When I play the video in QuickTime everything is fine. I don't know if I did something wrong when I imported the file but I am hoping for some help. Thank you.

I would be willing to bet the video is recorded as VFR, variable frame rate ... in other words, it creates more frames per second when it needs to for keeping up with screen changes, and less when it doesn't see much changing on your screen. This saves bandwidth of course, BUT ... PrPro is not setup to work well with VFR footage, it really needs CFR, constant FR. So ... highly recommended if your capture program doesn't allow setting CFR is the free program "Handbrake", which you can google for. Use that to convert the footage to CFR, then import that into PrPro.
Neil

Why does Adobe Premiere Pro CC 2014 cannot detect and install BlackMagicDesign's UltraStudio 4k?!

I have the new MAC Pro and I installed Adobe Premiere Pro CC 2014 few days ago.
I have the UltraStudio 4K by BlackMagicDesign connected through ThunderBolt.
BUT...
Premiere Pro CC cannot add it to the device control.

Did you install the UltraStudio Device driver before Adobe Premiere Pro CC 2014 or after it ?
Martin

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.

Premiere Pro CC 2014 on Mac - MP4's Green won't import

Hello!
I'm trying to import MP4's that I've recorded but when I attempt to import them they are just showing as solid green screens. I've tried quitting out of all Adobe Products, signing out and signing back into the products, and still not having any success.
Any help would be greatly appreciated!
Bryan

When i attempt to import XDCAM EX clips or MP4 files into Adobe Premiere Pro CS3, received the error message "Unsupported format or damaged file."
For MP4 files that give this error message, rename the file extension from MP4 to MPG or M4V. This will invoke an alternate import module that will correctly handle the file

Updated to Premiere Pro CC 2014 - keeps freezing and crashing

Everything was fine and dandy until I updated to the latest version last week. Now every 10 minutes, or sometimes randomly, my timeline will freeze on a frame and I'll have to restart the program. Other times, it just crashes and gives me the "quit unexpectedly" message.
What's going on and how do I fix? I'm on a Macbook Pro Retina 13" late 2013, 2.8GHz Intel Core i7, 16GB memory, Intel Iris graphics, OSX10.9.4.

I am having the same issue.
Adobe Premiere Pro CC Crash on Splash Screen

Premiere Pro CC 2014 running slow and problematic...

We have Adobe for Teams on 3 computers, all are:
HPZ820, Dual Proc with Intel(R) Xeon(R) CPU E5-2650 @ 2.00GHz, 32 GB RAM, Dual Video Cards Quadro 6000 4GB, Windows 7 64 bit with all the latest patches. All hardware is up to date (especially the Video Cards).
Everything worked on the first release of 2014 but a few weeks ago there was an "update" to Premiere. Since this update, projects work for a short period. When you start a new project and add footage, you can scrub the footage and play the footage with no issue. But the more assets you add, simple Titles, Shapes in the background etc. the slower Premiere Responds during playback. I have even set my playback resolution to 1/4. These issues are occurring on all 3 computers on our team and now we are way behind on projects. I opened an new project and imported in H264 footage from our Panasonic Camera. It played fine on the timeline. Then I added a title bar across all the footage. It choked in a few places but did play through. Then I added our standard logo that goes into all our videos. Again, it ran even slower in the monitor, eventually freezing on a frame while the audio would continue playing. At that point you couldn't even scrub to any part of the timeline and have anything show up on the program monitor. It was the image of the last thing it froze on. At one point the monitor showed what was on my desktop. I have even tested starting a new project, adding assets of simple AVI files then tried with WMV files, one by one but no matter what, I get the same results on all three computers. The weirdest part is I opened up an old project we did last month. It played once all the way through, the second time I played through, it froze on the first frame but the audio continued to play through. How can we roll back the update?

Hi,
Thank you for proving us with the detailed description.
Do you have any third party devise connected for playback like Matrox or AJA?
are the Graphic Drivers up to date for Nvidia?
If yes then can you perform a clean uninstall of all the drivers of Nvidia drivers and then install it again.
Are you facing the same issue on Software Only Mode?
Thank You
Arjun

I can't see the group ripper in premiere pro after 2014.1 update, and 2014.2 did not fix.

Please someone help me fix this I am literally going crazy as I have to edit in my notebook and am constantly hooking it up to different monitors, which calls for a different workspace most of the time. Thanks in advance.
To be clear I can not see the group ripper and therefore have to reset my workspace every time I want to redock an undocked panel group.

Click on the name and drag.

Audio glitch when seeking in Premiere Pro CC 2014.1 (Mac)

Don't have enough data yet for a full report but wanted to flag this to see if others are experiencing something similar.
Here's my process:
1. I have a couple tracks of audio. At some points in the timeline, there is no audio at all (e.g. after the end of my timeline).
2. Using "End" or "Down", I navigate to a cut that has silence after it (no audio clips)
3. I then use "Left" to navigate 1 frame back in time, to where there *is* an audio clip.
4. My headphones give me a staticky snap, and I think the glitch registers on the audio meters as a peak
Notes:
- The audio clip is not loud, and doesn't peak when playing normally
- Once it happens once on a particular cut, some kind of caching seems to happen so that the glitch doesn't repeat itself if I try immediately after.
I'll update this as I encounter more data.

This sounds to me like it could be a graphics related problem are you on the latest driver. Something else you could try, start a new project and import the one from the PC into that rather than directly opening it in the MAC

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.

Premiere Pro CC 2014 Crashing and Bogging Down on Documentary Film Project

We have been working in Premiere on this documentary film for months.
As we reach completion it is beginning to really bog down and crash a lot.
Equipment is
iMac 27 inch 3.5 GHz Intel Core i7 Late 2013 Model
Apple Cinema HD Display
32 GB 1600 Mhz DDR3 RAM
NVIDIA GeForce GTX 780M 4096 MB Graphics Card
1TB internal SSD Drive
We are running Premiere Pro CC 2014.0.1 and have remained there because we don't want to upgrade the software in the middle of the project.
The media is all on the external drive. It's a USB 3.0 connection. There is quite a lot of footage that we are working with.
We do have some After Effects comps that are linked in the project and we have exported the ones that are complete as QuickTimes to try to stop that from bogging us down.
Any advice on how we can manage this crashing and freezing problem would be much appreciated.
We don't have the cash to upgrade the computer and it has been working pretty well for us so far.
Here are things we have done:
Made a smaller timeline because we were working on one that was the entire movie.
Turned off the secondary monitor and unplugged it.
We are looking at moving the render cache off the external drive to a thunderbolt drive, but I'm concerned that this may take a long time.
Any recommendations would be greatly appreciated.

Splitting up the read/write items is rather a key to getting smoother operation out of PrPro. Either that or putting things on a large RAID-0/5, this sort of thing is covered over on the
Tweaker's Page ...
http://ppbm7.com/index.php/tweakers-page
And I highly recommend you take a look. Their info isn't just "we think ... " ... but the results of many many carefully crafted test sequences run on many machines with all sorts of hardware bits & pieces. You can also register, download the PBM test and run it on your own machine. It takes only a little while to do so, and with the logger app that's included and posting the results back to them, you can get a very good breakdown on where your machine is doing ok ... and where any choke points are occurring.
I think this would be good for you right now ... you need to get stuff done, not guess & try things.
Neil

Exporting from Premiere Pro CC 2014

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

Hi Maruf,
Maruf Noyoft wrote:
Kevin,
I reset as you suggested and it took care of it.
Great!
Maruf Noyoft wrote:
So, if you don't mind explaining me the cause of the problem that I had? Or
an article about it. It is just for me for getting to know better the program and the system.
Thank you very much and appreciate your help enormously.
Since preference files get touched by the application frequently, there is always the possibility of their corruption. When this happens, you start to see what we call "unexpected behaviors" from Premiere Pro. This problem happens infrequently, but it is a good first troubleshooting step to try on your own. This is the case with most every non-linear editing application I have used over the years (Final Cut Pro, Avid, Media 100, etc.).
Thanks,
Kevin

Premiere Pro CC 2014 on Mac and AMD Firepro 7000

Similar Messages

Maybe you are looking for