Convert audio in this file to wav without altering volume?

MikeLV wrote on 2/16/2020, 11:14 AM

SOLVED

Can someone download this small mts file and convert the audio in it to wav without altering the volume in either the source or resultant wav file, , and post the file for me to download? I'm troubleshooting... Thank you.

https://we.tl/t-cco0ppYRNF

Comments

Turd wrote on 2/16/2020, 11:43 AM

VP17

96kHz, 32 Bit (IEEE Float), Stereo, PCM (float):

Here

Note to self (everyone else please look away -- the note that follows is a reminder for mine eyes only): Figure out a clever, kick-booty signature that suggests I'm completely aware of how to properly and exhaustively party on and that I, in fact, engage in said act on a frequent and spontaneous basis.

MikeLV wrote on 2/16/2020, 11:48 AM

@john_dennis thank you for posting the file. When I add the same mts file, and your wav file onto the timeline, this is what I see in Vegas:

The volume of the mts file is significantly louder than the wav file. What does yours look like? Are the wave forms the same? Or is the mts audio much louder as shown in my screenshot?

I've taken this a step further and added the files to Resolve 16 and see the same thing, louder mts audio:

But when I play the mts file outside of an NLE, such as with VLC or WMP, the volume isn't loud like it plays in the NLEs. What can this possibly mean?

Marco. wrote on 2/16/2020, 11:53 AM

I'd guess it's kind of "welcome in the world of AC3 metadata". Some apps read and use it, some apps don't.

MikeLV wrote on 2/16/2020, 11:56 AM

@Turd, your wav file's volume is nearly identical to the volume of the mts file within Vegas.

john_dennis wrote on 2/16/2020, 12:08 PM

Between Vegas 9 and 17 something happened...

Investigating...

MikeLV wrote on 2/16/2020, 12:12 PM

My issue isn't with the wav, it's with the ac3, getting read as much louder than it was recorded

Marco. wrote on 2/16/2020, 12:23 PM

"Between Vegas 9 and 17 something happened..."

Imho, it's AC3 vs AC3 Pro and the way these AC3 decoder versions treat the metadata.

john_dennis wrote on 2/16/2020, 12:35 PM

Through the ages...

Someone please confirm Vegas Pro 16

@Marco.

"Imho, it's AC3 vs AC3 Pro and the way these AC3 decoder versions treat the metadata."

If you're correct. What's a guy with a camera and old projects to do?

Marco. wrote on 2/16/2020, 12:49 PM

The processes which seem to work here are:

  • Transcode to Wave using a tool like FFmpeg.
  • Extract the AC3 stream and re-wrap to M2TS (I used FFmpeg again).

Don't know if there still is a direct way to use the AC3 Pro decoder in VP17.

john_dennis wrote on 2/16/2020, 1:12 PM

@Marco.

The Good

I've never owned a camera that shoots anything but PCM.

The Bad

Unfortunately, I host 335 GB of video from my son's camera that shot AC3 in an .MTS wrapper.

The Good

I hope he lost the camera.

The Bad

He has an iPhone, now.

Joelson_Forte wrote on 2/16/2020, 1:53 PM

@MikeLV @john_dennis

STEP 1 Copy the folder compoundplug and ac3studioplug folder of the Vegas Pro 17 Build 321 located in C:\Program Files\VEGAS\Vegas Pro 17.0\FileIO Plug-Ins.

STEP 2 Paste this folder into Vegas Pro 17 Build 387 in the same location C:\Program Files\VEGAS\Vegas Pro 17.0\FileIO Plug-Ins to replace the compoundplug and ac3studioplug folder. I recommend doing a Backup of the original folder, in case you want to revert this change.  

This will make ac3 recognized as it used to be.

MikeLV wrote on 2/16/2020, 1:57 PM

@Joelson_Forte I don't have build 321 anymore, just the current version.

How can I obtain that folder in that build if it's no longer installed? Can you post it here if you have it?

Also, how can it be explained with the problem seemingly to also occur in Resolve? I don't really care for Resolve, but was baffled when I saw the waveforms there. If the compoundplug folder trick works, then I'll be a happy camper.

Joelson_Forte wrote on 2/16/2020, 2:13 PM

@MikeLV

I'm not sure if my machine's folder will work on yours because of the registry. But you can download the trial version of Vegas Pro 17 Build 321 here:

https://www.vegascreativesoftware.info/us/forum/vegas-pro-update-history-so-far--104998/?page=2#ca730549

MikeLV wrote on 2/16/2020, 2:19 PM

Thanks for the link - So I'd have to fully uninstall the current build, install the older build, copy the folder, uninstall the older build, reinstall the current build, and overwrite the current build's folder with the older one.. correct?

Did you run into this problem too? How did you know to replace the folder and all those dll files? I"d like to understand a bit more so I can relay this info to Magix

john_dennis wrote on 2/16/2020, 3:04 PM

I have spare SSDs and a Windows 10 Out of the Box image. I installed Vegas 17 Build 321 on a fresh image, never opened it saved the folder C:\Program Files\VEGAS\Vegas Pro 17.0\FileIO Plug-Ins to a separate drive. I replaced the folder on my normal SSD and the audio acted as it did for all other versions.

I'll likely revert to the Build 387 files.

MikeLV wrote on 2/16/2020, 3:08 PM

@john_dennis, did you swap the entire file io plugins folder, or just the compoundplug folder within it? I'm still in the process of testing this..

john_dennis wrote on 2/16/2020, 3:12 PM

I swapped the entire folder C:\Program Files\VEGAS\Vegas Pro 17.0\FileIO Plug-Ins.

MikeLV wrote on 2/16/2020, 3:13 PM

@Joelson_Forte, no go, as @john_dennis said, the audio from the mts file acted the same with the compoundplug folder from the 321 build. Nice effort though!

john_dennis wrote on 2/16/2020, 3:18 PM

You misunderstood. With the Build 321 FileI/O folder on Build 387, the audio decoded at the same levels that you expect and the same as all previous versions of Vegas Pro.

john_dennis wrote on 2/16/2020, 3:22 PM

I'm off this bug and restoring my system to it's default state now.

MikeLV wrote on 2/16/2020, 4:07 PM

As instructed by @Joelson_Forte and just confirmed by me, the only folders that need replacing are compoundplug and ac3studioplug. Once these folders are replaced from build 321, the ac3 audio loudness issue is resolved. I will update my other thread on this topic too.

fifonik wrote on 2/17/2020, 3:31 AM

Hm. I do not know how to re-produce the issue.

I have m2ts with AC3 from my camcorder (5.1). If I put it in VP17 (build 387), render it to wav and put the wav back in VP17 -- I have pretty much the same volume (inverted added tracks and got silence). What am I missing?

Camcorder: Panasonic X920

Desktop: MB: MSI B450M MORTAR TITANIUM, CPU: AMD Ryzen 3700X (not OC), RAM: G'Skill 16 GB DDR4@3200 (not OC), Graphics card: MSI RX580 8GB, SSD: Samsung 970 Evo Plus NVMe 500MB (OS), HDDs: Seagate & Toshiba 2TB, OS: Windows 10 Pro 1909

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17

john_dennis wrote on 2/17/2020, 9:01 AM

Compare the volume of the Vegas 17-387 rendered file to the volume of a file rendered from any other version of Vegas.

https://www.vegascreativesoftware.info/us/forum/convert-audio-in-this-file-to-wav-without-altering-volume--118897/#ca742129