what is this (insert swearword here)???

Use this option in the program to overcome this kind of question.

Ha! At least I learned something new ;-) Thanks, j-v!
I also found out that there were backup files in my actual program directory that I didn't notice as I only looked in the temp/scratch folder.... So yeah. Guess part of my rage was a bit over the top...

Still - crashes are a major PITA and I'm hoping for a fix.

I couldn^t make out WHAT exactly causes the crashes, but the one thing I can say is this:

- When I edit a timeline (cutting and moving clips) while watching the actual video, it crashes.

- If I do the same editing WITHOUT watching the video (i.e. just orienting myselfs around the waveforms to do the editing), it doesn't seem to crash.

So it has something to do with editing/moving clips while watching at the same time...

@rkm82 Troubleshooting suggestions: https://www.vegascreativesoftware.info/us/forum/faq-troubleshooting-crashing-and-stability--104785/

"- When I edit a timeline (cutting and moving clips) while watching the actual video, it crashes."

This bug has been in Vegas for at least a decade. It usually doesn't completely crash the app, it will just hang for a long time, and eventually will recover. Sometimes it does trigger an actual crash, though. Regardless, I've been battling it with it for as long as I can remember. I often delete clips while they are playing, if I have multiple possible shots on different tracks, or if editing multicam the old fashioned way (since performance can be less than optimal when editing in MC mode) and I decide I want to cut to another angle while vegas is playing the current one still.

Eventually I just got in the habit of always pausing the video before making the delete, but it does slow me down a bit and has been a long time annoyance.

I changed the GPU acceleration with NVIDIA (or OFF) and disabled Intel, under Preferences/video.
I have no more crashes, maybe a temporary solution.... but it works!
I hope this can help someone.

Variable frame rate media plays back with properly synchronized audio

Hmm, using VEGAS Pro 16 Update 3 (build 352) and when i edit video with VFR i have a issue with synchronization, and after rendering its still there. Is any way to resolve this?

In this and old version I have the GPU turned off. My video card is invisible in Vegas options.

I have GTX 970 and drivers 417.35

Old drivers is ok.

I'm using 417.22 without issue on my 970.

I am getting a grating distortion on the soundtrack of a video when I render it to MP4 using the AVC codec.

This happened with the build (307?) I had until earlier this evening, and having found and installed build 352 this evening, the same happens with that.

Audio is clean on renders using the MPEG2 codec, and on (audio-only) WAV export.

The only sound on the video is a clean (well below clipping), separately-recorded native 48kHz stereo WAV file. I apply no audio effects or level shifts in Vegas. The original sound file was 24-bit, but replacing it with a 16-bit version makes no difference. The four unused camera soundtracks are muted.

The distortion depends on changes of programme loudness; replacing the soundtrack with either a -12dB 250Hz sine wave or silence shows no visible distortion.

This must be a fault in the audio component of the AVC / MP4 encoder.

I have tried changing SO4 settings (whatever that does - it was referenced elsewhere on the web) to no avail.

Using my DAW to subtract the source WAV file from the same audio extracted from the faultily encoded MP4 file, the distortion components are quite evident - see this example at two levels of time magnification:

I don't know what's going on - I have rendered other projects with no problems.

Can anyone shed any light on this, please? My client is impatient to get an MP4 for review, and I can't hand over a render with audio in this condition!

Thanks,

Alan

I am getting a grating distortion on the soundtrack of a video when I render it to MP4 using the AVC codec.

This happened with the build (307?) I had until earlier this evening, and having found and installed build 352 this evening, the same happens with that.

Audio is clean on renders using the MPEG2 codec, and on (audio-only) WAV export.

The only sound on the video is a clean (well below clipping), separately-recorded native 48kHz stereo WAV file. I apply no audio effects or level shifts in Vegas. The original sound file was 24-bit, but replacing it with a 16-bit version makes no difference. The four unused camera soundtracks are muted.

The distortion depends on changes of programme loudness; replacing the soundtrack with either a -12dB 250Hz sine wave or silence shows no visible distortion.

This must be a fault in the audio component of the AVC / MP4 encoder.

I have tried changing SO4 settings (whatever that does - it was referenced elsewhere on the web) to no avail.

Using my DAW to subtract the source WAV file from the same audio extracted from the faultily encoded MP4 file, the distortion components are quite evident - see this example at two levels of time magnification:

I don't know what's going on - I have rendered other projects with no problems.

Can anyone shed any light on this, please? My client is impatient to get an MP4 for review, and I can't hand over a render with audio in this condition!

Thanks,

Alan

In the mean time, there are apps you can use to merge an audio (aac mp4 or mp3) file with an mp4 file, so you can export a silent mp4, then the audio separately and then merge it into your mp4 without having to recompress the video. Mp4boxGUI is one, if I remember right.

If you have ffmped installed, running this command should also do it:

ffmpeg -i pathtoyourvideo.mp4 -i pathtoyouraudio.wav \ -c:v copy -c:a aac -strict experimental output.mp4

It would be cool if Vegas Pro have auto locking alignment like in Photoshop/After Effects for the ease of use in positioning video/text/media etc

I am getting a grating distortion on the soundtrack of a video when I render it to MP4 using the AVC codec.

This happened with the build (307?) I had until earlier this evening, and having found and installed build 352 this evening, the same happens with that.

Audio is clean on renders using the MPEG2 codec, and on (audio-only) WAV export.

