WaveLab Pro 12
Version: 12.0.51 Build 15 - x64
Hello:
First I will say I’m new to WaveLab, although I’ve been recording since the 70’s. Thanks in advance for any assistance.
When I render uncompressed files (32 & 16 Bit WAV), the album title appears in the song title field instead of the song title. I’ve tried changing the naming scheme but it doesn’t seem to have any affect. You can see in the first screenshot I have the CD Text Track Title selected to appear as the Name. But in the second screenshot, you can see it’s not working because the name that appears in the title field should be the same as the file name minus the number prefix. Instead the song title is the album title. I had the same problem when I first rendered the compressed files, but I fixed that by changing the @CDTextTitle@ to @CDTextTrackTitle@.
I’ve tried various attributes in the naming scheme but it always wants to pull the album title.
Two questions to help solve this:
-
What are you choosing as the “Render Source”? Sometimes people choose to render Clips instead of “All Marked Regions” which would be the traditional album/CD Tracks.
-
What have you entered in the CD-Text Fields? Can you show a screen shot? My brain is a little fried after a long day but it would help to know if what the correct intended titles are for the song name(s) and album title.
Hi Justin:
Thanks for responding. I have “All Titles in Group” selected and I chose group A. - See the first image in the attached screenshots.
The following screenshots are the CD Text settings for the album and the first three songs. I didn’t include all of them, but they follow the same pattern for the remainder.
Thanks for the info. I’ll try to digest this and follow up later but it might be enough info for PG to help weigh in too.
Initially it looks correct so I wonder if the “Title” display in your 2nd screen shot of your original post is meant to display the Song Title or Release Title.
Wherever that’s from is not a field I’m familiar with. It must be grabbing that info from some metadata within the file is my current assumption.
Have you checked what the metadata looks like if you load the WAV file(s) into the Audio Editor of WaveLab or checked the metadata in a standalone metadata app?
The last thing would be to see if you get different results if you ignore the Title Group option and choose this render setting:
Hi Justin:
I’m attaching an example of what I believe is the correct information for a .wav file. I’m including a screenshot of what a CD song listing should look like in Windows File Explorer.
At the top of the screenshot is the Queens of the Stone Age CD - Era Vulgaris and it’s associated songs/information. You can see the first column appears to be the File Name (since it has the track number), the Title, which is the title of each song, the Album name/title, and the Authors (Queens of the Stone Age). Next to that I’ve included a screenshot of the properties of the file and you can see the information is presented just the same, with the Title, Contributing Artists, Album etc.
Below that I have a screenshot of how my data looks with the same columns shown. As you can see the Album field is not populated at all and as previously discussed, the Title is the Album instead of the song title.
Below that I added the Filename to my listing and it shows the same info as what’s in the Name field. It’s weird that the file extension is showing in both name columns. If it was the actual song name, it shouldn’t have the file extension (.wav) - I would think. I also included a screenshot of the properties of the file.
Lastly at the very bottom, I’ve included a screenshot of how the compressed files came over. You can see that the compressed files were written correctly. So it appears to only be an issue with uncompressed .wav files.
Is it possible, since I’m using the very latest release of WaveLab, that this is a bug and the mapping is incorrect?
Sorry to be a pain and thanks for your help.
Thanks for the info. I guess the next thing to check would be the Metadata Tab in the montage in which you are rendering the files from.
The Naming Scheme is for naming the rendered files, which seems correct. Windows Explorer must be also displaying metadata within the file.
It would be interesting to see what the WaveLab Audio Editor displays for embedded Metadata and if the album title is somehow added to the song title field, with no other info.
You may need to make sure that your metadata setting is not mapping the album title into the song title field.
This is how mine is set:
Hi Justin:
The compressed meta data (IDE v2) is coming through correctly. It’s the uncompressed .wav files that don’t have the correct information on them.
Maybe I’m mistaken, but I don’t think the metadata tab is used for uncompressed .wav files. I believe the CD Text is what’s written to .wav files. I don’t even see an option to generate .aiff uncompressed files, (but maybe I’m mistaken), so I don’t know about those. They’re irrelevant for this discussion anyway but it would be the only other completely uncompressed audio format I’m aware of.
I did an experiment and put plain text in the CD-Text Editor. You can see this in the attached screenshot. I put “Album Title Field” in the Album Title field, etc. and they came through just as I assumed. I think WaveLab’s technical support is going to have to fix this one, but maybe I’m completely misunderstanding how this all works.
I think PG will have to weigh in at this point. I’m on Mac and don’t have Windows but whether I render an mp3 or a WAV, the metadata is fully embedded and correct.
Sorry I could not help.
Hi Justin:
Who/what is PG? Should I contact Steinberg support?
Again, thanks for all your help.
PG is the creator and main developer of WaveLab and he is active on the forum here. Hopefully he will see this and respond.
That’s typically more direct for WaveLab related issues than the Steinberg support portal.
OK, I’ll keep my fingers crossed. Thanks again.
But after looking at your post again, the Metadata Tab is absolutely used for WAV files. CD-Text is just for CD-Text, but you can push certain CD-Text info to WAV files when rendering them.
Yeah, that makes sense, but from my experiment of putting the text in those album fields, it seems like that’s whats coming through. - And maybe that’s the issue itself, - it’s happening but it’s not supposed to.
All I can say is to check your Metadata Tab settings and make sure the proper settings and mapping are occurring to populate info from CD-Text and other areas.
Whether I’m rendering WAV or mp3 files, the info is embedded the same way with no extra work needed.
I copied the settings you have in your screenshot above and got the same (incorrect) results unfortunately.
I’ll keep experimenting, but I’m hoping PG will respond. Thanks.
Have you checked one of your files in the WaveLab Audio Editor or any other app that is known to display metadata accurately from a WAV file?
See attached. I still wonder if this is just a display issue with Windows Explorer:
Hi Justin:
OK, I think I’ve figured this out. It looks like all data for .wav files is coming from the RIFF tab in the metadata.
So here’s the list, RIFF fields on the left, .wav file Details on the right:
Name: Song Title
Copyright: Copyright
Genre: Genre
Artist: Contributing artists
Date: Year
(ITRK) Track Number: #
Product: Album
The file name is coming from the CD Text Editor - Song Title
The only .wav info I don’t see is the Subtitle. I can’t find if or where that would map from.
I understand the idea is to reference the CD Text fields using the @ so I’ll be replacing hard text for those where it makes sense, but at least I know where the data is coming from now.
Thanks for your help.
Interesting. If the Windows Explorer is using RIFF information to display metadata from WAV files then you may want to update your default metadata preset to populate the desired fields from your source WaveLab montage.
I personally really just pay attention to ID3v2 metadata which seems to be what most consumer apps use in my experience but maybe I’ll take the time to update my preset to include better RIFF population.
Thanks for taking the time to map this out.