When is Adobe going to fix this massive problem?  It forces my staff to keep 2 versions of Premiere on their workstations. One pre-AVI bug, and one post-AVI bug.  This is software that we pay every month for and this critical bug hasn't been fixed in over a year.  Can someone from Adobe please give us an update?  This bug is super easy to recreate! ... View more

Yup, one of the Premiere versions earlier this year totally broke AVI imports.... They can be imported but it takes MINUTES to import one file.  It's completely destroyed our ability to use the new versions of Premiere for our business workflow.  Adobe keeps on breaking things with new versions and this is a deal breaker.  I'll look into the beta version that Kevin mentions to see if this massive bug is fixed in that version. ... View more

Using Audition CC 2020. File->Export->Multitrack Mixdown ALWAYS forces one to reenter mixdown settings... every time. Extremely annoying. ... View more

Stephanie, it's possible to create custom export presets that you can use to export in film friendly framerates. I've attached 3 presets here that you can import and use to export at 16fps and 18fps (with and without sound). ... View more

I can't even get the Project Manager to output a small portion of our film to a consolidated directory with all required assets. This means that I need to give the DP the entire 18TB project, instead of only the media he needs to grade the film. Right now the Project Manager just quits after thinking for a few minutes with an error, asking me to try again. It's disappointing that the engineers actually coded in a message that says I should try again. This shows an awareness of randomness and instability with the code base that is disturbing. Regardless, I did try again. Nothing changed. And yes, flattening all of the consolidated media into one directory (if it did work) is extremely messy on a large project and I second the motion to maintain an original directory tree from the source material. ... View more

Amen! Markers seems like an old feature that hasn't been touched in a decade. There is also a current bug where they all get erased for no apparent reason. Every suggestion here is golden. ... View more

Agree. No one is asking for it to me removed. It certainly comes in handy, even in it's confusing implementation. I'd just like to disable it until some thought and alteration has been made to the interface. It's frustrating that this feature was added with no interface changes. When two large projects are loaded, it's a spaghetti mish-mash. ... View more

Amen. ... View more

It's a miracle!  Thanks combatTVgirl.  The key is changing the preview format for the sequence.  For some reason, having a preview format and resolution manually set to the same format and resolution as the sequence settings, enables Premiere to correctly choose the right export format.  Why does a preview format impact the correct export format?  Shouldn't the sequence resolution and framerate determine what 'Match Sequence Settings' is trying to match?!?!?!   Using the 'Create Sequence from Clip' on an imported 16fps ProRes file is somehow selecting a preview format of DVCPRO HD 1080i50, which in turn completely lobotimizes the export panel into choosing an available DVCPRO resolution (1440x1080) and 25fps when 'matching sequence settings'.     Anyways, thanks combatTVgirl. ... View more

It's very important to read the thread, especially my comments further down, before posting your solution.    Firstly:  Everyone keeps on giving advice on how to create a sequence in Premiere at 18fps.  That is not the problem.  I can easily create a sequence at 18fps by selecting 'Create sequence from clip' where the clip is already 18fps (created by our film scanning software).   Secondly:  CombatTVGirl, your solution to output a Quicktime video from Premiere at 18fps only works in Premiere CC 2019.... it doesn't work in Premiere CC2020... unless something has changed with the latest patch.... although I doubt this as Adobe themselves told me that exporting 18fps in Premiere 2020 wasn't possible unless you have already created a export preset that is hard-wired to 18fps.  CombatTVGirl, can you please confirm that you are performing this solution in an old Premiere version from 2019? ... View more

The problem with CC 2020 is not the ability to create sequences of unusual framerates, it's exporting those sequences at their framerates.  Choosing any Quicktime preset (just like H264 before it) now defaults to a set list of framerates (10, 12, 15, 23.97...etc), even when you choose to match the sequence framerate.  One has to have created a saved preset with the unusual framerate that must be chosen when exporting.  Matching sequence framerate doesn't work like it did in CC2019 (for Quicktime). ... View more

Adobe did give me a workaround by providing a few export presets for 16fps and 18fps.  I can use them in Premiere 2020 to export at those framerates.  Apparently it's possible to create presets with custom frame rates using generated Color Mattes but I didn't get into the details with the Adobe Technician.     Using Adobe After Affects is not an option for me as it would complicate and slow down my pipeline, which I need as fast and simple as possible. ... View more

Update:  Now Premiere 2020 has killed my workaround!  It's no longer possible to render sequences that are 18fps in Quicktime Prores at 18fps..... they are forced to 15fps just like H264.  This destroys my workflow and I need a solution from Adobe.  It's frustrating how many times new releases from Adobe break old features. ... View more

Hi Warren and Meg, Thanks for your input. I have no problems creating a sequence for 16fps and 18fps by using the 'Create Sequence from Clip' option.  My problem is exporting. Meg, you're using Quicktime, which seems to allow these framerates, at least for ProRes.  I'm exporting my ProRes intermediate in H264, which forces the framerate to 15fps.  This is my problem. I'm going to explore and see if I can find a different, more consumer friendly format (rather than ProRes 422+), that can output in 16 and 18fps. ... View more

1) Good, I'll try ProRes 2) Thanks for the resource.... although I'm sure Premiere is much different than when that article was written in 2016. 3) No scaling.  The mp4 files are the same resolution as the sequence and output resolution. 4) No frame rate conversions. 5) No color grades on the adjustment layer.... just the Timecode effect. ... View more

Thanks Kevin.  I will try these suggestions next time.  So I can now export ProRes files on a PC?  Haven't tried that yet. My system specs are: i7 5960X 32gb RAM Nvidia GTX 1070 OS drive: 240gb SSD Project drive: 27tb local Raid 0 ... View more

