# Ver 3.14 bug: file "cannot be opened for writing"
**URL:** https://community.mp3tag.de/t/ver-3-14-bug-file-cannot-be-opened-for-writing/56892
**Category:** Fixed Bugs
**Tags:** bug-fixed
**Created:** [March 31, 2022, 4:27pm UTC](https://community.mp3tag.de/t/ver-3-14-bug-file-cannot-be-opened-for-writing/56892 "2022-03-31T16:27:55Z")
**Posts on this page:** 16
**Page:** 1
### Author:  [@ssharro](https://community.mp3tag.de/u/ssharro)
#### Post date: [March 31, 2022, 4:27pm UTC](https://community.mp3tag.de/t/ver-3-14-bug-file-cannot-be-opened-for-writing/56892/1 "2022-03-31T16:27:55Z")
After updating to ver 3.14, I get an error indicating that the file I'm editing "cannot be opened for writing." The file is not in use by other applications.
When I open the same directory with a computer equipped with ver. 3.05, I get no error. And once I've made a change to the metadata using the ver 3.05 computer, the computer equipped with 3.14 can then open the file and make the changes I'm requesting.
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [March 31, 2022, 5:00pm UTC](https://community.mp3tag.de/t/ver-3-14-bug-file-cannot-be-opened-for-writing/56892/2 "2022-03-31T17:00:45Z")
could you check the original file with the procedure outlined here:
> [@Hints for asking Support Requests](https://community.mp3tag.de/t/hints-for-asking-support-requests/56190):
>
> If you need support using Mp3tag, you can help the community members that are about to support you in finding a solution or workaround to your problem, by following these simple guidelines. Be descriptive, also in what you’ve already tried Please give a short explanation what’s not working as expected or what you’re trying to achieve. It’s best to know any details about the problem at hand and especially, what steps you’ve already tried to solve it by yourself. Helpful information also includ…
I suspect that the file was broken prior to tagging and this was detected by 3.14 while 3.05 ignored that state.
see also the change log:
2022-02-04] CHG: added reporting of unsupported or corrupted file structure as error to 'Tag'
column.
---
### Author:  [@ssharro](https://community.mp3tag.de/u/ssharro)
#### Post date: [March 31, 2022, 5:56pm UTC](https://community.mp3tag.de/t/ver-3-14-bug-file-cannot-be-opened-for-writing/56892/3 "2022-03-31T17:56:37Z")
Ok. Fair enough.
What I've discovered is that the problem occurs with new music files created using the "Extract Regions" function in Sound Forge Pro 13. Apparently MP3Tag v. 3.15 recognizes some issue with the files this program generates that earlier versions of MP3Tag did not take issue with.
The files that are problematic to MP3Tag v. 3.15 do not seem corrupted and play normally using Media Player or other players.
In Sound Forge Pro 13, the only switch/parameter that can be changed in the Extract Regions function is whether to write long file names for the destination files. Toggling this did not have any effect on MP3Tag's problems with the files.
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [March 31, 2022, 5:59pm UTC](https://community.mp3tag.de/t/ver-3-14-bug-file-cannot-be-opened-for-writing/56892/4 "2022-03-31T17:59:32Z")
> [@ssharro](#):
>
> The files that are problematic to MP3Tag v. 3.15 do not seem corrupted and play normally using Media Player or other players.
This does not mean anything in respect to the tag structure of the files.
You would really do us all a favour if you could check the files with the linked tools.
> [@How to check files for errors?](https://community.mp3tag.de/t/how-to-check-files-for-errors/44633):
>
> It’s required and often helps to reduce support cycles to check files for errors before filing a bug report. Symptoms of erroneous files are often missing or wrong bitrate or length audible blips or skips tags seem to be sticky and cannot be removed There are some really good tools to check the files for errors, namely MP3 Diags — identifies many different issues in MP3 files Website: [http://mp3diags.sourceforge.net](http://mp3diags.sourceforge.net) Download: [MP3 Diags - Getting MP3 Diags](http://mp3diags.sourceforge.net/010_getting_the_program.html#binWindows) If the font size in MP3 Diags is …
Because only if the integrity has been verified, other probable causes can be examined.
---
### Author:  [@ssharro](https://community.mp3tag.de/u/ssharro)
#### Post date: [March 31, 2022, 6:43pm UTC](https://community.mp3tag.de/t/ver-3-14-bug-file-cannot-be-opened-for-writing/56892/5 "2022-03-31T18:43:32Z")
In examining one of the offending files, MP3 Diags found:
1. ID3V@ tag doesn't have an APIC frame (which is used to store images).
2. No normalization undo information found. The song is probably not normalized by MP3Gain or a similar program. As a result, it may sound too loud or too quiet when compared to songs from other albums.
So I guess this means that Sound Forge Pro 13 does not write these two items, which MP3Tag believes are important, in the sound files it produces with the Extract Regions function. Therefore, until and unless the folks at Magix (Sound Forge Pro) change how the program structures the files it produces in extracting regions, MP3Tag will no longer work with Sound Forge Pro.
Thanks for helping to clear this up.
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [March 31, 2022, 6:48pm UTC](https://community.mp3tag.de/t/ver-3-14-bug-file-cannot-be-opened-for-writing/56892/6 "2022-03-31T18:48:43Z")
No, it does not matter whether there is already an embedded picture or any mp3gain information for MP3tag to work.
I was looking much for unknown streams, invalid headers, streams with less than 10 frames.
This file that you just checked should be taggable with MP3tag.
Or could you supply such a file if the problem persists?
---
### Author:  [@Zerow](https://community.mp3tag.de/u/Zerow)
#### Post date: [April 1, 2022, 11:35am UTC](https://community.mp3tag.de/t/ver-3-14-bug-file-cannot-be-opened-for-writing/56892/7 "2022-04-01T11:35:01Z")
> [@ssharro](#):
>
> [...]
> Apparently MP3Tag v. 3.15
> [...]
You ment version 3.05?
---
### Author:  [@ssharro](https://community.mp3tag.de/u/ssharro)
#### Post date: [April 1, 2022, 2:20pm UTC](https://community.mp3tag.de/t/ver-3-14-bug-file-cannot-be-opened-for-writing/56892/8 "2022-04-01T14:20:44Z")
So sorry and just to be clear: MP3Tag version 3.05 has no problem with the files in question. It's version 3.14, the current version, that will not write to these files.
And as Ohrenkino pointed out. The log of changes has the following entry:
2022-02-04] CHG: added reporting of unsupported or corrupted file structure as error to 'Tag'
column.
---
### Author:  [@MotleyG](https://community.mp3tag.de/u/MotleyG)
#### Post date: [April 1, 2022, 2:28pm UTC](https://community.mp3tag.de/t/ver-3-14-bug-file-cannot-be-opened-for-writing/56892/9 "2022-04-01T14:28:58Z")
You can try the suggested repair tools regardless of whether the Sound Forge Pro software gets updated. Not only do they report errors they find, but there are various correction options to restore the proper header data for you.
> [@How to check files for errors?](https://community.mp3tag.de/t/how-to-check-files-for-errors/44633):
>
> It’s required and often helps to reduce support cycles to check files for errors before filing a bug report. Symptoms of erroneous files are often missing or wrong bitrate or length audible blips or skips tags seem to be sticky and cannot be removed There are some really good tools to check the files for errors, namely MP3 Diags — identifies many different issues in MP3 files Website: [http://mp3diags.sourceforge.net](http://mp3diags.sourceforge.net) Download: [MP3 Diags - Getting MP3 Diags](http://mp3diags.sourceforge.net/010_getting_the_program.html#binWindows) If the font size in MP3 Diags is …
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [April 1, 2022, 2:36pm UTC](https://community.mp3tag.de/t/ver-3-14-bug-file-cannot-be-opened-for-writing/56892/10 "2022-04-01T14:36:38Z")
It would be nice to get the hands on one of the not working files.
---
### Author:  [@ssharro](https://community.mp3tag.de/u/ssharro)
#### Post date: [April 1, 2022, 2:51pm UTC](https://community.mp3tag.de/t/ver-3-14-bug-file-cannot-be-opened-for-writing/56892/11 "2022-04-01T14:51:43Z")
Here's a link to a file produced by Sound Forge Pro 13's EXTRACT REGIONS tool:
> **[MP3Tag](https://www.dropbox.com/sh/11as6anyc784i3z/AAAHtkF5JOYjKG7HVkjGFBDZa?dl=0)**
>
> Shared with Dropbox
The Sound Forge Pro's EXTRACT REGIONS function only produces .wav files.
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [April 1, 2022, 3:14pm UTC](https://community.mp3tag.de/t/ver-3-14-bug-file-cannot-be-opened-for-writing/56892/12 "2022-04-01T15:14:23Z")
oh, it's a wav file!
I opened the file with Nero Wav Editor and saved it again and then had no problem to save a tag.
The support for tags of wav fiels in WE is scarce to virutally non-existent. So the windows explorer is yet again no good test environment to check MP3tags tagging capabilities.
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [April 2, 2022, 5:42pm UTC](https://community.mp3tag.de/t/ver-3-14-bug-file-cannot-be-opened-for-writing/56892/13 "2022-04-02T17:42:12Z")
I've analyzed the file and added a workaround for that with [Mp3tag v3.14a](https://community.mp3tag.de/t/455). Can you re-check?
---
### Author:  [@ssharro](https://community.mp3tag.de/u/ssharro)
#### Post date: [April 10, 2022, 6:42pm UTC](https://community.mp3tag.de/t/ver-3-14-bug-file-cannot-be-opened-for-writing/56892/14 "2022-04-10T18:42:12Z")
Yes. V3.14a is good. It allows altering the .wav files that I could not modify with v3.14.
Thank you for addressing the problem.
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [April 12, 2022, 9:16am UTC](https://community.mp3tag.de/t/ver-3-14-bug-file-cannot-be-opened-for-writing/56892/15 "2022-04-12T09:16:38Z")
Great! Thanks for confirming the workaround.
---
### Author:  [@system](https://community.mp3tag.de/u/system)
#### Post date: [May 12, 2022, 9:17am UTC](https://community.mp3tag.de/t/ver-3-14-bug-file-cannot-be-opened-for-writing/56892/16 "2022-05-12T09:17:09Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.