I'm not sure where to post this, but I figured that if I posted it here the people that need to see it will. I finally got mGB working with my new nanoloop USB. I have my midi keyboard sending midi to a simple patch in MaxMSP which I use to manipulate which channels are sent to the NanoUSB. Everything works fantastic, except for one issue.
If I turn the touch response on my keyboard off (or if the velocities for all my notes are the same), the 'sustain' function does not behave properly on PU2. Here is an audio clip that demonstrates what is happening:
https://www.dropbox.com/s/2r8ekzs8n1gk5 … glitch.mp3
And this is what I am doing in this clip:
1. Play simple staccato phrase with sustain function OFF to midi channel 1 (PU1)
2. Play same phrase with sustain function ON to midi channel 1
3. Play same phrase with sustain function OFF to midi channel 2 (PU2)
4. Play same phrase with sustain function ON to midi channel 2
It seems like when the velocities do not change on channel 2, mGB changes notes without retriggering the note. When I send notes to midi channel 5 with the sustain function ON on all channels, PU2 shows the same behavior and is simply silent when it gets to that channel's turn to play.
This begs the question- how are you supposed to correctly send note messages without retrigger messages, or retrigger messages without note messages to mGB?
Where can I find documentation on what midi messages do what on the mGB? I want to be able to change pulse width, panning, envelop, etc on the fly. I know this is possible, but how?
Would it be possible to release a tool that allows you to paste the bytes for replacing some of those noise WAV patterns with your own? Or at the very least the ROM location, so I can change it with my hex editor?
Since the NanoUSB is easy and cheap, mGB is becoming a much more plausible tool for many of us. Is there any reason why mGB is not open source?