Jump to content

Android Mixer still kicks in despite using Hi-Res output when using Dragonfly Cobalt


Recommended Posts

Poweramp Build 883-893
Oneplus 8 Pro (OxygenOS11 Latest stable)

Hey, When i tested the hi res output of 96khz/24 to my Dragonfly cobalt via USB Audio, the Dragonfly only registered 48Khz despite Power-amp saying that its delivering 96Khz audio (this was tested with UAPP uninstalled). When tested using UAPP, the Dragonfly registered 96khz. Is this a bug or am i doing something wrong?

Link to comment
Share on other sites

  • Replies 31
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

System reports 96khz to Poweramp. Still, the direct output often limited just to one instance, thus if any other player/audio source uses it or used recently and not released, you’ll get standard resolution - though it should show 48khz then.

Link to comment
Share on other sites

Posted (edited)

Dragonfly color is still reporting 48kHz after restart as well (and no other application running) though Poweramp still reports as 96kHz being pushed. Its like the android mixer system is still intercepting Poweramp's audio at the end.

Edited by Rowdyhorse4
Link to comment
Share on other sites

1 hour ago, maxmp said:

@Someguyonline right, this gives (saying) 95% accuracy as 5% of the devices report invalid data there (both hi-res may be played and low res reported and vice versa). Actual parameters in this case are visible by analyzing captured audio and playing 20-96khz sweeps.

Yeah, on my MTK based Redmi (MTK hi-fi), for some reason, I don't even see any indication that it's 192kHz output in dumpsys log. But Poweramp still reports it's 192kHz. But on the one with Qualcomm (Direct HD), I can see the output is 192kHz (matches with the info in Poweramp).

 

Link to comment
Share on other sites

  • 4 weeks later...

This is the adb dump for audio flinger.

All my music apps (Spotify, Tidal and Poweramp) displays 48khz on dragonfly (and i persume android auto as well) despite Poweramp reporting 96khz (example). only UAPP seems to bypass this issue all together.

Link to comment
Share on other sites

Posted (edited)
9 minutes ago, andrewilley said:

You take four weeks to reply, and then expect a solution in 24 hours?  As this is a very specialised and expensive bit of kit, I doubt Max has one to hand to do any testing.

Andre

Ah I'm sorry, It was not my intention to be rude or anything, if it was passed that way i'm truly sorry. Social skills isn't one of my strong point hahaha.

alright  thanks for the heads up though. yeah its expensive kit though from looking around it seems that people are saying that android OS just hijacks audio streams and puts it through its 48khz mixer unless you use apps that have specific drivers that support DIRECT. though i'm not an expert in this matter haha

Edited by Rowdyhorse4
Link to comment
Share on other sites

42 minutes ago, Rowdyhorse4 said:

Ah I'm sorry, It was not my intention to be rude or anything, 

Don't worry about it, it just seemed maybe a little bit early to be chasing.

Hopefully your log will give Max some ideas, but if the hardware required specific code to drive it directly, that may not be something we wants to do for lots of individual products.

Andre

Link to comment
Share on other sites

On 4/14/2021 at 12:18 PM, Rowdyhorse4 said:

This is the adb dump for audio flinger.

All my music apps (Spotify, Tidal and Poweramp) displays 48khz on dragonfly (and i persume android auto as well) despite Poweramp reporting 96khz (example). only UAPP seems to bypass this issue all together.

Hmm, from the log, I don't see a direct output thread as I expected. And Android mixer kicking in is normal. Don't worry about that.

 

The weird thing in my opinion is that the logs say there were no USB input nor any USB output threads.... However I am not an expert on this, and I won't be able to assist understanding the logs further.

 

Maybe Max would be able to shed some light on this.... I would suggest waiting for his input.

Link to comment
Share on other sites

2 minutes ago, John Titor said:

Hmm, from the log, I don't see a direct output thread as I expected. And Android mixer kicking in is normal. Don't worry about that.

 

The weird thing in my opinion is that the logs say there were no USB input nor any USB output threads.... However I am not an expert on this, and I won't be able to assist understanding the logs further.

 

Maybe Max would be able to shed some light on this.... I would suggest waiting for his input.

oh lol thats because I was using USB debugging and Dragonfly is a USB device so it wasn't connected. holy fuck now that i realize this is an absolute retard moment for me. let me pull up the flinger via Wireless ADB... once i figure out how to make it work

Link to comment
Share on other sites

1 minute ago, John Titor said:

Lol haha, but please don't post the log from there directly here. Save it into a txt file and drop it here. It's just that.... it's making the page too long and I have to scroll all the way to the bottom to reply  :)

standby, also will do, Good advice. this is the first time debugging for me haha

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...