Sorry Shivangi, but I'm not sure you read my post thoroughly... 1) The crash is not happening in the same place. 2) I do not have any effects applied aside from the 'timecode' effect.  I detailed the content of the sequence I'm rendering in my post. 3) I explained that I was switching the video renderer (to software). On a positive note, I was able to render without crashing by using software rendering.  Just took over twice as long to render. Just unfortunate that this 'professional' editor can't use my hardware.  Probably the best work-around for preventing crashes in Premiere is to shoot on film and cut them the old-fashioned way. ... View more

Warren, don't you find it unfair that you're paying $55 USD a month for professional software, with which you have to jump through all these hoops in order to use?  Are we professional editors or a software beta testers?  Is this the expected norm with subscription online updated software?  Because if is, I want to go back to the days when makers of software had to get it right BEFORE releasing it. I've subscribed to CC for over 4 years now.  At roughly $50 USD a month, that's over $2400 USD (or $3200 CAD at today's exchange rate).  Shouldn't the software given in exchange for this cost be reliable and efficient? ... View more

I like that this list is historical, and never meant to imply that all of these issues mentioned are outstanding and that there are not MANY duplicates..... but I still find it disturbing how many people are encountering show-stopping bugs.... We're not talking about little trivial UI wish list requests.  We're talking: 'I can't export my project' issues.  Those kinds of issues prevent people from using the fundamental tool that Premiere so often brags about on the website.   Perusing Adobe's marketing for Premiere on their website is disturbing. Crashes are happening for many people EVERY DAY, sometimes EVERY HOUR.  I just had 5 crashes this morning trying to render a simple sequence with 20 intermediate files. Since posting this message I've since discovered the 'resolved' and 'completed' status pulldown options to view what has been addressed from this list, which is useful.... but notice only about 140 out of 2700 issues posted are classified, with only 53 labeled 'resolved' or 'completed'.  That's 53 out of 2700... or 2%.   It doesn't feel like even one person at Adobe is working on curating and monitoring this list every day.  There should be a team just working on this list alone.... and I'm not talking about the engineers, I'm talking about people that categorize, prioritize, and respond to clients.  Can Adobe just spend a few hundred subscriptions from clients each month on this list? I see some posts in this list dated as early as July 1st, 2018.... so we're at least 6 months in, with 53 posted issues resolved.  There is probably hundreds of unique bugs in the code currently.  Forget features.  Lets focus the effort on fixing bugs and get Premiere stable... If a conservative estimate of 300 unique bugs are outstanding, at this rate, we're looking at 3 years to make Premiere stable.  And that's if old features don't get broken with new features added (at the rate they have been in the past). On a plus note, I upgraded Premiere to the latest version and was able to finally render my project.  Haven't done any editing yet so unsure if other issues exist.  Still amazed how slow the editing experience has become in Premiere.  We have games that update millions of polygons and textures on our computer at 90fps and yet Premiere can't move a few thousands of boxes around at more than 2fps.  It's unbelievable. ... View more

Yes, it's probably related to the display driver....not bugs in the display driver, but Premiere's inability to manage and interact with it.  Other applications seem to play well with the display drivers.   Premiere, not so much. Still getting random export crashes.  Best practice seems to be to queue exports in AME, save the queue, then close both Premiere and AME for 'fresh start' with the GPU.  Then open AME and start the queue.  Doing anything in Premiere with AME open usually gets AME to an unusable render state more often.  I still get these export crashes when exported directly from Premiere, so it's not only an AME issue. I've confirmed that this Lumetri bug does reach exports.  There is no pattern that I can see.  Sometimes Premiere behaves well, other times not. ... View more

I change the Master Red Settings of these clips, but the lumetri effect is applied on an adjustment layer over the top of my sequence. I don't think it happens in the render, only preview.... but I'll confirm tonight. ... View more

Thanks John! From my research, Exsate seems to be the best, most currently maintained option.  Thanks! ... View more

Jim Simon....The key word in my comment is 'suite'.  To my knowledge, none of the NLE's you list have such an extensive suite of tools as Adobe's CC.  Does AVID have tools like After Effects or Photoshop integrated?  Davinci Resolve has long dominated grading, but only recently has added editing.... and I don't think it's reached Premiere's capabilities yet.  Maybe in a few years.  Never heard of Hitfilm and know very little about Lightworks.  I moved from Sony Vegas to Premiere because of Vegas bugs.... only to have the CC development cycle begin to degrade Premiere.   To me, concurrent development of Premiere CC versions is insanity.... and any Adobe engineer who argues otherwise hasn't looked at a graph detailing the numbers in Premiere's bug database. Maybe I will try to edit the next large project in Resolve.... but it would be really nice to remain in the Adobe CC suite if they can return some stability.  Is it too much to ask after investing significant time learning Adobe software and spending thousands on a subscription? To be honest, Vegas was the most enjoyable editing experience for me... truly a pleasure to edit in.... quick intuitive controls.... until it became unreliable.... which is where Premiere is now.   I don't think I've sworn so much at a program in my entire life as I have at Premiere in the past months.  I can't even close Premiere sometimes without it crashing or hanging for silly-long delays. Kevin Monahan... I don't like having to limit use of my hardware and limit the scope of my project to use Premiere.  Maybe my expectations are unrealistic if big budget films have to split up their films in order to use Premiere.  I just don't understand why media management has to be so cumbersome in Premiere.  It would be really interesting to see exactly how the large films organize their films when using Premiere. ... View more