Closed balazsbanto closed 5 months ago
Hey, I think these may be floats actually. Explains why the capacity is 4 * number of frames. Not sure why they're floats, since it should be PCM_16bit by default, but I guess it gets turned into floats around this step of the process.
Changing the get/putShorts to use floats instead works.
Hey, indeed it's strange that the format is float, anyways, thanks for the update! Please ket me know if you figure it out from where does the format come from!
Describe the bug When attempting to apply custom post-processing to the microphone by overriding
capturePostProcessor
throughLiveKitOverrides
, issues arise with the audio output. Using simple gain modification as an example, I encounter one of two problems: If I do not adjust the endianness of the buffer, I only hear bursts of noise. If I set the endianness toByteOrder.LITTLE_ENDIAN
, the voice becomes somewhat audible but is still very noisy.To Reproduce Steps to reproduce the behavior: Modify the sample-app by overriding the
capturePostProcessor
:Expected behavior The voice volume should be noticeably lower when the capturePostProcessor is enabled, without introducing noise or altering the quality of the audio.
Device Info:
Additional context Adjusting the buffer's endianness was an attempt to mitigate the noise issue, but it only partially improves the audio quality, leaving it still very noisy.