The only sound on the video is a clean (well below clipping), separately-recorded native 48kHz stereo WAV file. I apply no audio effects or level shifts in Vegas. The original sound file was 24-bit, but replacing it with a 16-bit version makes no difference. The four unused camera soundtracks are muted.

The distortion depends on changes of programme loudness; replacing the soundtrack with either a -12dB 250Hz sine wave or silence shows no visible distortion.

This must be a fault in the audio component of the AVC / MP4 encoder.

I have tried changing SO4 settings (whatever that does - it was referenced elsewhere on the web) to no avail.

Using my DAW to subtract the source WAV file from the same audio extracted from the faultily encoded MP4 file, the distortion components are quite evident - see this example at two levels of time magnification:

I don't know what's going on - I have rendered other projects with no problems.

Can anyone shed any light on this, please? My client is impatient to get an MP4 for review, and I can't hand over a render with audio in this condition!

Thanks,

Alan

Thanks for the workaround suggestions, fr0sty!

I have just tried the (presumably legacy) Sony AVC plugin, and that appears to render clean audio.

The culprit seems to be the Magix mxavcaacplug.dll - after breaking my VMS15 out of retirement, it misbehaves in the same way. Same plugin (ver 1, Build 8532), but in a different folder, so not an individually corrupted file.

The investigation continues...

I forwarded that to the dev team to make sure they see it. Hopefully they can isolate it. What hardware are you using? What type of source media are you using in the project? If you can provide the mediainfo (free app, will give you the stats you need) on your files, as well as your project settings, that might help them.

I forwarded that to the dev team to make sure they see it. Hopefully they can isolate it. What hardware are you using? What type of source media are you using in the project? If you can provide the mediainfo (free app, will give you the stats you need) on your files, as well as your project settings, that might help them.

Thankyou.

My platform is:
GA-H170M-DSH3 mobo / i7-6700 proc / 32GB RAM / 480GB SSD + 2 x 2TB HDDs / Win 10 (up to date).

Vegas Pro 16 Build 352 (latest). Project settings 1920x1080, 25p, 48k audio (my regular format).

Stripping the project to the bone, the problem occurs even when rendering just a VEGAS solid colour generated media clip (i.e. no camera source media) along with the sound file (tried in WAV 24bit, 16bit and even mp3 formats).

I'm happy to discuss the problem direct with the dev team as it's not specific to the latest VP build and probably doesn't belong in this thread. How do I communicate with them?

 

I'm happy to discuss the problem direct with the dev team as it's not specific to the latest VP build and probably doesn't belong in this thread. How do I communicate with them?

https://support2.magix.com/customer/en/vegas/form

Maybe make sure to leave this forum link on the form so they can follow up easily.

If the plugin crash in this test, it is blacklisted for GPU-usage and would only work with CPU.

@VEGASPascal is there a way to See the Blacklist (as you can with the so4..), and perhaps Reset certain blacklisted plugins (after perhaps a driver update has been applied), or does this happen automatically in total Darkness.. ;-) ?

And, does that mean that Vegas now supports higher OpenCL versions?

Happy New Year, Prost!

Thanks, Nick, I noticed that...but thought (hoped) it was only relevant to the Intel GPU's. Is my only recourse, at this time, to uninstall V16 and re-install build 307?

@3d87c4 Based on that discussion, I fear that it might be. I suppose you could experiment with different GPU drivers. Please put in a Support Request anyway, and let us know what they say.

Were those disabled FX working OK for you before?

I'm starting to wonder if this new OpenCL compatibility test is a bad idea, or too aggressive, if it's disabling plugins that were working OK in previous versions. A strong compatibility warning rather than total disabling of a plugin might have been more prudent.

Still wondering about 360 stabilize...was that in build 307?

It was new in build 307. It's the last item in the "new features" section of the release notes. This comment implies that it must have been in there, since he was missing that FX in build 416 (presumably due to this new OpenCL blacklist).

so..this is insanity for sure, Ignite Pro working perfect always for me, so now I updated and the projects

is a waste, thank you Magix, real awesome thinking again, just blacklist it for everyone,

that's not aggressive or a bad idea that's just stupid

In search of the new blacklist:

Looking into the internal prefs, 'OpenCL' shows Version support for '1.1' and nvidia driver ver 285.58 as 'new'. Now, OpenCL1.1 was ratified 2010, and nvidia driver was released october 2011.

Happy New Year guys, current versions are OpenCL 2.2 and nvidia 417.35, please don't expect your users to also keep a 19 year old operating system alive to maintain stability..[/endofcheek]

Getting trouble with 352...

Renders ok but the preview is shot.

 

It happens if I import mp4 in a new project. But if I safe project and restart Vegas Pro 16 (352), then it works ok.

It also works fine if I take old project and use it as a template for new project.

I had a terrible sudden shutdown of Vegas 16 during editing, adjusting a video's transparancy and splitting clips (I send the error details) I updated to 16 (352) and again after 10 minutes of editing vagas locked up, now without any message! Restarting the program asked for a last-saved version, I did and lost my last edits. What is going on here Vegas programmers?

Where is 360Stabilizer ofx？

It is there, as it is.

My system is win7 and it cannot show 360Stabilizer ofx

Same for me, I can only see the FX Tiny Planet and not other 360 plugins.... Windows 7 64-bit, i7-2600... works fine on a i7 Laptop with Windows 10...(I can see all of the 360 plugins)...