[Dax Roggio]

6 years later, I would just like to say I would love to see this feature.

[Dax Roggio]

Thanks for your help, Abraham! I’m not sure if I did something differently this time or it was one of the adjustments you made, but I was able to enter my location by typing it directly into the location field of the edit profile page. It appears to have stuck this time.

[Dax Roggio]

Is there anyone we contact about this? I don’t see a technical support contact on the contact page. I’m still getting job notifications for New York with no way to change my location.

[Dax Roggio]

Yes.

[Dax Roggio]

Thanks for your help, but we’re going in circles with this thread. The problem isn’t with the location tracking. The problem we are having is that the one you set in account settings doesn’t stick.

In my case, I have set it for Philadelphia many times, where I am physically located, but it stills says Brooklyn on my profile front page and in the “Your Location” field of the edit profile page.

[Dax Roggio]

Were you ever able to change your location? No matter what I do, the location for my Creative Cow profile is stuck on Brooklyn. I’ve tried to set it to Phildelphia many times from different browsers and on different connections. When I click on “Manage Location,” it properly lists Philadelphia and shows Philly marked on the map, but the location on the main page of my profile refuses to update. Also, my job notifications are still coming in for the New York area, instead of Philadelphia.

[Dax Roggio]

I have been experiencing the same problem with my MacBook Pro (Late 2013, NVIDIA GT 750M, OS X 10.10.1). I have the latest CUDA driver installed through the control panel. After trying many troubleshooting options, I have been unable to find a solution. However, I have discovered some patterns that may shed some light on the source of the problem.

The funky display craziness affects all apps, but it only occurs after I have been running Premiere (CC 2014.1) or while Premiere is running.

More specifically, the problem only occurs if I have been working on a project that has Renderer set to CUDA (Project Settings > General > Video Rendering and Playback).

If I use OpenCL, the problem never starts.

So one solution for me personally would be to stick with OpenCL, which used to work just fine. However, OpenCL rendering in Premiere has stopped working properly for me for clips that have motion stabilization applied. Rendered clips come out with big black blocks. This is true for preview files within Premiere or when exporting through AME with OpenCL enabled. I don’t know if that issue is related to the CUDA problem or not. It did seem to start around the time I upgraded to Yosemite.

So the solution to original problem was to switch to CUDA, but that has led me to the problem described in this thread.

In summary, the issue is clearly related to CUDA, and it seems that the problem began for most people after upgrading to Yosemite. Premiere is clearly a culprit, although it’s the only app I run that actually uses CUDA. So it’s difficult to say whether it’s a Premiere problem or CUDA in general.

Turning Automatic graphics switching on or off doesn’t seem to have any bearing on the problem.

Lastly, I only installed the CUDA driver in the first place to run DaVinci Resolve, which won’t launch without it, even though it can use OpenCL. I tried uninstalling CUDA, but the OpenCL rendering issue remained. So I had to re-install it.

At this point, I’m hoping to see an update to either the CUDA driver, OS X, or Premiere Pro that addresses the issue. It would be nice to know if any of them were working on a solution.

[Dax Roggio]

I found your post because I have the same question. In FCP, you could press T four times to select all tracks backward (to the left). It doesn’t appear that Premiere has that ability, which is unfortunate.

[Dax Roggio]

[John-Michael Seng-Wheeler] “Being able to render as you go does save a bunch of time when last minute revisions pop up.”

That’s very true and well said. I’m surprised the lack of smart rendering and background rendering in Premiere doesn’t get more attention. I switched from FCP7, where I was used to being able to save to QuickTime in the rendered ProRes format much more quickly than I can export to it in Premiere.

The main upgrade I was hoping for in FCP8 was background rendering. Well, FCPX does have background rendering, but I won’t get into all the reasons why I have chosen Premiere over FCPX (for now).

I think a lot of Premiere Pro users don’t see background rendering as a must-have feature precisely because they are not used to utilizing smart rendering as FCP7 users are. Therefore, the idea of rendering as you go doesn’t make much sense in their view if you have a really fast system that can play back any combination of codecs and effects without rendering. But that doesn’t take into account other advantages.

Also, the “Use Preview Files” option causes a lot of confusion, because it does use smart rendering in a few rare circumstances (DV, some forms of XDCAM), but generally, it still re-encodes with a generational loss and marginal speed increases.

I go into much greater detail in my recent blog post: Why Adobe Premiere Pro needs background rendering

But to summarize the benefits of smart rendering as well as background rendering:

— Faster exports in many circumstances
— What you said: “Being able to render as you go does save a bunch of time when last minute revisions pop up.” And I mean, a BUNCH of time.
— On my iMac, I still need to render just to play clips that have effects applied to them. Waiting for clips to render to be able to continue working should be a thing of the past.
— Higher quality previews: I like to render to ProRes for higher quality full-screen previews, but it seems like a waste of time and hard drive space if the render files aren’t going to save me time in the export process.