ahlstromcj
commented
6 years ago Can you attach the file or email it to me? Also, is this the ALSA or JACK engine? Thanks for the report! So much to do! :-D
-------- Tim Deagan 13:05 Sun 09 Sep --------
Sigh, so sorry to be bringing up so much foo, I'm just so deep into trying to get Seq64 working in my flame effect project that stuff keeps surfacing.
Problem Description: Incorrect MIDI messages are occasionally substituted for desired messages.
Replication Detail: I have a very simple MIDI file that consists of a series of 8 sequential notes (notes 3C - 43) that are sent in sequence. When running, it occasionally substitutes an incorrect message (in the example below a NoteOn where a NoteOff should be,) for a desired message. I can recreate this behavior with a variety of note sequences. I'm splitting the output of the MIDI port and routing one side back into the machine where I am capturing the resulting input with amidi (results below.)
This was originally noticed when the 8 LEDs on the target MIDI device (representing a configurable set of 8 notes, in this case 3C-43) seemed to be blinking out of order when running various sequences. In performances, these LED indicate open or closed valves which are releasing high pressure propane vapor to create carefully timed fireballs (so, as you may guess, I'm anxious about inadvertantly sending them the wrong messages.)
The problem occurs randomly, approximately every 8-12 cycles of the sequence. I have not captured any
Normal Sequence: 90 3C 64 80 3C 40 90 3D 64 80 3D 40 90 3E 64 80 3E 40 90 3F 64 80 3F 40 90 40 64 80 40 40 90 41 64 80 41 40 90 42 64 80 42 40 90 43 64 80 43 40
Broken Sequence: 90 3C 64 80 3C 40 90 3D 64 80 3D 40 90 3E 64 80 3E 40 90 3F 64 80 3F 40 90 40 64 80 40 40 90 41 64 80 41 40 90 42 64 90 40 64 - Note40 NoteOn msg in place of the missing Note42 NoteOff msg (80 42 40) 90 43 64 80 43 40
— You are receiving this because you are subscribed to this thread. Reply to this email directly, [1]view it on GitHub, or [2]mute the thread.
References
Visible links
-- Bridge ahead. Pay troll.
TDeagan
Sigh, so sorry to be bringing up so much foo, I'm just so deep into trying to get Seq64 working in my flame effect project that stuff keeps surfacing.
Problem Description: Incorrect MIDI messages are occasionally substituted for desired messages.
System: Seq64rt (--disable-shared) running on (known problematic, see #160,) Raspberry Pi 3 with Raspian/Pixel (Debian Stretch) --alsa switch in place
Replication Detail: I have a very simple MIDI file that consists of a series of 8 sequential notes (notes 3C - 43) that are sent in sequence. When running, it occasionally substitutes an incorrect message (in the example below a NoteOn where a NoteOff should be,) for a desired message. I can recreate this behavior with a variety of note sequences. I'm splitting the output of the MIDI port and routing one side back into the machine where I am capturing the resulting input with amidi (results below.)
This was originally noticed when the 8 LEDs on the target MIDI device (representing a configurable set of 8 notes, in this case 3C-43) seemed to be blinking out of order when running various sequences. In performances, these LED indicate open or closed valves which are releasing high pressure propane vapor to create carefully timed fireballs (so, as you may guess, I'm anxious about inadvertantly sending them the wrong messages.)
The problem occurs randomly, approximately every 8-12 cycles of the sequence. I have not captured any
Normal Sequence: 90 3C 64 80 3C 40 90 3D 64 80 3D 40 90 3E 64 80 3E 40 90 3F 64 80 3F 40 90 40 64 80 40 40 90 41 64 80 41 40 90 42 64 80 42 40 90 43 64 80 43 40
Broken Sequence: 90 3C 64 80 3C 40 90 3D 64 80 3D 40 90 3E 64 80 3E 40 90 3F 64 80 3F 40 90 40 64 80 40 40 90 41 64 80 41 40 90 42 64 90 40 64 - Note40 NoteOn msg in place of the missing Note42 NoteOff msg (80 42 40) 90 43 64 80 43 40