Topic: wavelab/cd extraction question......

[F.O.Bean]

get this, my audio programs are going haywire on me, now wavelab is saying that it cant save a file that is larger than 2 GB, well, when i click on 'information' in wavelab, it says that the file is 1.23GB, WTF???

it does it on some and not others, and NONE of my wavs are more than 2GB

[F.O.Bean]

heres exactly what this error says, when i KNOW the files are not even close to 2GB and i def have the free space on my HD

"The file has become too large: it is not possible to write files larger than 2 gigabytes!"

i am fuggin c lueless, please help me

[the yokel]

Bean, are you doing any processing when you get the exceeded 2gig limit message appears?  If so, then it's probably a temp file problem.  Either split the wave in half & do your processing or go into preferences & change your temp files from 32bit to 24/16bit.  The latter will give you less precise results but will increase your processing time.  

[F.O.Bean]

Bean, are you doing any processing when you get the exceeded 2gig limit message appears?  If so, then it's probably a temp file problem.  Either split the wave in half & do your processing or go into preferences & change your temp files from 32bit to 24/16bit.  The latter will give you less precise results but will increase your processing time.  

no, JUST resampling from a 48k file wav to a 44.1k file wav, which it lets me do flawlessly, but once i go to save as, it goes haywire, and says i cannot save a file bigger than 2GB!!WTF???

[Uncle Jimmy]

Yeah, i'd say it's a temp file thing, if i had to guess. maybe in a situation like that, there needs to be an old copy and a new one in the same temp file. with each 1.23 GB, there you go.

Just a shot in the dark, there.

FWIW, EAC is frowned upon not because of anything wrong with EAC but because it signifies that a show has been expanded from shn or written as audio from wav and then converted back again.

(One more note: now that you have EAC working, you can read about offsets and get that figured out. It isn't totally necessary, but the real hard-cores figure that out. then they can take a shn, expand it, burn it, rip it back to wav, shn it again and get the same md5 files. it's not easy to do.)

good luck, make sure you have all your firmware updates.

UJ

[the yokel]

I'd still give turning down your temp files a try.  This probably isn't a fix for you but a workaround that might work as well.  Try clicking render to a new file after you've resampled instead of saving through the normal manner.  

[F.O.Bean]

so just resample in the master part and then 'render'

it seems it has werkewd flawlessly out of the blue

now if i could just get my sf 7.0 werking again, guess wavelab resampling will have to do