Topic: 722 > Wavelab 5 Issues

[CQBert]

Help -

I have pretty much got things set up here but I am having issues with wavelab opening a 24/192 file.

The transfers are good - the files are complete but when I try to open them in Wavelab I get nothing but a flat line.

I will appreciate any thoughts on this as I am not the tech guru.

CQBert

[Craig T]

open as a raw file and set the bit depth and sample rate?  I seem to recall getting a file with a bad header once open as a flat line.

[nickgregory]

this is the problem that Tim and I had....wavelab has problems opening any file bigger than 2 Gb...once we knocked down the splits to ever 2 Gb, we stopped having the problem

[keepongoin]

so, you just chop it into 2 smaller files (or however many you need) in CdWave or something?

[Craig T]

http://www.gidluckmastering.com/audiohck.zip

cuts big wav's to multiple 2GB wav's and fixes the file headers.

[nickgregory]

so, you just chop it into 2 smaller files (or however many you need) in CdWave or something?

you can do that I guess...

what we did was set the 722 to start a new file every 2 Gb and that worked great

[CQBert]

I'll give it a try...

Thanks!

[F.O.Bean]

this is the problem that Tim and I had....wavelab has problems opening any file bigger than 2 Gb...once we knocked down the splits to ever 2 Gb, we stopped having the problem

my weird problem about this was, i always had 16/48/44.1k files and they were NEVER bigger than 2GB, what gives knowledgable ones most of my LONG 16/48/44.1k wavs were about 1.25-1.50 GB each all i was trying to do was resample this stuff, maybe ihave to switch from32-bit float processing tomaybe 24-bit to take upless room just weird IMO anyway ya look at it

i have this same problem opening wavs in 16/48k, weird, cause the WHOLE 16/48k file is only about 1.4GB seems its ONLY in wavelab, and RARELY in sf 7.0, and i made my temp folders for them all in my biggest HD(many GB) guess i gotta split the files every so often so it worksbetter, but a PITA

EDIT: if anyonecan he out w. this weird error, thatwouldbegtreat,i like wavelab 5.0 thebest and it does thiscrap,so first person who helpsme out, gets a coupledvd's full of some of mybest tapes

[Scooter]

have you installed the update ffrom steinberg??  v5.01A build 231.  Where were these files recorded (jb3, d8 etc)??  I've been working w/ Wavelab 5 since it came out, never had an issue like this yet.  If the file is under 2gig, and the header is legit, you should have no probs... 

[Chris K]

bean
i had this happen to me. i had a 1.5gig file that i was trying to reample. wavlab 5 would spin its wheels and when the process was over it would spit out an error message that the resulting file was going to be over 2gig.

the workaround, open the file as normal, then instead of resampling, do
file>save as...

at the bottom, under "File Name" and "Save As Type" is a long button which might say "Wav/Stereo/48Hz/16bit/Attr" or somethin similar. click the box and another dialog box will open that lets you select different bit depths, and sample rates (amoung other things)

select how you want the saved file to end up, click ok, then save. might be a good idea to name it slightly different so you can distinguish between the two.

hope this helps
chris k

[trajhip2000]

Wavelab (even the most recent version) doesn't like files over 2 GB, and this can happen when you are processing 16-bit files (which may originally be under 2 GB) at higher word lengths (24/32-bit), since this can result in temporary files that are over 2 GB. I have run into this problem when trying to assemble 2 mono tracks, a mid and side signal, into one stereo track for processing with the Waves S1 processor - even tho the resultant file was only about 1.7 GB, for some reason Wavelab wanted to write a temp file over 2 GB, and it choked. The developers claim this will be fixed in a future release, but the expectation is this will not be just an update to the current version (5.x) but rather something like 6.x, so I wouldn't expect it anytime soon.

I have read that one possible workaround in some situations (like the one I ran into) is to use the Audio Montage setup with two mono files, but I haven't tried it, instead I assembled in Audition which has a 4 GB limit. There also is a rather clever way to do it in real-time by essentially playing the file back through Wavelab to process on-the-fly and re-record with automatic 2 GB splits, that has just been suggested in the Wavelab forum:

http://forum.cubase.net/phpbb2/viewtopic.php?t=10160

My problem now is I am recording 4-ch files at 24/96, and it's easy to go over 4 GB when mixing these, so even Audition chokes on them...

Steve

[Scooter]

you guys are correct about Wavelab choking when you are processing a file that becomes larger than 2gig because of processing.  This is a well known prob.  Bean's Q is not real clear, I thought he was saying that he can't even OPEN a 16/?? file that is under 2 gig.  He's getting a flat line.  If this is the prob, it has nothing to do w/ the 2gig limit.   

[CQBert]

To start with I have adjusted my max volume size on the 722 to 2gig...  hopefully to prevent any future issues.

What is the best way to take a 4gig file and cut it into two parts?  without loosing chunks?

Thanks,

CQBert

[MattD]

Will CD Wave open it? If not, you could try a batch utility ... I forget what it's called, but if you need it, I'll look it up for you.

[CQBert]

Thanks - I feel like a moron with this one..  not a clue