KIT PAD BUG
Using BM2 v2.4.6 / iPad3 iOS6:
When loading custom pad kits into a new song, many of the pads behave as if they are MUTED, but they aren't. The only workaround is to add an BLANK FX bus to the new song, then toggle each pad's FX bus assignment back and forth while tapping the pad until its audio glitches and starts playing. Technically, this means that any custom kit with FX bus pad assignments can NEVER BE SAVED ANYWHERE OUTSIDE OF ITS SONG OF ORIGIN, unless you're cool with A) setting up all your FX busses again and dicking around to get all the pads working or
constantly saving your song of origin off as new name. I doubt this was an intentional dev decision. By default, importing a kit should retain bus assignments and play samples even if there aren't busses to avoid confusion. Anyone got a better solution?
When loading custom pad kits into a new song, many of the pads behave as if they are MUTED, but they aren't. The only workaround is to add an BLANK FX bus to the new song, then toggle each pad's FX bus assignment back and forth while tapping the pad until its audio glitches and starts playing. Technically, this means that any custom kit with FX bus pad assignments can NEVER BE SAVED ANYWHERE OUTSIDE OF ITS SONG OF ORIGIN, unless you're cool with A) setting up all your FX busses again and dicking around to get all the pads working or
constantly saving your song of origin off as new name. I doubt this was an intentional dev decision. By default, importing a kit should retain bus assignments and play samples even if there aren't busses to avoid confusion. Anyone got a better solution?