Benjamin Reichman
Forum Replies Created
-
OK, scratch that. After repeating the steps a second time, it worked. Not sure why it didn’t the first time. But it’s working now — thanks, Lisa!
-
I’m having the same problem, but clearing my renders and cleaning my Media Database Cache (a tip I saw elsewhere) aren’t fixing it.
My workaround this afternoon is to tie up Premiere by choosing “Export” instead of “Queue,” and that works. But I still obviously need to solve this. Any other suggestions? Thanks!
-
Brian,
What laptop do you have? I ask because the Intel Iris Pro GPU, on the Retina MacBook Pro (among others) isn’t truly properly supported by Adobe yet. They offered support a couple of releases ago, but it’s still quite buggy (Warp Stabilizer doesn’t work, for example, and crashes can occur). If you also have Iris Pro, that would be another example of bugginess with this GPU. Hopefully Adobe can fix this soon. In the meantime, you–like me–will be stuck in software-only mode.
-
Sarah,
I have the same laptop and I’m not seeing this issue. What version of Mavericks are you on? OS X 10.9.4 has some fixes that are important for Premiere, so I’d recommend updating to that if you’re not already on 10.9.4.
Ben
-
Yes, the search function before CC 2014 was so slow as to be utterly unusable. (It would take up to 60 seconds–literally–after I typed a short word like “house” or “Sierra Leone” for the letters to simply appear in the box, and for the search to complete would take even longer sometimes.)
But now search actually works! One of my favorite fixes in CC 2014.
-
Was CC 2104 set to use the GPU while CC was set to use software-only? This is just a guess, but that might account for the difference.
-
Thanks, Abraham! I guess the Speedgrade forum isn’t the most popular if no one noticed this before. 😉
-
What version (CC or CC 2014) do you have? What are your computer’s specs? What kind of footage are you using? When did the problem start? What kind of hard drive(s) is the footage on and how much free space do they have?
If you answer these questions, we might be able to help.
-
I tried it this morning and it seems to work. So far, so good!
-
Steve, this comment is VERY helpful. Thank you! Exactly what I was afraid might happen with my dynamically linked AE comps. So I suppose the best workflow (when I eventually do take the plunge) is to open and resave the AE project with the same name (obviously keeping a backup of the original file in another folder), then open the Premiere project? That would avoid these issues, right?