MIDI note data dropout with SuperDirt MIDI about superdirt

[OscarSouth]

Just an update:

I've repeated this test on a different OS now (Manjaro) and the results are identical (wanted to confirm to myself that it wasn't an OS issue on my personal machine).

[telephon]

It is a supercollider issue, perhaps. Could you post an example that is using only MIDIOut to https://github.com/supercollider/supercollider/issues?

[OscarSouth]

@telephon do you mean an example of the MIDI data itself? This example was audio recorded from an audio unit on a different device being triggered by MIDI (no SuperDirt Audio), but I can easily record some MIDI and provide both (just making sure I'm understanding correctly before I post it).

[telephon]

@OscarSouth sorry, I wasn't very clear. What I meant was: could you try a simple example and see if the timing is off, too?

Something like:

// first, initialize your midi device.
(
MIDIClient.init;
MIDIClient.list; // to check, which are there, you can query them
)

(
// create a midi out connection
~midiOut = MIDIOut.newByName("FastLane USB", "Port A"); // substitute your own device here

 // you may want to adjust the latency here
~midiOut.latency = 0.0;
)

// and then:
(
Pbind(
	\type, \midi,
	\midiout, ~midiOut,
	\degree, Prand([1, 2, 3, [0, 5]], inf), 
	\dur, 0.1
).play
)

[OscarSouth]

I was giving a talk yesterday and have been very busy with prep for that so haven't done this yet. Sound check clip!:

https://twitter.com/oscarsouth/status/1024710325386588161

Will do it once I set my equipment back up at home.