Taperssection.com
Gear / Technical Help => Post-Processing, Computer / Streaming / Internet Devices & Related Activity => Topic started by: John R on April 08, 2006, 05:36:10 PM
-
align on sector boundries or no?
-
fix sbes first ;D
-
If you use cdwav to split tracks, it *should* be unneccessary.
-
newer versions of frontend correct SBE's while encoding
-
newer versions of frontend correct SBE's while encoding
If you use cdwav to split tracks, it *should* be unneccessary.
-
newer versions of frontend correct SBE's while encoding
If you use cdwav to split tracks, it *should* be unneccessary.
well from first hand experience, i have tracked about 5000+wavs in my experience w/ cdwave and still get them occassionally, and thats after putting markers at the beginning/end of each wav, saving and then re-opening
-
thanks guys. goldwave apparently cuts tracks w/sector boundries also, no problem.
jr
-
newer versions of frontend correct SBE's while encoding
If you use cdwav to split tracks, it *should* be unneccessary.
well from first hand experience, i have tracked about 5000+wavs in my experience w/ cdwave and still get them occassionally, and thats after putting markers at the beginning/end of each wav, saving and then re-opening
not doughting you bud, and adding a couple 0's isn't that big a deal.
if it's the first track of many, it can add up to quite a few though. and, not that i'm likely to hear the difference, my goal is to keep stuff as close to original as i can. not that i'm right or wrong, just mho.
peace, bro
-
newer versions of frontend correct SBE's while encoding
If you use cdwav to split tracks, it *should* be unneccessary.
well from first hand experience, i have tracked about 5000+wavs in my experience w/ cdwave and still get them occassionally, and thats after putting markers at the beginning/end of each wav, saving and then re-opening
not doughting you bud, and adding a couple 0's isn't that big a deal.
if it's the first track of many, it can add up to quite a few though. and, not that i'm likely to hear the difference, my goal is to keep stuff as close to original as i can. not that i'm right or wrong, just mho.
peace, bro
same here bro, thats the most editing i do on my shows ;)
-
if you use cd wave to track there is no reason not to save as flac from cd wave. skips a whole step and if done right there will bo no SBE's.
-
if you use cd wave to track there is no reason not to save as flac from cd wave. skips a whole step and if done right there will bo no SBE's.
I just like to see frontend actually verify each fil;e tho, same reason i cant bring myself to use dbpoweramp converter
-
I test the files after ;)
-
if you use cd wave to track there is no reason not to save as flac from cd wave. skips a whole step and if done right there will bo no SBE's.
unless you're doing 24bit files...cdwav doesn't compress the files, just makes flacs that are the same size as wavs.
-
if you use cd wave to track there is no reason not to save as flac from cd wave. skips a whole step and if done right there will bo no SBE's.
unless you're doing 24bit files...cdwav doesn't compress the files, just makes flacs that are the same size as wavs.
not true at all. I flac all my shows this way and that just isn't true. in fact a while back I did some test of different size wavs using cd wave and frontend. the compression was exactly the same using either one. as for 24 bit some folks have found that cd wave doesn't compress 24 bit as well as frontend.
-
yeah, i've noticed it to be the same with 16bit files - cdwav compresses the same as frontend, but 24bit files don't compress at all in cdwav.
-
anyone tried using this : http://thor.prohosting.com/roh0205/
a nice all in one frontend, of course you still have to track em with whatever but this thing is real easy to use and you can generate st5's with the click of a mouse instead of dos commands