I tried ripping a music CD for the first time to my HD ("Convert Audio CD to Audio Files")and ran into two problems. First, I get a "cannot open the local NERO databate" window. Second, I then attempted to continue and I get another message that I must either register for a "Lame MP3 Encoder" or if I select another MP3PRO option I must buy it. I'm at a standstill, and could use some guidance. I have the latest "good" Nero update.
The database error is just Nero doing an ET on trying to find the info for your CD, don't worry about that it is something you need to go into your settings about. As for encoding to LAME MP3, if you have a legal version of Nero Ultra or Premium you are entitled to a SN that will activate this feature, you can contact Nero to get one and they will email it to you. The MP3 Pro is a plugin that must be purchased.
__edit___ I linked to the plug-ins for Nero 6 http://www.bitburners.com/Nero_Audio_Plugins/ after I posted and re-read I realized we were talking about 7
I registered for the "Lame MP3", Nero e-mailed back with a new serial # (with the same number of digits as the one I received with Nero 7) with directions to place it where the Nero serial number is. I typed it in, and I got a message - that if I put this new # in, it may mess up the installation of Nero. Canned Precautionary warning??? Is this new (Lame MP3)serial supposed to replace the serial that came with my purchase?
No you do not replace your Nero Serial Number you need to add this one as a new SN. You will do it this way it works the same in either 6 or 7. Look in your StartSmart for the Nero Product Center, and you should get this screen. Your Lame Enc is a second SN you need to enter in order to unlock the encoder. If you can't find it then go in Nero Burning Rom, and you can get to it from there. Remember do not replace your original SN just add another SN.
I tried to enter the serial # per your instructions. No-Go. I e-mailed Nero Customer Service. They said they were aware of the problem, and that if I download the most current update that would fix it. I think I'll wait for the forum members to give the "all clear" before updating to a newer version. Thanks for your help.
