Using Oboe in your app? Add it here and we'll list it on the apps page

[philburk]

We need to test AAudio and Oboe on various devices. So if YOU have published an app that uses Oboe, please add a comment to this Issue. Include a link to the Play Store. Thanks!

See list here.

As a start, there are some apps in this repo. Also

1. GStomper uses AAudio.
2. CSound for Android uses Oboe

Also JUCE is using Oboe in experimental mode so that may be some apps there.

[philburk]

From Volcano Mobile https://play.google.com/store/apps/details?id=net.volcanomobile.fluidsynthmidi https://play.google.com/store/apps/details?id=net.volcanomobile.opl3midisynth

[philburk]

Flavio Antonioli wrote that n-Track Studio supports AAudio directly. It currently defaults to OpenSLES but AAudio can be selected in the Settings box. https://play.google.com/store/apps/details?id=com.ntrack.studio.demo

[Diljeet]

Hello Sir, Its an honor to talk to you.

I am the developer of app named Harmonium https://play.google.com/store/apps/details?id=harmonium.music.gameg.real.harmoniumfree It has many users at least 100,000 current users with oboe

I want to help, but don't want the app to be listed on oboe page (not yet), once oboe is in stable version you can list my app on oboe page if you like.

[snip]

Note from philburk - a long bug report was moved to to #227 so that we can address that issue.

[planethcom]

Thanks a lot Phil, for adding G-Stomper to the list :+1:

[atsushieno]

Are those VolcanoMobile apps really using Oboe or AAudio? I'm asking, because their source code never references either of those. (see https://github.com/VolcanoMobile/fluidsynth-android for reference)

[WrobelKrakow]

Hello,

I rewrite Music Player in Best Piano to use Oboe instead of Sound Pool. This app has more than 250k monthly installs.

You can add it to list.

[philburk]

atsushieno wrote:

Are those VolcanoMobile apps really using Oboe or AAudio?

Good question. The answer is yes.

I'm asking, because their source code never references either of those.

Perhaps the developer has not posted the most recent code on GitHub. Here is how you can verify the use of AAudio.

I ran 'adb logcat' while using Volcano Mobile OPL3 Synth and saw: 11-07 18:09:02.101 23777 23790 D AAudio : AAudioStreamBuilder_openStream() returns 0 = AAUDIO_OK for (0x7e770b8000) ----------------

So it is definitely calling AAudio.

I then ran VolcanoMobile FluidSynth and saw: 11-07 18:11:29.292 913 941 I ActivityManager: Start proc 24760:net.volcanomobile.fluidsynthmidi/u0a136 for service net.volcanomobile.fluidsynthmidi/.MidiSynth 11-07 18:11:29.420 24760 24773 D OboeAudio: AAudioLoader(): dlopen(libaaudio.so) returned 0xa16a557d02d13931 11-07 18:11:29.432 24760 24773 D AAudio : AAudioStreamBuilder_openStream() returns 0 = AAUDIO_OK for (0x7e7705cc00) ----------------

So it is calling Oboe, which calls AAudio.

I triggered these apps by launching the Mobileer MIDI Keyboard app and selecting them from the "Receivers" menu: https://source.android.com/devices/audio/midi_test.html#apps

[philburk]

I rewrite Music Player in Best Piano to use Oboe instead of Sound Pool.

I installed the version from November 7th on my Pixel XL. I entered: adb logcat | grep -i audio and then ran "Best Piano".

I did not see any "AAudio" messages. I only saw AudioTrack messages. I looked in Settings but did not see a way to enable it.

[WrobelKrakow]

I installed the version from November 7th on my Pixel XL. I entered: adb logcat | grep -i audio and then ran "Best Piano". I did not see any "AAudio" messages. I only saw AudioTrack messages. I looked in Settings but did not see a way to enable it.

I've set: #define OBOE_ENABLE_AAUDIO 0 to disable AAUDIO because I was thinking i may causes crashes. In next update I will turn it on.

[philburk]

disable AAUDIO because I was thinking i may causes crashes.

You are seeing crashes on 6.0, 7.0, 7.1, 8.0. They do not have AAudio. So Oboe will use OpenSL ES.

[WrobelKrakow]

disable AAUDIO because I was thinking i may causes crashes.

You are seeing crashes on 6.0, 7.0, 7.1, 8.0. They do not have AAudio. So Oboe will use OpenSL ES.

In new version Best Piano available on PlayStore is now using Oboe with AAudio.

