Skip to main content
andyp85260690
Known Participant
September 27, 2023
Answered

Multiple programs to process WAV files—Any potential issues?

  • September 27, 2023
  • 1 reply
  • 264 views

Hopefully a straightforward answer for this.

 
I'm having some issues with WAV file playback on a hardware sample player. The manufacture has recommended that I use Audacity to export my files (a metadata issue, possibly? Though I make sure I don't include any in my WAV exports). I've spent the last year using Adobe Audition which I'd like to keep using for editing/processing. So if I export a WAV from Audition, open the file again in Audacity, then save it from there, does anyone know if I'd encounter any issues such as a quality loss, or any other potential headaches? I'm on an iMac running Ventura 13.3. Thanks!
This topic has been closed for replies.
Correct answer SteveG_AudioMasters_

Since metadata is inherent in Wav files, you can't actually avoid it, even if you want to. Even if you input no individual data, the structure is still all there. That's how they can tell what software you used to create the file! The thing about metadata in Audition is that you can alter it to say anything you want - yes you can even change the name of the software you used.

 

One difference with Audacity as far as wav files is concerned is that they are encoded using libsndfile (they tag the 'creator tool' line in the meta with it, so it's easy to tell. I can't see any other difference. But of course there's also nothing to stop you doing exactly the same thing with Audition - there's an option to use it for wav files if you want. It might well be worth saving your files using libsndfile - there are a lot of coding options, as you'll find if you explore the save panel. There's also an option to exclude metadata in your save, although it doesn't really mean this - it just means that the meta framework is empty. It really does clear it out though, so that may be worth experimenting with too.

 

Bottom line is that Audition can manipulate metadata far more extensively than Audacity can. All you need to do is find out which settings Audacity's libsndfile is using, and replicate those in Audition.

1 reply

SteveG_AudioMasters_
Community Expert
SteveG_AudioMasters_Community ExpertCorrect answer
Community Expert
September 27, 2023

Since metadata is inherent in Wav files, you can't actually avoid it, even if you want to. Even if you input no individual data, the structure is still all there. That's how they can tell what software you used to create the file! The thing about metadata in Audition is that you can alter it to say anything you want - yes you can even change the name of the software you used.

 

One difference with Audacity as far as wav files is concerned is that they are encoded using libsndfile (they tag the 'creator tool' line in the meta with it, so it's easy to tell. I can't see any other difference. But of course there's also nothing to stop you doing exactly the same thing with Audition - there's an option to use it for wav files if you want. It might well be worth saving your files using libsndfile - there are a lot of coding options, as you'll find if you explore the save panel. There's also an option to exclude metadata in your save, although it doesn't really mean this - it just means that the meta framework is empty. It really does clear it out though, so that may be worth experimenting with too.

 

Bottom line is that Audition can manipulate metadata far more extensively than Audacity can. All you need to do is find out which settings Audacity's libsndfile is using, and replicate those in Audition.

andyp85260690
Known Participant
September 28, 2023

Thanks so much for such a comprehensive answer—that makes alot of sense (even with my limited understanding of such things). Theoretically then, I can contiue to use Audition but give it the encoding that Audacity uses as that would be the only difference in the WAV files, correct? If so, I'll give that a try as I'd like to avoid using multiple programs if I can. Why this particular hardware has a problem with the Audition encoding is beyond me, assuming the manufactorer's theory is correct of course.

 

Very much appreciated—thanks.