Topic: BASS for Android

[sg]

Hi,
what would be the best option to load (user selected) soundfonts on Android?

I use the ACTION_OPEN_DOCUMENT Intent to let the user select the soundfont.
As a result I get an Uri object from which I can retrieve a ParcelFileDescriptor object.

Is there any way to convert this Uri / ParcelFileDescriptor into a parameter that is compatible with the available BASS_MIDI_FontInit methods?


(I don't want to copy the whole soundfont into the app's storage.
This is my current temporary solution, because I have direct access to the file and file name there, but isn't perfect for very large soundfonts.
And loading it through a ByteBuffer results in an OutOfMemoryError for larger files)


Thanks!

[Ian @ un4seen]

When you don't have a filename to give, you can use BASS_MIDI_FontInitUser with BASS_FILEPROCS callback functions instead of BASS_MIDI_FontInit to load a soundfont. BASSMIDI will call your functions to get the file data as needed then.

[sg]

Ok thanks, I will try that!

[sg]

It seems that I am not able to implement the callback function FILESEEKPROC because InputStreams which I can open from URIs do not support seeking.

Apparently the only option to load user selected soundfonts is to copy them into a new file (in the app's storage), which is not perfect, but it works.

(If I'm wrong or there are other ways, feel free to share them, thanks!)

[Ian @ un4seen]

If you use a FileInputStream instead of InputStream then you should be able to seek via the getChannel().position method.

Looking at BASS_MIDI_FontInit again now, I think it should actually already support ParcelFileDescriptor, but the BASSMIDI.JAVA file doesn't contain the required overload yet. Please try adding this line to that file:

Code: [Select]

public static native int BASS_MIDI_FontInit(ParcelFileDescriptor file, int flags);

Also "import android.os.ParcelFileDescriptor;" at the top. And then try using your ParcelFileDescriptor with BASS_MIDI_FontInit.

[sg]

Thanks a lot for the info and help,
this works and is the best solution for my implementation!

[Ian @ un4seen]

Good to hear the BASSMIDI.JAVA update got things working for you. I have now put an updated BASSMIDI.JAVA file in the Android BASSMIDI package. Note a ParcelFileDescriptor overload is also available for BASS_MIDI_StreamCreateFile.

[gicci]

It seems that I am not able to implement the callback function FILESEEKPROC because InputStreams which I can open from URIs do not support seeking.

Apparently the only option to load user selected soundfonts is to copy them into a new file (in the app's storage), which is not perfect, but it works.

(If I'm wrong or there are other ways, feel free to share them, thanks!)

It seems that Ian solved your problem, but anyway I was able to implement a BASS_FILEPROCS that reads from a file the user selected with SAF. You should have done something like this:

Code: [Select]

        ContentResolver resolver = getApplication().getContentResolver();
        ParcelFileDescriptor parcelFileDescriptor = resolver.openFileDescriptor(document.getUri(), "r");
        fileDescriptor = parcelFileDescriptor.getFileDescriptor();
        FileChannel channel = new FileInputStream(fileDescriptor).getChannel();
You can then use the FileChannel to read the data and on it the position() operation should work. Be sure to store the fileDescriptor in a variable of the object to retain it: if it gets garbage collected the channel will be closed.

The difficult thing is to open a SFZ file because you need to fix the paths, but also this can be done.

[teq]

Hi there!
I use Unity with BASS and it works ok, except some cases usually with Samsung devices.
Recently received a message from user that he switched his device to Galaxy a53 and "All tracks crackle and pop while playing visibly in the app gui interface.  Soon as I minimize the app it starts playing perfectly smooth".
I don't have Samsung device yet so maybe there are some suggestions how to solve this?
I suspect hat i should offer audio output methods in the settings(OpenSL, AudioTrack, AAduio).
Currently i use default behavior.

[Ian @ un4seen]

Do you know what Android version the device is running? It looks like the official latest is Android 8.0, which means OpenSLES would be the default output system used but AAudio may also be available. If you can send a test version of your app to the user, please try setting the BASS_CONFIG_ANDROID_AAUDIO option to 1 before calling BASS_Init to enable AAudio, and if that doesn't help, also try raising the BASS_CONFIG_DEV_BUFFER setting (again before BASS_Init).

[teq]

Do you know what Android version the device is running? It looks like the official latest is Android 8.0, which means OpenSLES would be the default output system used but AAudio may also be available. If you can send a test version of your app to the user, please try setting the BASS_CONFIG_ANDROID_AAUDIO option to 1 before calling BASS_Init to enable AAudio, and if that doesn't help, also try raising the BASS_CONFIG_DEV_BUFFER setting (again before BASS_Init).

Thanks for the feedback! Sorry, it was a typo, not Galaxy A5, it was Samsung Galaxy A53 5G with Android 13.
Can i change output method or BASS_CONFIG_DEV_BUFFER after BASS_Init, so if user would like to change this option several times for finding the best sound?

[Ian @ un4seen]

You will need to call BASS_Init again to apply the changes, but you can use the BASS_DEVICE_REINIT flag when doing so, to retain the existing channels/handles. You can also toggle the BASS_DEVICE_AUDIOTRACK flag that way, to enable/disable using AudioTrack output instead of AAudio or OpenSLES.