I get the error with the following media files: 1. Long GOP 4K h264 files (Sony A7S) 2. Long GOP 1080p 50fps h264 files (Sony A7S)   As soon as I time ramp or speed change a clip, it will randomly crash on play (sometimes not on first try) As a solution, I make prores 422 LT proxies to bypass the issue. With 2019 release which I currently work, I get no issue with speed on the same clips.   Working on a typical 1920x1080 25fps sequence (Pro Res 422 Previews) Mercury Engine CUDA playback engine, with high quality playback off   I'm on Windows 10 Pro 1909 with the latest drivers. CPU: i9-7960X 16 core GPU: Nvidia GTX 1080 Ti 11GB RAM: 64GB DISK: Promise R6 (~600MB r/w) / CACHE: M.2 SSD (2.000+MB r/w)   ... View more

I feel you, I was tired being a "beta tester" as well. I took a decision last year, to be 1 major release behind, and haven't regreted it since. Seems to be the perfect balance for pro work. 🙂 ... View more

With respect, Not every problem is solved by removing settings. This used to be the case once, but nowdays the chance of settings becoming corrupted is less than 5% for a typical. user. We have to stop suggesting people to so. Sometimes we just have to accept that the latest version is only for testing, and not suitable for pro work.   This error is by now a known issue of 2020 release, causing it unusable until a proper fix is released.   ... View more

Same issue here. Forum seems to be full of these errors. Seems that Adobe will have to handle it ASAP. ... View more

I'm sorry to say that this fix doesn't work on Windows either. As soon as you speed up a clip and try to play it, premiere will freeze and will not terminate unless killing it from the task manager. Even if it doesn't crash, which is really 50% chance, it will only play a frame or two which is frustrating. It is 100% a bug, as this worked perfectly well on 2019 release.   ... View more

I just noticed on a fresh project that it is not related to master clip effects at all. All you have to do to reproduce it is have a clip with proxy on a timeline and then change the framerate or the size of the sequence while having the proxies toggled on. ... View more

I haven't tried that, and to be honest I don't want the proxies to be different than original master. It will be a nightmare later on. There is some kind of caching happening, that by toggling the proxies off and on goes away. So I could live with that. ... View more

Ann, I understand you want to help but not every problem is a preferences problem. We have to accept at some point that Premiere is full of Bugs. We are all tired of trying to debug and delete our preferences once every now and then. Setting up our preferences again is a time consuming process, which almost every-time has no effect on solving our issues. Neil, There are 2 or 3 posts with video, if you search for better terms such us lumetri color shift, play/pause, etc, showing why you should not use Lumetri for important jobs. Sure, I've used Lumetri a TON myself for quick projects that I don't care about the color too much. I would NEVER color-correct or grade a commercial or an important job with Lumetri however, knowing It's algorithms are faulty. Several adjustments (exposure, saturation, ect.) produce weird results compared with PRO tools such us DaVinci Resolve. I don't know who you talked to at NAB but that is something almost every PRO editor know. ... View more

It shows only the obsolete ones. DeReverb has no obsolete anyway. ... View more

I'm not talking about the old obsolete effects. I'm talking about the new Adobe Sensei effects that were introduced along with the Essential Sound panel in v11.0 ... View more

It is a known behavior that has now been acknowledged officially by Adobe. The User-Voice is full with such reports. It makes Lumetri completely useless. Right now the only option is to use good old RGB curves and/or fast color corrector. Also there are several bugs regarding LUTs, where you see a color shift while playing/pausing. Alternatively, if you have time, have a look at DaVinci Resolve. It seems Premiere is really far behind in color science from competition. ... View more

DeReverb is also missing after updating. I tried to reset plugin cache but It did not re-appear. Neither uninstall-reinstall or reseting plugin cache fixes the problem. Waiting for another hotfix. Way to go Adobe! ... View more

There are 2 reasons you might get blurry titles. Assuming you work on Full Playback Resolution and NOT on 1/2 or lower. 1. You are working on low resolution timeline. Titles are created on timeline resolution. If it looks blurry (not sharped) that means you are working on low res timeline. 2. You are working on the latest version of Premiere with Essential Graphics From my understanding, Premiere only applies anti-aliasing on graphics if High Quality Playback is enabled. That is the only way to see the final result (like on exported video). You need a beast machine however to maintain smooth playback. Also, on pause you can see anti-aliased version again. ... View more

It's Premiere Pro CC 2014 ... View more

I too confirm that the bug has not been fixed in 13.0.2. ... View more

Sure, but many times you need stroke for pre-rendered graphics, or for artistic look of certain layers. I've used it a million times to make slideshows with photos to make them look like polaroid photos. ... View more

Make sure you are not using High Quality Playback under both Source Monitor Settings (wrench tool) and Program Settings. It should not struggle on your machine. If it does, you are affected by a known 13.0.1 bug where it lags for no reason while playing certain codecs, even i-frame ones like cineform. I've made a relevant thread for that. ... View more

Alternative, if you mean stroke (border) for text or graphics, there is no such effect in premiere. A quick solution for this that I always use is to apply a radial-shadow with the following parameters. The projection distance is the stroke width. ... View more

I wouldn't want to be in your position. It really sucks, loosing your work. Is it possible that somehow you saved the project by mistake elsewhere? It's very suspicious that you did not find any Auto-Save folders in your project path. Also it's impossible to close premiere without getting a prompt to save your work. The Premiere 2017.1 bug you are referring to, has nothing to do with project saving. It was an ugly case where you might loose your media files if you saved them in the same folder you stored your cache while having cache auto-cleanup selected. I believe Premiere 13.0.1 requires at least High Sierra 10.13, so I guess this might be the reason. I will agree that at the time Premiere 13.0.1 is not yet stable and should be avoided anyway. ... View more

Any news from Adobe, when will this be fixed? Right now 13.x version is completely useless even for non-production. I've tried on multiple computers and I get the same behavior. I can't believe this passed the QA. ... View more

Has anyone figured out what's wrong with cineform playback? The problem still exists with 13.0.1. Several frame drops on rendered timeline using cineform 10bit as preview file format. The timeline is HD with High Quality playback set to off. So there shouldn't be any drop frames at all. The disk is high performance >600MBps read speed. ... View more

I tried to rollback the drivers with no results. Same problem. I've started a new discussion here. ... View more

I tried to rollback the drivers with no results. Same problem. I've started a new discussion here. ... View more

Yes, indeed, AME does export correct. So it somehow affects Premiere only. I will try tomorrow to rollback nvidia drivers to the first acceptable version for 13.0.x ... View more

Is it somehow similar to this? Premiere Pro CC 13.0.1 corrupt color problem. This forum seems to have many threads with similar problems. I'm also experiencing this by the way. ... View more