WaveLab 4 -Manual in PDF? --whats on page 214?

  • Thread starter Thread starter juglesh
  • Start date Start date
J

juglesh

New member
supposedly it answers the following questions:

I cant figure out the diff render vs. save. lets say i record a track from vinyl. If use straight cuts, the bit scope says that the whole thing is 16 bits, therefore i shouldnt have to use render or dither. and i could use 'save'

However, if i use fade ins and outs, the bitscope shows 24 bits during those fades and therefore dither is necessary.

I can save the wave (with the fades) using 'save as' or i could use the render in the master section.

If i use save, does it just pick a dither option for me? or does it truncate?

and when i use render, will it resample the whole thing? or just where the fades are, leaving the rest alone?

thanks for your time,
juglesh B>{)}
 
Rendering "applies" whatever effects you have added to the master section. Save just saves. (BTW, there is no resampling involved in rendering - not sure where you got that from.)

If you simply save a 24 bit bit file, it will remain at 24 bits (even if it's effectively only using 16 bits). If you want to reduce it to 16 bits, you need to go to Edit > Audio Properties and change the bit rate to 16 bits. However, it is normally advisable to dither first. To do this you have to choose one of the dithering algorithms in the dithering section of the Master, and then render (apply) it. However, after you do this it will still be a 24 bit file (only dithered down to 16 bits). Now would be the time to change the bit rate in Audio Properties which will truncate the file to 16 bits.

At this point you are ready to Save.
 
dachay2tnr said:
Rendering "applies" whatever effects you have added to the master section. Save just saves. .)

no effects in the master section, just fade in/out at beginning/end

(BTW, there is no resampling involved in rendering - not sure where you got that from.)

ok, i meant to say dither. will it dither the whole thing or just the fade in/out? I record from analog at 16bits, do the fades, now bitscope says 24bits. so, if it dithers the fade, then gets to the unchanged part (should still be 16bit here) does dithering from 16 bits to 16bits do anything?

If you simply save a 24 bit bit file, it will remain at 24 bits (even if it's effectively only using 16 bits). If you want to reduce it to 16 bits, you need to go to Edit > Audio Properties and change the bit rate to 16 bits. However, it is normally advisable to dither first. To do this you have to choose one of the dithering algorithms in the dithering section of the Master, and then render (apply) it.

ok, got that, but

However, after you do this it will still be a 24 bit file (only dithered down to 16 bits). Now would be the time to change the bit rate in Audio Properties which will truncate the file to 16 bits.

huh?

At this point you are ready to Save.

so, i have to render then save? or is 'create specific file' the same thing?

my main concern here is that i dont mess up the main part of the song. Its not such a big deal to me whether i dither or truncate the fades.

thanks,
juglesh
 
The steps normally to go from 24 bits to 16 bits would be:
1. Chose a dithering algorithm in the master section
2. Render (applies the dither)
3. Change bit rate (Edit > Audio Properties)
4. Save

I was a little puzzled by the fact that you stated you were starting with a 16 bit file. So I duplicated what you are doing, and to my surprise you are correct, the bit meter suddenly reads 24 bits in the section where the fade is applied. However, the file itself still reads as 16 bit - both at the bottom of the screen and in the Audio Properties window.

That being the case, it seems like you should just be able to apply the fade and resave the file. I would save it under a new name and check that the fade remains smooth in the new file.

You might want to go on to the Wavelab forum ( http://forum.cubase.net/cgi-bin/cubase.net/Ultimate.cgi ) and ask why the fade reading at 24 bits if the file is still a 16 bit file. I'm pretty sure the program works with a 32 bit floating rate, but I don't know why it would output a 24 bit result in a 16 bit file.
 
Back
Top