AC-3 Intermittant Silent Audio -AC-3 Encoder - MAGIX Community Forums Archive

Subject:AC-3 Intermittant Silent Audio Posted by: CommanderCody Date:12/29/2015 1:33:38 PM I'm using 'Dolby Digital AC-3 Studio' encoding from 'Movie Studio Platinum 13.0 (Build 942)' with the following settings: Audio: 192 Kbps, 48,000 Hz, Stereo, Automatic Gain Control off. Use this setting for stereo DVD soundtracks. Audio: 192 Kbps, 48,000 Hz, 24 Bit, Stereo, AC3 If I create a new project, load some AVI files and encode the audio, it seems to work fine. However, if I change one or more of the AVI files outside of MS and reopen MS using the .VF project file, I will often end up with completely silent AC3 audio after encoding. I can tell when it's going to happen because the audio processing is very fast - too fast. After unsuccessfully trying many different workarounds, I found that opening the MS app directly instead of from the .VF project file seemed to give me good AC3 audio results. I'm posting this in case anyone else is having this problem and is searching for a workaround, or maybe has a better one. Hopefully, Sony will look into fixing this for a future update.

I'm using 'Dolby Digital AC-3 Studio' encoding from 'Movie Studio Platinum 13.0 (Build 942)' with the following settings:

Audio: 192 Kbps, 48,000 Hz, Stereo, Automatic Gain Control off.
Use this setting for stereo DVD soundtracks.
Audio: 192 Kbps, 48,000 Hz, 24 Bit, Stereo, AC3

If I create a new project, load some AVI files and encode the audio, it seems to work fine.
However, if I change one or more of the AVI files outside of MS and reopen MS using the .VF project file, I will often end up with completely silent AC3 audio after encoding. I can tell when it's going to happen because the audio processing is very fast - too fast.

After unsuccessfully trying many different workarounds, I found that opening the MS app directly instead of from the .VF project file seemed to give me good AC3 audio results.

I'm posting this in case anyone else is having this problem and is searching for a workaround, or maybe has a better one. Hopefully, Sony will look into fixing this for a future update.