As I have clients who need to have accented characters in the artist name, I would like to keep these accented characters in the master files.
Most of the metadata is selectable from @CdText…@.
This means that there can be no accented characters in the metadata (the CD text is composed of ASCII characters only, not accented characters).
Thanks to @Justin_Perkins, I figured out how to use @CdTrackTitle@ instead of @CdTexttrackTitle@ to allow accented characters in the files for the track title.
What I understand is that there is no way (defined and forgotten) to set the metadata to a source other than CdText for any data other than the Track Title.
For example, the artist name is “Oxygéné”. If I put “Oxygene”, it doesn’t have the same meaning at all.
Did you find a solution in Wavelab to this problem ?
Yes, I know what you mean. The method I use allows me to have the accented song name be in the marker name which gets pushed to metadata, and the non accented name in the CD-Text track title which is also used in my naming scheme for safe file naming.
However, if the album title or artist name has an accent, I normally have to fix this in the 3rd party metadata app I normally just use for double checking things.
I don’t see a way to enter an accented album title or artist name and have that go to the metadata while the safer non accented version goes to the CD-Text.
It’s pretty rare when this happens but it would be nice to have better metadata/CD-Text entry options as the way it’s done now seems pretty nerdy and hidden.
This^^
There is no perfect solutions for the moment.
I’ll go with an external metadata editor for accented metadata in Master files.
But will keep avoiding accents in wavelab, as long as some projects may finish to a DDP.
Thanks again
For now, there is a good solution if the accented or special characters are just for song titles. If the accented or special characters are in the album title or artist name, I don’t have a great solution right now to send a safe version to the CD-Text but complete version to the metadata.
In other words, I don’t see how you can enter an album title that has an accent in the CD-Text editor (or anywhere) and have the accented version go to metadata for rendered files, and have the safe non-accented version go to the CD-Text.
I’ve only found a workaround for song titles, but not album title/artist name.
You have to type the accented and non-accented text in two different places.
One is the CD Text editor, and the other is the CD Track metadata dialog.
The CD Track metadata offers more or less the same fields as the CD-Text editor.
More typing of course, and two sets of text variables, but I can’t see how this can be avoided.
Thanks, I’ll look closer at the CD-Track Metadata area soon.
I think generally speaking, WaveLab could use a new approach to this and have one main point of entry for data that is easy to see (unlike the ID3v2 Metadata Window) and that info gets pushed everywhere, with an option to automatically reduce to ACSII friendly names for CD-Text.
I have a good test for this on a project tonight. The artist name has an accented character in it. Obviously, the CD-Text Editor won’t accept it with ASCII chosen, but I’ve put it in the CD Metadata window.
I made a little progress with this last night. As expected, you do need to enter the name in two places but I think it will at least save the need for editing in a another app.
I need to test more when I have time on a test montage that has no plugins so it’s faster to trial and error before saving a preset for it.
Yes. this is a pretty hidden and confusing feature that I never really noticed.
All that said, I do think a more clear and simple single entry point for the data (with the aid of spreadsheet input) that gets pushed everywhere with considerations for simplifying file names and CD-Text would really help clear up a lot of confusion, especially for newer users.
If you write in ID3v1 some Unicode data (anything with an accent, Japanese, etc.), there is a chance that the reader app doesn’t check if it is Unicode. (UTF-8). ID3v1 is an old standard without any character standard. WaveLab writes Unicode because this is the most universal standard.
If you write in ID3v2 some Unicode data, then if the reader app has no bug, it should understand Unicode (UTF-8).
If I understand well now, I think the best solution is the Third part program to modify accented metadata. Because managing two different Metadata settings and having to enter twice the infos looks very boring and source of errors, from one Wavelab project to another.
A “simple” automatic character “reduction” to ASCII for DDP would be good. Therefore we could only enter all the metadata once, with or without accents.
Do you have a map for all the metadata entries, fields and destinations please ?
