Skip to main content
Known Participant
December 9, 2017
Answered

Premiere Pro CC 2018 playback stop working after a while

  • December 9, 2017
  • 13 replies
  • 12971 views

Hello everybody,

Actually I've started editing some videos on my Surface Book with the latest version of Premiere Pro CC 2018, and I'm facing a very annoying bug.
Checking this forum I've seen other users are having the same or similar problem.

Description of the problem:
After a while using Premiere and randomly when editing a project and I click play on Program/Source monitor the play icon become the usual stop button and it stays like that. I can't revert it to play button.
Timeline doesn't play at all, it shows the last video frame. The software is working correctly, I can move the play head, select clips, but Source and Program monitor looks like frozen.

When this problem shows I can't close Premiere as usual. I've to force closing using Windows Task Manager.
The project is started from scratch.

Some further infos below:
PC: Surface Book, i5 6300U, 8GB DDR3 RAM, Intel HD520, GPU Nvidia Geforce, Toshiba 256GB SSD, 13,5" 3000x2000 display
Pr Pro version: version 12.0.0 (build 224)
Multimedia cache: on main SSD, with "if possible store cache files near the original footage" option enabled (so it creates the cache on the external SSD specified below);
Footage: Actually is on an external SSD, a Samsung T3 512GB USB3 portable drive;
Codec of footage: H264 in MOV Quicktime container (original Canon DSLR MP4 clips);

Effects on clips: none

Memory settings: 6.5GB dedicated to Adobe apps on a total of 8GB.
GPU: Cuda acceleration enabled, Nvidia Geforce Custom GPU from Nvidia for Microsoft Surface Book (Maxwell architecture). Actually is vital for me using the GPU acceleration, I can't work with just the software rendering performance.GPU Driver version: 23.21.13.8813, obtainable via Windows Update or Microsoft Surface website (I've installed from MS website). Updated the drivers Yesterday, I had the same issue even with the previous driver version;

Windows 10 x64: build 16299.98, latest updates installed (checked few minutes ago)
Other infos: Windows Defender AV disabled, no Others softwares running, just Premiere Pro

Thanks in advance who helps me troubleshoot this problem.

Added further info on Premiere CC settings.

This topic has been closed for replies.
Correct answer Rémi22141177l52f

Hi,

I had exactly the same issue on Premiere Pro 2022, on a new computer.

 

I noticed that each time this bug occurs, an event appears in the Event Viewer of Windows, tagged "Source = Display", with the following message: "Le pilote d'affichag igfx ne répondait plus" ("The display driver igfxn has stopped responding.").

In addition, the bug never occurs when my sequence has only audio tracks (all video tracks empty).

 

 

The following 2 solutions work perfectly for me:

I tried to translate menu names from my French computer, the exact names might be different.

 

1. Check if you have the latest driver for your display card.

Note that the card manufacturer (in my case: Intel) may have a newer version than the computer manufacturer (for me: Dell). Windows Update seems to check only the latest version from the computer manufacturer, you may have to download the driver directly from the card manufacturer website.

 

- or -

 

2. If the previous option does not work, deactivate the GPU acceleration.

On Premiere Pro, open your project, File > Project Settings... > General, change the video renderer to "Mercury Playback Engine Software Only", then [OK].

By the way, if you use After Effects, you are likely to face the same issue.

Here again: open your project, File >  Project Settings... > Effects & Video Renderer > Use: "Mercure Software Only".

and, always in After Effect, Edit > Preferences > Display : uncheck the option "Material acceleration for panels Composition, Layer and Yardage"

 

 

I hope this will help anyone Google will bring here 🙂

13 replies

andreamrgAuthor
Known Participant
December 19, 2017

Unfortunately the problem came back again after clearing the preferences and plugin cache, today.
This is a very annoying bug and Adobe should fix this as soon as possible, it happens very often and ruins any workflow and mind sanity.

mateuszw84507484
Participant
December 11, 2017

I've cleared the settings to keep Alt running, and it's fine for now. I hope that the trouble will not come back because personalization of the program has taken me again for 4 hours.

I am embarrassed that Adobe does not really have technical support for people who pay for using software every month. The only support is the forum where we guess how to solve the problem from other users.

No wonder that more and more people are giving up on Adobe and buying Final Cut.

From thursday, my assemblies are not working and these are real losses for my company.

mateuszw84507484
Participant
December 9, 2017

I have identical trouble.

I've cleaned up all comfoming and audio pick files, I've redesigned and reinstalled pro premiere, I updated the graphics card drivers. It still does not work :-(

andreamrgAuthor
Known Participant
December 9, 2017

Hi, thanks for your reply.
I'm sad that you are facing the same trouble.
Seems to be a bug of this version of Premiere. There are many users complaining.
Actually I'm trying to isolate the potential source of the problem.
In my case could be Lumetri or the autosave option in Premiere. The problem showed right after few seconds the project autosaved.
Also, I've deleted all the cache files in the dedicated Premiere Pro folder (with the path set in cache preferences menu).
Till now it's about 45 minutes the issue didn't show.
Finger crossed.

mateuszw84507484
Participant
December 11, 2017

Hello, thank you for the message.

For me, the audio comfoming and pick files did not help me.

Can you describe and describe what cache files you have cleared? Where is it on the adobe premier menu?

I read a lot a lot now. This problem has many users. Several people have helped reset the Premiere settings. It is done so that when you start Premiere we hold the Alt button. We will need to reset the entire layout and keyboard shortcuts later. A lot of work... :-(

I will just try this way.

Thank you for your message.