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

[F.O.Bean]

just wondering if anybody else uses it for audio cd extraction?

i have never used eac or dae or any of that, just wavelab for cd extraction, is this a good thing???

pros?? cons??

seems to do the job, but i know ppl gripe about eac right??

thanks,
  bean

[F.O.Bean]

anybody use it for extraction at all???

[Uncle Jimmy]

No. Use EAC.

[F.O.Bean]

No. Use EAC.

really?? any reason why??

[Uncle Jimmy]

Yeah. It's a bit-perfect audio ripper that mostly only rips. That's what it is for. It has several options to configure to your system and get the most out of your unique set-up.  

I started using it because it is the etree standard.
I still use it because there is nothing else like it.

Hope this helps. If not, check:
http://www.exactaudiocopy.de/

enjoy!

J----

[F.O.Bean]

Yeah. It's a bit-perfect audio ripper that mostly only rips. That's what it is for. It has several options to configure to your system and get the most out of your unique set-up.  

I started using it because it is the etree standard.
I still use it because there is nothing else like it.

Hope this helps. If not, check:
http://www.exactaudiocopy.de/

enjoy!

J----

thanks bro, +T jimmy

i will def check it out, i also may have to do a bit test on wavelab

[Uncle Jimmy]

here's just a couple things, since it seems you will be trying it out. There are different paranoia levels of error correction. This means that it will attempt to read a bit a certain amount of times (dep on the setting) and will take the statistically better result. In other words, when you are doing a really beat up disc ( i know... no one here ever uses their masters in the car or loans them to your girlfriend or whatever....) and it hits an error, it will try a bunch to get it right. If it can't, it will let you know in the log report the exact location of the suspicious position so you can edit any pops or glitches that would be a result of the bad sector or bit or whatever.

Then, on top of that, if you have a really rough disc (i know, i know, no one ever leaves their cd's face up for that cat to sit on and dig her nails into) you can use the "burst mode" which just blazes through a one-pass. Sometimes this is the only way to do it without EAC grinding to a halt. Then you can listen and be the judge yourself.

So, technically, it is bit-perfect when you set it to be, but that is a minor detail. It's the best ripper.

Good luck,
J----

[F.O.Bean]

trying now, thanks bro

[F.O.Bean]

oh yeah, which versiuon should i d/l??

[Uncle Jimmy]

the newest one should work, but if it doesn't, just go back one at a time. make sure you have and astpi layer installed and make sure the compatability mode is set right. the website should have that info for ya, but if it doesn't and you are having trouble, let me know and i'll continue to help if i can.

UJ

[F.O.Bean]

i d/l'd the 3rd newest one, not thew pre beta, the 11 one

it werked, but WOW, what freakin setting should i go on, this seems TOO complex honestly

i dont extract that much stuff at all, but man, id rather do it right, just looks really confusing at first

anybody have any "settings" for me, like really specific ones;-)

thanks for your input guyz

bean

[Uncle Jimmy]

OK, here's the thing. (Not infront of my PC right now, so i'm working from what is left of my short-term memory).

When you go to the drive options (might be EAC options... there are two) page, a box will pop up telling you to be careful of your setting. When you click OK, the drive options will come up and you can look at the tab that has secure and burst modes (maybe 1 more) as extraction options.

On the bottom of that you can examine C2 features and cache features. run those tests and it will configure the extraction mode for your drive. Most of the rest of the stuff is perference. feel free to look around, you wont hurt anything.

One thing i use a lot is the filename convention. when extracting, you can tell it to name the file whatever you want. for a 2 cd gov't mule show from feb 2, 1999 i would say:
govmule1999-02-02d1t%N

this will name the files :
govmule1999-02-02d1t01
govmule1999-02-02d1t02
govmule1999-02-02d1t03
...

[F.O.Bean]

+T jimmy, thanks bro

[Uncle Jimmy]

glad to help. let me know if it is working out for you after you have done some stuff.

peas,
UJ

[F.O.Bean]

one more q, why is EAC frowned upon in lineage???

i mean it is just an audio grabber

[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