I can’t render Files with accented characters in the FILE NAME.
In the invaluable video of Justin Perkins WaveLab Pro Workflows with Justin Perkins #10 | The Metadata Edition - YouTube @38:49 it is said that by checking the “Create windows compatible File names” check box, Wavelab replaces special characters (like “?”) by a “_”
But if unchecking this option allows the special characters to be in the file names, this doesn’t allow the accented characters the the file names.
And the rendering preset “24-bits Waves Tracks” is rendering “All marked regions” with File Name : “REGION NAME ARE USED”.
The fact is the rendered File names have NO accents, whereas my “Region Names” have accents yet.
I assume that by “Region name” it means “Track names” or what else could it be ?
And if you’re asking, I even tried to render by selecting “All CD tracks inGroup”, cause this applies the File Name : “CD track names are used”, and the result is the same : the rendered File names have NO accents, whereas my CD track Names have accents yet.
Actually, I find no way to render file names with the accents present in the track names.
FWIW, I have never tried to render files with accents in the name because it seems like a recipe for an issue downstream.
I think that video is somewhat current but I currently work in such a way that the accurate song title is each marker name and that name is pushed to metadata, but in the CD-Text Editor I use a simplified version of each song name (if needed) that complies with ASCII for CD/DDP RedBook compatibility and is also safe for file names.
Is there a reason you need accents in the file names? I guess PG will have to answer if WaveLab can put accents in the file names.
You may also want to specify if you’re on Windows or Mac.
I totally get this. However, part of my email template explains that file names for titles with special characters are simplified to prevent downstream issues. For example, Windows is much more sensitive to special characters in file names, especially if you’ve zipped the file on a Mac and it gets unzipped on Windows.
Other distribution systems may also reject or struggle with file names that have special characters.
I think it’s best practice to keep the file names basic and communicate that the name isn’t necessarily the official title that everybody will see.
The web-player I use for mastering approvals can display the metadata within the WAV files so my clients see the official titles in the web-player, as well as on the PDF I generate from WaveLab which has the real official titles with any special characters.
I simply explain that for CD-Text and file names, special characters may be omitted.
But still, rendering by selecting “All CD tracks inGroup” applies the File Name : “CD track names are used”, and the result is that the rendered File Names have NO accents, whereas my CD track Names have accents yet. Wavelab doesn’t do what is expected.
May be “CDtextTrackName” is used instead ?
No reason this should not work, as tests are often done for this.
The “Create windows compatible File names” is only about a few characters, and that has nothing to see with accented characters.
The only place where there is a limitation is for CD-Text because the standard does not allow anything but ASCII, or Japanese. Also, RIFF metadata should better be used with anything else than ASCII, because there is no stable standard for it.
Your post was not so clear, I must say. Please give a detailed example of what you are doing that produces an unexpected result.
If you’re using some of my presets, you may want to remove the “CDTextTrackTitle” option in the Naming Scheme and reset it to be just “Numeric Prefix”. I think the “CDTextTrackTitle” option was overwriting the “Region Names Are Used” option.
By doing that, I was able to render files with special characters entered as the Marker Names.
Yes. That is what I experienced too for some reason, which is why I mentioned setting it to Numeric Prefix again.
Anything beyond that is experimental territory as I haven’t tried it and don’t plan to add special characters to file names or figure out how to.
I can imagine that some digital distributors and file systems might reject files with special characters and accents in the file name, or other minor issues may occur.
No problem. It’s not a bother, I just wanted to clarify the reasoning for the way the presets I made work. After experiencing an issue years ago where I used a song title that ended in a question mark to name the file, and having that file not appear for a Windows users after unzipping the zip file, I made an effort to keep the file names basic to avoid downstream errors, and just keep the special characters in the CD-Text which supports a small amount of special characters) and metadata in the WAV and mp3 files which has basically unlimited support for special characters.
