Vegas Pro 17, Build 353 Doesn't Handle Imported MP3's

Rory-Martell wrote on 11/13/2019, 2:30 PM

This is my first post because this is the first time I've had such a problem with this software and I cannot find any answers elsewhere on the Internet.

Prior to Build 353, I was able to record audio files in Audacity, save them to MP3 (Bit Rate Mode: Constant, Quality: 128 kbps, Variable Speed: Fast, Channel Mode: Stereo), and then add those files to projects in Sony Vegas Pro 17 with no problem. After updating to Build 353, I get this (watch out headphone users) when I play any imported MP3 files (even ones that worked in Sony Vegas Pro 17 before Build 353). Here's the real strange part: if I "Open file in Audio Editor" from within Sony Vegas Pro and Sony Vegas Pro opens Audacity with the MP3 file making that horrific noise, the file is perfectly normal in Audacity.

Saving the Audacity file to WAV (only tested 32-bit) and adding to Sony Vegas Pro 17, Build 353 works just as I would expect the MP3 file to work.

 

So, what happened? What must I do to make MP3 files work as they did for Sony Vegas Pro 12, 16, and 17 (prior to Build 353)?

Comments

wwjd wrote on 11/14/2019, 10:19 AM

I've had this as well, and seems very random - some days MP3 work just fine, others (no changes) same file gets freaky. I also see the sound wave max out in the clip on the timeline, and also self mute if you pull the intro fade too close to the sound you are after in the wave.... it flattens out to nothing. I've had this in both versions of 17, and some in 15. GUESSING it's based on how the mp3 is made and I don't have an answer for the best way to beat it. Stick to WAV until they fix it.

EricLNZ wrote on 11/14/2019, 7:33 PM

This has cropped up before with Pro and VMS. With a problem file go into its properties and check which plug-in is being used. It's usually "mp3plug2.dll". But sometimes Vegas tries to use "mcplug2.dll" which appears to cause problems.

Rory-Martell wrote on 11/15/2019, 7:43 AM

@EricLNZ Thank you for that suggestion. I'll take a look and see if that's the problem. I hope it is something so simple because I've got a lot of audio files to convert to WAV otherwise.

Rory-Martell wrote on 11/15/2019, 10:37 AM

@EricLNZ You were exactly right. The plug-in associated with the file is mcplug2.dll. How do I change it back to mp3plug2.dll?

VEGASHeman wrote on 11/15/2019, 11:30 AM

We've had a few cases reported of this problem. Can you open the FileIO log (located in C:\Users\<USERNAME>\AppData\Local\VEGAS Pro\17.0\fileio_x64.log) and look for the presence of a line which should look like the following:

INFO 2019-09-23 10:39:39  Loading cached reader|renderer plugin 'MP3 File Format' from path 'C:\Program Files\VEGAS\VEGAS Pro 17.0\FileIO Plug-Ins\mp3plug2\mp3plug2.dll'

If that is missing, it would point to a problem loading that DLL (or one of it's dependent DLLs), and hence you end up with the wrong plugin loading it. In such a case, can you check your virus scanner logs and see if this file (or one of it's components) has been mistakenly blocked?

Rory-Martell wrote on 11/15/2019, 12:02 PM

@VEGASHeman Hi there. I'm sorry to say that I cannot verify if that was the problem. Since posting this morning, I did a "factory reset" (Ctrl+Shift double clicked on the Vegas executable) and that corrected the plug-in problem. Looking at the log now shows the MP3 File Format loading the mp3plug2.dll and my audio files are working again.

I apologize for my impatience.

EricLNZ wrote on 11/15/2019, 4:33 PM

No apologies needed as you've provided a possible solution for others who encounter this problem.

MAGIXheman's comments are interesting. Apart from virus checkers Registry Cleanup programmes can also sometimes remove items they shouldn't.

Ernad-Panjeta wrote on 11/28/2019, 3:02 PM

This has cropped up before with Pro and VMS. With a problem file go into its properties and check which plug-in is being used. It's usually "mp3plug2.dll". But sometimes Vegas tries to use "mcplug2.dll" which appears to cause problems.

I went into properties and can't see "mp3plug2.dll" or "mcplug2.dll" either sorry for bothering you.

alex-f wrote on 12/5/2019, 6:11 PM

I have the same problem, however it cannot be resolved after I reset nor re-install my Vegas Pro 17. I checked the log and also preference, it is using "mcplug2.dll", how can I change back to "mp3plug2.dll"?

alex-f wrote on 12/5/2019, 6:24 PM

We've had a few cases reported of this problem. Can you open the FileIO log (located in C:\Users\<USERNAME>\AppData\Local\VEGAS Pro\17.0\fileio_x64.log) and look for the presence of a line which should look like the following:

INFO 2019-09-23 10:39:39  Loading cached reader|renderer plugin 'MP3 File Format' from path 'C:\Program Files\VEGAS\VEGAS Pro 17.0\FileIO Plug-Ins\mp3plug2\mp3plug2.dll'

If that is missing, it would point to a problem loading that DLL (or one of it's dependent DLLs), and hence you end up with the wrong plugin loading it. In such a case, can you check your virus scanner logs and see if this file (or one of it's components) has been mistakenly blocked?

I have the same problem and it does not load mp3plug2, I also checked the anti-virus log and it does not block the DLL. however can I make it using mp3plug2.dll?

LalaMoreiraDJ wrote on 1/29/2020, 1:16 PM

Ctrl+Shift double clicked on the Vegas executable resolved this problem for me in Vegas 11 and 15.