I always create a 2-bar file for 1-bar fill, out of which the 1st bar is fill and the 2nd bar contains only a crash on beat 1.

I forwarded this question on to Goran, who creates the content, and this is what he responded: This is the response I received from support… Hope it helps… It’s an obvious and fair musical question into the process of using the product. 'Not sure why this was not posted here or even why it is not part of the basic midi beat creation instructions… If you get them, I’d appreciated getting a copy. Maybe they’ll see this thread and offer them up. Somebody had the SR-16 midi files, but not me. Please correct me if any of the above is not correct or there is a better way to fix the midi volume issue. That is going to be a lot of extra work though. I may try editing the midi volumes in my DAW to see if I can bring the volume up. There is an overall volume slider on the kit creation screen, but it does not seem to do anything. Once the kit is installed it seems to work fine, but the next issue is the overall volume of the kit (using SR-16 midi files), is a lot lower than the standard BeatBuddy kits.You have to create the kit, save it, then import it, then enable it (someone even said you should exit the manager before the import - not sure why). The manual for creating drum kits seems to be non-existant and the procedure for doing it is very convoluted.I downloaded a free Meta Data stripper from the app store for my Mac. Even if you have the 44.1k wav files, BeatBuddy may not play them do to the Meta Data attached to the file.My project was in 44.1k so when I exported each wav file it got converted. Phil’s files above are 96k and sound really bad until you down convert them. One thing that I did not realize was that BeatBuddy only seems to work with 44.1k files.I know this is an old thread, but it is still relevant to anyone attempting to move their beats and kits over from the Alesis SR-16.

Im in love with a stripper midi