schmollywood
Participant
schmollywood
Participant
Activity
‎May 19, 2019
05:03 AM
Hi everyone, Even though many of us are all used to the instability of Premiere would eventually stay with Adobe since other options werent really an option. Me too, for many years now. I work as a professional film maker mostly for tv networks since more than 20 years. Working with Premiere on my latest documentary has caused so many issues that I decided to share my experiences with you. Im running the latest versions of Premiere and Media Encoder as of today May 19th 2019 on my iMac Retina 5K 2017 4,2Ghz 40 GB Ram , Radeon Pro 580 8GB. Latest Mac OS Mojave 10.14.4 During editing Premiere would crash more often as Ive never seen before and in the worst kind of ways. I work with mixed footage from my Red-W , h.264 from a Sony, some Jpegs ...nothing I havent done before many times. Some Lumetri color correction was applied here and the, but no LUTs and I run exactly O third party plug-ins inside Premiere and Medie Encoder. Also, I run no other software during editing, no virus scanner, nothing. When crashing Premiere would suddenly give me the spinning beach ball, freeze and THEN crash the whole Mac. Trying to open other apps after the crash or even shutting off the iMac becomes impossible since the Finder also crashes. It basically feels like a giant memory leak issue. So my only option is shutting down the Mac by pressing the power button for several seconds. Now after relaunching Premiere it would show the splash sceen fine, but when opening the project file Premiere show nothing but white windows and crashes again. Holding the option shift button when relaunching Premiere would fix this problem and my project file would open fine after that, but only until the next random crash. Ive also tried to get help from Adobe. Their help agent told me some obvious maintenance fixes like deleting the media cache and preview files. It seemed to help for a while but shortly after that, the same crashes happened again. Somehow I managed to finish the edit. This is when things became even more catastrophic. I then tried to render the project using Media Encoder. The first render (Metal render engine) worked from start to finish, but when watching the result I noticed that the parts with RED footage were corrupted meaning the footage would show strange flashes every few seconds. So I changed the render engine from Metal to OpenCL. Rendering with OpenCL I would not be able to finish rendering the project. Media Encoder would crash EVERY time I tried. To troubleshoot this, Ive once again tried all the usual steps from deleting preview and media cache files, resetting the Preferences for both Premiere and Media Encoder, also I ran maintanance software in order to fix potential issues such as disk permissions. Ive even re-installed Premiere and Media Encoder. NOTHING helped. Of course opening another support ticket with Adobe is always possible, but to be frank I really had enough. Support would only go through the same same trouble shooting options and in the end the issues remain or return soon after. I am convinced that Premiere (at least on the Mac) is completely messed up. To call the latest update a "stabilty update" seems absolutely cynical to me. So what to do now ? Im seriously considering the switch to Resolve. Adobe charges about 50USD every month for my CC subscription and therefore I get a mess that has become totally unreliable for my projects.
... View more
‎Feb 06, 2018
12:52 PM
Also, the advice to swith off Hover Scrub seems to work. Ive used it this way now for a couple of hours without any further spinning ball of death. Since I dont use hover over anyway its a solution for me. I just hope it stays that way...Fingers crossed. One thing that is still quite catastrophic is subtitles. Ive just worked with subs now on a bigger television documentary for the first time and all I can say is the bugs that people reportet on since the new subtitle function has been introduced a while back are still present. The subs just suddenldy disappear both when previewed and when exported. The only solution is to restart Premiere, but even if the subs show up again in preview they might not export anyway. In the end my only real workaround was to try and export the subs by themselves and use the exported file as a layer. For a pro user software I think this is also quite bad...
... View more
‎Feb 06, 2018
01:47 AM
List view is working, but if you are trying to edit a big project its pretty much useless if you cant see a thumbnail of clips you want to find. I hope you will get this sorted asap. Its making my life as an editor hard every day when working on projects
... View more
‎Jan 21, 2018
04:44 PM
3 Upvotes
The crashing at closing the app is another everlasting bug which Im also experiencing with Premiere, not just this current version. I believe it could be related to which panels you have open. I noticed that when the Lumetri panel is open when you close the app the crash is more likeley to happen. Basically Premiere wont close down all the way but gets stuck and can onle be closed by force quitting the app. Ive had remote support sessions with Adobe support agents about this, but the problem was never solved. I experienced it on a current Macbook Pro with 16GB Ram and Im experiencing it on my 2017 iMac 40GB Ram , its doesnt matter which renderer , it happens with both Metal and Open CL , no difference.
... View more
‎Jan 18, 2018
10:24 AM
Actually the keyboard thing was sorted out by myself. Had to reset my preferences. BUT as for the spinning wheel / crash problem when scrolling through the media browser in thumbnail view it seemed to be related to having a second monitor connected. Turns out its NOT the problem. Today the same error happened several times without another monitor connected to the iMac. So unfortunately bad news.
... View more
‎Jan 12, 2018
02:55 PM
Also, some keyboard shortcuts in the current version of Premiere Pro CC Version 12.0.0 (Built 244) are acting up for me. When I make a selection in the timline that I want to delete or ripple delete by using the default Premiere Pro keyboard shortcuts Premiere will delete other stuff in the timeline instead (for example just my audio track or so) so I undo and try the same shortcut again. If Im lucky it will work the second time, but often I need to undo twice before the exact same keyboard shortcut does what its supposed to do. Ive tried using the default CS 6 shortcuts instead, same problem. Ive even tried making my own shortcuts, the same thing happens . Ive connected a different keyboard, a different USB port for my keyboard, Ive even tried a wireless keyboard, the problem is still there. Its very annoying. Any suggestions Kevin ?
... View more
‎Jan 12, 2018
02:39 PM
Some keyboard shortcuts in the current version of Premiere Pro CC Version 12.0.0 (Built 244) are acting up for me. When I make a selection in the timline that I want to delete or ripple delete by using the default Premiere Pro keyboard shortcuts Premiere will delete other stuff in the timeline instead (for example just my audio track or so) so I undo and try the same shortcut again. If Im lucky it will work the second time, but often I need to undo twice before the exact same keyboard shortcut does what its supposed to do. Ive tried using the default CS 6 shortcuts instead, same problem. Ive even tried making my own shortcuts, the same thing happens . Ive connected a different keyboard, a different USB port for my keyboard, Ive even tried a wireless keyboard, the problem is still there. Its very annoying. Also, since the latest version of PP is also struggeling with the "second screen bug" (meaning that connecting certain 2nd monitors will cause spinning wheel of death when browsing thumbnails of footage in the media browser) I was advised by an Adobe support agent to completely de-install and then re-install Creative cloud a few days back (which btw did not change a thing except for taking up a lot of my time) dont waste your time trying that since both problems (the one mentioned above and the second screen problem) still occur. 2017 iMac 4,2GHZ, 40GB Ram Radeon Pro 580 with 8GB High Sirra 10.13.2 Premiere Pro CC 12.0.0 (Built 244)
... View more
‎Jan 09, 2018
06:09 PM
1 Upvote
Im having the same problem since the latest Premiere update. Since then Ive had 3 remote support seasions with Adobe support. Only the third agent found what seems to be the issue and apparently its working with a second monitor. Theres been a similar issue in a recent version of Premiere with an external monitor connected to current USB-C Type Macbook Pros. That issue was apparently fixed. But now its having my older Apple Thunderbolt display connected as a second screen to my 2017 iMac 40GB 4,2Ghz with Radeon Pro 580 8GB GPU . The last Adobe agent I talked to suggested to try and disconnect it. After I did the problem disappeared. Ive submitted a bug report to Adobe. The second / external monitor issues with Premiere are getting ridiculous. Also still going strong and still not fixed is the tool switching delay issue. After running Premiere for a few hours switching tools will sometimes make the spinning wheel come up and it will spin for up to 15 seconds before the tool switch happens. In general I prefer editing with Premiere, but compared to other editing software its pretty slow hence not making full use of the GPU still. I really hope Adobe gets its act together for Mac editors real soon
... View more
‎Jan 04, 2018
02:24 PM
Done !
... View more
‎Jan 04, 2018
01:18 PM
Heres another update. Tonight I did another online remote session with one of your agents and it seems he found what stops this from happening. Sounds good, right , but unfortunatley it isnt. So he checked if I had a second monitor connected which I actually always do. Its my trusted Thunderbolt display.He then asked me to disconnect it and the problem seems to have disappeared. Well, guess what he told me when I asked him why this didnt occur with older versions of Premiere and also does not occur with any other video editing software I use ( FCP and Resolve) He said, and I quote: "this is software. Requirements , features, compatibilty everything changes all the time" . The agent went on to say "Your GPU seems to have trouble with the second monitor so its not a Premiere issue" . Seriously, this is crazy. As I said all other video software works fine. Premiere worked totally fine with this setup for months. Why cant these support agents even admid that its clearly a bug with the latest version ? Wouldnt you agree that is is cruicial for a lot of pro video editors to work with a second monitor connected ? The guy tried to sell it to me as if its a new feature that it doesnt work anymore now ! I know for a fact that theres been a bug in the previous version of Premiere with external monitors connected to a Macbook pro. Since I also run a Macbook pro with an external monitor Ive been through this issue also. Apparently thats been fixed with the latest version of Premiere I was told previously by Adobe support, but now this new issue related to external monitors is happening. System: iMac 2017 Processor : 4,2 Ghz Intel Core i7 40GB Ram High Sierra 10.13.2 GPU Radeon Pro 580 with 8GB Ram
... View more
‎Jan 04, 2018
11:32 AM
.... also, since one Adobe support rep suggested it may be related to the number of files viewed in the Media Browser (which once again has never been a problem before this version) , Ive also tried it with just half a dozen files, the same happens. As I mentioned above no matter if its Red footage or h.264, no matter if the render engine is Metal or OpenCL. Very very annoying. Also, after having two online remote support sessions without any solution and even after doing a completely useless re-intallation of CC apps it seems obvious that the problem is not related to my configuration
... View more
‎Jan 04, 2018
07:15 AM
Latest Mac OS High Sierra 10.13.2 . It happens with new projects also. After the second Adobe online support session I was adviced to do a complete re-intall of all Adobe Cloud apps which I actually did. Unfortunaltely no difference. So to summarize the problem occurs with Metal and OpenCL, it happens with all kinds of video files (Ive tried h.264 and R3D Red footage) . It happens after I re-intalled all Adobe cloud apps. It happens without ANY 3rd party plug-ins installed. It never happened before this current version of Premiere so I can only assume this is a bug. Please let me know what you think. Its very very hard to work like this....
... View more
‎Dec 28, 2017
02:41 PM
After updating Premiere Pro CC 2018 to version 12.0.0 on my iMac 2017 (40GB Ram) I am experiencing a problem with the Media Browser. Scrolling through Media Browser Thumbnails will randomly put Premiere into endless spinning wheel hang and from there I can only force quit. It happens very every few minutes of editing, but never ever happened before this version of Premiere no matter how large the project. The project it occured with has about 150 short clips. The footage is h.264 in UHD 4k straight from my Sony Alpha 7SII It does'nt matter if I use a fast external SSD with the footage on it or standard drive. No difference whatsoever. Today I had an Adobe support agent reset all permissions etc via remote online session. For a short moment the problem seemed to have disappeared, but it started happening again shortly after. He told me that the CPU usage was peaking when scrolling through the thumbnail files. It makes no difference if I use OPEN CL or METAL, the problem occurs on both. I assume this is another kind of memory leak bug. Ive filed a bug report
... View more
‎Oct 12, 2017
12:13 PM
1 Upvote
Still happening on the latest version of Premiere CC on my iMac 2017 even with 64Gb / 8GB of graphic ram !!! ) both with Sierra and now High Sierra and on my Macbook Pro 2017. Both machine have different GPUs , no difference. Its just unbelievable that this still happens Kevin. The only way to stop it from happening for a short while deleting user/lib/common and also deleting user/documents/adobe and also user/library/ preferences/adobe /Premiere Pro Honestly, Im so fed up with Adobes lousy support of Mac GPUs and how slow PP has become compared to FXPx and even Davinci Resolve which is really fast on the Mac and a full featured editor now that outruns PP in terms of speed and is FREE !!!
... View more
‎Sep 28, 2017
06:48 PM
Im experiencing the same on both my 2017 iMac 64 GB of RAM, 8 GB graphics ram And my MacBook 15 inch 2016 is Touch Bar. Latest version of Premiere Pro. Once again a very annoying bug that’s been happening for quite some time now and is simply unacceptable for so called pro Video editing software. Adobes Support for the Mac platform is simply terrible. Working with DaVinci resolve or Final cut pro is so unbelievably fast these days compared to Premiere But I’m actually considering to make the switch if this nonsense of Mac support by Adobe will continue. Get it together Adobe and fix your half assed Mac support please!!!
... View more
‎Jun 11, 2017
01:16 AM
Same problem when switching tools. The beach ball will appear and it will take about 10-15 seconds before the selected tool is available. Very annoying I hope Kevin-Monahan​ is reading this ...
... View more
‎Mar 08, 2017
07:30 AM
That is indeed very strange. Can I somehow send you one of the Red files (about 1GB) so you can try with this ? Its one of the files that flickered after exporting it in any of the codecs you tried. Thank you
... View more
‎Mar 07, 2017
03:16 PM
RameezKhan​ I was talking to your colleague Kevin Monahan in the meantime who asked me to try exporting the RED files without scaling in their original size (in my case 5K) with the Lumetri effect applied and see what happens. As a matter of fact the export of the file without downscaling the 5K to HD (e.g. h.265) works flawless. That means the error only happens if RED files (4k or 5k in my case) only show the error when they are exported in a smaller resolution. I hope this helps to solve the problem. Thank you
... View more
‎Mar 07, 2017
02:57 PM
Hi RameezKhan​, I did clean the media cache and even trashed preferences etc. Nothing worked. As for Adobe support I had 4 sessions. They were all closed by Adobe support after trying out all sort of steps with remote screens etc. The final answer of all of them are: "seems like a GPU driver issue". As I mentioned before I also contacted Apple support who were completely useless. The senior support guy never heard of "Premiere Pro CC" ... So here are the case numbers of the Adobe support sessions: 0188676507 0188678081 0188721457 0188722096
... View more
‎Mar 06, 2017
06:18 AM
@Kevin-Monahan You seemed to be helpful with other issues like this. Could you try to get behind this and check whats going on please ?
... View more
‎Mar 04, 2017
04:29 PM
Hi Taylor, Believe me if I say it has all worked before. Ive done this and other Lumetri effects a thousand times on red footage (4k 5k, 6k...) no problem at all even on my older MacBook Pro with Nvidia card 750GT. It just worked. Suddenly it stopped working. Unfortunately I dont know if it was the latest Sierra update or the latest Premiere update after which this started happening. And yes, other vignette effects done with third party plug-ins work fine, also any color correction third party plugs work fine. Other footage than Red footage works too, even with Lumetri, but Red footage does not. As you can see in the examples I postet on Vimeo it flickers heavily. This is just a very visible example. Its also other Lumetri effects that do this but more subtle. Of course Im being told by Adobe support its the GPU driver. Then again Apple will claim its a software issue with Adobe. So basically its the old "blame the other party" game Im stuck in.
... View more
‎Mar 04, 2017
02:36 PM
Unfortunately the GPU issues with Premiere never really stop. OpenCL and Metal renderer will cause a problem with Premiere Pro CC 2017 (Latest version) on Mac Sierra (10.12.3) when using Red footage (.R3D files). If you apply effects from their Lumetri color panel the exported file will flicker strangely. Its most visible when using the vignette effect. Heres an example with OpenCL: A005 C001 03022K 001 1 on Vimeo And this is the render with Metal: A005 C001 03022K 001 on Vimeo Its only visible on the rendered files NOT in Premiere preview. Ive testet it on two machines (MacBook Pro Late 2013 and MacBook Pro 2016 with Radeon 460 card) . It happens on both machines when using OpenCL or Metal with Premiere. It doesn't happen when I set the render engine to CUDA (which I can of course only do on the 2013 Macbook with an NVIDIA card) or "Software only" mode. Ive contacted Apple support over this, but they seemed very indifferent. The senior support guy I talked to didn't even know Premiere Pro....Any suggestions ? Thank you
... View more
‎Mar 04, 2017
05:53 AM
Hi Rameez, Unfortunately the GPU issues with Premiere never really stop. OpenCL and Metal renderer will cause a problem with Premiere Pro CC 2017 (Latest version) on Mac Sierra (10.12.3) when using Red footage (.R3D files). If you apply effects from their Lumetri color panel the exported file will flicker strangely. Its most visible when using the vignette effect. Heres an example with OpenCL: A005 C001 03022K 001 1 on Vimeo And this is the render with Metal: A005 C001 03022K 001 on Vimeo Its only visible on the rendered files NOT in Premiere preview. Ive testet it on two machines (MacBook Pro Late 2013 and MacBook Pro 2016 with Radeon 460 card) . It happens on both machines when using OpenCL or Metal with Premiere. It doesn't happen when I set the render engine to CUDA (which I can of course only do on the 2013 Macbook with an NVIDIA card) or "Software only" mode. Ive contacted Apple support over this, but they seemed very indifferent. The senior support guy I talked to didn't even know Premiere Pro....Any suggestions ? Thank you
... View more
‎Mar 02, 2017
02:39 PM
Hi, I'm experiencing a problem with RED footage when applying an effect in Lumetri. The easiest way to recreate this is to apply a vignette onto the Red footage. In the preview window everything looks fine when playing it back. But if I export the footage to any kind of codec (ProRes, MXF, h.264 etc.) the effect on the file that is exported will flicker. Other effects applied by Lumetri will also show a slight flicker, not as bad as a vignette, but still quite visible. Im only seeing this problem with RED footage in any resolution. -OPEN CL on my 15" MacBook Pro 2016 with Touch bar with Radeon 460GPU and on my late 2013 MacBook Pro 15"with Nvidia GPU will have the issue -Software render works fine -CUDA on my late 2013 MacBook Pro 15"with Nvidia GPU also outputs without the issue, but I dont really use CUDA since it has other huge compatibility issues with Premiere So I am wondering if you guys experience the same? It seems to me AMDs OpenCL driver are the cause. BTW Im using the latest version of Premiere Pro 2017.0.2 on the latest version of OS X Sierra 10.12.3.
... View more
‎Feb 16, 2017
04:50 PM
I am having an issue with the latest Premiere 2017 on my MacBook Pro 15" 2016 , latest Mac OS. When I apply a vignette via the Lumetrie color panel to any kind of Red footage the preview looks completely fine, but after I export the footage either in h.264 using the Vimeo HD preset or even when I export QuickTime ProRes full HD format, the vignette on the Red footage will flicker heavily whereas the same vignette on e.g h.264 footage looks completely fine. Only if I render out the Red footage in the same dimensions as the source footage the vignette looks fine. It makes no difference if I use OpenCL or Metal. If I use "Software only" the vignette won't even render out at all ! Ive tried it on my latest MacBook Pro with Radeon 460 gpu and on my 2013 Macbook with Nvidia gpu. It doesn't make a difference, same error ! Does anyone have a clue as to why this might be happening ? Thanks ! Ingo
... View more
‎Jan 19, 2017
02:37 PM
I'm afraid its not. Kevin from Adobe mentioned on the long thread on this issue that this latest update does not yet include the bug fix for this issue: Re: Graphics Issue on my macbook pro 2016 when using premiere
... View more
‎Jan 07, 2017
12:57 PM
P.S even if turns out in the end that Apple caused the error by faulty drivers or whatever its still no way to deal with this issue the way Adobe has since weeks now. Terri you even mentioned that Apple cares more about the consumer customer rather about the pros these days and therefore their driver support has become sloppy. Even this very fact should make Adobe even more cautious and on the watch out for their pro customers by testing for such issues straight away when new hardware comes out.
... View more
‎Jan 07, 2017
12:19 PM
1 Upvote
Terri I understand you are just doing your job here. So nothing personal. As you can probably tell by now Adobe has made a lot of people very angry. Yes its easy to direct the blame elsewhere (eg Apples bad drivers) but with this issue Adobe has made some profound mistakes themselves. First, when new hardware comes out the current software needs to be tested straight away for compatibility. If then a company such as Adobe discovers a bug of this magnitude its their responsibilty to inform us the customers. They didn although it would have not taken more than a few hours to come across this. Instead dozens of reports turned up over a months ago on Mac/ tech sites about this issue. When contacting Adobe customer support on Dec 28th they even claimed they have not heard of the issue yet. Meanwhile this very thread here as well as on other Mac sites filled up with complaints. Now an investigation is apparently going on, only after Adobes customers discovered this and voiced it on this very thread loud and clear. Also, to this day, Adobe still has not made ONE official announcement that these new Macbooks currently are completely incompatible with their video apps. I really wonder how is that even possible ? . So instead basically Adobe lets customers still believe that their software is working throughout the Mac platform when it is actually not. So please dont blame Apple here when its clearly Adobe making all these massive mistakes in how they deal with this. Dont lead more and more customers to believe the new Macbooks are working with Adobes video apps when it is clearly not true. Why does Adobe not make this official? Why do customers need to discover this issue themselves instead of being imformed by Adobe before hurting their professional business? Is that Adobes way to gain trust with theIr CC subscribers ? I dont think so
... View more
‎Jan 07, 2017
11:47 AM
Rather than using caution with postings on this forum thread please use a lot more caution when testing your software next time Adobe This issue could have been long resolved if someone at Adobe actually used enough caution and tested the video apps on the new Macbooks for just a few hours when they were released over a month ago. Instead noone cared until this very thread
... View more
‎Jan 04, 2017
05:11 PM
Not worth filling it in Jimbo They probably ignore our automated customer feedback just as much as what we are writing here and a couple dozen tech sites have been writing too since the end of November . Noone at Adobe cared, thats the sad reality
... View more
AdChoices