Thanks for the info Noel. Appreciated. :)

I get this error a lot and it's always with MP3's bought from....wait for it... Amazon.

I teach guitar and for each student i use a seperate Sonar project with Amplitube 3 and any material (audio files) that we're working on. I often purchase MP3's from Amazon of any songs my students want to learn. Lately (and I'm not outright saying since X1 but it's possible) I get the 'Out Of Memory' error when trying to import MP3s from Amazon. Strangely, not on all though, but on the majority.

Recent MP3s from Amazon that produce this error for me (off the top of my head)

Pyro - Kings Of Leon
Radioactive - Kings of Leon
Rolling In The Deep - Adele
Love Me Like You - Magic Numbers
Forever Lost - Magic Numbers
Mosely Shoals Deluxe (the whole double album) - Ocean Colour Scene
Who Knew - Pink
Paint it Black - Vennessa Carlton

I currently get around it by simply using Windows Media Player alongside Sonar. I will definetley get around to trying some of the fixes mentioned here.

Thanks
Dean

I've noticed "Out of Memory" errors on newer MP3s I purchased either from iTunes and Amazon. It seemed to effect only those artists that were of a current or classic popularity. 
A run through Sound Forge or Audacity or a DRM removal tool* fixed all that. 

*Of course, I do not advocate at all removing or bypassing DRM.

Noel,
 
Thank you for providing the answer.  By the hits shown on this thread, I think you can see there's a lot of interest, so I hope Cakewalk will make it a priority.  If other pro DAWs are not having this issue, there must be a practical solution.
 
Another thing to consider is that Microsoft frequently works with software developers to resolve errors like this.  If you can raise the issue to Microsoft then they may resolve it and put it in an update.  In a prior job, I often worked with Microsoft on things like this, and I found them to be very receptive.  This may be an option for you.
 
 

Noel,
 
Thank you for providing the answer.  By the hits shown on this thread, I think you can see there's a lot of interest, so I hope Cakewalk will make it a priority.  If other pro DAWs are not having this issue, there must be a practical solution.
 
Another thing to consider is that Microsoft frequently works with software developers to resolve errors like this.  If you can raise the issue to Microsoft then they may resolve it and put it in an update.  In a prior job, I often worked with Microsoft on things like this, and I found them to be very receptive.  This may be an option for you.
 
 

I have the same problem in Sonar 8.5. I was directed here. I also used to be able to do this without any problem. When I looked up the problem in Sonar help, I got the following paragraph. However, I'm not sure how to enact what they say. This is a line in the Wave section of the Aud.ini file that sets the buffer size for bouncing tracks. At a value of 0, the bounce buffer is the same size as the Mixing Latency value that you set in the Audio Options dialog. If you find that bouncing tracks, especially with certain soft synths, takes a very long time, you can set this value to 100, or some value between 0 and 350 so that the bounce buffer will use a more efficient size for bouncing, which has different requirements from normal playback latency. Note: on larger projects, setting this variable to a large value can cause out-of-memory errors.

Ok....I had the same problem in X1 importing an mp3 from Amazon.com.
 
Why am I importing an mp3?
 
Learning a cover song...easer with the loop function.
 
Anyway I got the same error (out of memory)
 
Turns out the suggestion regarding removing the cover art was spot on.
 
Dowload a program called media monkey. Remove the album art via the properties screen in Media Monkey. Drag and drop mp3 into sonar.
 
DONE.
 
Thanks!
 

I have had the problem numerous times.  Glad I followed this thread to find the reason why.  It would be very nice to have a permanent fix built into Sonar.

yoursong


I stripped all the tags that I could access with my tag editor program, and results are the same.  I can't access all the tags, some are called internal tags, I could strip a few internals, but most of them don't allow editing.
 
Part of the reason I put this on the user forum was to see if others are having the same problem, especially with mp3's from Amazon.

I've also seen this error-message.

A few days ago I was helping a friend getting started in Sonar.
I was thinking; a good way of getting to know the tools and workflow is to just import an existing song and then
try to "copy" it's sound just by listening to the original and, by ear, creating the same song with the tools available in Sonar.

For this I wanted to import an mp3-file to have as a template-track, but instead got this "Out of memory"-msg.

I really don't know the settings or resolution of the mp3-file since we just took one of her mp3-songs. But I can confirm that not only you have experienced this problem.

yoursong

When you say "most" mp3's fail to import, have you looked into what the differences are between the ones that do and the ones that don't?

 
I buy mp3's primarily from Amazon solely to A/B (Sure I'd prefer another format, but mp3 is what the retailers are selling, and what buyers are hearing on their players).  I've been using X1 since it came out.  Never had a problem before X1. The mp3s throw an out of memory error.  I've looked at the differences, I don't see any.  TAG formatting has been mentioned in the past, I don't see a difference there.  However, if Sonar is unable to read certain mp3s or TAG formats, I strongly believe Sonar should be fixed.
 
As far as shouting ... excuse me for that.  I'm very frustrated with this.  I'm trying to get attention from Cakewalk on this issue.  It's been brought up before and has not been adequately addressed, IMO.

If memory serves me right, I remember this exact conversation a few months ago on this forum about the exact same thing, something to do with the new mp3 format allowing full album covers inside the mp3 file...somehow and I don't remember how, one has to strip this info out and the mp3 will import fine..