Oboe on Chromebook

[rcvangemert]

Hi,
I use OBOE with my android app and find audio input and output selection with OBOE confusing when installed on a Chromebook. The Chromebook has an audio I/O selector in settings and it affects the OBOE selector.

How is it designed to work, should OBOE selection be independent of the Chromebook selection?

Thanks,
Robert

[rcvangemert]

Further checks seem to indicate that if you leave OBOE inputs and outputs on system defaults and use the chromebook audio selector to configure inputs and outputs.

[philburk]

If you leave the deviceId UNSPECIFIED than Oboe/AAudio will choose a default based on a complex algorithm.
If you have plugged in a headset then it is likely to use the headset.
It can also be affected by calling setCommunicationsDevice() when using Usage=VoiceCommunication.
If ChromeBook has a "default audio device" UI then it will, apparently, honor that.

[rcvangemert]

On a chromebook if you plugin in a usb mic it also selects that usb device as a output. The same happens when you plugin a external USB camera. Things get more tricky when you want a external usb camera with a external usb lapel mic. To date I think its best to plug in your devices and use the chromebook selector to select the desired inputs and outputs. Then launch the android app and select both default audio input and output. Thanks for verifying some of my observations.

…

On Sun, 23 Feb 2025, 06:10 Phil Burk, ***@***.***> wrote: If you leave the deviceId UNSPECIFIED than Oboe/AAudio will choose a default based on a complex algorithm. If you have plugged in a headset then it is likely to use the headset. It can also be affected by calling setCommunicationsDevice() when using Usage=VoiceCommunication. If ChromeBook has a "default audio device" UI then it will, apparently, honor that. — Reply to this email directly, view it on GitHub <#2166 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGSW3ESKYAJERR5ELZXZDD2RDDRTAVCNFSM6AAAAABXSVJGIWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRYG44DEOA> . You are receiving this because you authored the thread.Message ID: ***@***.***>