Pro Tools 12 - Video engine won't launch

[john1192]

Originally Posted by sauna-l

Quit PT
Use "PT Prefs" http://petegates.com/pg-pt-prefs.html
to trash Databases (check the last 7 boxes if you don't want to waste too much time checking which makes what)
Restart PT

hi, i had a phone call with the OP last week .. he does have the Pete Gates App .. thx for checking though ..

john (aka JOsh) still funny !!!!

[Austin4]

Just a quick update. I un-installed PT and re-installed version 12.4. Video engine works just fine. No issues. Now I'm in the process of re-installing all of my plug-ins. Anyone know of a quick way to find what I used to have?

[kings79]

Having the same issue...

http://duc.avid.com/showthread.php?t=392536

[john1192]

Originally Posted by Austin4

Just a quick update. I un-installed PT and re-installed version 12.4. Video engine works just fine. No issues. Now I'm in the process of re-installing all of my plug-ins. Anyone know of a quick way to find what I used to have?

hi aaron, did you drag all your plugins to the unused plugins folder .. the restart pro tools ... it will load all the Avid PLugins .. then you can drag the 3rd party ones in a few at a time (not sure how many you have??) ..

and making sure you have thre most up to date (stating the obvious here)

cheers john

[AVIDIVA]

I'm having this issue with Pro Tools 2018.10
It's Dec 8, 2018 for the record
Windows 7, 16GB
Steinberg UR22 MKII
NVidia GTX 970
ShadowPlay = off

I just updated the video drivers. Issue was happening before and after update.

It used to work last year but I have a project with video and the video engine won't start.

Bar gets full and nothing happens.

I tried:
Deleting contents from AppData\Roaming\Avid\Pro Tools folder
Deleting that odd plugins folder per AVID forum
UnInstalling and ReInstalling PT
Tried different video files by rendering different versions (waste of time)

Any suggestions?

[The Weed]

IIRC 2018.10 is not qualified for W7.

[AVIDIVA]

So, it's been a few days and the lastest PT update from AVID seems to have fixed the problem. (version 2018.12)

I guess...thanks AVID? I would like to believe that this thread was read and action was taken but considering how many people frequent this forum for advice, it's most likely coincidental that the update had a fix specifically for my issue.