Sound falls when AAudio Output (USB) set to 384khz.

[Loweaul]

A user from another forum droped me a issue which I had never seen before.

As the title described,  when he sets the sample rate to 384khz in AAudio Output (USB output particularly), the sound falls significantly (as he said), and if he sets it to 48khz, everything just back to normal.

And of course, the USB adapter he currently using supports 32bits/384khz, the chip as PA detects is CS43131, well, I'm not good at this part.

[Fitzian]

I do wonder if AAudio retains the same sort of limitations with DVC that Hi-Res output method had. 32/384 and DVC didn't exactly play well together for reasons..

[andrewilley]

Yes, it's worth trying with DVC turned off. You may find that the overall volume might be a bit lower though, so if that's a problem for you try using 192kHz instead. 

Andre

[Loweaul]

11 hours ago, andrewilley said:

Yes, it's worth trying with DVC turned off. You may find that the overall volume might be a bit lower though, so if that's a problem for you try using 192kHz instead. 

Andre

Thanks for replying, so it seems like a common issue? I don't really know how low the sound would be since I don't even have that kind of USB adapter (still having 3.5 mm headphones jack).

But personally I really want to know how does it happen in this way, well, if Max would somehow take a look of this thread. 😂

[Loweaul]

On 11/22/2024 at 2:57 AM, andrewilley said:

Yes, it's worth trying with DVC turned off. You may find that the overall volume might be a bit lower though, so if that's a problem for you try using 192kHz instead. 

Andre

Well, he tried to turn the DVC off which then solved the issue, but setting the Sample Rate to 192khz wouldn't solve the problem, for him the only way to save the sound level and DVC is using 48khz, which is still concerning. 🤔

By the way, a few days ago when I tried to access the website, the loading progress seemed to be complete, but the whole page was looking like unloaded, the avatars of different users was stacking on a spot, and the rest of the page was just pure sentences (with links), so it's unlikely to leave a reply for me in that time. And this was not the first time I met such a issue, I tried to use VPN but that didn't turn out fine. Was the website in maintenance?

[6b6561]

10 minutes ago, Loweaul said:

By the way, a few days ago when I tried to access the website, the loading progress seemed to be complete, but the whole page was looking like unloaded, the avatars of different users was stacking on a spot, and the rest of the page was just pure sentences (with links), so it's unlikely to leave a reply for me in that time. And this was not the first time I met such a issue, I tried to use VPN but that didn't turn out fine. Was the website in maintenance?

There was an issue with the site, took some time to realize that there was an issue as it didn't affect users before a browser cached file was expired.

 

[Loweaul]

4 hours ago, 6b6561 said:

There was an issue with the site, took some time to realize that there was an issue as it didn't affect users before a browser cached file was expired.

 

Thanks for replying! seems like a big issue 🤔

[andrewilley]

14 minutes ago, Loweaul said:

Thanks for replying! seems like a big issue 🤔

Actually a smallish issue, but big repercussions.

Andre

[Fitzian]

6 hours ago, Loweaul said:

Well, he tried to turn the DVC off which then solved the issue

As was suggested.

[Loweaul]

On 11/22/2024 at 1:36 AM, Fitzian said:

I do wonder if AAudio retains the same sort of limitations with DVC that Hi-Res output method had. 32/384 and DVC didn't exactly play well together for reasons..

Well... Sorry for missing this reply, I don't remember seeing this last time I checked the thread.

So you mean that there's a limitation with DVC when the sample rate is at 32/384 (in Hi-Res output), I never knew that before. 🤔

[Fitzian]

8 hours ago, Loweaul said:

Well... Sorry for missing this reply, I don't remember seeing this last time I checked the thread.

So you mean that there's a limitation with DVC when the sample rate is at 32/384 (in Hi-Res output), I never knew that before. 🤔

From the FAQ / DVC User Guide:

-Note: for Hi-Res, DVC support depends on firmware and firmware updates and may not work for some. In this case, either disable DVC via No DVC option in PA Settings -> Audio -> Output -> Hi-Res output -> your device or use standard definition output (AudioTrack, OpenSL, or AAudio).

Specific Devices

Samsung Hi-Res 384kHz

DVC is not supported for Samsung Hi-Res Output set to 384kHz. Select 192kHz to get DVC and hi-resolution audio.-

 

I myself do not know the exact means by which DVC functions or fails on one device vs another.

I know the text above focuses on "hi-res" (now deprecated on newer Android versions) and devices' output sample rates being hard-locked to a specific output bit depth. (384 tied to 32, 192 tied to 24, etc)

I'd guess it has something to do with going from floating point to integer, and how the extra bits beyond 24 that determine volume level are handled. 

[Loweaul]

15 hours ago, Fitzian said:

From the FAQ / DVC User Guide:

-Note: for Hi-Res, DVC support depends on firmware and firmware updates and may not work for some. In this case, either disable DVC via No DVC option in PA Settings -> Audio -> Output -> Hi-Res output -> your device or use standard definition output (AudioTrack, OpenSL, or AAudio).

Specific Devices

Samsung Hi-Res 384kHz

DVC is not supported for Samsung Hi-Res Output set to 384kHz. Select 192kHz to get DVC and hi-resolution audio.-

 

I myself do not know the exact means by which DVC functions or fails on one device vs another.

I know the text above focuses on "hi-res" (now deprecated on newer Android versions) and devices' output sample rates being hard-locked to a specific output bit depth. (384 tied to 32, 192 tied to 24, etc)

I'd guess it has something to do with going from floating point to integer, and how the extra bits beyond 24 that determine volume level are handled. 

Thanks for the explanation, well, I think we could only get further with Max's help. 🥲

But this is enough for me now, thanks a lot. 👍