As you say, this is a workaround, and a workaround I have been using for many years. It's a simple easy fix for Adobe to have the Sequences of the Timeline LOCKED in, so this never happens. It's utterly ridiculous. I am sick of putting all of the Sequences back on the Timeline, and or having to rearrange the Sequences in the Timeline every time I open up the Project again. Adobe needs to fix this problem right away!!!! ... View more

It's quite ridiculous. Whoever works on improving Premiere Pro, overlooks all kinds of things, and issues that could be easily fixed. There should be a way to LOCK the Sequences so that this never happens. It happens all of the time, and the only work around I know, is to put all of the Sequences into one bin, and when this happens, (which is all of the time) you have to click each sequence and then put them in order on the timeline. This is an easy fix for Adobe, and it should be done immediatlly. This is totally ludicrous, and it has been doing this for many years, when you reopen your Project. Either all of the Sequences are out of order, with a few missing, or all of the Sequences are missing with the exception of the last Sequence you were working on.  ... View more

What we need is ACES, that's what we need!!!!! ... View more

What's hilarious is Adobe implements ACES in After Effects, but doesn't implement ACES in Premiere Pro. WHAT A JOKE!!!!!!!! ... View more

I don't care how well Premiere Pro did at the Tool Farm Awards. The program is buggy. Plain and Simple. There is always something wrong with every update. That's what I am saying. That's the point. Anybody who has ever used Premiere Pro knows there is always one issue or another with the Program. Anyway, I have nothing more to say to you. Go away!!! ... View more

What part of what I wrote do you not understand??? I have used various kinds of Codecs!!! I have been using Premiere Pro for about 15 years. I know the Program inside out, and I have used every Codec under the sun. The flickering is to do with Premiere Pro's newest update. I went back to the edition before, and there is no flickering!!! It only flickers on certain shots in the newest update. Anyway. You are no help whatsoever, and don't seem to have a clue!!! Adobe has had flickering in the past, and with a new update, they will fix it. But what the rocket scientists at Adobe DON'T DO, is check the program inside and out, to see if any problems from past editions, are occuring in the newest release. Also, on your codec topic... Whether the codec is intermediate or not, if it is a codec Premiere Pro handles, there should never be any issues. Also, the last of my problems, is codec issues. I rarely have ever had any codec issues with rendering, or anything else!!! Have there been issues in the past with certain codecs??? (years ago) YES, but I am talking IN GENERAL... In General Premiere Pro is a buggy piece of garbage. If it is not one issue it is another, and just about every Premiere Pro user who has used Premiere Pro for any length of time, KNOWS Premiere Pro can be buggy. If it is not one issue it is another. It only takes a Google Search, or any search in these Forums, or anywhere else, to see the amounts of issues, bugs and problems, Premiere Pro has had over the years!!! There is not one Edition, I can ever remember that did not have one issue or another happening. I'm not sure what World you are living in, but in my World, and the World of millions of other Adobe Premiere Pro users, the program is BUGGY... It's a KNOWN FACT!!!! I have nothing else to say to you!!! ... View more

I have used every codec under the sun. It has nothing to do with what codecs are being used. The bottom line is... adobe is a buggy piece of garbage, and needs to be rebuilt from the ground up. What you are saying is nonsense. Premiere Pro has always had problems. If it's not one thing, it's another. If it's not one workaround, it's another. I have been using \Premiere Pro for many years. I know what has to be done. A Rebuild from scratch. This is why millions around the World are switching to Davinci Resolve. I don't like Davinci Resolve for a few reasons, and so I have been sticking with Premiere Pro... It has nothing to do with the codecs being used, although Premiere pro has had issues with that kind of thig in the past... I am talking in General... There is always one problem or another with Premiere Pro, and \it doesn't matter how powerful your workstation is, etc, etc. For instance in the newest update,, there is flickering with some footage. This problem was fixed in the past, and Adobe knows about this, yet, thay don't even check to make sure that problem will not happen again, with the new update... Believe me, I know all about Premiere Pro. I am an expert with using workarounds, for every problem that arises!!!! ... View more

Specific problem, ahahhhahaha... The problem is Premiere Pro needs to be built again from the ground up. It doesn't matter what update there is, etc, etc. There is always something buggy. Always a work around for certain problems... Always having to downgrade, until something is properly fixed, etc, etc. It's totally sickening!!!! I have been slowly moving to Resolve. I just wish Adobe would build Premiere Pro from the ground up, instead of stacking and stacking new builds on top of a program that has been buggy since day one!!!! ... View more

