Jason Guerra
Forum Replies Created
-
I would also go with option 2. There shouldn’t be a significant difference in final export with option 1 vs 2, but their will be a huge difference in editing. Option 1 will mean converting the framerate on the fly with Mercury Playback, which will slow down performance. Probably not much, but still. Also, I have noticed a significant difference in the way framerate conversion look in timeline vs final export, so with option 1, if you see a weird artifact from the conversion on your timeline, it won’t necessarily export that way. Option 2 avoid all of that.
If you want to be 100% sure about quality, take a small, 30 second to 1 minute, clip and test it with both options. That way you get to see with your own eyes and will know make sure you are satisfied with the results.
-
The problem is with Nvidia’s CUDA drivers. FCP does not leverage CUDA. FCP 7 does not use any GPU acceleration (one of the many reasons it’s slower), and FCP X uses OpenCL to power its GPU acceleration, so neither version will have this issue.
Premiere Pro can use either OpenCL or CUDA. CUDA is generally faster, but with this bug it’s obviously not the best tool right now. Unfortunately simply choosing OpenCL from PP’s Mercy Playback drop down in project settings does not resolve the issue. Several people, myself included, have restorted to completely removing the CUDA drivers and have found that resolves the issue. Kevin from Adobe posted a list of directories you need to delete in order to completely remove CUDA, earlier in this thread. All of these need to be removed, or a left over piece of the driver may still cause issues.
-
It is my understanding that the warranty extension program for the mid-2012 rMBP is a different issue then the one being discussed here. That issue was actually a manufacturing defect with the NVIDIA chip. It would cause the whole screen to go black when the chip got too hot. It didn’t always lock up, but because your screen was off you couldn’t see anything. It did cause lookups and crashes, but the full black screen was the most common symptom. Because it was a hardware issue, the only fix was to replace the card.
The issue we are discussing is software related. It is linked to the use of the CUDA driver from NVIDIA, especially when used with Premiere Pro. Its most common symptom is visual distortion and breakup of the image. The distortion is often limited to the viewer windows inside Premiere, and changes or goes away with as you continue to play the timeline. While this issue does cause system lookups and crashes, they are infrequent compared to the visual distortion issue. As this is software related, a hardware swap will not resolve it, I know, I tried swapping the hardware multiple times before finding this thred and realizing it was software. There is no available fix for this issue, though many of us have had success with uninstalling CUDA. You have to make sure it’s completely uninstalled, looking up and removing all the library folders, and not just removing the preference pane.
So if you think you have the hardware issue, send it in. If you think it’s the software issue, try uninstalling CUDA and seeing if you get any improvement with your problem.
-
Kevin, it’s entirely possible we have different bugs with that produce very similar visual distortion. I agree that it’s not limited to Yosemite, as I have seen the issue on Mavericks. But, as i said in my previous post, I have seen these visual distortions in Finder Safari, and Mission Control, when no Adobe program, none at all, not even the CC app, are running. So that means, the issue I am dealing with is either an OS bug that Apple hasn’t bothered to fix for multiple version of the system, or a CUDA bug. Based on the fact that I haven’t seen the issue on my machine, after uninstalling CUDA, and the lack of larger panic in the non-pro Mac using community, who don’t use CUDA, I have to conclude, the issue I am having is with that technology.
That doesn’t mean there isn’t an issue in PP that causes the same glitches on a Moutnain Lion based OpenCL system.
-
This started happening to me recently. I am using CC 2014. I never had the problem with my laptops trackpad, but when I started using an external mouse, I started seeing this problem. It only happens occasionally, but it’s annoying.
I have found a work around. If I drag any clip on the timeline to a new track, then back to its original position, I can then move to the cursor away form the timeline window with no issue.
-
I don’t know about end of days, people have been predicting that the entire time I’ve worked in post, even well before FCP-Gate. The vast majority of post shops and freelancers I know still use Macs and have no interest in anything else. So I also think Adobe is selling plenty of CC subscriptions to Mac users, and not just in the TV/film crowd.
As for Adobe ignoring the problem, it is frustrating. I have actually seen versions of this problem with Mavericks, so it’s been close to a year and a half. I will say it’s also a little unfair to lay the blame strictly at Adobe’s feet. NVIDIA, and Apple don’t even acknowledge the problem at all, at least not publicly. And I believe NVIDIA is most to blame, as it’s their drivers that cause the problem. Premiere, AE, run glitch free using OpenCL. CUDA has caused problems for me in Finder and Safari, when nothing else running.
For now I have uninstalled CUDA, I’ll take the OpenCL perfrmance hit over this mess. I keep an eye on this thred, and a few others on Adobe’s forums, to see if a real fix ever gets reported, but in the mean time, no CUDA for me.
-
The thread on the Adobe form is a little hard to flow, but if I understand it correctly 7.0.35 does NOT contain the fix. It is still unreleased. Is that correct? Because 7.0.35 is worse on my machine, and I mean much, much worse.
-
Hey Barnaby,
Not sure where you’re at with this, but I noticed your files where encoded as x264. I looked into it and PP doesn’t x264 support that natively, VLC and WMP does, which is why you’re only seeing the issue in Creative Cloud apps. There is a plug-in for x264, but it’s a bit pricy. So, your idea to re-encode is the cheeper fix.
Info on the plug-in can be found here. https://www.x264pro.com
-
I would call those video blocking artifacts (https://en.wikipedia.org/wiki/Compression_artifact).
The fact that you only see the issue in Premiere and not in VLC or WMP means it could be a problem with Premiere and not with the file. In Premiere are you seeing the issue at exactly the same section in the video? Does glitch look exactly the same each time? Do you see it when you go through frame by frame? If answer to those questions is ‘yes’, and the artifacts appear the exact same one on the exact same frames every time, that points to an issue with the file. If not, It’s probably an issue with Premiere.
Narrowing down the problem to either Premiere or the file is an important first step, because it will help you focus your trouble shooting in the right direction.
-
Ze’ev,
It actually sounds like you are experiencing two different issues. I have created new users, deleted settings, transferred all my work to an entirely new computer, and it didn’t resolve the video artifacts, but I also haven’t really had the slow playback and render issues you’ve described.
The slow playback and renders defiantly seems related to a corrupted setting file, and it seems like setting up a new profile solved that issues for you. So the good news is, it seems you have that one fixed.
The video artifacts is, based on my experience and everything here, a CUDA/OS X issue. This has become much better with the combination of OS X 10.10.2 and CUDA 6.5.45. For me, I can go multiple days without seeing the artifacting now, and a quick restart of my computer makes them go away again for days. But, the bad news is its seems to be entirely in Apple and NVIDIA’s hands to fully fix this issue. Hopefully 10.10.3 and the next CUDA update will finally do that.