Mulch was running fine until I started it today. I'm getting a red CPU meter readout. It goes white to red and it starts glitching/crackling and jittering on the timeline.
It's almost as if the CPU is maxing out. But it does it even on 10 per cent load. It even does it on some of the demo files.
Soundcard doesn't give me any problems in renoise (using the ASIO driver too) and it's fine playing audio generally outside of muclh.
I've got an M-Audio 24/96 card thats normally rock solid. It seems OK in mulch with directX sound. I've tried reinstalling my sound card drivers and have removed and re-installed mulch. But still the same problem,
Tried all the different buffers sizes and sample rates.
I noticed that when I reinstalled mulch it picked up my license number. so I wonder if I need to purge my muclh iun-nstallation somehow as it is maybe picking up old parameters?
Don't know what else to try. Other DAW programs seem to be running ASIO no problem. I don't have Windows XP updates enabled. Any advice much appreciated.
I had installed Reaper to have a look at it. That installation seems to have changed the buffer size on my soundcard to 64. When I changed it (using the M-Audio utility outside of mulch) to match the 512 seting in mulch it all went back to normal. panic over. Audiomulch is awesome.
You should definitely make sure the ASIO driver buffer size and the AudioMulch buffer size match. With most drivers this just happens. I will investigate whether there is any problem with AM.
The indicator turning red shows that AudioMulch has detected a problem with the buffer timing/glitching. This can indicate that there is a problem even when the CPU load is low.
Aside from possible issues with some plugins, you should find that you can go the other way and set the driver buffer size and AudioMulch buffer size to 64. (unless maybe you really are pushing a very high CPU load). After using your device's custom ASIO control panel you may need to press the "Reset Audio" button on the Audio Driver > ASIO page in AudioMulch to resync the available buffer sizes with the one(s) provided by your ASIO driver.
Thanks for the reply Ross. I think temporarily installing the Rearoute ASIO driver to evaluate how mulch could feed audio to Reaper caused the problem. I didn't notice until I used AM stand alone again, despite having uninstalled Reaper & Rearoute.