I just recently upgraded from WL 8.5 to 9.0 and now when I try and open some of the 24 bit/44.1 files that I rendered before the upgrade, I get prompted with a “special file format” screen to select the bit depth, sample rate, mono/stereo and byte order. No matter what I choose, I get an error stating that Wavelab cannot open the file.
I’ve rendered close to 400 songs for clients in WL 8 and 8.5 over the last 2 years and have followed the same procedure in every instance when it comes to rendering the final file so I am having trouble figuring out what’s different about some of my files.
Has anyone else seen this and is there a fix for it other than to revert back to the old version?
I’m on Windows 7/64 and am using WL 9.0.15 (build 544) - 64bit. I believe that I was on WL 8.5.13 previously? Same OS.
I had created a fresh install of Windows 7 for my Wavelab 9 system. Which means a new encryption key that won’t be compatible with files created with the previous Windows 7 install. So even though the files are standard WAV files, because they are encrypted with the old key, Wavelab can’t read them. Not Wavelab’s fault.
The only fix for this was to restore the Ghost image of the previous Windows 7 installation and then manually turn off encryption for every GREEN file and folder. A tedious and time-consuming process.
My thinking was that, by using a third party tool like WinZip (extract to here dialogue), the Windoze encryption issue would not occur. Perhaps this is why I haven’t seen this for some time.
I would hope that Apple and Microsoft have worked this out by now with El Capitan and Windows 8 and 10.
I know that folders/files zipped on Mountain Lion by ctrl-click would appear as green encrypted on Windows 7. But folders/files zipped by command line on Mountain Lion wouldn’t. So I made an Automator action droplet on Mountain Lion for zipping that zips dropped files or folders without creating the green encrypted cross platform problem. There were bug reports submitted to Apple about this quite a while ago.
But I think the problem was fixable on both ends, Mac and Windows, since 7zip would unzip on Win 7 without any indication of encryption I believe, and I’m pretty sure Microsoft received complaints and bug reports urging them to fix on their end too. Both Mac and Windows ends should have been fixed. Not sure what the outcome has been though.