Excuse this.

Excused.

I hardly if at all know the difference between bit and sample rate.

I noticed that.. therefore my post above (#13) .. and yes, Richard (post #22) - no leash

When you go to Files\Export. If you click on the file type arrow, do you see LAME listed at the bottom?


Mike

I don't know what the problem could be but I'll BUMP ya up. Maybe someone else knows.

Mike

AdamFH,

Sorry you went through the trouble of writing down the LAME instructions, but if you would have performed a search within these forums, you would have realized that back in 2005, I wrote the instructions for getting Lame to work in Sonar and also posted the link to an article that Craig Anderton wrote for using Lame in Sonar as well.

Craig Anderton SOS article 2005 ~~> http://www.soundonsound.com/sos/feb05/articles/sonarnotes.htm

Jesse G instructions from 2005 ~~> http://forum.cakewalk.com/tm.asp?m=627968&mpage=1&key=򙛨

I am glad that you were able to iron out your MP3 problems, but remember that most of the problems with simple task in Sonar have already been ironed our for use by other users. The reason for these forums is so that each user or forum member won't have to go through the same hassles as another. We learn from each others mistakes and benefit from each other triumphs, that is what makes this forum so great.

Make life simple and perform a search first.

Peace

I too was able to follow the instructions and got it working perfectly. Just in case anyone cares, if you send it for internet radio play, they usually want it at 192kbps and some places you sell mp3's won't take anything under 128. FYI.

I went with the Variable Bitrate option because it's supposed to be the best quality of the MP3's, so my command line looks like

lame -V2 --clipdetect -c %I %O

Worked great! Just make sure you hit save at the top of the page before you hit OK!!!!

just lie about where I live currently

I would if I were you. No sense in paying more for the same product just because of where you live. Do what you have to do.

I don't care what is not perfect in this. All I know is Adam has changed and I for one am delighted that Adam is being so positive. This is outstanding work. The important thing here is that Adam did the wok and then wanted to inform us all for our benefit. Good job Adam.

I say this as one that has Pro Audio 9 and thus I don't have a need for this. Adam you have my respect.

I wasn't aiming my post at you at all. It was for Adam really. Sorry that you were the one it was address to. You just happen to be the last on the thread.

The in reply to is often wrong.

ORIGINAL: AdamFH

I hardly if at all know the difference between bit and sample rate.

Bit rate is the size of each sample of audio in binary data. It has to do with how an analogue to digital converter takes a slice of audio and converts it to a binary number for storage in computer memory.

With an a 4 bit converter the range of values goes from 0000 to 1111. This gives a maximum of 16 different values. At CD quality, 16 bit words, the maximum value is 1111111111111111 or FFFF in hexadecimal, which turns into a maximum possible 65536 different audio slices for each converted sample.

The sample rate is the number of samples that the analogue to digital converter is processing per second. At CD quality the number of samples per second is 44,100 Herz (cycles per second), usually shown as 44.1KHz

When you see that 24 bit converters are capable of resolving 16777216 different sample values you get an idea of why you are going to see some significant benefits from using the higher bit rate, even when the sampling rate remains at 44.1KHz

PS I don't want to hijack this into a discussion on the merits of one rate over the other, I merely seek to offer an insight for the OP.

ORIGINAL: John

I know I should do everything perfectly. Sometimes I don't.

LOL - you're a good sport John

Can get by with 99 times?

Honest_Al

Surely it should read Patronizing_Al

The Cakewalk External Audio Encoder Setup doesn't seem to be working for me.
I have downloaded the lame dll and exe files and copied them to:
C:\Program Files\Cakewalk\Shared Plugins\Lame


Started the External Audio Encoder utility and filled in all the fields:

friendly name = Lame
extension = .mp3
Description = lame
path = C:\Program Files\Cakewalk\Shared Plugins\Lame
command line = 

Then I click "save"

The "Friendly name" disappears.  Nothing in the drop-down for "Friendly Name."
Click "close."

Go to File => Export => Audio and check the "Files of type" drop-down list, and Lame does not appear.  The old MP3 entry always brings up the "you need to activate..." message.

I'm running Sonar 8 PE 64-bit.  Do I need a different version of the free lame encoder? I looked for a 64-bit version, and don't see it.

According to the Sonar online manual, I should be able to see and edit my external encoder configuration using the  Cakewalk External Audio Encoder Setup utility, but when I re-open it I don't see any of the configurations that I've tried to create.  So I'm guessing that the configuration utility isn't saving anything.

I would go the easy route and simply activate the Cakewalk encoder, since I own a license for CWPA 9, but my CWPA 9 install disk got broken a couple of years ago... and the Cakewalk Encoder activation utility wants to see the media... apparently a serial number isn't enough proof.

Anybody got a cure for this pain in the ass?

Is a person that has no clue what they are doing better off exporting as a wav., downloading audacity and lame for audacity, and converting there? From something someone wrote, this seemed possible... Is that a difficult process, and does it take away from quality in any way?.. I don't see any point in having audacity taking up space if it will work in LE, so if I just need to change that 192 to something else, please do tell what that is.. :) (I'm recording acoustic guitar, voice.. 44.1 sample rate, if that makes any difference)

Personally I prefer to export the audio as a WAV file, and then handle the MP3 conversion outside of Sonar.  There are a few benefits to doing this...


Firstly, it's (often) much quicker to experiment with different MP3 settings on an already-exported WAV file, than it is to have Sonar re-render the audio AND do the mp3 conversion in one go for each set of MP3 settings you want to try.   And even if when not experimenting, I often find the need to do multiple different conversions.


Secondly I prefer to use all the features of MP3 encoding in a utility that's explicitly and only designed for the job.  And since I might be encoding WAV files that were not generated by Sonar, it maintains a level of consistency in approach when encoding to MP3.


Having said that, I think it's great that the Op shared the instructions as it's a useful thing to know how to do...

mysonar8


wish I could get it to install.. I keep getting an error message

well, you can't get help just by complaining.  what is the error message?  what exact steps are you using?  what version of lame are you using?  are you trying to use the lame executable or the raw code?  we'll have to have details to help you instead of just "wish I could get it to install."