Imported from the Apple Support Forums via the Wayback Machine 🔗
Yes, apparently it's a bug in Eclipse version >5.1.
But as you can't change the language code (which defaults to English anyway) and later versions of Eclipse have a CD-Text editor, what's the big deal? It would take a few seconds to fix it at the plant, so unless they're trying to hit you up for a "special handling" charge, I'd suggest that you told them to move ahead and fix it.
0
Apple Support Community member·
Imported from the Apple Support Forums via the Wayback Machine 🔗
so, this is a glitch with Eclipse 5.1 and higher and the language code is being burned correctly? i'm not sure how to confirm this.
the girl at the plant said the problem is easily fixed with the cd text editor, but needed written permission to make the changes from the client. my client called me wary of the plant making changes to the master.
thanks for your response, john. can anyone else (maybe from apple) confirm that the language code is being burned correctly?
thanks again, - nick
0
Apple Support Community member·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi Nick;
thanks for your response, john. can anyone else (maybe from apple) confirm that the language code is being burned correctly?
I can't speak for Apple, but I don't think that WaveBurner is burning any language code at all; in fact, I would suggest that the 'problem' is with Eclipse - which shouldn't spit out unnecessary error codes. The majority of CDs with CD-Text don't have the language code set, so Eclipse should have their preferences set so that the lack of this bit doesn't flag a warning, as most premastering software behaves like WaveBurner and doesn't set a language code. So Eclipse is (IMO) flagging the norm.
0
Apple Support Community member·
Imported from the Apple Support Forums via the Wayback Machine 🔗
OK - I got curious so I did a search - it seems that I was mostly correct, in that this is a known Eclipse bug: