bOing wrote:I saw nothing on the Roland site that might be helpful for 3rd party integration.
Same here.
bOing wrote:You might, however, try V-DrumLib or MidiPipe for ways to do that. I think this will be where I find my answers too.
Haven't tried MIDI pipe for this sort of thing; it's for routing/processing, isn't it?
VDrumLib bombs out as soon as I try to load anything from the TD into it. I've got the latest version, v1.1.1 PPC, but it's not a happy camper. I can't drag MIDI file versions of my sounds onto it either.
rentadrummer wrote:I don't think that the hi hat offers positional sensing; only bow and edge sounds, or open and closed. And if I'm not mistaken, the three zones on the ride refer to bell, bow and edge. The bow of the ride cymbal does offer positional sensing, but in some cases I've turned it off because I like the sound better without it.
Oh, so the sound abruptly changes from one sample/simulation to the next with no overlap? Yikes; I thought it was more sophisticated than that, but this is good news as it means I'm not really missing out on anything programming the hats from the keyboard. Thank you, Ron.
The ride uses one of the general-purpose controllers; I've forgotten which one, but it's as you've said - I'm only able to influence one of them. The thing is that a strike resets/zeroes the controller value in the TD's memory, meaning that I must input a new one before striking again. Perhaps a clipping scheme along the lines of the choking one I sent you will suffice; obviously it'll only work whilst programming as opposed to playing as I'll need to drag the notes in one at a time. The theory would be to store a single note and its immediately-preceding CC event; I could tweak the velocity of the note as well as the CC value (position) as an integral part of the process.
Another handy clipping set might consist of several controller-only clips at varying densities. These could prove useful for super-imposing over already-played material, IMHO. We'll see. No drama, farmer.
rentadrummer wrote:I've never triggered from a keyboard, but I can record a MIDI track for you by playing my kit, and send the file to you so you can see what the controller data looks like. Maybe it will give you some clues for editing.
As was the case with the tom data you sent me, Ron, I'd imagine it'd be handy to see. I've lost that original file, so if you could play the entire kit, focussing on one area at a time, but as "naturally" as possible, I'll very-much appreciate it, and would keep it for reference due to the lack of electronic kits around here.
rentadrummer wrote:As far as reordering the kits, VDrums Lib is the easiest way to do this. The other option is to back up to a CF card, and copy the kits one by one in the order you want them to appear.
VDL is out, I'm afraid, unless someone can compile it for UB. Oh, and the bugger won't respond to a machine that's been expanded, AFAIK.
The flash-card thing sounds doable but convoluted, and is the only interim-solution I've been able to think of. Once my preferred order has been established, It'll likely remain static. Not sure whether I should keep the new presets separate (but still ordered the same way as my originals), or mix them with the unexpanded ones - there are around 5 categories that I like to use, but if I were to keep them separated, there'd be 10, and auditioning would be trickier. Sounds like a typical monkey mission. LOL
Cheers, fellas. Thank you for everything.
Nicky
