No MP3/WAV Decoding on the 64-bit Build

If audio files will not decode, add properly or save correctly on the 64-bit build of InfraRecorder but the same job works in 32-bit, you have probably met the documented x64 codec difference — not a corrupt download and not a setting you missed.

The fact, verified from the official packages: the 32-bit build of InfraRecorder 0.53 bundles libsndfile support — its portable codecs folder contains libsndfile-1.dll with codec files including sndfile.irc, vorbis.irc and wma.irc. The 64-bit portable codecs folder contains vorbis.irc, wave.irc and wma.irc only: no libsndfile. Libsndfile is a library for reading and writing sampled audio files, so some audio decoding paths differ on x64, and historical user reports describe MP3 decoding in the x64 build as problematic. Both builds are the same final 0.53 from 2012, available from our download page; this guide sits in the troubleshooting hub because it is a workaround, not a repair.

What this problem looks like

  • An audio track that added and played in a project on the 32-bit build fails to add, decodes incorrectly or produces silence on the 64-bit build.
  • Saving or converting audio involving MP3 decoding behaves inconsistently on x64, while WAV-based work is less affected.
  • Data burning, ISO burning and disc copying on x64 are unaffected — no audio decoding is involved in those jobs.

Be precise about the distinction: the missing libsndfile affects decoding — reading audio files in. The separate MP3 plug-in affects encoding — saving tracks as MP3 out. Confusing the two sends people reinstalling the plug-in for a decoding problem it cannot fix. If the MP3 format itself is missing from the format list, start with MP3 Plug-in Not Appearing instead.

The workaround: use the 32-bit build for audio work

  1. Download the 32-bit portable build, ir053_portable.zip (4,764,169 bytes), from the download page. Portable avoids uninstalling your 64-bit copy.
  2. Extract it to its own folder — do not mix the two builds’ files or codecs folders.
  3. If you need MP3 output, copy the win32 lame.irc from the MP3 plug-in into this portable copy’s codecs folder and restart the program, as shown in Rip a CD to MP3.
  4. Open the same audio project or tracks in the 32-bit portable and repeat the job that failed on x64. Test with one track first and play the result.
  5. Keep the 64-bit build, if you like, for data and ISO work, and the 32-bit portable for audio. Together the ZIPs are under 10 MB.

The 32-bit build runs normally on 64-bit Windows — there is no rule that a 64-bit system needs the 64-bit build, and for this program the 32-bit build is the one with the fuller audio codec set. That is also why our general advice defaults to 32-bit for audio CDs from varied source files: converting troublesome source files to WAV first, then adding the WAVs, is a further workaround that sidesteps older decoding paths entirely, whether you use the installed or portable build.

What will not fix it

Reinstalling the same 64-bit build will not add a codec it never shipped with. Copying the 32-bit libsndfile-1.dll into the 64-bit codecs folder will not work either — a 64-bit program cannot load a 32-bit library — and downloading codec files from unrelated sites is a security risk with no verified benefit. There is no setting inside InfraRecorder that enables the missing codec, and because 0.53 is the final release from a discontinued project, no update will add it. The honest fix is the build swap above.

Choosing builds from now on

If your work is mostly audio — burning audio CDs, ripping and saving tracks, converting between formats — make the 32-bit build your default and avoid the problem entirely. If your work is data discs and images, either build is fine, and CD/DVD Burn Failed: What to Check covers the unrelated failures that can still happen. Understanding this one documented difference turns a confusing, intermittent-feeling fault into a two-minute test: same files, 32-bit portable, job done. Note it alongside the other platform quirks in InfraRecorder on Windows 11 if you are also on modern Windows.

A quick test that proves the diagnosis

You do not have to take the codec explanation on faith — test it in under five minutes. Take the exact audio file that failed on the 64-bit build and add it to a project in the 32-bit portable build, changing nothing else: same file, same computer, same drive. If it decodes and burns or saves correctly there, the variable you isolated is the build’s codec set, and the diagnosis is confirmed for your files. If it fails in both builds, the file itself is the suspect — convert it to WAV with a current converter, or replace it from its source, and test again. Either way the test ends the guesswork.

Record the result with your media notes. ‘These files need the 32-bit build’ is a durable fact about your library, and writing it down stops the same files causing the same confusion next year. It is also a good reason to standardise on the 32-bit portable on your USB stick if you move between machines: one build, the fuller codec set, and no per-machine surprises.

Keep both builds clearly labelled in separate folders, 32-bit and 64-bit, so a future session never mixes their codec folders. Half of this problem’s reputation for randomness comes from files copied between builds; clear folders remove that variable for good.

Similar Posts