> ## Content Index > Fetch the complete content index at: https://soundforgepro.com/llms.txt > Use this file to discover other available public pages before exploring further. # VEGAS Pro 20 AAC Codec Glitches: Import, Sync and Render Fixes - URL: https://soundforgepro.com/vegas-pro-aac-codec/ - Published: 2026-11-07T12:43:00.000Z - Updated: 2026-11-07T12:42:59.000Z - Description: AAC trouble in VEGAS Pro 20 to 2027 starts with two checks: what MediaInfo and File Properties say about the stream, and which build you're on. Then fix import, silent, garbled, drift or render problems in order, with a WAV fallback that skips the AAC decoder. - Author: Erick Finn - Tags: Troubleshooting, Boris FX **Start any AAC glitch in VEGAS Pro 20 or later with two checks: read what's really in the file with MediaInfo and VEGAS File Properties, then install the last build of your version. VEGAS Pro 21 through 2027 shipped their AAC and audio-decoding fixes in specific builds, so the build number decides whether a setting is worth touching at all.** VEGAS Pro 20 is the exception: none of its builds names an AAC fix, which makes a stubborn file on that version a rewrap or WAV job. I'd check the build before touching any preference. A setting flipped to dodge a bug that the next build already fixed stays flipped, and the legacy decoding option is the clearest case, because a VEGAS engineer says it takes the project off the new engine pipeline. After the two first checks come six more, in the order the symptoms show up: a file that won't import, an event that imports silent, garbled or chirping audio, drift, AAC renders that fail or come out wrong, and the WAV fallback that gets around all of them. A short list of what not to install closes the guide, since codec packs and hidden-tab tweaks still sit at the top of many old threads. ![Decision path for AAC problems in VEGAS Pro: check the stream and the build first, then five symptom branches for import failure, silent audio, garbled audio, drift and render problems, each with its fix](https://soundforgepro.com/content/images/2026/10/aac-symptom-fix-path.webp) Two checks first, then follow the branch that matches what you hear or see. ## Check what's in the file and which build you're on MediaInfo tells you what the file contains; VEGAS File Properties tells you which decoder VEGAS picked for it. Those are the two things Boris FX forum staff ask for before anything else. [The staff how-to on posting MediaInfo and VEGAS File Properties](https://forum.borisfx.com/t/21166?ref=soundforgepro.com) says to open the file in MediaInfo and switch to View > Text, then right-click the file in the VEGAS Explorer window, choose Properties and read the Plug-In section at the bottom. For a file already in the project, the same Properties sit on the General tab when you right-click it in Project Media or on the timeline. In [a VEGAS Pro 23 audio thread](https://forum.borisfx.com/t/22095?ref=soundforgepro.com), a staff member added that holding Shift gives more detail on the decoder. In the MediaInfo text, the Audio block carries the answers. Format says whether the track is AAC at all or AC-3 (Dolby Digital), which is a different codec with a different fix. Sampling rate and Bit rate mode matter later for renders. No Audio block means the file has no audio stream, and no VEGAS setting can play a track that isn't there. [MediaInfo](https://mediaarea.net/en/MediaInfo?ref=soundforgepro.com) is free for Windows, macOS and Linux. ![Two panels side by side: the MediaInfo text view with the Audio block lines Format, Sampling rate, Bit rate mode and Channels marked, and the VEGAS Pro file Properties General tab with its Plug-In section marked](https://soundforgepro.com/content/images/2026/10/aac-stream-check.webp) Read Format first: AAC and AC-3 fail for different reasons. Then check the build against the table in the next section. VEGAS Pro 2026 and 2027 patches don't install from inside the program. When a VEGAS Pro 2026 user was still getting low-bitrate AAC renders on build 105, the staff answer in [the thread about bad render audio](https://forum.borisfx.com/t/23540?ref=soundforgepro.com) was short: "Updates are in Boris Fx Hub, not within the program." One more check applies to VEGAS Pro 2026 trials. In [an August 2026 thread about an HEVC and AAC file VEGAS called an unknown type](https://forum.borisfx.com/t/25294?ref=soundforgepro.com), staff asked whether the trial was registered, because the demo version can't open most file types. Register it before you blame the codec. ## Last build per version and the audio fixes it carries Each version's last build carries every audio fix released for it. The table lists those builds and the AAC and audio lines worth knowing, from [the release history the forum moderators keep from each build's readme](https://forum.borisfx.com/t/24284?ref=soundforgepro.com) and the official release posts. | Version | Last build | Released | AAC and audio lines worth knowing | | -------------- | ------------------- | --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | VEGAS Pro 20 | Build 411 | June 19, 2023 | No AAC-specific fix in any build. Build 214 fixed hardware decoding of GoPro and DJI files; build 411 fixed crashes when decoding AVC and HEVC files. | | VEGAS Pro 21 | Build 315 | May 22, 2024 | Build 187: loud audio error in the final frames of some events, support for all media with MPEG audio, AC-3 imports at its proper length. Build 300: HE-AAC SBR audio reads properly, static burst on some formats gone. Build 314: mono plays at the proper rate, stereo AC-3 in MP4 reads, rendered audio back in sync. | | VEGAS Pro 22 | Build 250 | May 14, 2025 | Build 194: Default All sets the correct hardware decoder, some MP3 files no longer play silent. Build 237: AC-3 render sync. Build 239, marked unofficial in the history: variable frame rate fixes including audio sync. Build 248: AC3 on Windows 11 24H2. | | VEGAS Pro 23 | Build 356 | December 17, 2025 | Build 278: AC3 decoder for clean Windows 11 24H2 installs, File I/O Surrogate rewritten. Build 356: audio pops on stream 2 of some GH4 AVC files in MOV, audio in strangely multiplexed transport streams. | | VEGAS Pro 2026 | 2026.0.3, build 189 | [August 24, 2026](https://forum.borisfx.com/t/25206?ref=soundforgepro.com) | [Build 66](https://forum.borisfx.com/t/21161?ref=soundforgepro.com): AAC encoder update, better HE-AAC in MP4, new AAC routing in AV1, AVC and HEVC renders. [Build 143](https://forum.borisfx.com/t/24204?ref=soundforgepro.com): AAC export bitrate handling. Build 189: distorted float32 LPCM audio in MP4, MP4 rendering across templates. | | VEGAS Pro 2027 | Build 31 (launch) | [October 26, 2026](https://forum.borisfx.com/t/26201?ref=soundforgepro.com) | Decoding errors in 44.1 kHz, 256 kbps AAC renders longer than 33 seconds; wrong audio codec in MxCompound HEVC renders; broken WAV imports limited to their real length; truncated MP3 exports. | Operating systems narrow the upgrade path. [The VEGAS Pro 22 specifications](https://help.magix-hub.com/video/vegas/22/en/content/topics/1-before/specifications.htm?ref=soundforgepro.com) list Windows 10 and 11 and an internet connection for registration, while VEGAS Pro 2026 and 2027 list Windows 11\. For VEGAS Pro 2026, staff put it plainly in the same render-audio thread: build 143 "has been replaced by 189 with more audio decoding improvements". VEGAS Pro 20 is the odd one out. Its seven builds, 139 through 411, carry no AAC-named fix, so get onto build 411, and if the glitch survives it, the honest choices are converting the media or moving to a newer version. If VEGAS Pro 20 is the version giving you trouble and you're weighing an upgrade, the [VEGAS Pro 23 review](https://soundforgepro.com/vegas-pro-23-review/) covers what that release changed and who it suits. Plan the move before you make it: .veg files are upward compatible only, as staff reminded a VEGAS Pro 2026 user in that thread, so a project saved in the newer version won't open in the older one and a later rollback means rebuilding it. ## VEGAS won't import an AAC or M4A file AAC and M4A are on the official import list, so a refusal points at the file, not the format. [The VEGAS Pro 2026 specifications](https://cdn.borisfx.com/borisfx/Documentation/vegas/2026/en/content/topics/1-before/specifications.htm?ref=soundforgepro.com) list AIFF, AAC, MP2, MP3, M4A, OGG Vorbis, WAV, WMA and FLAC as audio import formats, and AAC as an export format; the audio rows read the same for VEGAS Pro 21, 22, 23 and 2027. A bare .aac file is usually a raw ADTS stream with no MP4 container around it, and that is where import trouble tends to start. In [a 2017 VEGAS Pro 14 thread about an AAC file exported from Audacity](https://steamcommunity.com/app/528200/discussions/0/1473095331491873430/?ref=soundforgepro.com), the replies offered the same two routes that still apply: put the AAC into an MP4 or M4A container, or convert it to WAV. The thread never confirmed which one worked. Rewrapping is quicker and costs no quality. With FFmpeg, `ffmpeg -i input.aac -c copy output.m4a` copies the audio into an M4A file without re-encoding it. [FFmpeg's documentation](https://ffmpeg.org/ffmpeg.html?ref=soundforgepro.com) describes `-c copy` as a stream copy with no decoding or encoding, fast and lossless, though it can fail on some files, and [the aac\_adtstoasc bitstream filter](https://ffmpeg.org/ffmpeg-bitstream-filters.html?ref=soundforgepro.com) that converts the ADTS header for MP4 and M4A is inserted automatically. If the M4A still won't import, convert to WAV instead with `ffmpeg -i input.aac -ar 48000 output.wav`. Check MediaInfo's Format line before going further, because AC-3 is a separate case that users often file under AAC. Clean installs of Windows 11 24H2 no longer include the system AC3 codec. VEGAS Pro 22 build 248 (April 15, 2025) added AC3 support on 24H2 systems, with a known issue that AC3 waveforms may not display on the timeline, and VEGAS Pro 23 build 278 (September 9, 2025) ships its own AC3 decoder for clean 24H2 installs. On VEGAS Pro 2026, also rule out the unregistered trial from the first checks. ## The clip imports but the audio is silent or missing Open the file in MediaInfo first: with no Audio block there's nothing for VEGAS to play, and the fix is a new export from the source device or app. When MediaInfo shows an AAC track but the timeline event has no audio, check whether the clip went in as a video-only event. For that case, [the VEGAS Pro 2026 help on adding media](https://cdn.borisfx.com/borisfx/Documentation/vegas/2026/en/content/topics/4-media/adding%5Fmediafilesproject.htm?ref=soundforgepro.com) says to right-click the event and choose Add Missing Stream for Selected Event to bring the other stream back. That command restores a stream left out on purpose. It doesn't decode a stream VEGAS can't read. When the stream is there and VEGAS still imports video only, the file needs a new audio track. In [an October 2026 Creative COW thread](https://creativecow.net/forums/thread/vegas-doesnt-capture-the-audio-in-my-videos/?ref=soundforgepro.com), MP4s made with a third-party converter came into VEGAS Pro 22 as video-only events, and the reply ran through the same list: check the stream in MediaInfo, re-convert with AAC or PCM audio, try Add Missing Stream. The poster never confirmed which step worked. Of the three, re-converting is the one that changes the file, so do it with Shutter Encoder or FFmpeg as described in the conversion section. One version-specific case belongs here. VEGAS Pro 22 build 194 (October 30, 2024) fixed some MP3 files playing with no audio, so on VEGAS Pro 22 check the build before converting an MP3 track. ## Garbled, chirping or static AAC audio Match your build against the releases that fixed this exact symptom before converting anything: - Build 187 of VEGAS Pro 21 (November 8, 2023) fixed a loud audio error in the final few frames of some events and added proper support for all media with MPEG audio. - Build 300, also VEGAS Pro 21 (April 6, 2024), reads HE-AAC SBR audio properly and removed a loud burst of static noise when decoding some file formats. - On VEGAS Pro 23, build 356 (December 17, 2025) fixed audio pops on stream 2 of some GH4 AVC files in MOV containers and audio in strangely multiplexed transport streams. - The 2026.0.3 update, build 189 (August 24, 2026), fixed distorted float32 LPCM audio in MP4 files. HE-AAC is a low-bitrate AAC profile. It stores a compact core and rebuilds the top of the spectrum from SBR (spectral band replication) data. A decoder that mishandles that layer gets the high end wrong, which is the part VEGAS Pro 21 build 300 put right. On VEGAS Pro 20, no build carries that line. Distortion that appears only after you cut or move clips points somewhere else. In [an April 2026 VEGAS Pro 23 thread](https://forum.borisfx.com/t/22095?ref=soundforgepro.com), audio on every clip turned high-pitched after edits, and the poster traced it to X-Mouse Button Control simulating Shift plus the mouse wheel, not to media, codecs, GPU or drivers. It's a single report, and pausing any input-remapping tool takes a minute. When the build is current and the file still sounds wrong, convert the audio to WAV and edit that. ## AAC audio drifts out of sync Drift in MP4s from phones, screen recorders and downloads is often a variable frame rate problem, and VEGAS has a documented preference for it. In Options > Preferences > File I/O, [the VEGAS Pro 2027 help](https://cdn.borisfx.com/borisfx/Documentation/vegas/2027/en/content/topics/12-preferences/preffileio.htm?ref=soundforgepro.com) describes Favor audio sync when playing Variable Frame rate (VFR) media as prioritizing audio sync over smooth video playback when it's checked; the help for VEGAS Pro 21, 22, 23 and 2026 describes the same option. It works on playback, so treat it as the first test, not the cure for a render. If the drift survives that, give VEGAS a cleaner file. In [an April 2026 thread about YouTube-downloaded MP4s](https://forum.borisfx.com/t/22288?ref=soundforgepro.com) that played out of sync, staff advice was to run them through HandBrake first, or through Shutter Encoder at the same resolution and frame rate, or to make video proxies. The thread didn't name the audio codec and the poster never confirmed a fix, so read it as the general route for problem MP4s. HandBrake writes video files only, which makes it the tool for a fresh MP4, not for a WAV. Two builds touched sync directly. VEGAS Pro 21 build 314 (May 15, 2024) fixed rendered audio going out of sync, and VEGAS Pro 22 build 239 (January 23, 2025) fixed variable frame rate problems including audio and video sync, although the moderator history marks that build as unofficial. ## File I/O decoder settings: what to toggle, what to leave alone Change one File I/O setting at a time, restart VEGAS after each change and put the setting back if nothing improves. Several toggles at once leave you with a fix you can't name and a changed setup you can't undo cleanly. ![VEGAS Pro File I/O preferences panel with four documented options marked 1 to 4: Favor audio sync for VFR media, Enable Hardware Decoding for supported formats, the hardware decoder list with NVIDIA NVDEC and Intel QSV, and the Default All button](https://soundforgepro.com/content/images/2026/10/file-io-decoder-options.webp) Test one option, restart, and switch it back if the audio doesn't change. Enable Hardware Decoding for supported formats switches hardware decoding of AVC and HEVC media on and off, and the list box under it picks the decoder, NVIDIA NVDEC or Intel QSV, according to [the VEGAS Pro 23 File I/O help](https://help.magix-hub.com/video/vegas/23/en/content/topics/12-preferences/preffileio.htm?ref=soundforgepro.com). It's a video setting. Switching it off is a fair test for a file that misbehaves in picture and sound together, not an audio fix. Default All in the Preferences dialog is the clean way back after experiments; on VEGAS Pro 22 it sets the correct default hardware decoder from build 194 on. The legacy AVC decoding option is the one I'd leave off. Users label it Enable legacy AVC decoding in their posts; the official File I/O help for VEGAS Pro 21 through 2027 doesn't describe it, and old threads still recommend it. [A VEGAS engineer explained in October 2026](https://forum.borisfx.com/t/26063?ref=soundforgepro.com) that "if the legacy decoding options are enabled, you're not using the new engine pipeline", that the new pipeline needs the new decoders and the new encoder, and that "legacy decoding should be disabled unless there's a very good reason to enable it." If you switch it on to test one file, switch it off again afterwards. VEGAS Pro 2027 build 31 moved the File I/O checkboxes into the main settings list as switches, so the options look different there, and it adds Enable legacy H26X (AVC/HEVC) render plug-in, which the 2027 help describes only as turning on the legacy AVC/HEVC render plug-in. The engineer's point covers it too: switching to a legacy component breaks the new pipeline. ## AAC render problems: failed, out of sync or the wrong bitrate Three checks cover the AAC render problems in the threads: a 48 kHz project, the true bitrate read in MediaInfo, and the last build. I'd set the project rate first. [Forum staff told a VEGAS Pro 2026 user](https://forum.borisfx.com/t/24279?ref=soundforgepro.com) with a 192 kHz project to "Set the project to 48khz or 48000hz not 192khz", adding that 48,000 Hz is normal for PCM audio with video. AAC encoders have a ceiling too. In [an August 2022 Voukoder thread](https://www.voukoder.org/forum/thread/1073-vegas-pro-18-render-instantly-finishing/?ref=soundforgepro.com), a VEGAS Pro 18 render through FFmpeg's AAC encoder finished instantly because the project ran at 192 kHz; that encoder tops out at 96 kHz, and changing the rate in VEGAS fixed it. That was the Voukoder plug-in, not VEGAS's built-in encoder. Bitrate needs MediaInfo, not the template number. AAC in a VEGAS render is variable bitrate, and [a VEGAS engineer's answer in an April 2026 bitrate thread](https://forum.borisfx.com/t/21593?ref=soundforgepro.com) was that "you need to use media info to see the true maximum bitrate used by the encoder." VEGAS Pro 2026 also had a real bug: builds 66 and 105 rendered AAC in AVC and HEVC MP4 files at about 128 kbps whatever the template said, which staff acknowledged in May 2026\. Build 143 (June 19, 2026) improved AAC export bitrate handling and build 189 replaced it, so a VEGAS Pro 2026 render stuck near 128 kbps is a build question first. VEGAS Pro 2027 build 31 brought its own AAC render fixes. The release post lists "decoding errors in certain AAC renders"; the readme lines in the moderator history are more specific: decoding errors in 44.1 kHz, 256 kbps AAC renders longer than 33 seconds, and incorrect audio codec selection in MxCompound HEVC renders. The same release widened PCM and AAC export choices for AVC and HEVC in MP4 and MOV, and the 192 kHz and 32-channel figures in that note belong to PCM, not AAC. For renders that drift, VEGAS Pro 21 build 314 fixed rendered audio going out of sync and VEGAS Pro 22 build 237 (January 22, 2025) synchronized AC-3 audio renders. When an AAC render still comes out wrong on the last build, take the audio around the encoder. [The staff workaround during the VEGAS Pro 2026 bitrate bug](https://forum.borisfx.com/t/23731?ref=soundforgepro.com): render the video as usual, export the audio on its own as WAV, convert the WAV to AAC in Shutter Encoder at the bitrate you need, then use Shutter Encoder to replace the AAC in the video render with the new file. If the WAV needs cleanup before it goes back under the picture, the [Sound Forge and VEGAS Pro workflow](https://soundforgepro.com/sound-forge-vegas-pro-workflow-video-editors/) walks the round-trip, and the [audio export QA checklist](https://soundforgepro.com/audio-export-qa-checklist/) catches the rest before upload. Renders that fail in every format, AAC or not, call for a reset as the last resort. Close VEGAS, hold Ctrl+Shift while double-clicking the desktop shortcut (not the Start menu entry) until the reset prompt appears, tick Delete all cached application data and click Yes, as [the staff reset how-to](https://forum.borisfx.com/t/24296?ref=soundforgepro.com) describes. It resets your personalized settings too, so note any custom preferences first. It was the confirmed fix in [a February 2025 Creative COW thread](https://creativecow.net/forums/thread/vegas-pro-20-renders-corrupt-or-unsupported-files/?ref=soundforgepro.com) where VEGAS Pro 20 renders came out corrupt or unsupported in every format. ## Convert or rewrap AAC with legitimate tools Rewrap when VEGAS rejects the container; convert to WAV when it misreads the audio. Rewrapping leaves the AAC data untouched. WAV is plain PCM, so it takes the AAC decoder out of the chain entirely. My rule is simple: once an AAC file has misbehaved, edit from a WAV copy and keep the original as the archive. FFmpeg does both from the command line. [FFmpeg's download page](https://ffmpeg.org/download.html?ref=soundforgepro.com) states that the project provides source code only and links ready-made Windows builds from gyan.dev and BtbN, so take a build from those links rather than from a download site. | Job | FFmpeg command | What it does | | ------------------------ | -------------------------------------------- | ----------------------------------------------- | | Rewrap a bare .aac | ffmpeg -i input.aac -c copy output.m4a | Copies the AAC into M4A with no re-encoding | | Bare .aac to WAV | ffmpeg -i input.aac -ar 48000 output.wav | Decodes to WAV at 48 kHz | | Audio from an MP4 to WAV | ffmpeg -i input.mp4 -vn -ar 48000 output.wav | \-vn drops the video, \-ar sets the sample rate | [Shutter Encoder](https://www.shutterencoder.com/?ref=soundforgepro.com) is the point-and-click route. It's free, runs FFmpeg underneath, offers Replace audio and Rewrap without re-encoding and converts to WAV; version 20.4 runs on 64-bit Windows 7 through 11 and on macOS. [HandBrake](https://handbrake.fr/features.php?ref=soundforgepro.com) writes MP4, MKV and WebM only, with AAC, MP3, FLAC, AC3 and other audio encoders, so keep it for re-encoding a problem video. For deliveries where AAC keeps causing trouble, a VEGAS user shared [an FFmpeg script](https://forum.borisfx.com/t/24692?ref=soundforgepro.com) that turns VEGAS MP4 renders into MOV files with WAV audio in place of AAC, without re-compressing the video; it's a user workflow, not a Boris FX tool. WAV is big: 48 kHz, 16-bit stereo comes to 192,000 bytes a second, about 11.5 MB a minute, and the [audio file size calculator](https://soundforgepro.com/audio-file-size-calculator/) gives the figure for your project length. Once the audio is WAV, the [Sound Forge conversion guide](https://soundforgepro.com/how-to-convert-audio-files-sound-forge-pro/) covers changing sample rate, bit depth or delivery format, and the [WAV vs FLAC vs MP3 guide](https://soundforgepro.com/wav-vs-flac-vs-mp3-editing-mastering-archive/) explains why lossy files make poor edit masters. ## What not to install Skip codec packs, unofficial decoder DLLs, registry edits and "AC3 fix" tools. AAC is on VEGAS's own import list, and the official fix for AC-3 on Windows 11 24H2 is a build: VEGAS Pro 22 build 248 or VEGAS Pro 23 build 278. The hidden Internal-tab tweaks in older threads and videos, which switch off the So4 Compound Reader or switch on MainConcept AVC/AAC, come from the VEGAS Pro 12 to 15 era. VEGAS Pro 21 build 300 changed the routing they relied on: AVC decoding goes through mxcompoundplug by default, and the So4CompoundPlug blacklisting was removed. No official or staff source documents these tweaks as an AAC fix, and the 2018 poster who reported one working warned that it could break decoding of iPhone videos. ## What 12 published support threads reported Across 12 published support threads about AAC and MP4 audio problems in VEGAS Pro, a fix was confirmed in 6, and no two of those 6 were the same fix. Re-encoding or converting the source was suggested in 4 threads, [a separate WAV render](https://soundforgepro.com/vegas-pro-render-audio/) in 2, and 5 threads ended without a confirmed fix. The threads run from VEGAS Pro 14 in 2017 to VEGAS Pro 2026 in 2026\. Two aren't AAC-specific (the VEGAS Pro 20 thread where every render format failed, and an April 2026 thread that never named the audio codec), and one turned out to be AC-3; they stay in because the symptoms and the fixes people reach for are the same. | Symptom | Threads | Versions and years | What fixed it | | --------------------------------- | ------- | --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Won't import | 2 | VEGAS Pro 14 (2017); version not stated, trial suspected (2026) | Neither confirmed. Replies suggested rewrapping into MP4 or M4A, converting to WAV, re-encoding in Shutter Encoder and registering the trial. | | Silent event | 1 | VEGAS Pro 22 (2026) | Not confirmed. Reply: MediaInfo, re-convert with AAC or PCM audio, Add Missing Stream. | | Garbled or high-pitched | 1 | VEGAS Pro 23 (2026) | Confirmed: an input-remapping tool, not the media. | | Drift | 2 | VEGAS Pro 15 (2018); not stated (2026) | 2018: a hidden Internal-tab setting, confirmed by the poster and excluded here as advice. 2026: HandBrake or Shutter Encoder re-encode or proxies suggested, not confirmed. | | Render fails or comes out corrupt | 2 | VEGAS Pro 18 with Voukoder (2022); VEGAS Pro 20 (2025) | Both confirmed: a lower project sample rate; the Ctrl+Shift reset with cached data deleted. | | Render bitrate | 3 | VEGAS Pro 2026 (2026) | Build 143 confirmed by a user in one thread and named by staff in another, with build 189 as its replacement. [The third thread](https://forum.borisfx.com/t/21904?ref=soundforgepro.com) had no confirmed fix; staff offered the WAV workaround. | | AC-3 filed as AAC | 1 | VEGAS Pro 21 (2025) | A third-party AC3 tool, reported working and excluded here as advice. The official fixes are VEGAS Pro 22 build 248 and VEGAS Pro 23 build 278. | Six confirmed fixes and no repeats says the order of checks matters more than any single trick. MediaInfo or File Properties came up before any fix was tried in 5 of the 12, and in 1 of the 12 the cause sat outside the media entirely. The legacy AVC decoding toggle came up in 2 threads and was never confirmed as the fix. Read the file, update, then rewrap or convert, and keep the project-rate check, the input-tool test and the reset for the cases that sequence doesn't reach. ## Verdict: read, update, then convert My verdict: identify the stream, get onto the last build of your version, then rewrap or convert before you touch a hidden setting. Keep legacy decoding off unless you're testing one file, and switch it back afterwards. On VEGAS Pro 20 a stubborn AAC file is a conversion job, because build 411 is the end of the line and no build of that version names an AAC fix. On VEGAS Pro 2026, build 189 is the floor for AAC renders; on VEGAS Pro 2027, watch Boris FX Hub for the first patch after build 31\. VEGAS belongs to the Boris FX family now, and the [Boris FX hub](https://soundforgepro.com/boris-fx/) maps the rest of that lineup.