Do MIDI Solutions products introduce any noticeable delay?
MIDI Solutions Processors use fast processing algorithms to ensure that received data is processed and transmitted byte by byte whenever possible. This means that transmission of outgoing data bytes is started even before all bytes of an incoming MIDI message have been received, resulting in latency times that are very small. There are only two circumstances in which MIDI data can be delayed longer. The first is when multiple MIDI messages arrive at the input of a merger at exactly the same moment, one of the messages must be delayed to allow the other to pass through (this of course is a limitation of MIDI, not of the merger). The second is if an outgoing result depends on the value of the following byte. For example, if a MIDI Solutions product is programmed to filter all volume messages above a value of 100, then the third byte of the message (which specifies the volume level) must be received before the MIDI Solutions product can determine whether or not the message should be trans
MIDI Solutions Processors use fast processing algorithms to ensure that received data is processed and transmitted byte by byte whenever possible. This means that transmission of outgoing data bytes is started even before all bytes of an incoming MIDI message have been received, resulting in latency times that are very small. There are only two circumstances in which MIDI data can be delayed longer. The first is when multiple MIDI messages arrive at the input of a merger at exactly the same moment, one of the messages must be delayed to allow the other to pass through (this of course is a limitation of MIDI, not of the merger). The second is if an outgoing result depends on the value of the following byte. For example, if a MIDI Solutions product is programmed to filter all volume messages above a value of 100, then the third byte of the message (which specifies the volume level) must be received before the MIDI Solutions product can determine whether or not the message should be trans
MIDI Solutions Processors use fast processing algorithms to ensure that received data is processed and transmitted byte by byte whenever possible. This means that transmission of outgoing data bytes is started even before all bytes of an incoming MIDI message have been received, resulting in latency times that are very small. There are only two circumstances in which MIDI data can be delayed longer. The first is when multiple MIDI messages arrive at the input of a merger at exactly the same moment, one of the messages must be buffered to allow the other to pass through (this of course is a limitation of MIDI, not of the merger). The second is if an outgoing result depends on the value of the following byte. For example, if a MIDI Solutions product is programmed to filter all volume messages above a value of 100, then the third byte of the message (which specifies the volume level) must be received before the MIDI Solutions product can determine whether or not the message should be tran
