-
Notifications
You must be signed in to change notification settings - Fork 572
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
is it possible to query native input format #275
Comments
Hello
vectorAudioData is of type std::vector<float>, So I was wondering, if there is working low latency code with oboe, so I would know that I have to find the solution somewhere in my code (if I can't find the mistake, non low latency inputstream will also do). |
Please file separate Issues for different topics. Otherwise it is very hard to track and we cannot close one without closing them all. Please file a separate Issue for "oboe::DataCallbackResult::Stop not stopping the callback". Please include OS version and other details. |
If you do not specify the format then Oboe and AAudio should choose the best format. Then you can query it after the stream is opened. There is not currently a way to query before opening the stream. Unfortunately in AudioFlinger, a FLOAT input stream will not get a FAST path. This is being tracked internally as b/38268031 In P we added code to AAudio to open an Int16 stream and then convert to FLOAT internally. |
Please also file a separate Issue for "When I play the recorded data from the low latency inputstream it sounds really bad, mangled." Please include the device and OS. This may be a timing issue for MMAP. |
|
Hello
When creating a low latency input stream, by looking at aaudio echo, I found out that I had to set the format to oboe::AudioFormat::I16.
By default oboe selected float (which works fine for output) and created a non low latency stream.
(oboe::PerformanceMode::LowLatency was requested, tried it on a Nexus 5X with Android 8.1)
So I was wondering if there is a way to query the needed input format for a low latency inputstream.
Also was wondering if it depends on the android version, the android device or is it always oboe::AudioFormat::I16 for input streams?
two offtopic minor questions I'd like to ask:
The results I got were as expected on the audio device, for example no more audio output. Still, in the logs I could see that the callback still got called repeatedly. So I was wondering if that's how it should be. From the name oboe::DataCallbackResult::Stop I would have expected the stream to stop (ideally still playing the frames provided in the callbackcall that returned oboe::DataCallbackResult::Stop).
thanks in advance
schmaden
The text was updated successfully, but these errors were encountered: