Topic: optimizing wavelab for 24 bit

[rabhan]

aheeem: read http://24bitfaq.org/



1.21:

It should be noted that not all software packages share the same level of stability, bit-transparentness, human interface design, and ease and speed of file handling.  The author has found the Sonic Foundry products to provide a great balance of these criteria, while others have found Steinberg’s Cubase and Wavelab to be preferable.  Stability of a program also depends very greatly on the OS, drivers, hardware platform, and other programs and processes running in the background.  Be sure to see 4.2.2 for issues concerning the handling the limits of file sizes when recording and editing, as many programs are not capable of recording for extended periods of time.
 


and i believe you want 16bit temp files.

[dmonterisi]

so you want 16 bit temp files when recording 24 bit files?  

[dklein]

Wavelab and all sound recording apps are programs, not background processes. recording is NOT a background process.

what Windows is referring to with regards to "background processes" is internal services like Messenger, rundll, IIS, etc...

My understanding is this is about how much processor time windows will give to apps running in the background (everything but the single one running in the foreground) AND services.  Shouldn't be a problem with either setting - recording doesn't take much in the way of resources (that's why just about any old machine can do it).

[dklein]

so you want 16 bit temp files when recording 24 bit files?  

Temp files are for processing, not recording (things like amplitude adjustment, eq, fades).  But you certainly wouldn't want to take your 24 bit files and process them in 16 bit!

Wavelab records directly to the file without the use of temp files - and that's good because if you crash, you've still got a file to work with.  The only problem is that the header doesn't get properly written, which is why the file has data but can't be read.  The header contains info about the number of data chunks in the file (really, that's what they're called).  

[rabhan]

i had to set my temp files at 16bit, see this:

http://www.taperssection.com/yabbse/index.php?board=5;action=display;threadid=4755

[rabhan]

if you dont want to read the thread:

JON,

This is an easy fix.  Go into your properties, and change the default temporary file from 32-bit float point to 16 bit.  This should resolve all of the issues you are having with the 2gb file limit.  The temp file creates a 4gb file in 32-bit as oppposed to the actual size!

Daryan

[dklein]

ok...but then does it still makes sense to record in 24 bit.  I think your resampling process will drop to 16 bit resolution.  Something else, doesn't make sense here - if you have a 1.2GB 24 bit file, it should open as a 1.6GB 32 bit file.  (file size * 32/24)  This is what happens to the temp files when I open up a 24 bit file in 32 bit with Cool Edit Pro.

At the very least, try setting your temp files to 24 bit.

Wavelab help says:

This pop-up allows you to select a resolution for the temporary files that WaveLab creates when you work. You can choose between 16 bit, 24 bit and 32 bit float files. Some general guidelines:

 If you ever plan to export your files in 24 or 32 bit format, use this resolution or a higher one for your temporary files as well.
 Even if you only work with 16 bit files, selecting 24 bit for your temporary files can improve audio quality slightly.
 For less critical applications where speed and disk space are crucial factors, use 16 bit temporary files.

I have a 1.2 GB file I'm going to try the same thing on with it set to 32 bit.  Let's see what it does...

[rabhan]

well why cant wavelab do 24bit on my laptop with files that are only 1.5g?

[dklein]

this is some weird shit.  I got the same error.  Makes no sense...

I'll try cool edit pro for a resample on the same file - I've seen temp file in use by CEP that are >4 GB.

[dklein]

It's running...I'm off to a show.  I'll post the results later.

[dklein]

Well, Cool Edit Pro had no problem resampling a 1.7GB, 24/44.1 to 24/48.  And it did it in 32 bit format.  When I looked in the temp directory, the temp file created was 4GB.

I'd like to understand this a little bit more but so far I'd say I'm not really enjoying Wavelab 4.  I find the interface awkward and these kinds of limitations seem, well, limiting!  Maybe someone who knows the software well can give some guidance.  The only reason I went to wavelab was for the auto split feature on recording

On the other hand, I've always loved Cool Edit Pro and just upgraded to v2.0 and it seems just as easy with more cool features.  For recording, I'll have to check if it has autosplit or if it somehow bypasses the 2GB limit.

[dklein]

Looks like a wavelab limitation.  Apparently this board is moderated by Steinberg developers...
http://forum.cubase.net/forum/Forum3/HTML/004847.html

suddenly feeling quite down on wavelab as a serious tool.  

[Simp-Dawg]

i wish sound forge would do auto split...i really like sf for recording!

[rabhan]

i just found CEPRO 1.0, what are the advantages of 2.0?

also why is 1.0 or 1.1 better?

[rabhan]

just saw this:

"Cool Edit Pro is now Adobe Audition. Syntrillium. ... On August 18th, 2003 Adobe released  a rebranded version of Cool Edit Pro 2.1 as Adobe Audition™ software. ...  "