Something weird, by chance I was experimenting recently with encoding 5.1 (via the ac3 template) and it worked OK, but after the upgrade from windows 10 (1803) to (1809) the output files are silent. I can still and hear 5.1 source files in Vegas 16 timeline.
I can also still play (in a player) the old .ac3 output file (and hear 5.1) made before the upgrade, so there is nothing wrong with my sound system.
Does anyone experience this issue as well?
OS Build 17763.168 of December 5? There were data-loss problems with a previous 1809 build.
yes I have OS Build 17763.168 of December 5, I never installed the previous 1809 builds. I installed the OS Build 17763.168 of December 5 yesterday (or was it the day before, I cant remember - goldfish memory!)
Feel free to check if it is also an issue on 1803 OS windows 10, I cannot re-check/investigate it anymore on 1803 as I obviously upgraded.
Which player did you test with?
I just checked and it worked fine rendered with VP16 build 307, playbacked via VLC player on Windows 10 version 1803.
Good news Marco, I just found the reason, an old bug I found in an old post, if you overwrite an existing .ac3 rendered file you get the silent issue. If you delete the produced file and re-render, the sound is back.
So it is a bug, and fortunately there is a workaround.
The bug is in Vegas 15 build 416 and Vegas 16 build 307
Strange, works fine here even when overwriting the existing file.
Which windows version do you have?
Just as I wrote above: 1803
Sorry I overlooked you posted your version already, so that may be the reason it works for you, I know it maybe a bit far fetched. But I can perfectly simulate the issue on my 1809, new file = sound, overwrite = silent. Tested on V15 and V16
Just downloaded the latest VLC, but the issue persists. At least there is a workaround, just delete your destination files with the same name to avoid overwrites ...
I just got confirmation from Magix Pro Support: [Ticket#2018121017008397]
This is an issue our developers are aware of and are hoping to have resolved in a future update of the application. We apologize for the inconvenience