Wavelab 8.5.20
Loaded a 16 bit master. Rendered single format, used “Match input stream” option. The result is 32 bit files.
Philip
If you touched the audio in any way like a 0.01 gain change or dithering,fade in/out, it will go to 32 bits.
Open the bit meter to see what’s happening.
I think it always does that (32 bit result) if the render is from the Montage, even if no plugs, no gain change, and Bit is set for “Match Source File”. It does the same thing in 8.0.4 (32 bit result). I think it’s a question for PG whether it should do that or not, but that’s what it does.
It works as expected (16 bit result) if rendering from the Audio File workspace, even with gain change or plugs. That maybe seems a little odd if dither is not being applied, but that’s the way it’s working here with 8.0.4. Would need to remember to dither if using gain change or plugins.
yikes…, I will test tomorrow at the studio… It shouldn’t be doing that.
I always use my own presets when rendering. Usually use “16 bit,etc” and not “Match Source File”.
I usually never render something I didn’t process, so I have dithering “on” most of the time and I make sure it gets saved to 16 bit (or whatever I need) and don’t leave it at “Match Source File”.
The Montage is considered as a “32 bit float”, that is, the highest quality source, whatever its content.
Did a quick test…
– New Montage > 44.1 > added 16 bit/44.1 file > Reads 16bit on bit meter > Render “as is” with “Match Source File”…
Open file. Opens 32 bit but the bit meter shows 16 which means the audio wasn’t touched and is only a 32 bit container.
If I save to 16 bit it will just truncate without a problem (I suppose)…
– Did the same but I changed gain to 0.5 db… Opens at 32 bit > Bit meter reads 32 bit.
So I guess it wasn’t a bad idea to have my own presets obviously checking everything twice before rendering.
It’s great having all those metering tools in WL… The cost of the program is well worth it.
Thanks for the replies!
I’ve been thinking about this. If that is the case, why have the option at all when working with montages? “Match Source File” implies something else in my world. It’s just semantics but I think it’s confusing.
Philip
As soon as you change anything (level, envelope, plugin), the audio signal becomes 32 bit float (for DSP works), in the montage. Hence this choice to consider the montage as a 32 bit float entity.
Yes, this I understood. But why have the option of “Match Source File” when the output always will be 32 bit? Wouldn’t it be better if it said something like Match Montage Stream (32 bit float) or just remove the option to avoid confusion?
Or is there a montage scenario where “Match Source File” actually outputs anything else then 32 bit float?
Best,
Philip
1 Like
A file format is a preset that can be applied on montages and audio files. Hence the naming had to be chosen generic.
I really wish we had the old behaviour whereby the rendered file from an audio montage could be set to 16bit. I use the montage for sound design in games and having to convert every file to 16 bit after is a frustrating waste of time.
having to convert every file to 16 bit after is a frustrating waste of time
You don’t have to do this “after”. You just need to specify 16 bit in the render file format options, and you get what you need.
Philippe
And if you tick the checkmark it will also be remembered as preferred file format.
This render feature is yet to be fixed, where all selected clips are rendered as 32-bit float files from Montage. Wavelab show 32-bit float even though files could be of 24 bits or 16 bits.
There was a bug in WL6 where all clips were rendered in 16 bits and no option existed to change bit rate of rendered clips from Montage.
There is nothing to fix.
The output of a montage is 32 bit float by obvious design (this is an audio processing engine).
If you want a lower bit resolution, you have to select it explicitly.
1 Like
The Previous two menu of Channels and Sample Rate are matched to the source file, I thought Match source file should also match to the bit rate of clips.
If you were giving an option to only render 32-bit float by default, to an audio montage I have with 30 clips of 24-bit files, the “Match Source File” word has no meaning before that?
If that is the case, why is this menu of “Save As” showing the right bit rate of source file? Although it is not a Montage.
“Source File” means “Audio File” if you process an audio file.
“Source File” means “Audio Montage” if you process an audio montage.
Clips are based on audio file, but they generally undergo all sorts of processing like levelling and plugins. Hence their original bit resolution is lost in these processes.
Thank you for explaining.
Even when the original bit resolution is lost, it would have been easier workflow to edit or level files and render in what resolution it was before.
Melodyne export failed to incorporate render in source file format.
You edit a track, and then you open Wavelab to find the bitrate of the file, which is not seen anywhere in Melodyne and then choose the same bit and sample rate again and export.
Good tool to see original everything before processing and after is “Mediainfo”
and of course in WaveLab also File > Info
sure there is more ways…
regards S-EH