Skip to main content
NangaParbat
NangaParbat
Known Participant
December 2, 2017
Question

"Premiere Pro debug event" How to execute Premiere stable?

  • December 2, 2017
  • 1 reply
  • 474 views

Hello,

sometimes the workflow with Premiere is very time-consuming and annoying because it is not stable running. Every day I work with Premiere getting some "unexpected Errors" and today a debug event and Premiere is just closing and the work since last saving is lost.

How can Premiere be executed more stable? Its really sad for Adobe.

Thanks

    This topic has been closed for replies.

    1 reply

    R Neil Haugen
    R Neil Haugen
    Legend
    December 2, 2017

    For some, there seem to be stability problems. For many of us, it's rock stable. Sometimes we fellow users can help get someone with stability issues running stable. But to do so requires that we understand your machine, your media & effects used, and the way you use PrPro to work.

    So ... OS/CPU/RAM/GPU/vRAM, the driver number for that GPU; the number-dot-number version of PrPro (not "latest" please ... the CC Desktop app is so often wrong); the media types you use, including codecs & frame-rate & frame-size, and produced by camera, DSLR, drone, screen capture, what; typical effects that you use especially when using multiple at the same time; any 3rd-party plugins and or programs that may have "touched" the media.

    Plus a bit of how you work can be helpful ... and what you're doing at the times it goes bonkers is also helpful.

    Neil

    Everyone's mileage always varies ...
    NangaParbat
    NangaParbatAuthor
    Known Participant
    December 3, 2017

    Hello R Neil Haugen,

    "stable as a rock" is definitely not the appropriate term in my experience. Loosing every day half an hour because of the instability of Premiere (Errors, restart, save backup...) is really annoying.

    Of course I can give you some information about my system:

    OS: Win10 Education, 64 bit

    PC: Lenovo Idea-PC, Inteil i5-3350P Quad-Core 3,1 GHz, 8 GB RAM

    GPU and vRAM see picture:

    Premiere Pro CC:

    2017.1.2. v11.0 Oasis

    In the project I use:

    Most video files are: *mts-files (Sony AVCHD from CX900E camera 1920 x 1080)

    But I also use: *.wav, *.mp3, *.png, *jpeg, *.mp4

    Sequence-Settings:

    1920 x 1080

    02;02;36;03, 50,00 fps

    48000 Hz - Stereo

    VR-Projektion: Ohne

    About the project:

    Includes about 700 clips (*mts), the main effects I use is "fast colour correction", "stabilization"

    But what I mainly suspect what courses the errors:

    I use for comment a USB-microphone with the "Tapco USB interface" (Driver 10.0.15063.502).

    And as I described in this post here (What is going on with my audio level? Mysterious swelling of audio ) Premiere seems to have a problem with this device. I am getting a heavy overload of my audio level and a kind of backcoupling, although the microphone is not plugged in. Changing the delay-time of the microphone from 500ms back to 200ms and back again to 500ms "solves" the problem temporarily. When I use the microphone, I have to put it back to 500ms, otherwise the USB-connection seems to be too slowly.

    So I hope this helps for the moment, would be great if you know some advice!

    Thanks very much!

    By the way this is one of the other error messages I get periodically. The information from Premiere "unknown error" does not really help me where I have to search for the problem.  Luckily Premiere does not close in this case and it can be clicked away...

    R Neil Haugen
    R Neil Haugen
    Legend
    December 4, 2017

    Sony AVCHD seems to be troublesome for some users. A general comment with that media, I do strongly suggest "ingesting" it into PrPro from the Media Browser rather than say drag/drop from Explorer; but I've known of a couple users who got better stability doing the drag/drop.

    Mp3 file may work, and/or some may work and others not. And some that worked for the last month may glitch the project tomorrow, so it is normally suggested to convert all mp3 to WAV before ingesting.

    At this point, I would recommend swapping out your mp3 to WAV and dumping your cache files with PrPro closed.Then when you start up PrPro allowing it time to regenerate the audio and cache files before starting to work.

    And let's see if some others have suggestions.

    Neil

    Everyone's mileage always varies ...
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices