Author Topic: 722 > Wavelab 5 Issues (Read 6890 times)

CQBert · « **on:** March 28, 2005, 05:55:00 PM »

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 · « **Reply #1 on:** March 28, 2005, 06:05:13 PM »

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 · « **Reply #2 on:** March 28, 2005, 06:09:57 PM »

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 · « **Reply #3 on:** March 28, 2005, 06:14:00 PM »

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

Craig T · « **Reply #4 on:** March 28, 2005, 06:14:55 PM »

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

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

nickgregory · « **Reply #5 on:** March 28, 2005, 06:15:05 PM »

Quote from: keepongoin' on March 28, 2005, 06:14:00 PM

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 · « **Reply #6 on:** March 28, 2005, 09:32:53 PM »

I'll give it a try...

Thanks!

F.O.Bean · « **Reply #7 on:** March 29, 2005, 04:51:52 AM »

Quote from: nickgregory on March 28, 2005, 06:09:57 PM

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 · « **Reply #8 on:** March 29, 2005, 11:05:30 AM »

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 · « **Reply #9 on:** March 29, 2005, 12:29:42 PM »

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 · « **Reply #10 on:** March 29, 2005, 02:04:03 PM »

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 · « **Reply #11 on:** March 29, 2005, 03:46:39 PM »

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 · « **Reply #12 on:** March 29, 2005, 05:01:44 PM »

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 · « **Reply #13 on:** March 29, 2005, 05:04:21 PM »

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 · « **Reply #14 on:** March 29, 2005, 05:11:09 PM »

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

Craig T · « **Reply #15 on:** March 29, 2005, 05:35:48 PM »

I'll say it again for those who missed it...

Quote from: Craig T on March 28, 2005, 06:14:55 PM

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

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

F.O.Bean · « **Reply #16 on:** March 29, 2005, 06:27:04 PM »

my bad, i didnt mean it wouldnt OPEN a 16/48k wav, only when saving it spits out that '2GB limit' thing

so would this go away if i changed the processing to 24-bit instead of 32-bit float

guess i'll just stick w/ sf 7.0 for now

Scooter · « **Reply #17 on:** March 29, 2005, 06:32:46 PM »

gotcha. I do this; if i have a continous file that is large like that, but under 2 gig, i'll open it and first thing split it into CD length files. then go back and process the smaller files. no worries about reaching the 2 gig limit during processing. i don't know for sure that 24bit processing will make the temp files smaller, but i would think that it would result in lower quality processing...

CQBert · « **Reply #18 on:** March 29, 2005, 08:17:50 PM »

I am trying the utility... no good results.. After typing in the main file name I give it two sub names.. hit enter and poof.. they are nowhere to be found.

Again - I plead moron.. what am I doing wrong..

-T yo me for this one..

CQBert

CQBert · « **Reply #19 on:** April 06, 2005, 06:12:37 PM »

Looks like I took another step towards success.. The Cracker/Camper show has transfered fine, got it normalized and tracked..

I'd love some help with the creation of a DVD-a Audio Montage if anyone has some to give..

I may be slow at this but I will get it eventually.

CQBert

MattD · « **Reply #20 on:** April 06, 2005, 07:40:03 PM »

How's this for weird. When I tried doing a real time transfer, WaveLab 4.01 was the only program that didn't like the incoming 722 stream. It recorded it as 0 dBFS white noise. My sound card passed the digital audio through fine and every other recording app I tried was fine. Wavelab gets along fine with my other gear, too, just not this.

Weird.

CQBert · « **Reply #21 on:** April 06, 2005, 07:59:18 PM »

Does 4.0 do 24 Bit?

Not sure...

CQBert

MattD · « **Reply #22 on:** April 06, 2005, 09:55:02 PM »

Yeah ... used to do it before I had a means of transferring from Mac to PC with my ULN-2.

CQBert · « **Reply #23 on:** April 06, 2005, 10:11:57 PM »

That may be one for the support forum...

When I uploaded my first 24/192 the computer would play the wav but Wavelab thought is was nothing but flatline..

Tried to transfer again.. same result.. took the back up source for the gig and wrote it off

CQBErt

F.O.Bean · « **Reply #24 on:** April 06, 2005, 10:46:14 PM »

Quote from: Scooter on March 29, 2005, 06:32:46 PM

gotcha. I do this; if i have a continous file that is large like that, but under 2 gig, i'll open it and first thing split it into CD length files. then go back and process the smaller files. no worries about reaching the 2 gig limit during processing. i don't know for sure that 24bit processing will make the temp files smaller, but i would think that it would result in lower quality processing...

gotcha, excellent, +T scooter

its just a pain to open them incdwave, split the larger files in half, then re-open in wavelab, process, then re-open in cdwave to track

but i like wavelab 5.0 betterthan sf 7.0, and wavelab is MUCH quicker for the same job/task IMO

Scooter · « **Reply #25 on:** April 07, 2005, 01:00:28 AM »

Quote from: Bean on April 06, 2005, 10:46:14 PM

Quote from: Scooter on March 29, 2005, 06:32:46 PM
gotcha. I do this; if i have a continous file that is large like that, but under 2 gig, i'll open it and first thing split it into CD length files. then go back and process the smaller files. no worries about reaching the 2 gig limit during processing. i don't know for sure that 24bit processing will make the temp files smaller, but i would think that it would result in lower quality processing...

gotcha, excellent, +T scooter

its just a pain to open them incdwave, split the larger files in half, then re-open in wavelab, process, then re-open in cdwave to track

but i like wavelab 5.0 betterthan sf 7.0, and wavelab is MUCH quicker for the same job/task IMO

ya, wavelab seems to be much faster than SF for most tasks, thats why i switched years back. FWIW, if after you drop your track markers in WL, and then rclick markers>edit marker, then choose "quantize to cd frame", then use autosplit, i have not had sector boundry issues doing that. if this holds true, you wouldn't need cdwave. YMMV. T back to ya!