Vegas Pro 14 MP3 Audio issues

NickHope wrote on 10/4/2016, 10:02 AM

Can you upoad the file?
I'm running Windows Home 10 build 1067 build 14393.222

If you have a YouTube account you can get one of AVsupport's problem files like this:

Click on your circular avatar at the top right of the YouTube page
Click on "Creator Studio"
Click on "Create" on the left
Choose "Audio Library"
Search "Microchip" or "Pressure"

Quitter wrote on 10/4/2016, 10:18 AM

Microchip 1:54 Jason Farnham?
and
Pressure 2:00 Riot ?

NickHope wrote on 10/4/2016, 10:22 AM

Microchip 1:54 Jason Farnham?
and
Pressure 2:00 Riot ?

Yeah. What decoder???

Quitter wrote on 10/4/2016, 10:24 AM

Nothing wrong in Vp14
Mpeg Layer 3
mp3plug2.dll

NickHope wrote on 10/4/2016, 10:37 AM

I'm puzzled how kcfonman ended up with this file location: D:\Program Files\FileIO Plug-Ins\mp3plug2 I've never heard of that before. My VP13 path is C:\Program Files\Sony\Vegas Pro 13.0\FileIO Plug-Ins\mp3plug2

Quitter wrote on 10/4/2016, 10:50 AM

mine too
he has a strange installation, VP14 on C VP13 on D?

AVsupport wrote on 10/4/2016, 4:58 PM

AVsupport, in your Vegas Pro 14 program folder, subfolder "FileIO Plug-Ins", is there another subfolder "mp3plug2" available and in there a file "mp3plug2.dll"?

I use Windows 10 Home, version 1511, build 10586.589.

@Marco, just checked,

Yes I have the bespoke mp3plug2.dll in the Vegas plugin folder, V.14.0.0.161, digitally signed, should be working fine. So, I'm inclined to think it's not the actual mp3 codec...

AVsupport wrote on 10/4/2016, 5:04 PM

I'm puzzled how kcfonman ended up with this file location: D:\Program Files\FileIO Plug-Ins\mp3plug2 I've never heard of that before. My VP13 path is C:\Program Files\Sony\Vegas Pro 13.0\FileIO Plug-Ins\mp3plug2

Yes, whilst this is true and puzzeling, mine is fine (VEGAS folder on C: 'C:\Program Files\VEGAS\VEGAS Pro 14.0\FileIO Plug-Ins'), but not producing working results. So I rule that out as a cause issue also.

Marco. wrote on 10/4/2016, 5:10 PM

"So, I'm inclined to think it's not the actual mp3 codec..."

But I used same media file as you did (Googles "microchip.mp3"). I think it's something different.

AVsupport wrote on 10/4/2016, 5:13 PM

Also: just dug out some other old MP3's that I had sitting somewhere on my drives, came from different sources, same problem..double check @Quitter: you said the files play fine in VP14? with windows 1067/14393.222??

Marco. wrote on 10/4/2016, 5:18 PM

Do you have a codec pack or any other mp3 codec installed on your Windows system?

Quitter wrote on 10/4/2016, 5:33 PM

@Quitter: you said the files play fine in VP14? with windows 1067/14393.222??

Yes, i have no problems

NickHope wrote on 10/4/2016, 10:29 PM

kfconman and AVsupport, what is the default player for MP3s on your systems? i.e. What program do they open in if you double click them in File Explorer?

AVsupport wrote on 10/5/2016, 1:15 AM

I m not there to confirm, but from memory its windows default: groove music?

kcfonman wrote on 10/5/2016, 8:09 PM

Windows Media Player. It is not a Windows problems. It is how Vegas Pro 4 registered the media elements. None of my other Sony applciations are having problems with MP3 files. Only Vegas Pro 4. Acid, Sound Forge and Vegas Pro 13 have no issues. You can see that in the media properties between the 2 applications in my prior post.

AVsupport wrote on 10/9/2016, 2:15 AM

Have spotted another funny thing the other day as i was importing XAVC-S clips: even though they imported fine into the project, the VP14 file manager displayed the icons as MP3! Will further investigate. /edit: cannot replicate above...strange...eyes??

kcfonman wrote on 10/17/2016, 7:56 PM

I had to uninstall the application and reinstall. I did notice that the uninstall process did not remove all the registry entries. I had to clean out 24 entries for a clean install. Now all my MP3 files show as MP3 and use the correct dll file to paly them.

AVsupport wrote on 10/18/2016, 5:00 AM

sounds interesting thanks...was there a particular word you searched the registry for those redundant keys? what was your reason for reinstall?

kcfonman wrote on 10/18/2016, 6:58 AM

I used Vegas as the key word. I had to be carefule not to remove elements of VegasPro 13. They were in the schemes HKEY_USERS, CLISD, and for some reason under controlpanel->MicrosoftInputDevices->mouse->Exceptions. There were 6 events there. I don't remeber where the other 6 where at.

NickHope wrote on 10/18/2016, 7:36 AM

Or you can use a registry cleaner such as Ccleaner free. A fully system backup is recommended before you use it, and make a backup of the registry when it prompts you.

AVsupport wrote on 10/19/2016, 9:57 PM

hmm..sorry I'm a bit shy of the ol' registry cleaners...I had a bit of a look around, found this quite interesting:

looks like the Vegas14 installer entries are missing in one occasion the source disk information (this is not the case with VP13). Guessing, if installer doesn't interrupt install because of accepting faults, then there might be some missing information somewhere. And perhaps uninstaller can't uninstall what's not properly installed. Other versions might be working because of residuals? but thats all just a guess...i rather wait for a revised installer version before I try above [...still waiting...]