The index changes when you render eg. 10 files at the same time, at each individual render.
But it does not change if you manually render 1 file, then 1 file, then 1 file, etc..
If you want a specifix index, update the “Counter Start” value in the dialog.
Sorry but I dont really understand. The naming scheme shows that the file should be named with the track index in the name and int he preview shows that it is correctly named is named with the track index 09, however when rendered the track index is ignored? Are you saying that I have to manually input the track index when rendering a single file from a multiple index montage. That doesnt really make sense. So if I render only 2 tracks out from a say 10 track montage, they will be prefixed by 01 and 02?
I still can’t reproduce the problem.
Note however that when you render the titles of a specific group, the index starts at one in the specific group. But in all cases it should be there.
Please send me your audio montage (no audio file needed).
As well as the preset you use for the naming scheme.
With this information, I should hopefully be able to reproduce your problem.
OK, where do I send it?
Wavelab naming error.zip (110.8 KB) never mind figured out how to attach it
On your previous picture, you mention “all titles in group C”.
But in your audio montage there is no group C, only group A.
Nevertheless, I try “all titles in group A”, “All titles”, “selected title”, and in all cases the title index is there in the final file name.
I guess you know it, but in your naming scheme there is a path separator, meaning that a sub-folder is going to be created. Ok?
Are you using the latest WaveLab version, 13.0.20?
Hi, yes I know the naming scheme folder creation, that’s intentional. If I put all in group A or C and it’s a single title, the result is the same. I ma on the latest version of Wavelab, first thing I checked when this happened. Im on Mac OS 15.7.5 (24G624). thx.
Just to make sure this is what I get in the sub-folder.
(using “Render All Titles”).
What do you get instead?
01-Blood, Sweat & Tears_2444_V2 (for approuval).wav
02-Control_2444_V2 (for approuval).wav
03-Propaganda (Up Yours)_2444_V2 (for approuval).wav
04-Delusions_2444_V2 (for approuval).wav
05-Yann_2444_V2 (for approuval).wav
06-Whats The News Today_2444_V2 (for approuval).wav
07-Push & Shove_2444_V2 (for approuval).wav
08-Hymn for Mankind_2444_V2 (for approuval).wav
09-The Limelight_2444_V2 (for approuval).wav
I get the same as you. But testing it out I found some very strange which I could reproduce. So if I start up Wavelab fresh and render title group and just have one of the titles in a different group (eg. all in A except last track in C) then this title will be rendered with a 01 Index. However, if I first do render all titles and then run the render of just one title using “Title Group” then the index becomes correct. If I restart Wavelab and run the same thing the index will again start at 01.
Yes, this is what I try to explain earlier: the title index is relative to the title group, not to the album. Now, I don’t know if this is the right design or not (but nobody complained so far).
Well what’s strange is it seems only relative, if you havent run the whole group yet. And in the naming scheme it is called track index, so the track number on the album. I see no benefit of having it index to the group. I mean if someone asks me for a revision of just one album track then what would be the best way to do this so that I get the right track number without having to change index number or rename the file?
Use “Selected Title” as source.
In WaveLab 13.0.30, it will be changed to that the title index variable is always relative to the album, and not to the title group.
