Hello all,
I've revisited this. I've managed to get a glib build working for Android
(even if I had to hack a few things), and made Atsushi Eno's fork build
with it. I also created a little app to demonstrate.
If you have a Debian distro (or don't mind changing a few bits to get it to
work for yo
converted to cmake
add this in your CMakeFiles.txt to make FluidSynth available to your project
# configure import libs
set(distribution_DIR ${CMAKE_SOURCE_DIR}/../../../../distribution)
### INCLUDE FluidSynth LIBRARY ###
# Get the absolute path to the FluidSynth library directory
get_filename_
https://github.com/googlesamples/android-audio-high-performance/tree/master/SimpleSynth
this a simple synth which generate a sin tone.
just replace the implementation of int Synthesizer::render with a call to
fluid_synth_write.
This project use cmake to build the android native libraries, but yo
OK, thanks - it's certainly easier to build, but I'm really not clear where
I should be calling fluid_synth_write_* - in a driver I've written myself?
Are there any examples I can follow?
On 18 January 2018 at 09:14, Philippe Simons
wrote:
> The issue I have with an audio driver on Android, is t
The issue I have with an audio driver on Android, is that it will never
cover all the uses cases that a dev might need.
For ex:
OpenSL is great for real-time MIDI rendering because it allows to work with
very small buffers. (15ms)
But for a MIDI player, working with small buffer is not a option (i
Ok, further progress, once I sorted out my own dumb JNI bugs..
I can load a soundfont, play a MIDI file, but it rarely gets to the end -
it stops, and won't start again until I restart the test app. The logcat is
full of:
[ 01-17 22:50:13.890 2651: 2717 D/ ]
Hi, this is also my first post to the fluidsynth list, so apologies in
advance for any inadvertent breaches of etiquette!
I've been struggling to build that same fork for a few days, and did manage
it in the end. The problems came down to:
- my Mint distro was not recognised by the setup script (
: FluidSynth mailing list
Subject: Re: [fluid-dev] Android Support
https://github.com/VolcanoMobile/fluidsynth-android
this is my fork of Fluidsynth
basically, I removed the glib dep and all the drivers, so it's up to you to
call fluid_synth_write_s16 to fill a buffer.
it can be a OpenSL b
> what do you think about the idea of a "fluidsynth core" type of build config?
> ie. It just builds the bits required to synthesize the sample data, and no
> audio drivers.
If cmake doesnt find ALSA, OSS, JACK, etc. it wont build any audio drivers.
There are even cmake options like -Denable-ja
It's great that fluidsynth provides audio drivers, but for those of us who
want to take care of actually playing the audio ourselves (in my case I'm
mixing in other waveforms) what do you think about the idea of a
"fluidsynth core" type of build config?
ie. It just builds the bits required to synt
> I read http://fluidsynth.sourceforge.net/api/ and basically understand how to
> set the synthesizer up, but unfortunately I don’t have a clue what to send to
> fluid_synth_write_s16 if I don’t have a driver.
You would use fluid_synth_write_*() to pull synthesized audio from the synth
and man
about this audio
stuff is how to send MIDI commands, so I guess I’m just missing too much
information. Thanks for your time, though.
Best regards,
Nick
From: Philippe Simons
Sent: Sunday, January 7, 2018 9:09 PM
To: FluidSynth mailing list
Subject: Re: [fluid-dev] Android Support
https
building just works out of the box, I could probably look
> after it from there.
>
> I was already briefly in contact with Atsushi, but no solution yet. Maybe
> one of you guys could poke him?
>
>
> Best regards,
>
> Nick
>
> -Original Message----- From: Tom
From: Tom M.
Sent: Sunday, January 7, 2018 7:17 PM
To: Nick Heyworth
Cc: fluid-dev@nongnu.org
Subject: Re: [fluid-dev] Android Support
Supporting OpenSLES would definitely be a nice feature and I already asked
Atsushi to draft another PR at github, but no reaction so far:
https://sourcefo
Supporting OpenSLES would definitely be a nice feature and I already asked
Atsushi to draft another PR at github, but no reaction so far:
https://sourceforge.net/p/fluidsynth/code-git/merge-requests/3/
Overall it looks quite well, however I have no means to actually test this, so
any effort I p
15 matches
Mail list logo