I downgraded and it is working fine now. The problem is OVERALL... I as well as many Premiere Pro users are sick and tired of downgrading, until Adobe does a new update to fix a problem. The glitching is a KNOWN problem that happens every now and then with certain updates. Adobe knows this, and it should be something that is checked before they unleash any update on the public. IN GENERAL I am just getting sick and tired of Adobe, and always looking up ways to fix problems, and come up with workarounds, etc, etc... Premiere Pro needs to be built again from the ground up. That's the heart of the problem, and the reason many people are jumping ship, and moving to Davinci Resolve. There are a few things I don't like about Resolve, such as not being able to save a project to various drives as I go. Another thing I don't like is the exporting options, (rendering) and a couple of other things, but I am slowly moving over to Resolve, and have been using Resolve more often these days for various things. I just wish Adobe would build Premiere Pro from the ground up. Adobe continues to stack builds upon builds on a program that is buggy to begin with.  ... View more

Instead of Adobe Users keeping an eye on beta, and always f*cking around with this bullsh*t, why doesn't adobe just get things right the first time??? Adobe knows there has been problems in the past with glitching, so anytime a new update happens, this SAME EXACT ISSUE should be thouroughly checked, along with any other problems Adobe has had in the past. Once a problem is fixed with a new update, the same exact problem, should be put on a list of problems for the Adobe Team to check with all future updates!!! No wonder so many people are switching to Davinci Resolve. I'm not too far behind everyone who has been switching, if Adobe doesn't smarten up!!! Premiere Pro should be built from the ground up. This is the huge problem in general with Premiere Pro... Instead of just building on the garbage as it is now, it should be built again from the ground up. I like using Premiere Pro, but I would be lying if I said I was not getting sick of Adobe, and the constant problems with Premiere Pro, and always looking for workarounds and fixes. It is truly f*cking Sickening!!!! ... View more

Desktop. I got it working, by Disabling the Computers Internal Display Driver, by going to Device Drivers. i am not asking for a list. I am asking Adobe, to make it so that it recognizes all Cuda Video cards. I had to make a Cuda recognized text, and put it in the Premiere Folder, and it still would not work, so then I found out about turning off the Display driver that the Computer comes with. GTX 780. The Video Card has always worked fine, but I have had to add it to the Cuda Supported text many times, and now the Cuda Supported text doesn't even exist, so you have to make that text, and include your Video Card. I am saying, adobe should make it where Premiere Pro Recognizes any Video Card that has Cuda, so that thousands of people, do not have to find work around for Premiere Pro to recognize the Card. i could care a less about seeing a list of Tested Cards. All you have to do is a search on the net, and you will see that this is a problem, and people have to do workarounds to get Premiere Pro to Recognize the Card, because it is not apart of the "Tested/Cerified List" I am also peeved off because in the newest Update there is no Adaptive Noise Reduction Plugin, which I had used on various Sound Clips, before the Update. AND NO I AM NOT DIALING BACK TO AN OLDER VERSION OF Premiere Pro, so that I will get the Adaptaive Noise Reduction Plugin again. if Adobe is going to remove a Plugin, they should make the Plugin available to Download somehow, so that this nonsense doesn't happen. I am moving over to Davinci Resolve Studio soon anyway. I am sick of the bugs, and the nonsense with Adobe. ... View more

An alternative, and then you show us a link to some inferior garbage??? First of all, Adobe should have never stop including Encore with all of the upgrades. A project can be Burned onto a Bluray or DVD in one step. there is no Exporting of the media to be rendered, and then brought back into some other burner ware, etc... Anyway, sometime the people at Adobe make some really dumb decisions, and this is one of those decisions. yes, there is still a workaround way to hunt it down and get Encore, but what a joke!!! Bring back Encore you knobs at Adboe!!!!! ... View more

ANOTHER WORK AROUND. I just ran into this same exact problem and this is RIDICULOUS. Adobe had a similar problem before, but at least the project would open with 5.5. This is what you have to do, and from what I have read not even the Adobe people here seem to know what to say. (From what I saw so far) This is the best work around that I know. As soon as you slow down any footage, or use the Warp Stabilizer, etc, you have to render the footage right away by Exporting the Media, and after it is rendered, bring it back into the Project as a new clip. In days gone past, if you trimmed a project and/or copied all of the file of a project, anything that had the speed changed, or reversed, or when using certain plugins, effects, etc, the footage would not make it into the trimmed, and/or copied project properly, but the project would always open and work, unless you Trimmed the Project, and/or copies all of the files. This was the only time that it was a problem, and I learned the work around at that time, and that was to export the clip right away, and import it back in after it was rendered. (using a Lossless codec, such as Lagareth, and using the best settings) The technicians at Adobe should be concentrating on getting this problem fixed right away. This is an OUTRAGE!!! Because of my past experience with Premiere Pro 5.5, I do know that another work around is making a new project and importing the corrupt project in sequence by sequence. I have seen that solution as a work around,but what is shocking is the Adobe people don't seem to have a clue as to what is going on. The bottom line is that when you slow or speed any clip, and/or do other things to various clips, use warp stabilizer, etc, it will screw up the program. That is the bottom line, and this problem needs to be fixed right away!!!!! ... View more