Saving MP3 Error

Report · May 08, 2023

I reported this as a bug a couple of months ago and, not surprisingly, got zero response from Adobe, so I'm hoping to have some better luck tracking down the problem here.

I frequently get this error when I'm trying to save an MP3 file, regardless of whether I'm using "save," "Save as," or "save selection." The destination IS available and is not full. Normally, if I click "ok" and immediately try again, it saves just fine (but it's added steps because when saving an MP3, it doesn't highligh the file name text and I have to retype the name every time), and sometimes even says the file already exists and asks if I want to replace it. (Insert eye roll here).
This time, it will not allow me to save this file as an MP3 at all. It allowed me to save it as a WAV in the exact same "full or unavailable" folder, but it keeps giving me the above error whenever I try to save it as an MP3.

This only ever happens with MP3s, which I'm required to use in some instances, so figuring out a solution would save me a lot of time and aggravation.

I'm at a loss. Help?

Report · May 08, 2023

Commenting again (because there's no edit button?) to add that I was finally able to save it as an MP3 by opening the WAV version and using "save as" but that's not an optimal solution to do that every time.

Report · May 08, 2023

I'm honestly not sure whether this will be helpful to you at all but ...

My standard process, having edited the original .wav file (in my most common case, a church service) is to save the .wav file and then immediately do Save as.. (Ctrl+Shift+S) to .mp3. Clearly, this is to the same folder as the original and edited .wavs, but it has never (so far!) failed. The Save location is to an internal drive but I honestly do not know whether that has any bearing on this problem.

So, the only difference between your solution and what I do is, because I do the save to .mp3 immediately after the save to .wav there is no neccessity for me to reopen the .wav because it is still open, thus saving one step in your workflow.

HTH

Report · May 08, 2023

Thanks for the suggestion! I did actually try that before posting, and I'd also rather skip having a second step and an unnecessary (and much larger) extra file for as many times as I need to save MP3s. I appreciate you, though!

Report · May 08, 2023

I have read elsewhere (can't currently locate it) that this may be an issue with a Windows update (assuming you're using Windows, of course). And if it is, that it's related to something they may have altered the default on, related to file permissions. If I can find any more information, I'll post it.

Report · May 09, 2023

I appreciate that. While I can't say for sure whether or not it's related to a Windows update (and yes, I'm using Windows) I can say it has happened on two different laptops, one using Windows 10 and the current one using Windows 11. But if it's a permissions issue I'd love to know where to look to see if that resolves it!

Report · Aug 25, 2023

@JessWrightLXL We feel sorry that you are running into this problem. We want to solve it ASAP and are actively looking into this bug - unfortunately we are not able to repro it at our end.
Can you please share a screen recording to demonstrate this bug? You can also share one source file for which you are seeing this problem during export. You can upload the file in any cloud storage and share the link @ audbugs@adobe.com
Looking forward for you help.

Report · Aug 28, 2023

I have just emailed you links to a screen recording of the error happening, and the file I was working on when I was finally able to save it. For reference, I've included the screen recording here as well.

Report · Aug 28, 2023

Just wanted to add I am having the exact same issue. This was after I imported the mp3 into a multi-track and then attempted to save the multi-track. Must like above, I am able to save as WAV as a workaround but it becomes very annoying.

Report · Nov 14, 2024

This same issue happens to me EVERY time. I clean the cache which sometimes helps. But not always.

Report · Nov 14, 2024

@Martin380856895c9z Can you please share the Audition build number where you are seeing the issue?

Report · Nov 15, 2024

@SankarDeySarkar in my experience, it's every build number. I posted this a year and a half ago. I sent you a screen recording of it in 2023, when I was using Audition 23.0. It continued to happen in Audition 24.0, and now that I'm using Audition 25.0, it still happens.

Report · Dec 01, 2024

I also have the same error. But even saving as .wav first then doing "Save As ..." doesn't help.

This has been happening consistently (not always, but nearly all the time) for three years, and I update everytime Creative Cloud tells me to. Today, I can't even do the "Save as ..." trick.

The only consistently-successful solution I've found is quitting Audition and converting the .wav to .mp3 using Adobe Media Converter. This is a serious issue, Adobe. Please look into it.

Report · Dec 02, 2024

Yesterday I edited a 48kHz 16 bit wav to remove gaps etc and then used Save as.. to save the processed version. I then used Save as.. again to produce an .mp3 copy of the processed wave, all without problem. Using AA 25.0.0.47.

So, I rather think there is very little, if anything for Adobe.... to look into, sorry,

Report · Dec 02, 2024

Cool cool cool, you went through multiple steps to do what should be available in one step and have therefore decreed there's not a problem, despite several people having the same issue over multiple years. Inserting eye roll here.

Report · Dec 02, 2024

I'm not at all sure why you consider this should be available in one step? My work process is as I stated it because I want to keep the original wav, the "processed" wav AND the .mp3. I have never tried to go "straight" to an .mp3 because that is simply NOT a suitable workflow for me.

Report · Dec 02, 2024

Then this thread is probably not FOR you. There is clearly a bug that affects other people consistently and frequently and if it does not happen to you, that's great. That doesn't mean there's nothing for Adobe to look into.

Report · Dec 02, 2024

Not FOR me? Possibly so, but the fact that this bug cannot be universally reproduced is highly relevant to the discussion, surely? And since it does not affect ALL users do you not accept that the "opposing" (to you) view is equally valid?

In such circumstances, I really do not know how Adobe can even begin to look into it, sorry.

Report · Dec 02, 2024

Yes, not for you. If it's not a thing you experience, it's not for you. You not knowing what Adobe can do about it doesn't mean nothing can be done about it. The fact that I am not the only person who regularly experiences the problem, plus the fact that it happens so often on various computers and various build numbers that I can readily and easily screen record the issue happening means there is a trackable problem that can be solved. Again, you not knowing what to do about it is entirely irrelevent unless or until you are a coder for Adobe. So thanks for stopping by.

Report · Dec 02, 2024

Hmm...

So we have a situation where several people experience the same problem, and others (perhaps unfortunately including the developers) can't reproduce it at all. So what do we do?

It's all very well saying it's trackable on your machine, and I'm perfectly happy to believe that, but I think you're either going to have to give us a bit more, otherwise we won't be able to distinguish what's different about the machines that exhibit this, and those that don't. Yes I know the developers should be doing this really, but I think we can probably do a bit more here first, even if it's only to remove a few possibilities.

One of the things I noticed about your original screen-grab was that it doesn't only say that the disk might be full - it also says that the destination might not be available, and I believe that may be significant because of the way any save (and write) works in Waveform view. They are based on saves from a temp file, so can we have a look at that? How do you have the primary temp file set up on your machine? It would be an interesting experiment, if you have an external SSD available, to relocate your temp file to a folder on that and see if anything alters about this behaviour.

Report · Dec 04, 2024

@SteveG_AudioMasters_ my temp file is set up in the default place. I don't have an external drive available, but this is the first time anyone suggested it might be related to the temp files. I wonder if adding a secondary temp location would be helpful?

Report · Dec 04, 2024

Also, I'm not sure whether this is related, but I found this thread in which a similar issue seems to be happening, and there's a claim this was resolved with build 24. I didn't have any add-ons installed when I started experiencing this issue, so I'm not convinced this is the same thing, but it seems to be close. https://community.adobe.com/t5/audition-bugs/quot-error-1-creating-file-the-destination-may-be-full-...

Report · Dec 04, 2024

I've yet to find out why there's a secondary temp file location - I haven't had one set up for years now, and everything works fine.

As for the other thread, and the issue in general - as I said, the temp file thing is an experiment to eliminate it as a possibility. I realise that the devs said that it was fixed, but from all the comments still turning up, I'm a little suspicious of that, to say the least. But if we assume that their version of 'fixed' isn't necessarily the entire issue, we still have to look elsewhere for other clues. And the temp files are a prime suspect, especially because the save appears to work correctly from saving and then re-opening a wav file - it's almost like the encoder won't encode from what's currently open. Another thing that might be related to that directly is that the MP3 encoder currently shipping with Audition isn't the original Fraunhofer one, but LAME - I think that there are several possibilities for linking issues with this, however you look at it.