Any body else have this issue? It's really a PITA because I'm trying to create a custom MIDI map in AD2 for Slate Drums4 and it's not working 100%, and I don't know if this issue is part of the problem. I've got a difference of two octaves/key ranges between the two keyboards. ![]() Even allowing for the possibility that they're using the different conventions, that's a difference of only one octave/key range on the keyboard. ![]() It may be a USA/European thing? AD2 is a European product. One convention says C3, the other says it's C4. I know there are two Midi conventions, which revolve around what is considered middle C. Sonar PRV says C3 (there are no MIDI note numbers in the PRV, just the standard piano keys). Same for the kick: AD2 says note 36, key C1. ![]() So, for example, the AD2 keyboard replica is indicating the open snare hit is Midi note 38 and the key on the keyboard is D1. Every AD2 note is off by two octave ranges compared with Sonar's PRV, where I can see the MIDI notes AD2 is generating in the PRV grid. I can go into its Map Window and see which kit pieces are triggered by which MIDI note on a keyboard replica. I can see midi data going into AD2, but no sound is output until I change to a different kit and then back again. ![]() In AD2 the correct kit is selected (with a next to the kit name - presumably indicating it thinks something has been edited - which it hasn't). Help! Addictive Drums 2 MIDI Note ranges/numbers off compared with Sonar PRV? When I save, close and then re-open the project the drums don't sound.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |