Quote:
Originally Posted by 24-96 Mastering  One plant delayed processing because of that Eclipse error, telling my client that "there is an error in the image delivered". Very, very annoying.
Of course the "error" can extremely easily be "fixed" (using Eclipse's own CD-text editor), but whether that option is explored at all, or whether the project is instead needlessly put on hold, will depend on the plant and the engineer present that day.
Indeed they will be fine. Hardly any of the common DDP authoring applications, to my knowledge, set the CD-Text language flag before Eclipse started showing it as an error - i.e. zillions of CDs in all kinds of languages have been produced and displayed just fine over the years. I assume that no CD players actually need the language flag to be set - if any did, they wouldn't have been able to play/display a great number of current CDs. Why Eclipse changed preferences to identify the absence of that flag as an error is beyond me. |
I was not aware you could change the cd text within eclipse...during image copy? may have been something that could be done in mastering, but never came up in my testing dept. We would sometimes reauthor ourselves with client permission if it failed more than twice and they didn't want to proceed "as is" with a waiver. (always with reference copy approval)
I agree, eclipse has gotten more and more sensitive with each new version and often would depend on the drives testing also...some drives would have errors that others would pass fine. Not to mention eclipse's explanation of errors were often vague and unhelpful. We often had to set certain errors to warning or ignore (including many of the cd text errors) after testing them and realizing that there was no harm done with a majority of the new errors.