So I updated to the lastest CC version of premiere, and the project I was working on the previous day is now giving me trouble.I get the following warning:"A low-level exception occurred in: lvcode64.dll (GetAVICodecs)"Then, when I try to drag any .mxf clips from my bin (shot on a Canon XF350s, XF300s, and XF100s) it won't let me drop them onto the video portion of the timeline but will let me drop them on the audio portion of the time line. Specifically in a sequences set for those cameras.Explain this malarkey and render aid!My system specs if Relevant:Motherboard: MSI – Z370-A PROCPU: Intel Core i3-8350KMemory: GeIL POTENZA DDR4-2400 2 x 8GBGraphic Card: MSI GeForce GTX 1050 2GBHard Drive: Seagate BarraCuda Pro 2TBCPU Cooling: Cooler Master – Hyper 212 EVOCase: DIYPC – Solo-T1-RPower Supply: EVGA – 500W 80+ BronzeNow, when I first finished the update and tried to open, it said I needed to update the drivers of my graphics card. I was still able to open before hand, and found this problem initially. Then I went to NVidia's website and updated my drivers and installed their stupid Nvidia Experience program which threw me for a loop because it was replacing my real audio drivers and couldn't hear — until I set it back which was a minor annoyance, but then when I opened Premiere again I was having the same problems as I initially described above.I seek solutions. I will answer any additional questions to acquire those solutions. Be you fellows frustrated in this manner on the ground or techs from on high within the lofty prowess and resources of adobe itself, I plead your aid.Moderator note: please avoid using profanity. We have users of all ages reading these forums.

Participating Frequently

Answered

Just did the update to 2019 and opening a project from the other day is giving me trouble

Forum|Forum|7 years ago
October 15, 2018
23 replies
17634 views

So I updated to the lastest CC version of premiere, and the project I was working on the previous day is now giving me trouble.

I get the following warning:
"A low-level exception occurred in: lvcode64.dll (GetAVICodecs)"
Then, when I try to drag any .mxf clips from my bin (shot on a Canon XF350s, XF300s, and XF100s) it won't let me drop them onto the video portion of the timeline but will let me drop them on the audio portion of the time line. Specifically in a sequences set for those cameras.

Explain this malarkey and render aid!

My system specs if Relevant:

Motherboard: MSI – Z370-A PRO
CPU: Intel Core i3-8350K
Memory: GeIL POTENZA DDR4-2400 2 x 8GB
Graphic Card: MSI GeForce GTX 1050 2GB
Hard Drive: Seagate BarraCuda Pro 2TB
CPU Cooling: Cooler Master – Hyper 212 EVO
Case: DIYPC – Solo-T1-R
Power Supply: EVGA – 500W 80+ Bronze

Now, when I first finished the update and tried to open, it said I needed to update the drivers of my graphics card. I was still able to open before hand, and found this problem initially. Then I went to NVidia's website and updated my drivers and installed their stupid Nvidia Experience program which threw me for a loop because it was replacing my real audio drivers and couldn't hear — until I set it back which was a minor annoyance, but then when I opened Premiere again I was having the same problems as I initially described above.

I seek solutions. I will answer any additional questions to acquire those solutions. Be you fellows frustrated in this manner on the ground or techs from on high within the lofty prowess and resources of adobe itself, I plead your aid.

Moderator note: please avoid using profanity. We have users of all ages reading these forums.

This topic has been closed for replies.

Correct answer Wes Howell

Our latest patch released last week has a fix related to some of the issues mentioned in this thread.

It is a small dedicated patch related to a few key fixes. (link below)

Bugs fixed in versions 13.0.1 and 13.0 releases of Premiere Pro

Please make sure your version of 13.0 is updated with this patch. Notice the link above provides useful info on related issues.

If other issues remain, please feel free to reach out to me with applicable info.

Thanks!

Wes

Show previous replies

eddiel43018052

Participating Frequently

Premiere Pro 2019 is awful. I can't open up projects I created last week in 2018. 2019 is not good. I'm reinstalling it right now. Hoping that will resolve the issue.

eddiel43018052

Participating Frequently

Or a project I created half-an-hour ago.

C

Carlos Ziade

Community Expert

Okay some routine steps to follow when opening older projects in newer versions :

01. Clean Media Cache

02. Delete all render files and video/audio previews

For Windows users, this is recommended, download this driver :

NVIDIA has publicly released windows ODE drivers that support the CUDA 9.2 SDK used in the latest release of Premiere Pro. This is not the Microsoft default driver, but you can download this driver directly from NVIDIA: NVIDIA DRIVERS Quadro Desktop/Quadro Notebook Driver Release 410 WHQL (of the 410 series drivers).

Next, Please refer the System Requirements and Hardware Acceleration Requirements :

Adobe Premiere Pro CC System Requirements

diegohblack

Known Participant

The upgrade gave me trouble too, but of a different kind. I don't have a Logitech camera.

My trouble is that all the audio that I had edited in Adobe Audition is now in slow motion.

Anyone knows the solution? It feels to me that the Hz are off.

Thanks

M

markb59696186

Participant

I am getting the same exact error. I've tried uninstalling Premiere, reinstalling NVDIA drivers, then reinstalling Premiere to no avail. I even uninstalled all of my Logitech hardware and software as well.

Please help, Adobe!

paulo99

Participating Frequently

You may need to manually delete the file. I had the same issue even after uninstalling.

M

markb59696186

Participant

I can't even *find* the file. It's not in my Sys32

J

JoshM.

Participant

I'm getting a similar message opening a new project.

J

JoshM.

Participant

So the m3jpeg errors were from the Morgan M-Jpeg codec. Still trying to figure out "Exporter"

Jeff Bugbee

Community Expert

Firstly: NEVER open older projects in a newer version of Premiere.

Secondly: NEVER open older projects in a newer version of Premiere.

That is a recipe for disaster which is why it's 1st and 2nd.

Third: Create a new project in 2019. Attempt to import your old project. See if that makes a difference.

If that doesn't work, create a new project in 2019, attempt to import the raw footage (not from the old project, just the raw footage) to see if you get the same error.

billbyrnes@live.com

Inspiring

I just created a new project. As soon as I created a blank sequence, I got the “low level exception” error. There were no media whatsoever in the new project and sequence. I then imported the original project, deleted the blank sequence. The problem is the same. I get the error when I first start an open PP and any project. If I close a project and open it again, I DO NOT get the error.

Bill Byrnes

[personal info deleted, forum policy]

M

mstephenschicago

Participant

I noticed Premiere had a pretty large minimum requirement spec bump. Is the graphics card supported?

damiens95898921

Participating Frequently

Hi,

I don't have this problem but "lvcod64.dll" seems to be related to Logitech Webcam software/driver.

Maybe your webcam is setup by default like capture device since the premiere pro CC 2019 update?

Try to remove/rename the file under C:\windows\system32 (or other system disk) and make a new test.

Hope this will be useful for you guys.

Damien SB.

paulo99

Participating Frequently

This is what I did to temporary solve the issue.

- I uninstalled my Logitech software and deleted the .dll in question. Once deleted, all is good!

But, once i re-install the Logitech drivers, the same problem persisted. Definitely, a Logitech related issue somehow.

paulo99

Participating Frequently

Just to add one more thing. Even though the error still occurs after re-installing the Logitech drivers, I am now able to edit on the Timeline with the error showing on the bottom right. The driver removal/adding process somehow allowed me to able work on the timeline with no issues. (so far)