[jbloit]

Hi,

We're releasing a series of music education apps using Oboe this week: https://play.google.com/store/apps/developer?id=Les+Talens+Lyriques

Julien

[julioz]

SoundCloud is using Oboe as well. We also wrote about the integration.

[dturner]

Thanks very much for the write up 👍 Added SoundCloud to the list of apps using Oboe.

[erincdemir]

Hey, Don't forget to add my app 😂: https://play.google.com/store/apps/details?id=com.minitunes

Google Oboe implemented in version 2.0 Thanks again to Oboe Team Erinç

[dturner]

Done, thanks for letting us know.

[barsoosayque]

I've written an oboe wrapper (though it isn't fully complete yet) for libGDX. Here be the link. Thought that perhaps this may be useful for some people lurking in the wild net trying to replace the default libGDX android audio module.

[philburk]

@barsoosayque - thanks! libGDX Oboe added.

[atsushieno]

Fluidsynth 2.1 is released, which is the first stable version that supports Oboe: https://github.com/FluidSynth/fluidsynth/releases/tag/v2.1.0

[philburk]

@atsushieno - thanks, I added FluidSynth to AppsUsingOboe

[barsoosayque]

Sorry to bother again, but I recently moved my library from gitlab to github, and I kindly ask you to change libGDX Oboe link to barsoosayque/libgdx-oboe (since I want to remove the gitlab repo in month or so, and it would be nice to prevent confusion with broken links).

[kheldiente]

Hi all, I've released a piano rhythm game called Pinoy Piano: https://play.google.com/store/apps/details?id=kheldiente.midien.pinoypiano&hl=en. I believe this is using the 1.2-stable release. I'm planning to bump it to 1.3-stable soon. Thanks oboe team!

[philburk]

Thanks - I updated libGDX and added Pinoy Piano

[rpattabi]

Please consider adding Pocket Shruti Box. It is using oboe since v2.3.0. In our case, pure data is accessing audio device through oboe. We still provide a way to switch to opensl engine as a fallback (Menu > Audio Issues? > Old Engine). We call oboe as "New Engine" in that dialog.

This is the first step of integrating oboe into our apps. Pocket Shruti Box only uses output stream, though we don't have much issues with opensl engine. We hope to upgrade to oboe to our other app Shruti Carnatic Tuner which uses both input and output streams and has glitchy playback on certain devices through old opensl engine. We think switching to oboe this will help address device specific issues.

[mikedotalmond]

Quieter, Calm - https://play.google.com/store/apps/details?id=quieter.app.calm

Uses Oboe for the all the audio synthesis and effects.

[dturner]

Added Quieter Calm and Pocket Shruti Box

[strommj]

Hey everyone, thanks for the great work. I'm currently using Oboe in my metronome app, "Musicians Aide": https://play.google.com/store/apps/details?id=com.musiciansAide.app

[HitRo-Lab]

Hi all,

Thanks for this awesome library. We're using Oboe in AudioLab Karaoke offline feature to record audio with the lowest latency. https://play.google.com/store/apps/details?id=com.hitrolab.audioeditor

HitRo

[rpattabi]

Please consider adding Shruti Carnatic Tuner. It is using oboe since v7.0.6 release.

Here is something about our use of oboe:

• In our case, pure data is accessing audio device through oboe.
• The main reason why we switched to oboe is our hope that it can help address device specific issues. As per our testing, it indeed helped to address some device specific issues we saw with our opensl engine.
• We're tracking the master branch instead of releases as there are important fixes that are yet to get into release.
• We use both input and output streams. Only one stream is in started state at a time. Other stream will be in stopped state or may yet to be opened. Earlier we attempted at Duplex stream and found that synchronizing between input and output streams is challenging which caused audio glitches and other issues.
• By the way, we still provide a way to switch to opensl engine as a fallback (Menu > Audio Issues? > Old Engine). We call oboe as "New Engine" in that dialog.

A word about oboe team:

We're very thankful for oboe team for providing excellent support. It is clear that they have a good process to work closely with us app developers, AOSP, and even device manufacturers. At times it feels like there is lot more work load for the small team to handle though. The open communication channels is one of the important reasons why we felt more confident about switching to oboe. I wish more google teams learn from oboe team in this regard.

[dturner]

@rpattabi thanks for your kind words - that means a lot :)

Added new apps in this commit https://github.com/google/oboe/commit/9d2aa648537390f666a541836e8756967385e754