So far MIDI components are running on the Android platform, with the exception no input handler is connected to any MIDI input device.
The problem is noted in the Androidapi.Midi.Devices.pas file (line 185), where an JMidiReceiver instance is having issues connecting to JMidiOutputPort.
MIDI output devices are working as expected.
Android somehow managed to break every sense in calling MIDI output devices for input ports, and MIDI input devices for output ports. They say we have to see it from the device point of view, but this is causing confusion because MIDI input and output devices has been understood the other way around since 1983.
MIDI input and output devices are called input and output devices by these components, regardless of how Android see these. Only low-level codes working with Android Midi API need to be aware of this naming mishandling.
/Normann
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So far MIDI components are running on the Android platform, with the exception no input handler is connected to any MIDI input device.
The problem is noted in the Androidapi.Midi.Devices.pas file (line 185), where an JMidiReceiver instance is having issues connecting to JMidiOutputPort.
MIDI output devices are working as expected.
Android somehow managed to break every sense in calling MIDI output devices for input ports, and MIDI input devices for output ports. They say we have to see it from the device point of view, but this is causing confusion because MIDI input and output devices has been understood the other way around since 1983.
MIDI input and output devices are called input and output devices by these components, regardless of how Android see these. Only low-level codes working with Android Midi API need to be aware of this naming mishandling.
/Normann