I have been trying to trigger my Nava today with a external MIDI device but I can't get it to work correctly.
What I have found happens is that the NAVA will trigger a sound only once when it receives the correct MIDI note, the unit need to be powered off and restarted for it to respond to a MIDI note signal again.
I'm using firmware version 1.018.
Has anyone else noticed this?
MIDI Bug?
Anyone?
I really want to be able to trigger my Nava with MIDI and currently I can not do it.
I really want to be able to trigger my Nava with MIDI and currently I can not do it.
I think I've worked out the problem....
The Nava doesn't recognise a Midi Note On Message With a Velocity of 0 as a Note Off.
i.e.
This MIDI Message should trigger the bass drum twice, but it only triggers it once because the Nava never "sees" a Note Off message.
This MIDI message triggers the bass drum twice.
The difference between the two is that the 2nd and 4th lines of the first group of messages sends the Note Off as Note On with 0 velocity, where as the second group's 2nd and 4th lines are proper Note Off messages.
The Yocto treats "Note On 0 velocity" correctly (as per the official MIDI spec) as Note Off where as the Nava doesn't.
Can this please be fixed?
The Nava doesn't recognise a Midi Note On Message With a Velocity of 0 as a Note Off.
i.e.
This MIDI Message should trigger the bass drum twice, but it only triggers it once because the Nava never "sees" a Note Off message.
Code: Select all
90 24 76 Chn# 1 Note On C-1 Vel:118
90 24 00 Chn# 1 Note Off C-1 (optimised)
90 24 76 Chn# 1 Note On C-1 Vel:118
90 24 00 Chn# 1 Note Off C-1 (optimized)
This MIDI message triggers the bass drum twice.
Code: Select all
90 24 66 Chn# 1 Note On C-1 Vel:102
80 24 40 Chn# 1 Note Off C-1 Vel:64
90 24 66 Chn# 1 Note On C-1 Vel:102
80 24 40 Chn# 1 Note Off C-1 Vel:64
The Yocto treats "Note On 0 velocity" correctly (as per the official MIDI spec) as Note Off where as the Nava doesn't.
Can this please be fixed?
Problem solved!
I suggested the above to Vincent and he has fixed the issue in a new beta firmware.
I guess he'll post a new version in the near future.
I suggested the above to Vincent and he has fixed the issue in a new beta firmware.
I guess he'll post a new version in the near future.
Great work!
Is the beta firmware already available? If yes where can I get it?
Cheers
Cheers