Forum Replies Created

  • Gregory David

    August 30, 2017 at 5:45 pm in reply to: CC17 Flickering supers after render

    I have this issue too. It started after the Adobe upgrade in April. My 1080p sequences have gh4 3840 x 2160, psd or png images and PSD generated titles. Both open CL and Metal are corrupting renders, so I edit with open cl for playback speed and then output using software only.

    Having been through the calamitous 3 month period while Adobe and Apple ironed out the bugs on my new MacBook Pro last year, this new “Bug” is not welcome. I am tired of work arounds and instability. Adobe crashes a lot. I am busy getting getting up to speed on FCPX and will not be renewing with Adobe in January. This ends my 5 year “experiment” with Premiere.

  • Gregory David

    December 22, 2015 at 5:38 pm in reply to: Can’t duplicate a sequence

    It’s not random for me. I’m so tired of adobe pulling the rug from under my feet. I don’t want relearn how use my edit and photo apps every couple of months. This is my last year paying for these “features”.

  • Gregory David

    December 5, 2014 at 1:32 pm in reply to: Graphics problem after Yosemite upgrade

    Great that out experience is shortening other editors path to being able to work. I encourage anybody who has had these issues, has removed CUDA from their system and is now problem free, to post their experience. We need this sorted out. I wan’t the speed the CUDA gives me!

  • Gregory David

    November 24, 2014 at 7:59 pm in reply to: Graphics problem after Yosemite upgrade

    These issues have been driving me crazy. Won’t bore with all the crap and just cut to the chase. I removed the CUDA driver: Cuda com.nvidia.cuda.launcher.plist (LaunchDaemons) and com.nvidia.CUDASoftwareUpdate (LaunchAgents) AND.. ISSUES GONE – both dropping of video, which was the worst one and all the graphics garbage. I have just done a successful export using OpenCL. I don’t know whats going on here or what to do to get reasonable performance back on my early 2013 macbook pro 2.7ghz with 16meg ram, but this clearly isolates the problem and gives me a way to work. Good luck to you!

  • Oh my God, Thank you!

  • Gregory David

    November 12, 2014 at 3:57 pm in reply to: Loss of Video in Program Monitor (goes to black)

    I had an idea that maybe the graphics glitches had something to do with scaling the screen for more space (apple preferences)and switched to best for display. Allas, no change.

  • Gregory David

    November 11, 2014 at 6:47 pm in reply to: Graphics problem after Yosemite upgrade

    I have the same issue. Worse, I lose video in the program monitor and often in the source monitor. The only thing that fixes it is to switch from Cuda to software only and back again, or a restart. Of course you loose your renders if you do this.

    I am on a macbook pro early 2013 16gg ram – 11 given to Pr. I have just done a clean install to try to clear it up. The cuda driver is the most recent and privileges are correct.

    I am unfortunately on Yosemite, but I was having very similar issues on the previous OS.

    I think the issue is with the Cuda driver and the way Pr reads from the previews. Needless to say I am not a happy camper.

  • Hi, I bought the 1000HD for a travel kit because it is so small and light. I use a 5D with WA prime on on it and for my purposes it works great but it needs a very light touch for rotational changes and because of it’s relatively low mass I think there is more friction in the gimbal movement, so it’s very sensitive. I also find that to get no rock at all, the swing time is set around 2.7 secs which is pretty slow. Even more sensitive. the 4000 may be overkill for the GH3 though, maybe try out the 2000?

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy