Since build 216 (I have the b261 now but nothing changed actually), VEGAS is doing some weird things with audio rendering.
The conditions to reproduce this are not really clear for me but I may have isolated two points which can cause the bug:
- the first one when the veg file is open, to change one of the audio files (the mp3 one mainly) with the same name but the properties not being 100% identical (in my case the comment of the file can be slightly different, or I just forget to write it while in the first ver the comment was set).
- the second one is to split some wav audio tracks and to remove some parts (just to avoid the CPU going crazy while previewing the audio file). [I never split the mp3 one]
The audio files used in these types of projects are one mp3 file and several wav files (min. 2).
mp3 file does not have any effect on it, wav files have at least 2 and up to 4 effects on each of them (often ExpressFX and iZotope plugins).
The master track also has an effect (compressor).
However, I noticed something which seems to predict when the audio file I'm rendering is going to be empty:
when you begin rendering ("Render as...") and after you selected the preset for rendering, VEGAS loses the focus on its own window and the focus is set on another window.
If the focus is on VEGAS, the audio file is fine.
The focus loss would be the cause of these "no spectrum" rendered files, but what would cause this focus problem? No idea...
The only way I found to work around is to open a new VEGAS instance and to try reproducing all what I have done in the project, and to avoid splitting tracks.
(Windows 10 64bit on VEGAS Pro 15.0 261, and also on b216. I also have an ASIO driver on the computer (2.14)
I thought the bug could be caused by the So4 dll, but since the bug also appears in b261, I doubt this would be the cause...)