![]() Fluidsynth has its audio abstraction layer in their drivers source directory, so the only thing I had to do would be just to add another one there, right?įirst, fluidsynth needed to be built with Android NDK toolchains. For Android, AudioTrack and OpenSL ES are the available choices (when I was implementing it there was no AAudio nor Oboe). Fluidsynth is a software synthesizer that supports various audio APIs but not for Android. It was not simple first of all, it does not make sense if there is no sound output. It was designed to make it capable to run a software MIDI synthesizer through the service, so why not porting any of the existing bits? I thought so, and ended up to bring Fluidsynth into Android land. A technically-looking-cool feature is that it supports virtual MIDI device services so that anyone can implement a MIDI device service that can provide either MIDI input devices or MIDI output devices (or both) that other apps can connect as clients and play them just like other operating systems (Windows, Mac, Linux, iOS…). Since Android 6.0, it supports its own MIDI API as well as MIDI connection over BLE, so it became possible to connect MIDI devices to Android (if you would like to read my Japanese article, it’s part of the book “Android Masters!”). One of my unknown projects is Fluidsynth for Android. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |