Skip to main content
M
Mei111111
Known Participant
August 3, 2017
Question

All the fixes you list are work-arounds

  • August 3, 2017
  • 1 reply
  • 3107 views

Mod Notes: Branched. Re: the Unofficial Troubleshooting Guide

Thanks for writing this Jim, it's very thorough and useful.

What I'm about to say isn't aimed at you, but at Adobe.

----

I think it's a massive shame that this guide needs to be written. All the fixes you list are work-arounds to faults in Adobe's software. The problems aren't aren't caused by users making mistakes or not understanding things, they're down to bugs in the (expensive) Adobe product.

Adobe themselves could never write this guide, because it would have to start with, "We know our software is very buggy and often crashes. We're not going to fix it, but here are some ways to minimise the pain we're causing you..."

      This topic has been closed for replies.

      1 reply

      Kevin-Monahan
      Community Manager
      Kevin-MonahanCommunity Manager
      Community Manager
      October 30, 2017

      Hi Mei,

      I think it's a massive shame that this guide needs to be written. All the fixes you list are work-arounds to faults in Adobe's software. The problems aren't aren't caused by users making mistakes or not understanding things, they're down to bugs in the (expensive) Adobe product


      Actually, I do believe most troubleshooting issues are related to making errors, not understanding things, in addition to issues with the software. It's OK, because it can be a confusing combination of these things and it's a lot to know and process. Sorry about that.

      I've been working on NLEs both as an editor and in NLE engineering before I worked at Adobe and I find that a lot of the troubleshooting listed here pertains to not only Premiere Pro, but all NLE editing systems. I agree that Premiere Pro is not perfect, but with such complicated applications, similar issues do crop up.

      I feel that most of these are known issues to experienced video editors (reset prefs, try other media, remove plug-ins), however, I do feel the pain of users that are new to this kind of level of computer and NLE troubleshooting. It's a lot to know and be aware of!

      I think that these are the things that make the video editing "job" of both the creative and the technical that much more challenging. I always expect the worst, prepare for that scenario, and then hope failure doesn't happen. With good training, you can overcome failures and experience them less often.

      I apologize for the lack of an official troubleshooting guide. I'll continue to press for one.

      Thanks,
      Kevin

      Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
        D
        Duncan McEwan
        Participating Frequently
        November 1, 2017

        Actually, Kevin, Mei is correct. Many times the software "breaks." This can happen after an update of either your product, or the OS. What usually happens when an update is created, is the install folder ends up with executable files, both .exe and .dll files that are from different batches of compile runs. An update comes out, and made a change in all an internal function call is handled, and that call is to a function in a .dll files that is either older, or newer than the file with the calling function. My installation of Premiere Pro 2017 currently has almost all of the files with the same creation dates. One is older, and one is newer. These could be the cause of some problems, however, I am not currently having any, as I didn't skip step one in this post!

        Other times, problems are caused by Adobe getting tired of paying royalties. Recently, Adobe announced they were ending support fro Dolby audio, reverting the operating system's handling. Now, the executable files needed to be kept in sync will come from two different vendors: Adobe/Microsoft or Adobe/Apple. This will exacerbate the problem after Apple or Microsoft "update" their operating systems. It also takes the feature away from Windows 7 users such as my self. Adobe's idea of a 'fix' is for me to update to Windows 7. There is only one big problem with my downgrading my system to Windows 10: I neither drink, nor do drugs, both being operator requirements for this operator to install Windows 10 on any hardware I own, but I digress. (I also noticed that, although Adobe is now saving the cost of the Dolby royalties, my month subscription rate has not dropped a penny.)

        In short, if Adobe is going to send out an update, or upgrade, be sure to check ALL of the dependencies, and to re-compile ALL of the .dll files, not just the ones that have had changes made to their code. Compilers get updates too, and might be generating assembly/machine code differently which may not be entirely compatible with the code in older .dll files. (Btw, Adobe seems to be a lot better about this than other software vendors.)

        Me: I've been editing since film. I've been programming computers since punch cards. I currently provide in-house support for Adobe Premiere Pro in a Mac environment. I also produce and edit video on Premiere Pro as a freelancer. Due to my extensive experience with Macs, and OS X, I run my own editing system on a dedicated Windows PC.

        D
        Duncan McEwan
        Participating Frequently
        November 2, 2017

        Jeez, so much anger in this thread.

        Jim and I don't always see eye-to-eye on these forums, but I think he's done a great job compiling all this information for everyone.

        Yes, Premiere has issues. Yes, some of them are absurd, even inexcusable, and should be fixed as soon as possible. But UNTIL that happens, this sort of troubleshooting guide is the best chance you've got for getting things working again.

        You don't have to like it, but becoming more familiar with your hardware and software WILL help you solve a huge number of your issues. Just yesterday I talked to a guy who didn't realize he shouldn't be editing footage off of an external HDD. Last week, I helped a guy figure out that he had accidentally put his sequence into 'Audio Time Units' mode.

        This guide is HONEST. And the truth hurts. But don't attack Jim for being the messenger.


        Without following the steps in Jim's guide, you will have no way to know for sure that a problem is being caused by Premiere, or your O.S.

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices