Jason Guerra
Forum Replies Created
-
You’re learning a new system. It’s never going to be exactly like your old system. But, most of the differences are just little things that require retaining a few simple habits like keyboard shortcuts. I have been using both Premiere Pro and FCP X for about two years now, and I honestly hate it when a project forces me to go back to FCP 7. It turns out there are a lot of both little and big thins in 7 that aren’t that smooth, you’re just used to them. When you get used to something else, they start to stick out like a sore thumb.
-
You can set it to [modifier key] + return. So, command + return, or option + return. It’s not quite as smooth as FCP 7, but it’s a small change to get used to.
-
Peter,
That’s what I am seeing too. Perviously the artifacts would linger on the screen, and change from frame to frame, making editing impossible until my machine was restarted. Now they are small glitches that I barely catch. It’s still a little annoying, because I have to go back and confirm it’s not a damaged frame by watching it a few times. It pops up once or twice, then goes away without even restarting Premiere, much less the whole computer. Overall it’s an improvement.
One note, I have seen the visual artifacts appear when I am not running a single CUDA powered program. It can happen when all I have running is Finder, and Safari. It’s extremely rare, both before and after the latest updates, but it happens. Also, I have no issues on the same machine in BootCamp (Windows 8.1) running games and other tasks off the GeForce 750m. Neither of those facts are specially Adobe related, but I wanted to mention, on the off chance it does help.
-
Yes, I have seen it with 6.5.45. It’s much less frequent, and typically effects smaller areas of the screen on anything past 10.10.2 and 6.5.36. But 6.5.45 has not resolved the issue.
-
Aaaaaand, spoke too soon. I am seeing the graphical artifacting with 10.10.2 and CUDA 6.5.36. So far, it’s been very small little artifacts on only a portion of the screen or window. Before it would distort the whole viewer window. With that, and the fact that it took two days, not two hours, to reproduce the error, it’s defiantly getting much better, but it’s still an issue.
-
If your playback engine is set to OpenCL then it’s offloading a lot of the rendering to the GPU and even rendering on the fly during playback. Mercury Engine is cool that way. That also means it still wouldn’t necessarily show up as being very processor or RAM intensive. Premiere is very GPU driven. As an experiment you can try changing the playback engine to the “software only” setting. That should force Premiere to relay less on the GPU and more on the other system resources. I would’t recommend keeping it set that way, it uses the GPU for a reason, but it should show you the difference.
Have you tried exporting through Adobe Media Encoder? Media Encoder will usually grab every bit of system resource it can.
-
Are you seeing those numbers while editing, rendering or exporting? Is Premiere running slowing, or it just seems like it’s running light on resources? Are you using Mercy Playback Engine? Can you provide more detail?
If you are simply editing, 2-3% or a nice processor and 1-2GB of RAM is reasonable. Editing supported media isn’t very resource intensive. You should see massive spikes in resource utilization when rendering or exporting. Premiere is designed to take up as much of the available system power as it needs, but only when it actually needs it.
-
It’s a little to early to say it’s 100% fixed, but I have been using the final release of 10.10.2 for the last couple of days and have yet to see the issue. I was on CUDA 6.5.36 and just updated to 6.5.45. Given how random the issue can be, I won’t be satisfied that it’s fully fixed until I can go a full week without seeing it, but two days with out it is still an improvement.
-
That’s what I was worried the answer would be. I like the rectified waveform, and vertical expansion doesn’t really solve my problem. I guess it’s feature request time.
-
I have had this same issue with both a first gen 2011 Retina MacBook Pro, and the 2014 model. The 2011 was a GT 650M and the 2014 is the GT 750M. All that is to say, it doesn’t seem to be hardware specific. It’s actually fairly random when it occurs for me. Though it has seemed to get batter recently, and I am not sure if that is related to the newest CUDA updates, the OS X 10.10.2 public beta build I am running or the fact that I have recently started using my machine with an external monitor. it still occurs once or twice a day, but it used to be every time I open Premiere, without fail.