Midi in 10.5

Audio Plugins
1

Hi jules,

We have been having a problem with 10.5.sdk, where midi messages were not being added to the processors midi buffer. Went through and found that the problem was related to a change between 10.4u and 10.5 sdks. The parameter list of startnote in 10.5 is different, the last patameter inStartframe needs to be UInt32 instead of long as in 10.4
You have fixed HandleMidiEvent which had a similar problem between sdk versions. Keep up the good work!

2

I’m a little confused… If you’re talking about

ComponentResult StartNote (MusicDeviceInstrumentID, MusicDeviceGroupID, NoteInstanceID&, UInt32, const MusicDeviceNoteParams&) { return noErr; }

…then surely I changed it to UInt32 ages ago?

3

Sorry jules, handle midi event needs to be changed from:

OSStatus HandleMidiEvent (UInt8 nStatus,
UInt8 inChannel,
UInt8 inData1,
UInt8 inData2,
long inStartFrame)

to

OSStatus HandleMidiEvent (UInt8 nStatus,
UInt8 inChannel,
UInt8 inData1,
UInt8 inData2,
UInt32 inStartFrame)

in 10.5

4

But I fixed that a while ago with a conditional macro (?) Or do you mean that I need to add both versions of the functions like I did for StartNote, rather than using a macro to decide which one to build?

5

I love this forum…! I did the switch outlined above, and now I get MIDI events in my buffer as well. Thanks!

Jules, I am on the newest Juce trunk 1.46, and still had to “hack” this… Just to let you know :slight_smile: Great work on the plugin stuff though. Awesome to the max.

  • A