• SONAR
  • TUTORIAL: Getting LAME MP3 Encoder to Work With SONAR (p.9)
2015/07/18 02:52:22
mudgel
thomasabarnes
Aaron's utility is useful to an extent, but it doesn't have ID3 Info support.
 
I hope he's OK, though.
 
EDIT
 
OK, I wasn't aware, but Aaron's MP3 Patch has limited id3 info support (three fields of id3 info), but you can't enter id3 info inside SONAR. You have to enter the id3 info before you apply the patch.
 
Heck, it's only like $9.99 now to get the activation for the Cakewalk MP3 Encoder. And ID3 info encoding is comprehensive. I think it would be worth it, just to buy the activation. The free stuff is lacking in it's feature set and/or doesn't have the convenience to be used without leaving SONAR. 
 
 


I should really have mentioned that it is the best of any free version that can be connected to Sonar.
With the Platinum update to MP3 export features a lot of people aren't aware of the improvements.
Aaron's patch is sort of obsolete except for any die hard who won't fork out the $10 to use the Cakewalk one which is also permanent as each subsequent version always picks it up.
2015/07/18 03:55:49
thomasabarnes
Roger Mudgel. I hear you.
 
I'm gonna update to Platinum sooner or later.
 
Also, I went to softpedia and saw the reply Vern C mentions. It's good he's been active somewhere 3 months ago. And hope he's OK at present. 
 
He also wrote of plans (under Future Plans) for some extensive ID3 info encoding updates on his to-do list. See: http://www.autohotkey.com/board/topic/66927-aarons-sonar-mp3-patch-v564/ He says he's been waiting for some command line bug to be fixed in SONAR. He hasn't had much luck in getting X3 running well for him, according to what he wrote in the comment post at softpedia I linked to above. So, it makes me wonder if the thing he asserted to be a bug has been fixed, and if he still plans to make updates to his Patch.
 
Anyway, his patch is a good freeware for SONAR users who don't have the Cakewalk MP3 Encoder activated in SONAR.
 
Edit:
 
Oh yeah, the change log for his Patch reflects versions up to 5.6.5.0. I don't see a working download for any version pass 5.6.3.0. The download for the 5.6.4.0 version available via one of the links I posted above is for version 5.6.4.0, but the download link doesn't work for me. And according to the change log 5.6.4.0 and 5.6.5.0 were released in March 2012.
2015/07/18 04:08:56
mudgel
I've asked again that he contacts me and maybe this time he will.
2015/07/19 02:05:54
kevinwal
Thanks, mudgel for posting this!
 
Hey guys, I know this seems way too complicated, but don't give up, Lame happens to be an excellent encoder that produces very high quality output. It's just a little opaque, having been developed by nerdy Unix people (which I once was.) For most people, the settings you really need are actually pretty simple.
 
You should create a system restore point before  you starting copying files anywhere into the programs subtree. That way, if something gets munged up it's a quick restore to fix it. 
 
First, I downloaded the zip containing the 64 bit binary files. I then extracted all the files and dropped them in C:\Program Files\Lame. Once that was done, I set things up in the external encoding utility dialog:
 
For Path, I put C:\Program Files\Lame
 
For the Command Line, I have this:
 
lame -V0 --tt %T --tg "Rock" --tl "My Awesome Album Name" --ta "My Awesome Band Name" %I %O
 
The first thing to understand is that the %T, %I and %O names are placeholders for values that Sonar will provide when Lame runs. You can see the various attribute names and their meanings at the bottom of the external encoder dialog.

%T The song title from the the project info dialog
%I The name of the WAV file that Sonar generates when you export audio; this will be the input to Lame.
%O The name of the MP3 file that Lame will generate.
 
Next are the parameters to control the Lame encoding:
 
-V is the parameter that specifies the quality setting for Variable Bit Rate. It defaults to 4, and decimal values can be specified, like: 4.51
0 is the highest quality but produces bigger files. 9.999 provides the lowest quality with much smaller files.
 
Since file size matters very little to me, I use 0, the highest quality setting. 1 and 2 also produce very good output with somewhat smaller sizes. Experiment to see what balance you're happy with.
 
Next are the parameters that specify how to tag your music file with information useful to the user. You can specify the title, the artist name, the album name, you can even embed an image of your album art in the file. This data is used by music services and media players to show the user.
 
Note that these parameters start with two dashes "--". They won't work with one. Ask me how I know. The lame settings I use are:
 
--tt %T  - this tells Lame to use the title provided by Sonar. You can also just enter a literal name like, "My Awesome Song".
--tg "Rock" - this tags the genre as "Rock". This comes from a list in the help docs, or you can run Lame from the command line to get a list, like this:
 
lame --genre-list
 
--tl "My Awesome Album Name" - the album name. I change this a lot, obviously.
--ta "My Awesome Band Name"  - the name of the artist. I also change this as needed.
 
And that should produce a very good sounding MP3 tagged with useful information about your song. For most of us it's really all we need unless your sending the file to some service with very specific requirements. Whatever those may be, Lame can no doubt do them, it's really very capable.
 
I hope this helps you!
2015/07/19 02:24:34
mudgel
That's a great resource but you know for most folks it's just as easy to pay $9.99 download a file, run it and it's all done for you. Especially since Cakewalk have upgraded to Lame v 3.99 during the Platinum cycle sometime.
2015/07/19 11:01:47
kevinwal
mudgel
That's a great resource but you know for most folks it's just as easy to pay $9.99 download a file, run it and it's all done for you. Especially since Cakewalk have upgraded to Lame v 3.99 during the Platinum cycle sometime.



Hey, ten bucks is ten bucks. :)
2015/07/19 11:16:26
mudgel
Yeh that's true. So for anyone in that situation there's this way.
Despite the best of explanations, there are many folks who seem to have a problem getting it to work for them.

I might try putting a few of the tutorials or procedures to the test and see how well they work. Maybe they can be improved on.
2015/07/19 18:45:44
kevinwal
I have my share of problems with the external encoder utility. Sometimes when I select the lame entry in the list none of the fields change from what was selected before so I have to re-type everything all over again to prevent the wrong data from being written. Am I the only one to experience this?
2015/07/19 19:19:13
mudgel
I've been using the Cakewalk one for quite a few years now but I used the external setup until about Sonar 8.

I'll have to see what I can do. Obviously I'll have to temporarily uninstall the Cakewalk MP3 encoder. That will need a bit of checking out first.

I'll get back to you.
2015/07/19 19:32:28
Keni
Ive had settings partially change, but only if i select the export, but then cancel out of it. When i next run it, i see all the settings except bit are the same and must adjust it...

But if i allow the expirt to complete, the now current settings still remain in place....

Im a bit confused with the 3.99 update and yet again needing to get it enabled on my laptop...

Strange here as i find the lame 3.99 fokder in shared utils, but it has not yet been enabled here while on my DAW, i dont see the folder but the cakewalk-supplied encoder is enabled and working... Might it be the 3.99 installed elsewhere? Can i check this somehow?.

...and once again can someone remind me how to go about activating? Im surprized that hasnt become built in at this point. Ive had it since the pro-audio release with it when mp3 wasnt as commonly needed...

For so few dollars it really should be folded into the core!

Keni
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account