# MP3 reports cannot open file for writing

**URL:** https://community.mp3tag.de/t/mp3-reports-cannot-open-file-for-writing/45266
**Category:** Support
**Created:** [April 27, 2019, 10:43pm UTC](https://community.mp3tag.de/t/mp3-reports-cannot-open-file-for-writing/45266 "2019-04-27T22:43:50Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![poster](https://community.mp3tag.de/user_avatar/community.mp3tag.de/poster/32/4881_2.png) [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [April 1, 2022, 5:47pm UTC](https://community.mp3tag.de/t/mp3-reports-cannot-open-file-for-writing/45266/8 "2022-04-01T17:47:55Z")

</div>

> [@NormalReaction](#):
>
> I appreciate the point about checking that Cubase has not somehow created a wav file with the wrong structure, but how can I do this, and if it has, what is the solution.

The easiest way is to rewrite the file (lossless) with a tool defined in MP3tag. I had to use it very often because my favorite recording tool used to create wave-files with a wrong header.

> [@User-defined Tools](https://community.mp3tag.de/t/user-defined-tools/966/7):
>
> Example — Re-encode WAV using ffmpeg Some WAV files [have an invalid structure](https://community.mp3tag.de/t/how-to-check-files-for-errors/44633) or extra junk bytes at some RIFF chunks so re-encoding the file might fix the problems. You can use the excellent [ffmpeg](http://ffmpeg.org/download.html#build-windows) command line utility as a user-defined tool from within Mp3tag. Name wav2wav Path Please locate the path of your ffmpeg.exe Parameter -i "%\_filename\_ext%" "%\_folderpath%\%\_filename%\_out.wav"

---

_[View the full topic](https://community.mp3tag.de/t/mp3-reports-cannot-open-file-for-writing/45266)._