Warp Stabilizer bug on Mac OpenCL
I've seen other people discussing this problem in some forums but didn't find it addressed here. After updating to Premiere Pro 2018 on a 2011 iMac (El Capitan) with OpenCL GPU acceleration enabled, Warp Stabilizer now produces a terrible ripple effect across the image, like underwater or heat wave distortion. The problem is fixed when GPU acceleration is turned off, but then playback and render speeds are miserably slow. I've been working with warp stabilizer since it was released and have used it on hundreds of projects, but I've never experienced this problem until updating to Premiere 2018. So I know that this is a software issue and not user error.
Same issue but on cuda and mercury engine rendering.
One moment stabiliser works fine, next one it breaks and stutters the same way as described here, worse still - on the same previously stabilised footage, without any change or action taken, just suddenly changed smooth result to stutter.
I solved it by... resetting workspace view to default. Someone else here solved by... changing the language.What has that got to do with footage stabiliser is beyond me.
Typical adobe, coding of the highest caliber.
Robbie Oberholzer commented
Sami Sänpäkkilä commented
Please fix this!
Martijn Koevoets commented
Same issue with my iMac (27-inch, Mid 2011) with AMD Radeon HD 6970M 2048MB, using Rolling Shutter Repair (set to pixel motion) helps as a workaround, but it slows down both my workflow and exporting videos.
James Weaver commented
Yeah same with me! 2010 Mac pro, ATI Radeon HD 5770 1024 MB. Premiere 2017 is fine. Premiere 2018 creates weird ripples. Still hasn't been fixed!
Same issue here. Mid-2011 AMD Radeon HD6970 1024 MB. Just terrible!
Chris Brooke commented
Have the same issue on mid2012 iMac running OS X Sierra with CC18. Warp now creates a ripple like effect. Rolled back to CC17 to complete the project with no issues using the same footage so definitely a problem specifically with the 2018 release. Previous CC18 updates do not seem to have addressed this.
Same problem here. This is a bit of a show-stopper for me on a project - and it seems to occur whether I have acceleration on or not. This is on a late 2013 iMac with a NVIDIA GeForce GT 750M 1024 MB, running High Sierra