Arturia Forums

Harware Legacy versions => Origin => Origin Technical Issues => Topic started by: ASch on September 02, 2012, 08:16:16 pm

Title: MIDI Message Queue bug
Post by: ASch on September 02, 2012, 08:16:16 pm
I'm sending programmatic MIDI messages to my Origin

Scenario 1:

I have a multi loaded, I want to change the program in one of the slots.  I send a MIDI program change message immediately followed by a control change message (control 64, value 127) to turn the hold on. The program changes as expected.  The hold button lights, but the program has NOT actually gone into hold mode.

Scenario 2:

I have a multi loaded, I want to change the program in one of the slots.  I send a MIDI program change message.  I wait some time (not sure of the optimal pause value yet) and then send a control change message (control 64, value 127) to turn the hold on. The program changes as expected.  The hold button lights, and now the program HAS gone into hold mode.

Diagnosis:

In the first case, the program has not finished loading before the hold message is received.  For some reason the UI responds to the hold message, but the program itself does not receive it.

It the second case, the program has enough time to complete loading and receives the hold message and responds accordingly.

Preferred remedy:

Fix the MIDI message queue so the message is correctly delivered to the program.

Alternative remedy:

Fix the UI so it does not report an incorrect status.

Andreas
Title: Re: MIDI Message Queue bug
Post by: ASch on September 05, 2012, 09:18:29 am
Some experiments suggest that a 75ms pause after loading a program into a slot is sufficient before sending further MIDI messages.  50ms is definitely not enough for the program to complete loading...

Andreas