Audacity Forum

I'm using Audacity 2.0.3 still, with Win7. If I export a project as multiple WAV files, the WAV file metadata does not contain any track numbers, artist or album title, etc. They're blanks, while other software like cdex will gladly put in track numbers when ripping music.

So am I missing something? Does 2.0.4 improve this? Or is the only way Audacity can indicate track numbers, is in the filename? i.e. it will show
01 Filename.wav, 02 Filename.wav, but the only way it can put the track numbers in, is in the filename??

I've only seen one piece of software, a pricey professional package, that claims to edit WAV file metadata. Apparently there is no shareware or "cheapware" that will touch WAV files, beyond the filename?

hellosailor wrote:I'm using Audacity 2.0.3 still, with Win7. If I export a project as multiple WAV files, the WAV file metadata does not contain any track numbers, artist or album title, etc. They're blanks, while other software like cdex will gladly put in track numbers when ripping music.

So am I missing something? Does 2.0.4 improve this?

Yes.

If you subscribed to our announcements list or looked at our home page you would have learned that 2.0.4 now supports LIST INFO tags and ID3 tags for all seven default Metadata Editor tags.

More information here: http://wiki.audacityteam.org/wiki/WAV#Metadata .


Gale

Thank you, Gale! That's great news.

Dare I hope that next year might find a stand-alone WAV tag editor, or at least, a way to simply fix existing WAV files without importing, opening, and resaving them one by one?

hellosailor wrote:Dare I hope that next year might find a stand-alone WAV tag editor, or at least, a way to simply fix existing WAV files without importing, opening, and resaving them one by

If you mean "provided by Audacity", probably not.

Many of the more flexible ID3 tag editors will read ID3 tags in WAV files. Otherwise I think most people would edit tags of WAV files in their player application and accept that only that player would probably be able to read the tags.

I use dBPowerAmp to edit tags on the rare occasions I want to. It works as a shell extension, so you can right-click over a file to edit the metadata directly. It reads LIST INFO and ID3 in WAV files.


Gale

I don't know, Gale. It has been a year probably since I went looking for a WAV file tag editor, and at that time nothing (nothing) would do it, except supposedly one high priced professional app that of course was designed for the professional market.

Lots of things will READ the tags, but at that time, none wrote them. Windows7 of course refuses to edit the file properties (tags) in the same way it would edit MP3 tags, I haven't tried Win8. WMP isn't any help at all, although it can make a WAV file ripped from a CD with some of the tag data.

After more than three decades of PCs, it is surprising that there are still such basic gaps with no tools. I've seen numerous posts online asking for one, but any reply that says "Oh you can use..." is inevitably flat out wrong. Evidence that dogs can still access the internet.<G>

Audacity 2.0.4 is already installed and happy here, so at least that won't be a problem going forward on projects. The legacy library, otoh, still could use one.

hellosailor wrote: After more than three decades of PCs, it is surprising that there are still such basic gaps with no tools.

This particular gap is probably because the "WAV (Microsoft) PCM" file specification does not include any specification for metadata (it does not exclude the use of metadata either). On the other hand, BWF is an extension of WAV format, primarily used in professional applications, that does specify metadata.
My gripe is that 3 decades of PCs on, lousy quality MP3s are as popular as ever

No published file specification? How curious, I'd guess a legacy of the old days before "compatibility" was spoken. Still, it should be so hard to figure out what is in the files and how. Although I'll admit I tried "just" using a hex editor to change information, and that bombed. Probably because something is generating a check code and I didn't look for that.

Ratty MP3s don't surprise me in the least. I used to have extremely good hearing and whenever a high-end audio shop tried to convince me a pricier product was better, they'd be flustered that I could a/b the two apart. I did a hearing test last year and found out how much I've lost (not a lot, just the top end) which probably explains why so many things sound so much better [sic] these days. But tin ears...yeah, there's a lot of them around.

What I'd like to know is why so many CDs have track breaks that simply don't match up with the tracks. I've found some that need to come in Audacity (thanks again) to be stitched back together, so they can be split in the proper places.

hellosailor,

If you want tagged lossless files, I suggest using FLAC or ALAC (lossless compression) instead of WAV. The tagging is more standardized, and as a bonus the file size will almost be cut in half!

DVDdoug wrote:If you want tagged lossless files, I suggest using FLAC or ALAC (lossless compression) instead of WAV. The tagging is more standardized, and as a bonus the file size will almost be cut in half!

FLAC is one of my favourites - it's a well established standard and it doesn't have Apple or Microsoft changing the format every time they want to sell an update Tagging FLAC files is well supported in Foobar2000 (one of my favourite media players on Windows).

What I'd like to know is why so many CDs have track breaks that simply don't match up with the tracks.

I think it has to do with the drive and your ripping software. EAC allows you to detect gaps as a separate step. I've never had a problem and never bothered with it...

When copying individual tracks or copying a CD, I've never noticed a problem If I'm copying a CD, I'll rip to one big WAV file can create a cue sheet. Or if I'm ripping a "live" CD, I'll rip it to one big WAV file, then if I want to make separate song files I'll edit to fade-in and fade-out the crowd noise.