• SONAR
  • The End of the MP3 Encoder Controversy - MP3 for Free! (p.7)
2017/04/29 23:07:03
abacab
Beepster
Just in case any Bakers or anyone else in the know pops in I'm still curious about the stuff I was rambling about in this post....
 
http://forum.cakewalk.com/FindPost/3598569
 
Dunking chains.
 
:-)




The Cakewalk MP3 encoder seems to have been removed from the store.
 
Would be nice if the Bakers made it a free download for use with our older Cakeware! 
2017/04/29 23:13:21
John
Beepster
Just in case any Bakers or anyone else in the know pops in I'm still curious about the stuff I was rambling about in this post....
 
http://forum.cakewalk.com/FindPost/3598569
 
Dunking chains.
 
:-)


It should work without having to do anything.
2017/04/29 23:46:54
abacab
John
 
It should work without having to do anything.




It's my understanding that MP3 will only be "built-in" to 2017.04 and later.
 
So if you are running anything older than that you will need to install something...
2017/04/30 11:53:22
soens
It appears that my mp3 export didn't work because the project format (48/24) didn't match the export format (44.1/16).
 
I didn't know these had to match but they do for this to work.
2017/04/30 13:09:41
JohnEgan
chuckebaby
Im throwing a huge free MP3 encoder party.
All kinds of extentions (Wav, Aif, Flac) are all going to be here.  

LOL, great, Is it BYOD(AW)? 
Cheers
2017/05/24 00:37:38
abacab
Just saw this article on Fraunhofer at AVS Forum ...
 
Fraunhofer IIS Pulls the Plug on MP3 Licensing
http://www.avsforum.com/f...er-iis-pulls-plug-mp3/
2017/05/24 02:35:59
cparmerlee
It is good news that the royalties are no longer required.  But we are talking about 10 bucks for what was pretty LAME (literally and figuratively).  I already paid, so I don't care about that.  I am more interested in seeing stronger capabilities on the mastering/publication side.  We have had lengthy discussion about the arcane ways that Sonar makes it difficult to something as basic as exporting the mix of the entire song.  This whole area needs to be a lot stronger, simpler, and more intuitive.  MP3 is part of that.
 
I rarely use the SONAR MP3 converter.  It is very slow compared to external tools.  Moreover, it is extremely crude.  Instead I use the Sonnox converter.  That program includes features that prevent the conversion of a WAV that is too hot.  Even if the WAV didn't clip, it can clip after compression, and Sonnox detects/prevents that.  Another nice feature of Sonnox is that ability to easily preview the sound of various compression settings, including the ability to see visualize what part of the spectrum is being damaged most by compression.
 
So, I really hope Cakewalk looks upon this as an opportunity not to end the $10 hassle, but as a much bigger opportunity to make their product much more useful.
2017/05/24 13:51:50
57Gregy
In the beginning, I didn't know mp3s from mumps.
While searching for an encoder, I discovered my Windows Media Center Edition computer already had one.
2017/05/24 14:22:30
TheMaartian
abacab
Just saw this article on Fraunhofer at AVS Forum ...
 
Fraunhofer IIS Pulls the Plug on MP3 Licensing
http://www.avsforum.com/f...er-iis-pulls-plug-mp3/


I don't know what's going on with the AVS forum site, but when I clicked on that link, the first thing that happened was a popover to another page telling me that I was running an old version of Chrome and needed to update. It offered a .JS file. Chrome's check-for-update feature, on the other hand, told me I was up-to-date with some version of v58. The .JS file had a 59 in the filename. I passed.
2017/05/24 15:14:28
abacab
TheMaartian
abacab
Just saw this article on Fraunhofer at AVS Forum ...
 
Fraunhofer IIS Pulls the Plug on MP3 Licensing
http://www.avsforum.com/f...er-iis-pulls-plug-mp3/


I don't know what's going on with the AVS forum site, but when I clicked on that link, the first thing that happened was a popover to another page telling me that I was running an old version of Chrome and needed to update. It offered a .JS file. Chrome's check-for-update feature, on the other hand, told me I was up-to-date with some version of v58. The .JS file had a 59 in the filename. I passed.




That is a fake Chrome update malware.  I got hit with a similar fake Firefox update on a different site.  Definitely do not ever click to run any .js file that is presented to you!!!
 
These exploits are generally distributed via 3rd party advertising networks that websites have no control over.  Google "malvertising" for more info on the topic.
 
The best defense is to run a good adblocker in your browser, and never click on anything suspicious.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account