Cakewalk's LAME encoder is built in. We don't redist a dll. You must have something you manually installed.

Noel Borthwick [Cakewalk]
Cakewalk's LAME encoder is built in. We don't redist a dll. You must have something you manually installed.

Thanks Noel...
 
Does this mean that if I have previously purchased the cakewalk encoder and I am running Foxboro, when I use the mp3 export it is now using 3.99?
 
Keni
 

When i setup lame for some of my clients, I've been suing the following command line and all seems well. It was so long ago that I set this up, I don't remember what all the commands stand for except for %I nad %O being input and output.... I also know that changing the 320 (highest setting) to 192 etc. makes smaller lower quality files...
 
lame -b 320 -m j %I %O
 
 

Hi Keni:
 
If you paid for the Cakewalk MP3 Encoder activation, check your Cakewalk store account for the link to download the Activation file, if you're using SONAR X64, you may have to contact Cakewalk for the x64 Activation download link. The one in the store account used to be for the 32bit version of SONAR. I just keep the Activation file for both 32bit and 64bit, so I never had to download it again.
 
When you use the Cakewalk MP3 Encoder in Platinum (latest version) it uses Lame 3.99. Sometime during the SONAR 2015 release, Cakewalk, finally :), updated the Encoder to use Lame 3.99.

Thanks Thomas...

I must have the fike somewhere as your words sounded familiar... I think i activated the 64 bit version on my DAW... So im guessing its running the 64 bit version... But i haven't activated it on the laptop yet...

My generator hours are comming up so i'll take a look...

Also, Keni:
 
You shouldn't have to use any command line stuff with Lame. Just get Aaron's SONAR MP3 patch via the link to SONAR Utilities in Mudgel's signature. With Aaron's patch all you need to do is run the patch and select "Add All Mp3 Options," and select the bit rate you want via a dropdown menu in SONAR's Export Audio dialog. For example, in the "Files of type" dropdown menu of the Export Audio dialog, just choose something like "MP3 256 kbps-keep wav file or "MP3 256 kbps-discard wav file."
 
Or use the Cakewalk MP3 Encoder. :)
 
Hope that helps.
 

thomasabarnes
Also, Keni:
 
You shouldn't have to use any command line stuff with Lame. Just get Aaron's SONAR MP3 patch via the link to SONAR Utilities in Mudgel's signature. With Aaron's patch all you need to do is run the patch and select "Add All Mp3 Options," and select the bit rate you want via a dropdown menu in SONAR's Export Audio dialog. For example, in the "Files of type" dropdown menu of the Export Audio dialog, just choose something like "MP3 256 kbps-keep wav file or "MP3 256 kbps-discard wav file."
 
Or use the Cakewalk MP3 Encoder. :)
 
Hope that helps.
 

If you have the Cakewalk encoder you shouldn't be installing Aaron's patch over the top.
Cakewalk have complied their own version of Lame called TTSLAME. You don't want to go throwing another version of the Lame encoder int the mix and generate different reg keys that will call on a dll somewhere else.

Mudgel:
 
Aaron's Patch wont interfere with the use of the Cakewalk Mp3 encoder when a user uses it to encode mp3 files. Cakewalk's encoder references the TTSLame.dll in the SONAR root directory, and Arron's Patch makes bit rate selections available in the "Files of type" drop down menu of SONAR's Export Audio dialog which, when/if any are selected, reference the LAME encoder that is installed in the location Aaron's patch is installed to.
 
But if one has Cakewalk's Encoder activated, there is no need to use Aaron's Patch method for encoding Mp3 files. In that case, just use the Cakewalk Encoder. :)

But isn't that where you select files of this type MP3 when you export using the Cakewalk encoder? I think I really will have to uninstall the Cakewalk encoder and test all these others to see what's going on. I thought I had done this earlier but I may not have uninstalled Cakewalk's encoder properly.

The only way I know to uninstall Cakewalk's Encoder is to remove the TTSLame.dll, and if you do that, SONAR wont even startup!
 
And if using the SONAR External Encoder, just get a copy of Lame and place all the files in a isolated location and folder that will just be used by the External Encoder, and set the Path of the Cakewalk External Audio Encoder Setup dialog to that particular isolated folder, and it will not interfere with any other Lame installations you have. The External Encoder will just reference the Lame library you have in that particular folder.