You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Platforms you faced the error (IOS or Android or both?)
Android
Expected behavior
When I switch AudioSourceAndroid between MIC, DEFAULT, VOICE_COMMUNICATION etc I'm expecting the audio source to change. Specifically, I'm trying to get it to use the mic on a connected bluetooth headset rather than the onboard mic.
Actual behavior
It always records from the onboard mic, despite trying each option.
Steps to reproduce the behavior
Pass in an AudioSet with one of AudioSourceAndroidType.
const audioSet = {
AudioSourceAndroid: AudioSourceAndroidType.VOICE_COMMUNICATION,
};
/** Open the mic and start the recorder */
const uri = await audioRecorderPlayerRef.current.startRecorder(
audioPath,
audioSet,
true,
);
Can anyone help? It's quite likely I'm just mis-understanding how this works. So apologies in advance.
The text was updated successfully, but these errors were encountered:
Android version
14
Version of react-native-audio-recorder-player
3.6.11
Version of React Native
0.74
Platforms you faced the error (IOS or Android or both?)
Android
Expected behavior
When I switch AudioSourceAndroid between MIC, DEFAULT, VOICE_COMMUNICATION etc I'm expecting the audio source to change. Specifically, I'm trying to get it to use the mic on a connected bluetooth headset rather than the onboard mic.
Actual behavior
It always records from the onboard mic, despite trying each option.
Steps to reproduce the behavior
Pass in an AudioSet with one of AudioSourceAndroidType.
const audioSet = {
AudioSourceAndroid: AudioSourceAndroidType.VOICE_COMMUNICATION,
};
/** Open the mic and start the recorder */
const uri = await audioRecorderPlayerRef.current.startRecorder(
audioPath,
audioSet,
true,
);
Can anyone help? It's quite likely I'm just mis-understanding how this works. So apologies in advance.
The text was updated successfully, but these errors were encountered: