Hello,
So I'm a long term user of AudioMulch 1.0, and I've just downloaded 2.0 to see what all the fuss is about. So far so good, but unfortunately, one particular document I'm trying to open (made in 1.0) gives the following error message:
"Access Violation at address 0x004C4AD4 in module C:\Programs Files\AudioMulch 2.0.2\mulch2.exe . Read of address 0x00000000 ."
I'm having no problems opening any other documents as far as I'm aware (yet to get through all 50+ documents I made in 1.0), and I don't think there's anything particularly unusual about this particular document (using no VSTs or contraptions that haven't been used elsewhere), and had no problems opening it in 1.0 obviously.
I'm actually using AudioMulch 2.0.2 on a brand new laptop. I'm sure I've installed the drivers for my soundcard fine (like I say, no problems opening and playing other 1.0-made documents).
Any suggestions? I'll keep trying in the meantime...
Cheers,
berksy
oh, and I'm running Windows XP Professional SP3.
well i've tried a few things, like installing 1.0 on my laptop - and the document runs fine on that. I've also downloaded the latest DirectX and change Audio Driver to DirectSound (from ASIO) but that hasn't changed things.
Any suggestions?
I think i might try and pick apart the document in 1.0, removing VSTs/contraptions and try and open it up in 2.0, and see if there's any problems.
Cheers,
berksy
Thanks for sending the document. It seems to be related to MIDI controlling the Drums volume. If you un-map the MIDI control in AM1 and then re-do the mapping in AM2 it will probably load. Ultimately this is a pretty bad bug though, and I'm working on fixing it for 2.0.3 (out this week or next)
Alright, I'll give that a go. I never would've thought of that, though i guess you have updated the Drums contraption considerably since AM1.
Glad my problem was of some use to you (!!!) and thank you again for your time!
Cheers,
Richard
This should now be fixed in version 2.0.3 (just released). Please advise if the problem shows up again -- Ross.
yep, this is now fixed. Cheers Ross!
berksy