wav file impossible problem / error from content packs

Proc wrote on 3/3/2010, 2:42 PM

I have been using Magix music maker for a little while now and this is the first real problem I can't seem to find an answer for , all help and information on this is going to be most welcome.

The problem is as follows, when I start Magix music maker and use the filemanager to navigate to my .wav files stored in the Magix directory along with all the other sound files and music files I have they show up just fine. When I try to place them into the bars to play them however the following error message occurs:

"The file format of <File name and dir> cannot be read by MAGIX Music Maker. Please ensure that the affected drive is not full or write protected. (Program files(x86) Folder, Disk Not full, Nothing write protected not even the my documents area for the save files, why bother with WRITE protection when you can't READ the file is strange enough in my eyes as it is).
If you do not have read or write acces to this path, please contact the administrator (me :S).

The strange things which are the biggests clues I have solving this problem so far are these.
1: I have no write/read problems with any others files of the same type in similar processes
2: The wav files can be played by MAGIX Music Maker without any problem as a sample with the file manager by single clicking them
3: The wav files are useable by the Song Maker feature of MAGIX Music Maker and show up in the bars and are playable, but when I add one from the dir or the file manager , the exact same, the error occurs again!!!

that pretty much excludes the file itself from being the problem or MAGIX being unable to read it, I'm guessing it's something within the software or something?

Anyway hope somebody has any thoughts on this, would be much appreciated.

And furthermore, I am using Windows 7 , might be usefull to know.

Comments

Proc wrote on 3/4/2010, 11:46 AM
I found the answer myself actually, and good news MAGIX team, it's not the software, the question was narrowed down to either two problems.

Either the software is letting me down or Windows 7 is, well it was Microsoft this time guys. Running the program as administrator and again trying to remove all folders with the read-only flag ( which is always coming back since some files are write protected) was enough to fix the problem. It's a W7 Security thing.

hopefully this helps other people in the future! please run it as admin!!!