Just tried to burn some music cds with VV3 on a plextor 12/32. Did not see a burn-proof check box, nor is it mentioned in the documentation. Does VV3 support it, or does it have any other buffer under-run prevention?
It was answered sometime back, by SonicEPM I think. That's why there is a search option at the top of this window. In the long run it can save you lots of time and also take you to threads that add more insight to similar topics.
So-called burn-proof and other buffer underrun protection schemes are really part of the firmware for a particular drive. If yours has it, it should kick in by itself. Yes VV3 has a hook for it. Don't think you need to or should you change hidden system preferences to modify it.
thanks for the response. I did know there is a search option, and I actually used it. It did not turn out any answer. Could it be the topic was too old that the search no longer includes it? How long are the topics kept anyway?
Well, burn-proof is actually more than firmware alone. The writing software has to enable it on a per use base. Your words of "hidden system preferences" reminded me of the "internal tab" in the preferences, and I just took a look. Not surprisingly, there is an "Enable burn proof" option, and the default is "FALSE".
Read up on this (as in search the web for it, I don't have time to look up sources and cannot guarantee perfect quotes).
Burn proof technologies are supposed to drop a recoverable error on to a CD that the burner can restart after. This gives the drive enough time to refill its buffer. While data CDs contain error correction information, audio CDs do not. What good would burn proof do for you in Vegas? Maybe video CDs. I don't know about them.
did some search too, and ended up at the Sanyo site, the inventor of Burn-proof. It seems to me that burn-proof will stop writing when buffer underflows, as opposed to dropping an error (maybe that's just an illusion by Sanyo). It claims that it determines where to resume writing by comparing the data in the write buffer and the data already written. And it only leaves a small gap that is no bigger than a normal gap existing on any standard cd, cd-r, and cd-rw. Sounds pretty good, don't know how well it really works.
The Red book standard allows error correction just like other format. CD-r uses the orange book, but the audio disc (or audio portion of a disc) created with cd-r still goes by the red bood standard.
Here is an excertp of the red bood standard:
Data on a audio CD is organized into frames. Each frame contains up to 24 bytes of user data, synchronization, LECC (Logical Error Correction Code), and data for control and display. Frame are interleaved with other frames into a single, spiral so that scratches or defects will not destroy a single frame beyond correction. Rather, a scratch will destroy a small portion of many frames, all of which can be recovered in other frames.
why would you think audio CDs won't tolerate a gap?
But what is in that Logical Error Correction Code? How do audio CD players correct for errors? Most of them interpolate between two consecutive samples. Just a straight line. Lots of errors will result in reduced fidelity. My friends Alpine CD changer would sum the channels to try to get enough information for play back. This resulted in loss os stereo and high frequencies. My Pioneer in my truck seems to insert a random value in place of errors. Lots of errors make it sound like I'm listening to a weak FM station. How do I know what was happening? Because it was my song that I burnt on my Plextor 8/20 at varying speeds to test which speed had the best results. The same CDs would produce these different results in these two CD changers. Lots of people say to burn at 2x if you're sending a CD off to a mastering house. Doesn't work with my 8/20. 8x or forget it. I haven't done such exhaustive tests with my 40/12/40.
Do you want to burn a CD with burnproof technology that delivers results like this? Ever heard of BLER - Block Error Rates? Why would you care about the error rate if all errors were recoverable?
Red Book CD Audio can recover many errors losslessly, because the error correction is happening at the Reed/Solomon code level. What you're talking about is error concealment, which has to kick in when the error correction doesn't have enough information to work with.
Both CD Audio and CD-ROM use error detection and correction. CD-ROM has *more*, since unrecoverable errors are way more serious in an Excel spreadsheet than in *NSync's latest tune.
BLER also goes up with faster burn rates, so if you're serious about reducing BLER, burn slower. Then you don't even need BurnProof <g>.
Dennis:
Thanks for the clarification on the error correction for audio CDs. I guess it just sucks (at least compared to data error correction). So we don't want to depend on burn proof for audio. Or, can it be shown that no amount of burn proof kicking in affects CD-Audio audibly?
As for:
"BLER also goes up with faster burn rates, so if you're serious about reducing BLER, burn slower. Then you don't even need BurnProof <g>."
If BLER has anything to do with the errors I can audibly hear, I can disprove this myth. As I stated, my Plextor 8/20 produces garbage burns at 2x and excellent burns at 8x. My 40x seems to do fine at all speeds (so far).
I don't have statistics on how much BurnProof affects BLER and/or audible errors, but I would think it wouldn't make too much difference. For one, it doesn't have to kick in very often, and so therefore the errors (if any) would be pretty far apart and (in threory) not very big. So, they should be correctable.
Interesting to hear that your 2x burns are worse then your 8x burns. Perhaps that drive is more stable at 8x (like maybe it has some resonance at 2x that affects the burn?). I don't know.
Unfortunately, machines that measure BLER are expensive. Interestingly, the use a regular CD-ROM drive with an add-on card. Perhaps someday consumer drivers will have a way of dumping the same information, then you could measure your own burns (and commercial, stamped, CD's as well, they have plenty of BLER too!). I've always wished my CD player had a readout of BLER (or some other metric) so you could see how close a CD is to not reading, or if it's concealing errors, etc. I'm just a tweak, I guess <g>.