Unable to import MP3s sometimes

Question

I have GB4 with the latest updates (I guess that makes it GB 4.1 then) and I've noticed that I can't import MP3s sometimes. I can't figure out why, other than to conclude that it's a bug.
I can actually import any MP3 ok, be it from the filesystem or or from the browser within GB. It shows a progress bar, and also another saying "converting" I think, before adding the track. After it is imported, I can play it and such. I can also look inside of the bundle and see that there is a .aif version of the MP3 in the Media directory. So, it all sounds good so far.
Well, the problem starts as soon as I Save the project. As soon as I do that, the corresponding .aif file is deleted from inside the media directory, in the project's bundle. However, if I keep working, the track continues to play fine. The problem only is noticeable if I close the project, or quit, and try to open it again. When I do that, sure enough, GB complains that it can't find the corresponding .AIF file, and prompts with a dialog asking if I want to "skip" or "search"
Choosing either option of course, makes no difference. the end result is that the project opens, and there is a "file not found" label on the segment pertaining to that imported track. So, that in turn means when you try and play, that track won't be heard, as it has no file associated with it.
The odd thing, is that some MP3 files do seem to import ok. Oh, and before you ask, they all are mp3's with the lowercase .mp3 extension. I can always tell if it does, because the progress bar is much shorter, and as far as I can tell, it's actually skipping the "conversion" step. How a good file is represented in the media folder is that you have the actual MP3 file added, along with another file with the same name, but with a .oww extension. I don't know what this file is for. However, if a file is imported in this manner, when I Save the project, sure enough, both the MP3 and the .oww file are not erased from the media directory. And of course, if I reopen the project, it is able to open that track successfully.
So, I'm at a loss. I know that all imported files must be 44 Khz files, and as far as I can tell, both the ones that seem to work and fail, are 44 KHz files. I thinkt the one that did work correcly did have a higher bit rate than some others, at 160 Kib/s, but I doubt that the bit rate makes any difference.
I haven't tried converting the ones that don't "stick" by converting to AIF manually and importing the AIF to see if it sticks, but I would guess it would. I think all hte AACs that I've tried importing always work, so as far as I know so far, it's only a problem with MP3 files.
Another thing worth noting, I'm using a network level account, that isn't an admin account. Also, my home directory resides on an NFS share, that's mounted at boot time, but a network share shouldn't matter. But I was thinking that maybe there's a bug that may be exacerbated when using this feature as a non-admin account.
So, GB devs/Apple support, if you're reading this, I urge you to test your products with non-admin users and network accounts, such as mine. I have been using OSX in this configuration since 10.0, and over the years I have seen software that has made some bad assumptions of applications location, home directory location, HFS filesystem, etc. So, I urge you to test your software with these configurations as well, as people like me do have these setups, however rare they may be.

Answer 1

One thing I forgot to add. When importing an MP3 that won't work, I do see lines logged in console.log that say "Unsupported MP3 file" So, apparently that means that some MP3 files are unsupported, but really if that were the case, why would it even allow me to import it in the first place? If it were really unsupported, shouldn't it produce a dialog saying such, and cancel the import process? As it is, it's far worse, since it's importing it, so you think it's compatible. Then next time you open the project you realize it silently deleted that import.