It’s also not controller manufacturer specific - the issues here can be shown with an Arturia controller and an older KORG Triton Extreme controller.įurther, I pointed an Ableton project - which uses C2 - G3 - at MIDI View. This is about the mismatch between the MIDI standard and how TD is manipulating the incoming data (and therefore, the output as well).

This has nothing to do with what I am trying to build. So I still think this is a significant mismatch in how TD interprets MIDI values.Īs previously noted, C2 through G3 should be mapping to a MIDI note value of 36, 38, 40, 41, 43, 45, 47, 48, 50, 52, 53, 55 per multiple available MIDI reference charts. Every other DAW and application I have used will see the C2 as MIDI Note 36 - not 48… not 49. What’s more, rather than being an offset of 12 (perhaps because of some quirk of how Middle C is assigned in TD), this is an odd offset of 13!?!īeen working with MIDI since the early 90s… so I’m really curious where this offset is being introduced so I can understand it if it pops up anywhere else. But I’d prefer to understand where this offset originates. Through trial and error, I was able to determine that the notes that were previously starting with 36, etc… have now shifted to C2 at 49 (see below chart).

However, when I tried to set this very same project up using Touchdesigner as the note generator, I found a 13 value offset in how the note numbers were assigned. Those notes correspond to MIDI note values 36, 38, 40, 41, 43, 45, 47, 48, 50, 52, 53, 55 per multiple available reference charts. I have confirmed through three other methods (MIDI Monitor, VCV Rack, and Ableton) that those are indeed the notes I am using. I’m working with an external hardware MIDI project and have noticed a variance in how Touchdesigner treats MIDI note assignment.įirst, keep in mind that this project does not use TDAbleton, and I do not want to use it for this purpose.

Midi note number 33