About heavy Midi

Integrations Pure Data
1

Hi，I read the description of heavy midi on the official website of the heavy compiler. Each original midi object has a new alternative object. For example, the original [notein] will be replaced with [r __hv_notein].

so I tried to do this, because my Seed have a Din midi in, and as a result, the external midi note successfully entered Daisy Seed, which is very stable.

But I found that the original [notein] had three outlets, note number, velocity, channel, but there was only one outlet under [r __hv_notein]. How can I identify the channel and velocity? And I found that other hv midi objects also have this problem.

2

Why are you replacing the object? You can just use [notein] and be done.
The compiler does the replacing, this is not something that you should be doing.

Of course make sure your board json has

  "defines": {
    "HAS_MIDI": 1
  },

Our documentation is for both users and developers, maybe we should split this up more in the future if this is causing confusion :wink:

If you really want to know how this receiver works internally look at the object implementation here: hvcc/hvcc/interpreters/pd2hv/libs/pd/notein.pd at develop · Wasted-Audio/hvcc · GitHub

3

Thank you for your reply. I tried taking [note in] but it didn’t work. Did I write my board json correctly? My JSON referenced Daisy Field’s template

  "defines": {
    "OOPSY_TARGET_HAS_MIDI_INPUT": 1
  },

Or do you have to write it according to the JSON you posted？

4

That is the legacy syntax, it’s recommended to use the new one.

Eventually we want to have some better ways for configuring MIDI. Some way to be able to assign specific uart ports and USB to different “ports” inside of the patch.

5

Okay, thank you. I’ll give it a try.