Related
There does not seem to be ANY app or implementation of a parametric equalizer for ANY device.
Whether it is something that uses the hardware parametric EQ present on some DAC's, something that does it in software, be it the audio player or a system-wide app like the way dspmanager works, where is the parametric EQ?
Sure it may be a challenge to control the hardware properly, but every media player has a fixed-band equalizer. It is not much more work to make it fully parametric.
The early iPods had enough capability to run a 5 band parametric with Rockbox firmware. Many users get these powerful phones in order to be able to stream music, and have it sound right.
Is there ANY app for ANY phone that can correct frequency response precisely?
Search for astro player nova. It's got a 5 band.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
Sorry, thank you.
Is there one that works globally, as DSP Manager does, but parametric? If it doesn't appear within a month I am undertaking my first Android project...
A computer replacement (Just snickered imagining someone using the HDMI out with a USB keyboard and mouse into the charging port) without a parametric eq is a car without a stereo.
Well Astro Player and Astro Player Nova both have 18 band, but no parametric.
Come on, it HAS to exist. Even a little private project somewhere.
k00zk0 said:
There does not seem to be ANY app or implementation of a parametric equalizer for ANY device.
Whether it is something that uses the hardware parametric EQ present on some DAC's, something that does it in software, be it the audio player or a system-wide app like the way dspmanager works, where is the parametric EQ?
Sure it may be a challenge to control the hardware properly, but every media player has a fixed-band equalizer. It is not much more work to make it fully parametric.
The early iPods had enough capability to run a 5 band parametric with Rockbox firmware. Many users get these powerful phones in order to be able to stream music, and have it sound right.
Is there ANY app for ANY phone that can correct frequency response precisely?
Click to expand...
Click to collapse
what kind of phone do you have?
k00zk0 said:
Sorry, thank you.
Is there one that works globally, as DSP Manager does, but parametric? If it doesn't appear within a month I am undertaking my first Android project...
A computer replacement (Just snickered imagining someone using the HDMI out with a USB keyboard and mouse into the charging port) without a parametric eq is a car without a stereo.
Click to expand...
Click to collapse
Did you ever find one or make one?
I agree
Too old post, but I googled it searching about this...
There is too many opinions at forum from "audiophile" aboutapps like dsp manager, v4a or any other eq, but some times thats make not complete result or has no result directly.
In my opinion the most direct way from file to hardware, the best audio quality we make. But at the same time the most common headphones/earphones has poor frequency response/sensibility to enjoy our music and need a little frequency correction and some dynamics compression maybe, for some music genres or movie's audio.
This is where I would like to have a simple linear phase sound processor, with at most 3 bell parametric bands, one for bass boost, one for put in mid/high range for attenuate certain resonant peak (particularly in common earphones 4 a 6 kHz freq response is awfully bad), and one more for trebles. And a dynamic comp to prevent eq result overflow and boost low level sounds. No MORE
sorry my poor English.
Try adsp player for android
Hey, all.
I installed Malaysk's latest ROM on my Eonon GA5151F. It's one of the HuiFei units for a Mazda. Instantly I noticed the sound quality is garbage and am determined to turn it around. On second thought, it might a KDL type unit ... it doesn't actually say under hardware info.
I followed aluver's awesome advice on getting USB audio working after finally getting a FiiO E18 in the mail.
I'm stuck: I can only play via UAPP (USB Audio Player Pro) and even when I do play in UAPP, the sound quickly becomes jumbled and distorted. If I set to 25ms for the buffer, I get about 20 seconds of play time before it crashes.
I've tried a regular 1m cable and even a tiny, short .25m cable but no change.
I do see that I have better luck using alluver's provided audio.primary.rk30board.so file but that only gives me the 20 seconds of play time. That file is 133K in size while the one installed on the unit (or maybe it's from the Malaysk ROM) is 213K. I did not see anywhere in my unit's file to edit and hard write the pcmC2D0c.
Any ideas?
Note: I see a similar thread of a similar issue but thought it would be rude to light back.
I tried to open up the unit but the CD drive is preventing me from getting a good look in. The USB cable that runs from inside to outside the unit is quite long. Seems like it might actually be 1.5 meters.
How can I get in there to pull this thing out and try a short cord? Or should I look in to a powered USB hub (such as the one sold by Carnetix)?
How interesting: I purchased a 7-port powered USB hub (these are quite hard to find in stores!) and now it works! I just plugged the thing in and connected a regular 1m cable to the hub and FiiO and UAPP plays without issue. I did have to enable the first two tweaks in the settings but it's a good start.
Issue continues though: only UAPP will play for me. I am guessing this is a driver issue but not sure where to begin on solving this.
Also, if I have the device turned on while the head unit boots, the head unit sits in safe mode.
@supaneko
Congradulations! Now you have enough power to supply your E18.
About how to make it possible all android sounds going to E18 without UAPP.
All ROMs higher than 4.2 android have audio.primary.rk30board.so file without that numbers to change - it's dynamic.
I have found the other way on 4.4 to make sound routing. It's more right way. Through ALSA.
But I'm not sure I can write a guide now, because I can't remember all I did in details.
And, secondly, I hope there is a more simple way, that was founded by kumarai, that I did not tested yet. His solution is to use system.img from KGL_rk3188_h(20151019) in his ROM. He says he just copied my drivers and wrote insmod strings to install-recovery.sh and all works flawlessly, with hot-plug, as I have working too.
Here is his post with that custom ROM on russian KGL HU forum http://4pda.ru/forum/index.php?showtopic=704299&view=findpost&p=45437941
You can try it (at your own risk, of course)
aluver, your kindness is contagious. Thank you for that.
I will try the link you provided and report back. I'm guessing flashing system.img shouldn't kill me because I can always reflash if needed.
At this point, I am still super determined to get this working. You've helped me in the right direction, aluver. Thanks again!
Well .... I thought that would be useful but I am on an RK3188 unit and then, it also dawned on me, I have the latest Malaysk ROM running. I was thinking I could just install this and extract the install-recovery.sh but it's not for the same unit.
I downloaded the update.rar listed and it only had an update.img in it. I tried to extract it using simg2img but it gives me an error.
I've PM'ed kumarai on here in hopes that he can help me out.
I'll give it another go tomorrow.
@supaneko
Oh, sorry, I thought you have RK3066. That image is not for RK3188 HU of course. But I think it makes things simpler. The trick of kumarai was exactly RK3188 system.img. It must work on RK3188 ROM "from the box" with your HU...
You just need to check what system.img version (date) Malaysk has used for the ROM you have. Or just give me a link to your ROM version. I'll check it by myself.
I use RK3xxx Firmware Tools for unpacking Rockchip update.img, system.img, boot.img & recovery.img
aluver said:
@supaneko
Oh, sorry, I thought you have RK3066. That image is not for RK3188 HU of course. But I think it makes things simpler. The trick of kumarai was exactly RK3188 system.img. It must work on RK3188 ROM "from the box" with your HU...
You just need to check what system.img version (date) Malaysk has used for the ROM you have. Or just give me a link to your ROM version. I'll check it by myself.
I use RK3xxx Firmware Tools for unpacking Rockchip update.img, system.img, boot.img & recovery.img
Click to expand...
Click to collapse
I am using the latest (posted here anyway) Malaysk ROM for 800x480 RK3188: https://yadi.sk/d/R0RY7sxbmmuwi
I located the RK3xxx Tools but .... they're for Windows and I'm on Linux. :\
I'd appreciate the help, aluver.
I have compared system folders of ROMs from kumarai and yours from the link you provided.
They are differ by files at /system/lib
but files at /system/lib/hw are the same
I think something in libaudioflinger.so or other library at /system/lib may do the trick with sound routing.
kumarai's system version 20151012.145613
yours - has a later date - 20151130.180905
Don't understand what's wrong with it...
Now I going to find Malaysk's ROM with same version of system.img as kumarai has.
Can't find needed version among Malaysk's ROMs. Looks like he didn't use that.
The previous to yours version has 20150824.182544 system.img only.
But I have another solution for routing for now.
You can replace audio.primary.rk30board.so by my patched version (already tested on RK3188). Do a backup of the original file, check it's permissions before.
Copy attached audio.primary.rk30board.so to /system/lib/hw folder and change permissions to original file had.
Power off HU and wait few minutes it complitely turned off.
After Power on check the sound is going to DAC (you may hear effect even without reboot - just after replacing the file).
If you will have a problem with sound stucks after some time, you'll need to edit /etc/audio_policy.conf (make backup first)
Delete whole this alsa_usb part of it:
Code:
alsa_usb {
outputs {
alsa_usb {
sampling_rates 44100|48000
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_ANLG_DOCK_HEADSET|AUDIO_DEVICE_OUT_DGTL_DOCK_HEADSET
}
}
inputs {
alsa_usb {
sampling_rates 8000|11025|16000|22050|32000|44100|48000
channel_masks AUDIO_CHANNEL_IN_MONO|AUDIO_CHANNEL_IN_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_IN_ANLG_DOCK_HEADSET
}
}
}
Because it can make a conflict. Reboot is needed to take effect.
By the way, did you have checked insmod's result? It must load all 4 modules *.ko without any errors.
Good luck and post any information about your progress.
SUCCESS!!
The insmod commands were already in there thanks to your original post, aluver. I replaced the .so file originally supplied in that post with what you attached here and ... it works! The ALSA lines were already in there so I didn't need to change that.
IT WORKS! I am terribly excited.
One final thing: if I have the FiiO device turned on when the Android boots, the unit boots into Safe Mode. I suspect there might not be much of a solution for this. Any ideas, aluver?
Alright. Made the drive home and ... it kept on working! I am so happy, aluver. Thank you.
I saw in another thread a mention about the volume control not working. This does indeed seem to be the case for me as well. I tried using the alsa_amixer command in Terminal but get a "Command not found" error when I do.
Out of curiosity, what DSP do you use, aluver?
supaneko said:
The ALSA lines were already in there so I didn't need to change that.
Click to expand...
Click to collapse
You didn't understand - You have to DELETE all that strings I wrote from audio_policy.conf and save it. They make a conflict I think.
supaneko said:
One final thing: if I have the FiiO device turned on when the Android boots, the unit boots into Safe Mode. I suspect there might not be much of a solution for this. Any ideas, aluver?
Click to expand...
Click to collapse
I think this problem should gone, if you delete strings from audio_policy.conf as I told you.
supaneko said:
Alright. Made the drive home and ... it kept on working!
Click to expand...
Click to collapse
Sorry, can't understand this... What drive?
supaneko said:
I saw in another thread a mention about the volume control not working. This does indeed seem to be the case for me as well. I tried using the alsa_amixer command in Terminal but get a "Command not found" error when I do.
Click to expand...
Click to collapse
Did you install Alsamixer from google play? It must be installed before use of mtc-service and\or alsa_amixer commands.
I think we need to make sound routing scheme better. As for me, I made it through alsa, not by replacing digits in audio.primary.rk30board.so.
With alsa configuring, we can make lossless 24bit volume control. Now we have a dynamic range losses because of 16bit volume control only.
Each -6dB from max digital volume are equal to 1-bit of bit depth loss.
I.e. if you listening music at volume position 10 of 30, it is about -40dB, you hear about (16bit - 40/6)~=10bit sound only!
But we know that a human's ear is logarithmic, so we can hear this losses.
To prevent that we can do the trick with adding amount of zero LSBs to make 24bit sound from 16bit source.
Then the digital volume will not become by fear for us.
Sorry for my English. I hope you understand.
supaneko said:
Out of curiosity, what DSP do you use, aluver?
Click to expand...
Click to collapse
I have russian amplifier with built-in modified by myself 8-channels DSP, based on 2 chips Analog Devices ADAU1701. But this DSP is not "for all". The sound processing algorithms for it I build in SigmaStudio. This is hard for usual people, but is very interesting for me .
The chain is: HU RK3066 Android 4.4.4 -> HiFiMeDIY Sabre U2 24/96 USB-DAC -> toslink -> Ryazanpribor X1 mkII (w/mod DSP X5 8channels)-> Focal Performance PS165FX, P25F+Pioneer GM-D8601
aluver said:
You didn't understand - You have to DELETE all that strings I wrote from audio_policy.conf and save it. They make a conflict I think.
I think this problem should gone, if you delete strings from audio_policy.conf as I told you.
Sorry, can't understand this... What drive?
Did you install Alsamixer from google play? It must be installed before use of mtc-service and\or alsa_amixer commands.
I think we need to make sound routing scheme better. As for me, I made it through alsa, not by replacing digits in audio.primary.rk30board.so.
With alsa configuring, we can make lossless 24bit volume control. Now we have a dynamic range losses because of 16bit volume control only.
Each -6dB from max digital volume are equal to 1-bit of bit depth loss.
I.e. if you listening music at volume position 10 of 30, it is about -40dB, you hear about (16bit - 40/6)~=10bit sound only!
But we know that a human's ear is logarithmic, so we can hear this losses.
To prevent that we can do the trick with adding amount of zero LSBs to make 24bit sound from 16bit source.
Then the digital volume will not become by fear for us.
Sorry for my English. I hope you understand.
I have russian amplifier with built-in modified by myself 8-channels DSP, based on 2 chips Analog Devices ADAU1701. But this DSP is not "for all". The sound processing algorithms for it I build in SigmaStudio. This is hard for usual people, but is very interesting for me .
The chain is: HU RK3066 Android 4.4.4 -> HiFiMeDIY Sabre U2 24/96 USB-DAC -> toslink -> Ryazanpribor X1 mkII (w/mod DSP X5 8channels)-> Focal Performance PS165FX, P25F+Pioneer GM-D8601
Click to expand...
Click to collapse
You amaze me, aluver. Again, thank you.
I installed Alsamixer AND the modified MCT service app. Volume control is working! There is one bug though: when I hit the volume up or down, a + and - toast pops up. The problem is that if I go from a volume of 30 down to 0, this +/i will pop up 30 times ... that's along with the volume bar at the bottom of the screen. I can turn it off by turning off the Media keys option in MCT but doing that kills, well, the media keys.
Also, I removed the lines specified from audio_policy.conf. If the FiiO is turned on while Android boots, it still goes in to Safe Mode. I did notice that after removing those lines, I started to get crackling, hissing, and just overall poor sound quality so I re-added the lines and the problems went away. It's still TOO QUIET though!
How can I make these changes you mention in ALSA? I have some sharp hearing myself and it's driving me nuts that things just don't sound as good as they should. I am curious to see your own ALSA parameters.
Quite the setup you have, aluver. I find it inspiring. One day, maybe I'll have the patience to program my own slopes and equalizations. We'll see.
supaneko said:
You amaze me, aluver. Again, thank you.
I installed Alsamixer AND the modified MCT service app. Volume control is working! There is one bug though: when I hit the volume up or down, a + and - toast pops up. The problem is that if I go from a volume of 30 down to 0, this +/i will pop up 30 times ... that's along with the volume bar at the bottom of the screen. I can turn it off by turning off the Media keys option in MCT but doing that kills, well, the media keys.
Click to expand...
Click to collapse
I am glad to help somebody, who has a good target About a + and - toast popups - it can be disabled in the code of mtc-service. I do not like that too, but have no time to make this job.
supaneko said:
Also, I removed the lines specified from audio_policy.conf. If the FiiO is turned on while Android boots, it still goes in to Safe Mode. I did notice that after removing those lines, I started to get crackling, hissing, and just overall poor sound quality so I re-added the lines and the problems went away. It's still TOO QUIET though!
Click to expand...
Click to collapse
It is very interesting effect.... I can't explain it yet. Let's try to determine the problem's cause by looking at logs. Just install CatLog from google play and try to show me what happens at start of HU with FiiO turned on.
supaneko said:
How can I make these changes you mention in ALSA? I have some sharp hearing myself and it's driving me nuts that things just don't sound as good as they should. I am curious to see your own ALSA parameters.
Click to expand...
Click to collapse
Sorry, but I cannot write it right now. I need to collect all information and copy changed drivers from my HU. Then I going to do a full guide. I made my installation at summer, and I am affraid to forget some details.
supaneko said:
Quite the setup you have, aluver. I find it inspiring. One day, maybe I'll have the patience to program my own slopes and equalizations. We'll see.
Click to expand...
Click to collapse
Thank you. All is in our hands. Keep moving
I forgot about "too quiet". Didn't you install any android mixers or volume regulators?
aluver, I haven't forgotten. Been a very busy week.
I got a new DSP and put that in (though not as fancy as your's ). Totally resolved my volume/gain issues but I'm wondering: what do you mean about the volume and the bits changing from 24?
I installed CatLog and when I did a reboot with the DAC powered on, the unit got stuck in a bootloop. It's never done that before. I'll have to give it a try again tomorrow or figure out what's changed to cause that. I'll report back again soon.
Thanks again, aluver!
@supaneko
What DSP did you get? Does it have a remote volume control unit? And what's the cause for volume/gain issues?
About bit depth and volume - read this http://www.head-fi.org/t/671220/eff...e-to-keep-software-at-full-volume-is-nonsense
That is why I say we need 24bit for the lossless volume regulating within HU.
If you have DSP with remote control unit now, you better use that, because it has 56 or 64 bit of internal processing deph (Volume at HU must be 100%).
About a bootloop. You can try to comment the 4 usb-audio driver insmod strings in install-recovery.sh (check the permissions after that! do not lose root!), then reboot without them, run catlog, and then type insmod commands at terminal emulator (don't forget "su" at first), and see what happens in catlog.
aluver said:
@supaneko
What DSP did you get? Does it have a remote volume control unit? And what's the cause for volume/gain issues?
About bit depth and volume - read this http://www.head-fi.org/t/671220/eff...e-to-keep-software-at-full-volume-is-nonsense
That is why I say we need 24bit for the lossless volume regulating within HU.
If you have DSP with remote control unit now, you better use that, because it has 56 or 64 bit of internal processing deph (Volume at HU must be 100%).
About a bootloop. You can try to comment the 4 usb-audio driver insmod strings in install-recovery.sh (check the permissions after that! do not lose root!), then reboot without them, run catlog, and then type insmod commands at terminal emulator (don't forget "su" at first), and see what happens in catlog.
Click to expand...
Click to collapse
@aluver, I picked up an AudioControl DQDX. It has a remote control but it only controls the bass or sets the various delays and other settings. I am thinking of swapping out the DAC I picked up with another single DIN head unit that supports DAC. That way, I can control the volume with an analog dial and still have steering wheel controls work. That's down the road though. I need to upgrade my amp and some other items first. Might just use the volume control on the DAC I picked up for now.
I'll post the CatLog logs in a bit. Thanks again, aluver.
Wow, your DSP is very rare in my world AudioControl's conceptuality is a vintage radicalism.
I don't understand why are you going to swap your DAC with a single DIN HU. In most cases analog volume control can't be used when you build a system with DSP. And analog volume control has it's own noise...
I think you better have to think about swapping of DSP. Something like Helix DSP Pro or anything else, more widely using our time.
About using the volume control on the DAC - You better have to connect your DSP and DAC by digital interface if you don't want to kill the sound by needless DA-AD conversions.
You make me laugh, aluver.
Yeah, one day I'll have the cash for a Helix DSP but ... for now ... I have to be budget conscious. Helix DSP is certainly in the plans though. Just gotta get the "eaiser" stuff like this Android head unit working first!
Again, I'll post the logs later!
aluver, I'm looking over the specs of the Helix DSP and ... wow. I'm impressed. I've added it to my bucket list. Will have to pick one up after I swap out my speakers for better ones.
Those Focal's you run, did you find them too bright at all? I've heard the Focals can be a little bright and I am sensitive to the higher freqs.
Many of you included myself complain about stock music player. It has uncountable problems but as far as I know it is the only player which can use the built in high end DAC. The most annoying thing is that it plays song in alphabetic order if files appear at all and secondly it is very slow.
I would suggest a temporary solution what I did and it works perfectly so far.
Delete all playlist (m3u, cue etc.).
Remove a metadata from files too.
Remove all songs with metadata from the phone!!!
Delete all record from "My Playlist" in the initial screen. (I was able to do it just one by one)
Reset Music Player by deleting cache and data in Application Settings
Reboot phone
Then open Music Player and play songs from Folder option. It will be enough fast and all songs appear and in filename order.
In order to remove metadata from files I would suggest using Mp3tag
http://www.mp3tag.de/en/
If you collect your files in any structure on the PC, all you can do is to move root folder into Mp3tag screen, select all songs and remove tags by right clicking. Then you can copy files to phone.
!!! Be careful !!!
Don't remove tags from your archive music folder. You cannot undo. Always create temporary folder and copy wishing music files there in order to remove metadata (tags).
Good lock!
obladi64 said:
as far as I know it is the only player which can use the built in high end DAC.
Click to expand...
Click to collapse
where the heck did you read this load of bull?
Flaîm said:
where the heck did you read this load of bull?
Click to expand...
Click to collapse
I have read discussions about it but no one was sure in any other player uses it obviously. If you know such please share it with evidence too. Thanks in advance.
obladi64 said:
I have read discussions about it but no one was sure in any other player uses it obviously. If you know such please share it with evidence too. Thanks in advance.
Click to expand...
Click to collapse
unless your device somehow is capable of utilizing magic to process and output audio there's nothing but the only active DAC to do this task, which you can set in your audio settings.
edit: sorry for being a sarcastic ****
Flaîm said:
unless your device somehow is capable of utilizing magic to process and output audio there's nothing but the only active DAC to do this task, which you can set in your audio settings.
edit: sorry for being a sarcastic ****
Click to expand...
Click to collapse
Except there is two DAC for output : AKM and SD820 built-in.
Flaîm said:
unless your device somehow is capable of utilizing magic to process and output audio there's nothing but the only active DAC to do this task, which you can set in your audio settings.
edit: sorry for being a sarcastic ****
Click to expand...
Click to collapse
Ok I was not so precize. Other players don't use AKM dac directly. They do it just via Android which convert all audio input to 48/16 output. Let me know if I am wrong but justify it with something please. Of course then this stream goes to AKM DAC but this not the way we wish it. I welcome any non stock player which can drive dac directly in same way as stock one does. Sooner or later it will be available hopefully but now I don't know any.
If the "Headset HiFi" control in Settings is to switch between SD820 and AKM DACs, then I'm able to use the AKM DAC with other media players that pass audio processing/decoding to the OS (as opposed to fancier players that utilize their own built-in decoding methods/codecs). In my music player of choice (Clean Music), I can switch between the two "Headset HiFi" options (Standard & Super) in the middle of a song and, after a pause to transition, hear a difference between them.
obladi64 said:
Ok I was not so precize. Other players don't use AKM dac directly. They do it just via Android which convert all audio input to 48/16 output. Let me know if I am wrong but justify it with something please. Of course then this stream goes to AKM DAC but this not the way we wish it. I welcome any non stock player which can drive dac directly in same way as stock one does. Sooner or later it will be available hopefully but now I don't know any.
Click to expand...
Click to collapse
didnt know of that. any sources that this is the case?
edit:
according to this documentation it should be a systemwide default value - unless ZTE ****ed that up
https://developer.android.com/reference/android/media/AudioFormat.html
xtermmin said:
If the "Headset HiFi" control in Settings is to switch between SD820 and AKM DACs, then I'm able to use the AKM DAC with other media players that pass audio processing/decoding to the OS (as opposed to fancier players that utilize their own built-in decoding methods/codecs). In my music player of choice (Clean Music), I can switch between the two "Headset HiFi" options (Standard & Super) in the middle of a song and, after a pause to transition, hear a difference between them.
Click to expand...
Click to collapse
I have bad news which is good news actually. SD820 DAC is not used in A7 at all. There are two additional DACs and one ADC. "AKM AK4961 DSP CODEC, which can be considered the primary chipset for Hi-Fi audio playback and recording. The AKM AK4490EN DAC is an independent Hi-Fi audio sampler". This later is what you turn on when set "Headset HiFi" option. So SD820 ADC/DAC don't play at all.
http://www.androidauthority.com/taking-audio-next-level-zte-axon-7-706898/
and same is on ZTE site as well.
I have doubts that you can hear the difference between the two AKM chips while you don't between Clean Player and the built in ZTE player. Although I don't listen 4961 but I do Clean Player. The difference is significant especially if record is 44.1 kHz because conversion of it to 48 kHz is more difficult than of 96kHz record.
obladi64 said:
I have bad news which is good news actually. SD820 DAC is not used in A7 at all. There are two additional DACs and one ADC. "AKM AK4961 DSP CODEC, which can be considered the primary chipset for Hi-Fi audio playback and recording. The AKM AK4490EN DAC is an independent Hi-Fi audio sampler". This later is what you turn on when set "Headset HiFi" option. So SD820 ADC/DAC don't play at all.
http://www.androidauthority.com/taking-audio-next-level-zte-axon-7-706898/
and same is on ZTE site as well.
I have doubts that you can hear the difference between the two AKM chips while you don't between Clean Player and the built in ZTE player. Although I don't listen 4961 but I do Clean Player. The difference is significant especially if record is 44.1 kHz because conversion of it to 48 kHz is more difficult than of 96kHz record.
Click to expand...
Click to collapse
Actually, the SD820 DAC is used and enabled. People with fancy players like PowerAmp (the latest alpha) report that in the app's settings, the only DAC that shows up in the list is the SD820 DAC. No AKM DAC listed.
I'm not an audiophile or anything, but when I have Super selected, the audio has a little more of a "punch" to it, while Standard I can kinda hear a bit of a ceiling. (this is all without ATMOS, of course)
xtermmin said:
Actually, the SD820 DAC is used and enabled. People with fancy players like PowerAmp (the latest alpha) report that in the app's settings, the only DAC that shows up in the list is the SD820 DAC. No AKM DAC listed.
I'm not an audiophile or anything, but when I have Super selected, the audio has a little more of a "punch" to it, while Standard I can kinda hear a bit of a ceiling. (this is all without ATMOS, of course)
Click to expand...
Click to collapse
SD820 in Poweramp: I cannot say anything pro or contra. I try to be smart from commercial b...ts. I don't know any well detailed technical quide. Based on these as engineer I would say that SD820 DAC is not used at all. Phone reports SD820 DAC for third party softwares due to compatibility reason but in real AKM chips works. Like I said I don't know it surly but most likely. I am also searching for the correct answer.
I believe that you hear the difference especialy if PowerAmp turns SD820 on somehow.
Otherwise the two AKM chips are different therefore they should sound differently. To hear it is just question of headphone price. Of course it is without ATMOS.
guess we need @rikin93 to use his contacts to get a definitive answer
Flaîm said:
didnt know of that. any sources that this is the case?
edit:
according to this documentation it should be a systemwide default value - unless ZTE ****ed that up
https://developer.android.com/reference/android/media/AudioFormat.html
Click to expand...
Click to collapse
No. It is justify my concern rather.
"Expressed in Hz, the sample rate in an AudioFormat instance expresses the number of audio samples for each channel per second in the content you are playing or recording. It is not the sample rate at which content is rendered or produced. For instance a sound at a media sample rate of 8000Hz can be played on a device operating at a sample rate of 48000Hz; the sample rate conversion is automatically handled by the platform, it will not play at 6x speed."
obladi64 said:
No. It is justify my concern rather.
"Expressed in Hz, the sample rate in an AudioFormat instance expresses the number of audio samples for each channel per second in the content you are playing or recording. It is not the sample rate at which content is rendered or produced. For instance a sound at a media sample rate of 8000Hz can be played on a device operating at a sample rate of 48000Hz; the sample rate conversion is automatically handled by the platform, it will not play at 6x speed."
Click to expand...
Click to collapse
you missed the important part:
As of API M, sample rates up to 192kHz are supported for AudioRecord and AudioTrack, with sample rate conversion performed as needed. To improve efficiency and avoid lossy conversions, it is recommended to match the sample rate for AudioRecord and AudioTrack to the endpoint device sample rate, and limit the sample rate to no more than 48kHz unless there are special device capabilities that warrant a higher rate.
Click to expand...
Click to collapse
which means that it can be programmed to output at 192 khz, but 48 khz should be the default value if there's no additional hardware.
or am i just misinterpreting this whole paragraph?
so either no player can play at 192 khz, or every player plays at 192 khz
Flaîm said:
you missed the important part:
which means that it can be programmed to output at 192 khz, but 48 khz should be the default value if there's no additional hardware.
or am i just misinterpreting this whole paragraph?
so either no player can play at 192 khz, or every player plays at 192 khz
Click to expand...
Click to collapse
Yes, someting like that. Since it is Androud part it is 48 kHz. I used Clean player as altarnative and I prove that there is difference between this and stock.
So as I understand it says that every source is converted to 48kHz and this is sent to dac. You can play 44.1 or 192 kHz source it doesn't matter streams will be converted to 48. Stock player alone can bypass it so far. And it is important in case of CDs as well becuase 44.1 to 48 conversion is the one of the ugliest thing can happen here.
obladi64 said:
Yes, someting like that. Since it is Androud part it is 48 kHz. I used Clean player as altarnative and I prove that there is difference between this and stock.
So as I understand it says that every source is converted to 48kHz and this is sent to dac. You can play 44.1 or 192 kHz source it doesn't matter streams will be converted to 48. Stock player alone can bypass it so far. And it is important in case of CDs as well becuase 44.1 to 48 conversion is the one of the ugliest thing can happen here.
Click to expand...
Click to collapse
i just tested listening to some flacs in my regular player, vlc player and the zte player with my beyerdynamic custom one pro. either all of them were outputting the same format, or i am just not able to hear the difference.
Flaîm said:
i just tested listening to some flacs in my regular player, vlc player and the zte player with my beyerdynamic custom one pro. either all of them were outputting the same format, or i am just not able to hear the difference.
Click to expand...
Click to collapse
So I am not fan of VLC Player therefore it is not installed on my phone. May be I felt wrongly and there is no difference because it doesn't exist at all and every player drives DAC appropriately. All I know is that I listened music by Clean Music for weeks and than I exchanged to ZTE player. Going through the music repertoire I was surprised. Anyway I am human too.
After all the fact is that you didn't here difference proves only one thing, namely you cannot hear the difference. Here and now.
I will study developer link what you suggested more thoroughly and also I am still waiting for the correct technical details from Android experts. Until I use ZTE player which works fine in above mentioned way. All song appears, all in order, no lag and sound brilliant. What else is needed?
Music Player DAC issue **Fixed**
Hi, I have a fix to using the DAC on non-stock music apps.
So I received my Axon yesterday.
Ipgraded from the Lenovo Vibe X3. I first ran in on the DAC problem on the X3.
In my experience all of these dedicated DAC phones follow the same approach, i.e., LG V10, Vivo Xplay 5, Vibe X3, Axon 7, and (I as sum) LG V20 as well.
There is already a thread on XDA explaining this in detail. -> http://forum.xda-developers.com/lg-v10/general/music-apps-using-dac-t3252596
In short, the apps listed on the V10 page will use the DAC. Although the Vibe X3 had a dedicated DAC toggle, and the Axon 7 doesn't.
To test whether the DAC is being used by a music app on the Axon 7 is:
1. Plugin high fidelity headphones (so you will be able to hear and verify the difference in music), if you can do it with regular earphones/headphones, good for you. and kickass hearing btw
2. Play music on the music app you want to test. (Refer the LG link I posted)
3. while the music s running in the background, go to Settings -> Sounds & Vibration -> Headset Hi-Fi -> and switch between Standard & Super settings.
IF that app is using the DAC, you'll notice a slight pause (when the DAC switches on/off) and of course the difference in sound quality.
Note: Switch Dolby off or ignore it when testing the app, cos for some reason switching Dolby Atmos on/off produces the same gap in playback as the DAC.
On the Vibe X3 it didn't.
I used to use PowerAmp earlier, cos I found that best for my taste.
Then I discovered Neutron, and fell in love with that.
However then I bought a DAC phone & both Power-amp & Neutron don't use the DAC(or I wasn't able to make them)
As per a lot of users online "Poweramp Alpha" can be made to use the DAC on such phones, somehow. I tried fiddling around with it, got fed-up & left it.
If someone has the patience to figure it out AND explain it to me, I'd be grateful, cos Poweramp is my player of choice in terms of UI & ease of usability.
Neutrons latest changelogs mention it can use DAC usage as an update. But I can't notice the difference in the method listed above, or maybe its referring to USB DACs.
Now my player of choice adter going through the list of DAC supported music apps is Pulsar. - https://play.google.com/store/apps/details?id=com.rhmsoft.pulsar
Reason being, I found it to be the lightest/cleanest player which supports the DAC and can relatively smoothly handle my 10K+ collection of 320kbps MP3 & FLAC collection.
You guys can go through the list of apps on the LG V10 page and decide. which suits you best.
h/t @stupc. I've found his thread to be the most informative and bang on in solving the problem of 3rd party DAC phones throughout the net. And trust me, I've searched. Went crazy trying to solve this when I first bought the X3
Hope this helps.
Mods: Please move the post/thread to the appropriate section if required and close the thread as solved.
Hit Thanks if this helped.
Evil0verlord said:
[...]
Click to expand...
Click to collapse
thank you for your answer.
the method to check whether the seperate DAC is being used supports my observation, that i wasnt able to hear a difference between all 3 players i've used.
but i guess the question remains whether the output is in 48khz or 192khz for all of them :/
I'm sceptical about the differing sound quality when switching the "Headset HiFi" setting. I noticed that the volume increases significantly when the setting is on, and goes quieter when switched off. This is a well known and proven psychological sales tactic for audio. The human brain subconsciously associates louder sound to be of higher quality.
In this case it would be very difficult to perfectly volume match the on/off setting of the "Headset HiFi" toggle for a proper blind test. I don't believe any user testing can be trusted unless it's done blind, as confirmation bias could easily take precedence.
Some good reading:
https://en.m.wikipedia.org/wiki/Psychoacoustics
EDIT: I just did some more rudimentary testing with consumer quality mp3s and the ZTE music app, toggling the Headset HiFi setting on/off. The difference in frequency response is very noticeable even when not using high end FLAC encodings. There are significant bumps in bass and treble, even when compared to other sources I have with known flat sound signatures.
So you're asking, what does this mean? There's two scenarios:
1) if the Headset HiFi toggle is indeed switching between the Axon high end DAC and the SD820 standard DAC, the Axon DAC is far from neutral and has a coloured sound with unnaturally increased bass and treble response. This is arguably positive for the average consumer who likes the visceral sensation of an unnatural U-shaped equalizer, but will be disappointing for audiophiles looking for a flat sound signature.
2) the second possibility is that the Headset HiFi toggle does not change which DAC the system is using, but rather is like a Loudness button found on many stereos. When volume decreases, the human ear perceives low and high frequencies dropping off faster than other mid range ones. Loudness buttons are added to stereos so that low volume listening frequency response sounds closer to what the ear perceives at higher volumes.
I have a RoadNavi S160 (Android) installed as a head unit in my car, stock speakers + undearseat subwoofer ( Connected to the rear speakers ). I have flashed the unit with rooted Kotix ROM which has a preinstalled V4A.
I've managed to get it to work with PowerAmp, but thats where it ends...
1. Which settings shoulld i be working with? (headset? speaker? bluetooth? USB? - or all of them? )
I have tried to play around with them, but i am totally lost! - only the speaker tab makes a difference to the sound.
2. The IRS files don't seem to make any difference to the sound ( I can change them, and driver status shows as processing )
3. With the equlizer only(no IRS) the speakers sound either too flat or too distorted
I am not after a highest quality audio, but would like to hear a nice punchy bass and decent vocals ( without cracking speakers! )
Thank you all
Can you use PowerAMP (the app itself?)
If yes! Well Poweramp uses something called "DirectMusicControl" so it will only use PowerAmp no matter what you set in Viper4Android!
Go to settings --> Audio --> Enhanced Settings (in my case the last point on Audio) --> First Entry is the "DirectVolumeControl"
Klick the box so it's unticked and play some music with poweramp while you open up Viper and set everything to your liking!
WARNING: Maybe you should reset ViperSettings to default if possible not that you blow away speakers
Thanks for the reply!
I have already managed to get those two to work together and since posting my initial question I've figured out the way to use the IRS's ( turns out I copied a folder full of files into the kernel, instead of extracting just the files into the existing kernel folder ).
But I must say that I am struggling to get it working as well as it probably can.
The settings within the "headset" tab seem to have no effect whatsoever, and only the settings from the "speaker" tab seem to make a difference.
Having said that, no matter what IRS I use, it just sounds wrong ( too quite, too loud, not enough bass or too much bass )
Thinking about it - is there a way to default v4a to set parameters within the headset tab instead of the speaker?
This would enable me to have a greater controll ( and possibly sort my issues ) over bass, clarity etc.?
Thanks
Patrick050289 said:
Thinking about it - is there a way to default v4a to set parameters within the headset tab instead of the speaker?
This would enable me to have a greater controll ( and possibly sort my issues ) over bass, clarity etc.?
Thanks
Click to expand...
Click to collapse
go to headseat tab, in setting (3dot at upper left at v4a 2.4.0) choose lock effect mode headset
Hello,
i bought a LG V30 a few days ago, because i want to use it as DAC or DAC/AMP.
Before i used an Axon 7 with Viper4Android, a headphone amp (Schiit Vali2) and a custom VDC file for Viper4Android with these settings.
https://www.dropbox.com/s/v999jbft39506ma/Sennheiser HD800.pdf?dl=0
It made a huge difference to use my headphone (Sennheiser HD800) with or without these parametric equalizer settings.
Perhabs it is useful for you, here a link with many different eq settings. Think this can improve sound quality of many headphones or inears.
https://www.reddit.com/r/oratory1990/wiki/index/list_of_presets
1. Most important part, i want the best possible sound quality. Ainur Sauron, Ainur Narsil, Whiskeyomega Soundmods, https://forum.xda-developers.com/lg-v30/themes/magisk-bring-24-bit-output-aosp-pie-t3900863 .....
Dont know, because im new with this phone...
2. I need a parametric equalizer with 10 bands. Viper4Android use VDC files, but i read somewhere that Viper4Android only can handle 48000. And i wanna use the full potential from this Quad DAC.
It is an option for me to use USB Audio Player Pro and if i am right, it is possible to use inbuild parametric eq with only 6 bands.
3. If best sound quality is only with stock roms possible, its ok for me. But if it makes no difference i prefer custom roms. My device is H930, do you have any recommendations?
Hope someone can help me to squeeze the best audio quality from these wonderful device.
Thank you
Adriano
I don't think you can use viper4android with the DAC because viper4android will resample the audio back down to 16 bit @ 48khz. Thus it's pointless to use the DAC + v4a at the same time. Someone correct me if I'm wrong.
Sent from my SM-G955U using Tapatalk
Hi
1.) best possible sound quality - thus you want as little processing as possible (audiophile paradigm) - go with AINUR NARSIL
2.) viper4android is outdated, closed source and is supposed to offer worse quality vs. JamesDSP, both are limited to 48 kHz though
https://github.com/james34602/JamesDSPManager
https://forum.xda-developers.com/android/apps-games/app-reformed-dsp-manager-t3607970
So if you want to go that route, you'll limit yourself to 48 kHz and 16 bit.
according to https://github.com/jaakkopasanen/AutoEq
USB Audio Player PRO
USB Audio Player PRO is an Android app with improved USB audio drivers for usage with USB DACs. USB Audio Player PRO is not system-wide but works with local files and many streaming services though not with Spotify. USB Audio Player has Toneboosters Morphit plugin which has parametric equalizer. This app and the plugin are not free.
Click to expand...
Click to collapse
UAPP with the Morphit plugin (additional purchase) would be the (best?) way to go to retain best possible quality with a parametric equalizer.
Someone needs to try that though and e.g. toggle the quad / SABRE DAC and see how well it works with UAPP and the MorphIt plugin
3.) nope, in fact there's more processing on LG Stock ROMs and thus it sounds warmer and different than the less processed and colder output on AOSP-based ROMs - thus the quality on AOSP-based ROMs should be closer to source (less processing = "better", less additional artifacts and distortions)
LG Stock ROMs are a must though if you're dependent on voLTE or voWiFi
Hope that helps