This is a weird problem in terms of trying to resolve, (I think) but I hope you guys can point me in some direction. There is a material on these files I would like to save, but I'm really concerned that it may be lost (but desperately hoping this is not the case)
I have an old Audiomulch file, with a header reading:
Note: This also occurs when I attempt to open with 0.9b20,0.9b21 which are the only
available old versions of audiomulch I have backed up
Note: DR005 is an old version of fxpansions line of vst drum modules.
I currently suspect 2 things:
1. Either the wav file paths defined within the dr005 vst parameters have changed, and its breaking because it doesn't error out cleanly for this scenario
2. Since the Audiomulch version I've attempted with up to this point dosen't match what the file was originally saved with, that there is some am version incompatibility bug thats causing this.
Actually as I was writing this, I realized there was an easy way to test my suspicion #1. So I opened the file with AM 2.0.2, the dr005 fails, afterwhich I simply replace with a blank dr005 vst, load a wav sample into one of the drum banks, and save as new test audiomulch file. Then moved the wav sample from its original path, reopened the audiomulch file and it opened without failing. I couldnt play the wav sample, but I could see the wav filename as is a feature with dr005. So I guess that eliminates my suspicion #1.
I also broke out a hex editor on the original audiomulch file to see if I could make out the dr005 parameters and unfortunately I cannot make out the most critical item, the wav file paths defined for the drum banks. I suspect its within the , but what's within chunk doesn't look like plain text, but some other binary format which I haven't made out yet.
Can anyone point me in a direction towards solution to this?
Gee Wiz I hope so!