trigger problem

[scanz]

while working on the attached sampler project I noticed that if samples are triggered to close to each other the sound gets cut off instead of playing all the way through and sometimes don't sound at all. wasn't sure how to build my own trigger so made the trigger pads by re working a midi keyboard made by loopytunes. not sure if that's where the problem lies or if the sampler is the issue.this is only the second fs project I've done so not sure how to fix it, I thought someone on the forum might be able to help.cheers.

[Spogg]

Hello Mr Scanz!

Sorry for the delay; I've been a bit busy with real life!

I found 2 issues.

-the MIDI note-off from my keyboard was also triggering a sample. This is down to the implementation of MIDI where a note OFF is specified by the NOTE ON at Velocity = zero. This is done so as not to keep sending status bytes and is referred to as RUNNING STATUS see http://www.music-software-development.c ... orial.html
This was resolved by using a little module (not by me) which I have patched into your MIDI inputs. M-Audio use running status for example (my keyboard) and others may do too, so it's a good idea to always put one of these in for simple sample triggering or arpeggiators etc. but not needed when making a polyphonic synth using the MIDI and Voice prims.

-the MIDI generator modules were using sample length to set the note-on time. This means that on longer samples the MIDI message was not always transmitted when rapidly hitting a note/pad. I simply disconnected the note length input and set each one to a fixed time of 10mS and it works fine now on rapid notes.

I do like the look of this project so I hope you make good progress with it.

Cheers

Spogg