Topic: 722 > Wavelab 5 Issues

[Craig T]

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

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

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

[F.O.Bean]

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]

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]

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]

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]

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]

Does 4.0 do 24 Bit?

Not sure...

CQBert

[MattD]

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

[CQBert]

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]

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]

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!