I've had some issues with the LoopBe1 Monitor application, it won't install properly and when it runs i get an error Have this issue been seen before and if so is there a fix for this? I'm suspecting this is a Windows 10 issue with the way Aerodrums integrates with the windows MidiMap.dll but I've not been able to confirm this. If I set the MIDI out in Aerodrums to MMSytem, Microsoft MIDI Mapper (Default) or MMSystem, Microsoft GS Wavetable Synth the the application successfully sends MIDI data to these two options but not to any other. I've uninstalled and reinstalled virtual MIDI devices and Aerodrums a number of times with no success. This confirmed that MIDI using these virtual devices was working and passing data. I was able to successfully route MIDI in and out using both loopMIDI and loopBe1. I've tried a number of alternatives to loopBe1 none worked, so I decided to test the virtual midi connection using Kontakt 5. I've spent the past 3 days trying to work out why Aerodrums no longer sends MIDI via loopBe1, it was working on first install but has since stopped after an audio drive crash and reset.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |