[George Dean]

Hi Kelly,

The oldest version I have is Sony VP13, which acts like your version 10, when the audio files is deleted the envelope goes flat. I was using Magix VP16 for my test.

OK, so here is another work around. Open your project with the original audio files and volume envelope. Write down which audio is first in the track. Now close your project. Rename all the audio files or move them from the folder so Vegas will not find them when it loads the project. Now load your project and when Vegas prompts select to find a replacement for the audio file that was listed first on the track. Leave the rest off-line. This works in VP13, hope it works for version 10.

Best Regards……George

[George Dean]

Hi Kelly,

Maybe yes and maybe no!

Are all the audio clips on the same track? When you rendered out the single new audio file and left the envelope on the track, that rendered file you sent out to have the hiss removed will also reflect any adjustments you made with the audio envelope and these are now baked in.

If you load your project and delete all the audio clips from the track with the envelope, the envelope will stay on that track and not change. Now you can load the single audio render (that you received back from the hiss doctor) on that track, aligning it at the same start point, and everything should be as before you rendered and sent it out (of course now without the hiss!). Off course the results of any adjustments in the audio envelope will depend on the rendered envelope now being baked in.

If you have multiple audio clips in multiple tracks with multiple audio envelopes, now you have a completely different monster to slay!!

Best Regards……George

[George Dean]

Hi Trung,

If the audio plays in something like VLC player or Windows, I would run it through Handbrake or MediaER Tool Kit to convert it and then bring it into Vegas Pro 14.

I’m not an audio guy so I’m not sure what is in the specs Mediainfo is showing that Vegas doesn’t like, but they are way different from mp4 samples that I have.

Best Regards……George

[George Dean]

Adam, can you upload here a small/short source media sample, maybe something around 50 meg or smaller?

Best Regards……George

[George Dean]

Adam, is that Mediainfo report on your source media? If it is, your source is progressive, not interlaced. Also 8,000 kb/s bit rate seems like a delivery rate rather than a capture bit rate. I don’t use OBS, but I know of many that do and as far as I know all of them are recording in progressive with OBS.

Best Regards……George

[George Dean]

Hi Amber,

“I did notice that it changed from Draft (Full) to Preview (Auto), would that have anything to do with it…?“, No.

Did you try: change the setting in Preferences > Video (tab) ‘GPU acceleration of video processing’ to ‘None’?

Does that change anything?

What is your source footage from, screen capture program, a camera, smart phone?

Can you try the Mediainfo thing again, here is what one of my source files report, which is pretty typical, and as you can see provides a lot of detail….

Also, have you done any Track Motion or Pan&Crop? Can you upload your .veg project file? It will not include any source media or sensitive stills, audio, or video, but I can then look at what you may have done in the timeline to cause your issue.

Best Regards……George

[George Dean]

Hi Amber,

Did you try the full reset? Hold down the ‘Ctrl+Shift’ keys while you double left click on the Vegas Pro desktop shortcut. When the little window pops up, click in the box ‘Delete all cached application data’, then left click ‘Yes’. This will reset Vegas Pro to it’s original installation settings and delete the pesky cached application data that will sometimes build up cause Vegas Pro to do strange things.

Also, have you changed the setting in Preferences > Video (tab) ‘Accelerate video processing’ to ‘None’?

Did any of the changes help?

Mediainfo can be downloaded here: https://mediaarea.net/en/MediaInfo

Start Mediainfo, select the ‘View’ tab and then select ‘Text’ mode. Then select the ‘File’ tab and load your source media. Then post a screenshot of the spec’s report.

Best Regards……George

[George Dean]

Hi amber,

It’s difficult to tell what is going on be the limited data and screenshot you have provided, so there are many things you can try, which may or may not help.

You could try a full reset of Vegas Pro. You can change the Preference > Video tab, acceleration of video processing to ‘None’ and use CPU only during rendering.

Screenshots of your project settings, render template settings, screenshot of Mediainfo (in text mode) of your source media specs, and a little larger area screenshot of your preview window, all may help members to help you.

Best Regards……George

[George Dean]

Hi symmetrie,

If the ofx is New Blue, I would uninstall it (actually whatever it was) and see if that clears things up. Also, have you tried a full reset? Hold down the ‘Ctrl+Shift; keys while you double left click on the Vegas Pro desktop shortcut. When the small window pops up, click on the box ‘Delete all cached application data’, then left click on ‘Yes’. This will reset Vegas Pro to it’s original install default settings, and clear all the pesky built up cached application data that can sometimes make Vegas do strange things.

Best Regards……George

[George Dean]

Hi Greg,

Not sure what “all my current settings and addons” entail, the best way is to determine that yourself, by downloading the free 30 day trial. Then you will see first hand what works and doesn’t.

Also I would recommend you look at the latest version 16, as it has additional features over version 15 and the latest build of version 16, build 361 seems like the most stable.

If you Vegas Pro 13 is build 453, or earlier, you have the Sony version. If that is correct, there is a name space difference between your VP13 and any VP newer. As you know, VP15 is produced by Magix, not Sony. So, any scripts you may have added to VP13, will not function in VP14/15/16 until the name space has been changed (not that difficult, see below).

If you have add-ons that were packaged with VP13, they may or may not work with VP 14/15/16 as they may have been a special deal for VP13 only promotion. If you have purchased full packages of add-on, they may or may not work with VP14/15/16 until you download the version that is compatible with the Magix branded versions.

Window sizes and configurations have never progressed from an older version to a newer version, so they would have to be changed in the new version.

To change the name space in script files of older scripts designed for Sony Vegas to work in the newer VP version branded by Magix, there is a tool downloadable from ‘tools4vegas’ designed by Wayne Waag (a member here you may be familiar with) called ‘VegasScriptConverter.exe’. This tool makes it simple and quick to convert scripts from or to working with Sony vs Magix versions. If you need the link, let me know.

Best Regards……George