🚀 go-pugleaf

I have the same problem on 2 completely separate machines running 1.5 - I can't seem to disable midi completely from the program, which appears to be causing conflicts. I have removed all midi in and out devices in device order, and set the Device Properties midi in and out to Midi Mapper (the only other option available on either system)

System A is running Pyramix (a post-production DAW) connected to a Mackie Baby Hui midi controller, with an M-audio FastTrack Pro soundcard. Pyramix is fine, but Audition goes nutso - in multitrack, channel 1's red record indicator flashes constantly, as does the record meter. CPU usage hits 100% constantly. When playing in Audition, the flashing stops. Edit view works fine. However, the system resources can slow Pyramix to a crawl. Exiting Audition always asks to save a blank multitrack session, and on clicking "NO" crashes. Then the system returns to normal.

System B is running Sonar LE and an M-Audio USB keyboard. Opening Audition always produces a "Opening MDI input" error, saying "specified device is already in use. Wait until it is free and then try again". Otherwise the program works fine.

How can I block all midi data from hitting Audition and causing these conflicts? Any help gratefully received.