ISRC code in WAV file

I know that there is still not a worldwide standard for ISRC in WAV files, but as of now, where is the best place to embed the ISRC code in a WAV file and exactly what tab would I use in the Wavelab metadata options?

I should note that I want to make sure that the ISRC code entered in the montage is embedded into the WAV when rendered from the montage.

I already emded a lot of info to mp3 and WAV by default when rendering, but only the mp3 ID3 tag has a dedicated ISRC field as far as I can see.

There is no official place. But there is this one:

Thanks, I use this one already. ID3 doesn’t work with WAV though right?

I’ve heard of people finding a place to embed ISRC in WAV files so I wanted to check if you had a suggested place or had heard of anything like this.

The place that Sequoia uses is the EBU defined space. And they advertise as being the first to do so. But there’s space for this in Wavelab defined in this thread:
Metadata in wav has gotten extremely complicated.

Id3 v2 works with wav.
And this is also possible as bob points out.

PG, the Wikipedia page for ID3 says ID3v2 is widely used in MP3 and AIFF (where it’s stored in an IFF chunk called ID3). Then it says that this could be done in WAV, but isn’t. Are you the first to do this? I think it’s great if that’s the case, but I don’t think I’ve seen this anywhere else.

Wikipedia is wrong. ID3v2 is supported in Wav by a variety of softwares. For instance, VLC, one of the most used multimedia reader, supports it (try to add a picture to a .wav, from WaveLab, and it will appear in VLC).

Thanks PG. That’s great.
One question. Since the EBU standard for ISRC is one of the accepted (and possibly required) places to put the code, would it be possible in an update to include that block of text, with an ISRC variable, in a preset somewhere on the AXML chunk page?

Yes, I would also really appreciate a more obvious and official place to place the ISRC code in a WAV file

Could someone please help me understand the practical use for this. In the context that, for example, iTunes Producer still requires you to enter the ISRC manually.

How are you producing a report for a batch of files for a quality control check and have the client sign off on the ISRCs allocated?

Paul, you’re absolutely right. All of this still requires a lot of extra work entering from here to there. Last time I checked Tunecore it also required manual ISRC entry. I think at this point it’s more about just having the code in there somewhere, not that it’s going to pass on down the line smoothly. At some point the record labels will start asking for it in wav I think, just as they do for CD masters now. One thing that really surprised me is that the record labels or distributors don’t even use the ISRC field that’s in ID3 for their MP3s and AACs. They have their own custom fields in ID3 for the ISRC. It’s kind of crazy IMO, but I guess it works for them. You can’t buy a song off iTunes, open it up in a tag editor and look at the ISRC code in the ISRC field. It’s not there. It’s hidden in a custom field, and the field seems to be different for different retailers. CDs you can load and read the ISRC, but not AACs from iTunes or MP3s from Amazon. (at least the last time I checked a few months ago). Getting the ISRC from the Wav to the AAC or MP3 is mapping that they’re going to have to do.

The way I do it is from a montage, with a sheet like the CD report. Since I’m usually supplying album files just like the CD, it seems to work ok.

They have their own custom fields in ID3 for the ISRC

FYI, you can create custom ID3v2 fields in WaveLab.

Thanks PG, I didn’t know. Most record companies make their own AAC and MP3 files anyway (or the retailers do), but even if we made those files, iTunes puts the ISRC in a different custom field than Amazon does. And I think Amazon different than Google. So it’s sort of a no win situation. They sort it out on their end anyway. At this point, even if we could figure out ways to get it into exactly the right spaces in the ID3 in wav, they probably wouldn’t want that because they have their own systems in place for doing what they’re doing.

btw, I think you’ve done an amazing job with the metadata section. I can’t imagine any other program’s come close.

btw, I think you’ve done an amazing job with the metadata section. I can’t imagine any other program’s come close.

I agree :sunglasses:

I also agree. The metadata features are the main thing that keep me using Wavelab on a daily basis. I’m too far deep into the OSX world to use a PC (even in BootCamp) so in my opinion Wavelab is quite easily the best overall OSX option for mastering (especially if you need more than 2 audio tracks/lanes.

Looking forward to update 8.0.3!

PG, sorry, jperkinski’s and my ISRC request got followed by too many long posts by me, so got buried, but this was the gist:

Would it be possible to build into a Wavelab update a more elegant way of having the EBU standard ISRC coded in WAV? I know I can paste the EBU xml code into the axml box, but it seems like there’s probably a more user friendly way to build this into the program, with the requisite code already there, maybe even just a factory preset, I don’t know. The EBU standard is the way approved by IFPI and USISRC, so I think that’s going to be the official field the record labels are going to ask for when they start asking for ISRC in WAV.

Also, according to this article, the EBU way is the way Sequoia, Pyramix, and Sadie are doing it:

jperkinski, in the meantime you can copy and paste the following xml into the AXML box, and just leave it there, or save it as a preset. I’ve put the Wavelab ISRC variable in there so it will derive the ISRC for each file from the ISRCs in your montage.

<ebucore:ebuCoreMain xmlns:dc="" xmlns:ebucore=“urn:ebu:metadata-schema:ebuCore_2012”>
<ebucore:identifier typeLabel=“GUID” typeDefinition=“Globally Unique Identifier” formatLabel=“ISRC” formatDefinition=“International Standard Recording Code” formatLink=“”>

I will add such a factory preset in next version. At least it will be useful as a reference.

Thank you Philippe !

Excellent, thank you!

Maybe WL can help set the standard for embedding in WAV files which is long overdue.