Ok, Thanks a lot!
Think, I will show minimum as API 28 cause I have tested it personally.
I understand risks now.
As for "artifacts" - agree, that was wrong word.
I'm using extract with drums kits from Titanic 200. To my taste these
are most naturally sounding kits from available free banks.
At pr
> how could it work on Samsung A50 phone with Api-28 (Android 9) ?
Apparently, this particular function in6addr_any is already available
in API 28. Which is why it works in this particular case.
> And what should I set as minimum target version for the app ?
The minimum target version should be
Том,
Sorry for stupid questions, but i feel slightly confused.
If fluidsynth was build against Api-29 (which is Android 10) how could
it work on Samsung A50 phone with Api-28 (Android 9) ?
And what should I set as minimum target version for the app ?
If, for example I will set it to Api-27 (Androi
The Asus TF300 has an NVIDIA Tegra 3 CPU. This is an ARM Cortex-A9
based processor. And this in turn implements the ARMv7A architecture.
So, the architectures are not the problem.
The real problem seems to be
dlopen failed: cannot locate symbol in6addr_any
The fluidsynth 2.1.5 Android binaries w
Hello Tom,
Thanks for your comments.
Regarding the issue with armeabi-7A - I made several experiments and
it works as follows:
My app supports Android from 23 up to 29.
The test release of the app which was built just for armeabi-7A plays
fine on modern phones with 64 -bit CPU.
Have tested on Xia
> 1) Not enough loud:
It's not clear what you mean by "artifacts". Is it clipping?
Interruptions? Distortions?
Ideally provide the broken audio rendering. But without the soundfont
and a test MIDI it's very hard to tell what's wrong. Try a different
audio driver. Or use the file renderer to write
