Skip to main content
Inspiring
November 4, 2022
Question

Destination File error

  • November 4, 2022
  • 1 reply
  • 702 views

Hello - 

I'm currently using Audition 23.0.0.54 on a Macbook Pro 2019 running Ventura 13.0.

Every time I mix down a session or clip into folder and want to overwrite a previous file, I get this error message that says:

The destination file "[insert folder name]" is currently opened for editing and cannot be overwritten.  Please choose a new file name.

 

This happens with every folder I save a file into.  Once I choose a folder - I cannot overwrite a session within that folder.

 

I don't want a new file name, I simply want to overwrite an older file. 

 

Any thoughts are welcome.  

 

Thank you!

 

-G.

 

This topic has been closed for replies.

1 reply

SteveG_AudioMasters_
Community Expert
Community Expert
November 4, 2022

You are talking about Files and Sessions as though they are the same thing; they aren't.

 

If you have opened an MP3 file in a session, then yes, that's the message you will get, quite correctly, if you try to update it. The chances are that if you close the file in the session before trying to save it with the same name, it might work (haven't ever needed to do that), but it's obeying the normal rules for files - you can't save to one that's open in an app.

 

If you want to update a session file, it's very easy - just hit File>Save. The reason that this works is that the session file, as such, isn't being accessed; it's been read to open the session, but that's all - so a Save of this is legitimate.

Inspiring
November 4, 2022

maybe i'm not being clear. I have no open file inside my audition session. 

 

if i record a new track and try to export / mixdown either the entire session or simply the clip - i get thet error if i want to use a name of a file that previously exists in that folder.  Every other program I use whether it's Protools, Final Cut, Premiere, Logic, or Photoshop will ask me if I want to replace the file with the same name.  Not Audition. It simply does not allow the save.  I dont know if this is a glitch or a preferences / protection setting I'm unaware of.  But I do know it has nothing to do with the semantics of calling something a file or a session. Thanks.