Closed prasenjitghoshcse closed 1 month ago
The Android binaries were indeed compiled without oboe support. I need to investigate.
Selecting oboe as audio driver through settings parameters, should use oboe and produce audio in Android.
PS: Make sure to evaluate the return value. In this case FLUID_FAILED will be returned, allowing you to handle that error.
This bug seems to be a regression from da7e0d197ef3ff5a3dfdb09b6242f7db931a7f13. I fixed it, pls try those binaries and let me know if it works again: https://dev.azure.com/tommbrt/tommbrt/_build/results?buildId=10637&view=artifacts&pathAsName=false&type=publishedArtifacts
Hi, yes, the binaries you provided works. Thanks for your quick help.
Is there going to be any official release? or I should use the binary you provided?
Ok, great. Fluidsynth 2.3.7 will have binaries as usual. I'll probably take 1-2 weeks until the release.
Thanks for the report!
FluidSynth version
2.3.6 prebuild library package for Android
Describe the bug
Oboe audio driver is not producing any sound in Android. Even if liboboe.so is excluded in the build script, there is no linking error. Seems OBOE dependency is missing in this version of the package.
Expected behavior
Selecting oboe as audio driver through settings parameters, should use oboe and produce audio in Android.
Steps to reproduce
In CMakeList.txt if I place following block for creating my own library, there is no link failure.
target_link_libraries( native-lib
liboboe --------- Note oboe is not linked
)
Additional context
Following is the full CMakeLists.txt