MP3 Import Problem (Out Of Memory Error) SOLVED!

I had this as part of the CPU utilization thread but I figured I'd post a new message to keep that one true to the CPU meter problems.

Turns out, it's the tagging from Foobar 2000 that Sonar does not like for some reason.

1. Record in Reaper
2. Render to mp3 in Reaper, either CBR or VBR.
3. Import to Sonar 8.5 either via menu or drag and drop, works fine.
4. Tag in Foobar 2000, artist, composer etc. Save file.
5. Try to open in Sonar either drag and drop or via menu and bang "Out Of Memory" error instantly.

So, Foobar 2000 is doing something weird with the tagging that Sonar doesn't like but other DAW software seems to ignore. Not sure what, but it's repeatable every single time.

Just thought I would share in case some other poor soul has the same or similar problem.

Just tried it here.

I didn't record the test file in Reaper (it was recorded in SONAR and encoded in Adobe Audition), but the MP3 was tagged in Foobar 2000 (as is my normal routine). I chose a moderately large file (10Mb) in hopes that if it really was an out-of-memory error a large file might have a better chance of failing. I am on XP with 3GB RAM, but I didn't expect that to make a difference (when Windows reports "out of memory" it is almost never actually out of memory).

My import chugged away for several minutes (seemed to take a long time, but then I'm not accustomed to importing MP3s into SONAR, only waves), but eventually it did import OK. This suggests it is either specific to your system or specific to your MP3 files.

If you'd like to send me an actual file that consistently fails for you, PM me and I'll give you my email address (or my ftp server if you prefer). I'd be happy to try to replicate your symptoms here.

bitflipper


Just tried it here.

I didn't record the test file in Reaper (it was recorded in SONAR and encoded in Adobe Audition), but the MP3 was tagged in Foobar 2000 (as is my normal routine). I chose a moderately large file (10Mb) in hopes that if it really was an out-of-memory error a large file might have a better chance of failing. I am on XP with 3GB RAM, but I didn't expect that to make a difference (when Windows reports "out of memory" it is almost never actually out of memory).

My import chugged away for several minutes (seemed to take a long time, but then I'm not accustomed to importing MP3s into SONAR, only waves), but eventually it did import OK. This suggests it is either specific to your system or specific to your MP3 files.

If you'd like to send me an actual file that consistently fails for you, PM me and I'll give you my email address (or my ftp server if you prefer). I'd be happy to try to replicate your symptoms here.

Sure why not!
PM me your email or wherever you want the file sent.
I'm curious to see what's going on.

Most of these files are around 3MB. Size doesn't seem to matter :)

@wormser: At least you have narrowed it down and have a work-around for now.

@bitflipper: Great that you tested this out. Always nice when people help out.

Keep us informed...

The problem turned out to be that SONAR (as with Windows Explorer, Windows Media Player and many other applications) does not yet support ID3v2.4 tags, which is what Foobar2000 writes by default. ID3v2.3 tags are OK.

wormser's workaround was to go into the advanced preferences for Foobar and uncheck the "use padding" option, which actually does more than suppress string padding. It effectively causes Foobar to write ID3v2.3 tags.

This thread deserves a special place in the history of cooperative troubleshooting on the forum. It is terse elegant and easy to follow. Now there is nothing to do but wait for Bapu.

I guess that's why they call it Foobar (which should be spelled FUBAR).