Related
Hi! I'm a musician and would like to know if there is a good way to connect a stereo microphone to the Samsung Galaxy SIV (3,5 input jack, USB or Bluetooth).
Thanks.
What do you means?
Wanna a good earphone?
jomiber said:
Hi! I'm a musician and would like to know if there is a good way to connect a stereo microphone to the Samsung Galaxy SIV (3,5 input jack, USB or Bluetooth).
Thanks.
Click to expand...
Click to collapse
I wanna take high quality recordings.
Thanks, but I don't want to listen music. I need to record sounds in high quality with my smartphone.
Actually, with the app RecForge Pro, you can use the top and bottom mics on the GS4 to make stereo recordings. The quality is actually very good. The only limitation is that that mics will overload somewhere around 100 dbs, so you can't record a super loud concert. I have a nice Tascam recorder, but I actually just use the RecForge Pro and my GS4 to record our quiet jams/practices. Just make sure, in RecForge Pro, in the Settings to set File Format to Stereo Native. You can set recording level and can recording in 16 bit wav, MP3, or Ogg. RecForge 2 is out from the same guy, but it's in beta and does not yet allow stereo recording.
harpdoc said:
Actually, with the app RecForge Pro, you can use the top and bottom mics on the GS4 to make stereo recordings. The quality is actually very good. The only limitation is that that mics will overload somewhere around 100 dbs, so you can't record a super loud concert. I have a nice Tascam recorder, but I actually just use the RecForge Pro and my GS4 to record our quiet jams/practices. Just make sure, in RecForge Pro, in the Settings to set File Format to Stereo Native. You can set recording level and can recording in 16 bit wav, MP3, or Ogg. RecForge 2 is out from the same guy, but it's in beta and does not yet allow stereo recording.
Click to expand...
Click to collapse
I do actually record a lot with the phones mikes, too (before that with my S2 either).
But it would be a hell of a project, to transform our device to a stereo-recording with better HQ Mikrophones attached.
There is access to the mics. With enough soldering and additional wires and some non permanent connectors, it could be practicable.
BUT i am no expert in circuits - so i will let that part handle someone else! There certainly would be a need for something like that.
Putting a small hightech mike anywhere with a small Smartphone is not that obvious than having a real Recorder with you to have a good bootleg!
jomiber said:
Thanks, but I don't want to listen music. I need to record sounds in high quality with my smartphone.
Click to expand...
Click to collapse
I'm a studio musician myself and have looked into this a bit. You might want to have a leer at USB Audio Recorder Pro (in the play store); getting a high-quality ADC (with built-in mic pre) that is documented as working with that software; and an OTG cable.
Email the gentleman who created USB ARP and he'll give you a few choices that are proven.
Beyond that, get a high-quality USB analog-to-digital converter that works with the software I mentioned and use the mic that you would for a normal recording. I favor the AKG C414 for guitar, but that's just my preference. For field recordings, there are numerous setups to research on sites dedicated to that area.
One issue with Android is that it isn't a real-time OS, and there aren't as many music creation software options that work as there are for iOS. That's also because Apple has a legacy business with pro recording. The only reason I ever bought a mac is because I had to in order to work. All of the recording studios in New York required me to be proficient on it, since I'm a keyboardist and often end up running the show.
However, when it comes to smartphones, I tend to buy Android. I much prefer offerings by Samsung, HTC and Google to the iPhone.
Tablets are another matter. I love my Nexus 7 2014 for everything else, but for music creation and recording, the iPad Air destroys it. That's what I'd tend to use: an iPA with any of the proven ADCs that work with that tablet (and the camera kit) as well as PCs and Macs (no point in having to buy different I/O for my laptop).
The Surface Pro tablets have the potential to do the same in theory (legacy software, true Windows 8.1, etc.), but I haven't had any experience with them. You can read about people who have had on Gearslutz, which might be a better place to ask about recording on the S4.
Thanks for your answers!!!!! They have been very usefull!!!
http://www.ebay.it/itm/Cavo-sdoppia...289?pt=Computer_portatili&hash=item1c3b265d51 this will allow you to connect any microhpone to the audio jack.
Hey has anyone gotten UHQ to work on bluetooth? I just got in the update and it enables when I plug my headphones into the phone but not when connected via BT. Thanks
Sent from my SM-G920V using XDA Free mobile app
whatnow275 said:
Hey has anyone gotten UHQ to work on bluetooth? I just got in the update and it enables when I plug my headphones into the phone but not when connected via BT. Thanks
Sent from my SM-G920V using XDA Free mobile app
Click to expand...
Click to collapse
Not entirely sure if BT can support the bitrate requirement for UHQ. BT isn't really a data heavy protocol.
Sent from my iPhone using Tapatalk
LNJ said:
Not entirely sure if BT can support the bitrate requirement for UHQ. BT isn't really a data heavy protocol.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Okay thanks. Yeah I know BT isnt great for HQ but I guess I was under the impression that the tweaks would work on either.
Sent from my SM-G920V using XDA Free mobile app
whatnow275 said:
Okay thanks. Yeah I know BT isnt great for HQ but I guess I was under the impression that the tweaks would work on either.
Sent from my SM-G920V using XDA Free mobile app
Click to expand...
Click to collapse
To use UHQ on bluetooth connectivity, you must have a compatible Bluetooth Headphone. Check out Samsung Level On Wireless Pro.
Samsung Level on Pro with S7 EDGE
I am currently listening to 24\192 tracks on my S7 edge with PowerAMP alpha and a bluetooth attached Level on Pro. I had my doubts when I read the specs but it is extremely likely that it works for this combination of hardware and software . UHQ via Bluetooth does work.
Galaxy S6 (S6 Edge, Edge+) and S7 (S7 Edge) support UHQ-BT codec developed by Samsung (don't mix with Samsung UHQ upscaler used in stock Music application). This codec allows audio transmittion via Bluetooth 4.0 at a pretty high resulution: 24 bit / 96 kHz (2 channels stereo). In order to be able to use this feature you must use Bluetooth audio device, which supports this codec, for example, headphones Samsung Level series. In order to enable UHQ-BT you need to download the application Samsung Level from Google Play Market and make sure that "UHQ" is enabled. 24 / 96 is the TOP possible limit of UHQ-BT codec for a pair S7 (S7E) + Level headphones. Of course it also depends on the audio file (stream) you're trying to play. If the file itself has low audio resolution with high compression then you cannot get high audio quality. The best audio quality will be when listening to audio files in lossless format (such as flac) with resolution 24 bit / 96 kHz. But there's also a question of how such high resolution was created. One thing is it was made from the original studio recording (made in 24, 36 or 48 bit resolution on professional equipment). And the other thing is if the source for lossless 24/96 audio file was a crappy mp3. A special case would be some vinyl-rip made by an enthusiast on some high-end analog - digital pair. You can find them with resolution as high as 24/192. But most of the time you get some background noise and vinyl crackle. So, the point of such high resolution for vinyl rips in the first place is rather doubtful in my opinion... Also, since UHQ-BT top capability is 24/96 audio resolution, there's no point in using 24/192 for our pair (S7 + Level headphones) UHQ-BT will downscale it to its 24/96 anyway... Other high-res BT codecs available: aptX HD, developed by Qualcomm, which supports HD audio with resolution 24/44, which is a little lower than UHQ-BT. Standard aptX supports CD-audio with resolution up to 16/44, which is even lower. Samsung Galaxy S6 (S6E) and S7 (S7E) support aptX, but do not support aptX HD. If you have a BT audio devise, which supports aptX and are unwilling to get Samsung Level series headphones (Level U, Level U Pro, Level U Pro ANC, Level On, etc...) then aptX supported quality with 16/44 resolution is the highest possible that you'll get. And if your headphones do not support aptX then you will get even lower resolution. The bottomline is get Samsung Level series headphones, if you want to get the highest BT wireless audio quality.
Now, as far as Samsung UHQ upscaler, which is built-in in the Samsung stock Music application, this is a feature, which increases audio resolution programmably. This helps to get the audio sound a little "more smooth" compared with original low-res quality. It removes to certain extent the "digitalness" of the sound, "making connection" between sound "dots" smoother. But it cannot make up high frequency sounds between dots, which may be lost due to low resolution and/or high compression. It simply "doesn't know" they existed.
Hey guys. I swear when I say this that I had a S6 for 2 years and the old samsung music app allowed to enable the UHQ mode even when connected to standard Bluetooth headphones and scrappy speakers started aounding great. In fact I was just surprised at how much of a difference it made. But I updated the app and since then have never gotten it to work over Bluetooth. It still works for wired headphones. But honest to good this feature actually worked and made no difference to which speaker it was connected to.
So I am pretty sure there must be a way to get it to work it is definitely a software matter. I am sure some of you smart folks can figure it out.
What if?
skg27 said:
Galaxy S6 (S6 Edge, Edge+) and S7 (S7 Edge) support UHQ-BT codec developed by Samsung (don't mix with Samsung UHQ upscaler used in stock Music application). This codec allows audio transmittion via Bluetooth 4.0 at a pretty high resulution: 24 bit / 96 kHz (2 channels stereo). In order to be able to use this feature you must use Bluetooth audio device, which supports this codec, for example, headphones Samsung Level series. In order to enable UHQ-BT you need to download the application Samsung Level from Google Play Market and make sure that "UHQ" is enabled. 24 / 96 is the TOP possible limit of UHQ-BT codec for a pair S7 (S7E) + Level headphones. Of course it also depends on the audio file (stream) you're trying to play. If the file itself has low audio resolution with high compression then you cannot get high audio quality. The best audio quality will be when listening to audio files in lossless format (such as flac) with resolution 24 bit / 96 kHz. But there's also a question of how such high resolution was created. One thing is it was made from the original studio recording (made in 24, 36 or 48 bit resolution on professional equipment). And the other thing is if the source for lossless 24/96 audio file was a crappy mp3. A special case would be some vinyl-rip made by an enthusiast on some high-end analog - digital pair. You can find them with resolution as high as 24/192. But most of the time you get some background noise and vinyl crackle. So, the point of such high resolution for vinyl rips in the first place is rather doubtful in my opinion... Also, since UHQ-BT top capability is 24/96 audio resolution, there's no point in using 24/192 for our pair (S7 + Level headphones) UHQ-BT will downscale it to its 24/96 anyway... Other high-res BT codecs available: aptX HD, developed by Qualcomm, which supports HD audio with resolution 24/44, which is a little lower than UHQ-BT. Standard aptX supports CD-audio with resolution up to 16/44, which is even lower. Samsung Galaxy S6 (S6E) and S7 (S7E) support aptX, but do not support aptX HD. If you have a BT audio devise, which supports aptX and are unwilling to get Samsung Level series headphones (Level U, Level U Pro, Level U Pro ANC, Level On, etc...) then aptX supported quality with 16/44 resolution is the highest possible that you'll get. And if your headphones do not support aptX then you will get even lower resolution. The bottomline is get Samsung Level series headphones, if you want to get the highest BT wireless audio quality.
Now, as far as Samsung UHQ upscaler, which is built-in in the Samsung stock Music application, this is a feature, which increases audio resolution programmably. This helps to get the audio sound a little "more smooth" compared with original low-res quality. It removes to certain extent the "digitalness" of the sound, "making connection" between sound "dots" smoother. But it cannot make up high frequency sounds between dots, which may be lost due to low resolution and/or high compression. It simply "doesn't know" they existed.
Click to expand...
Click to collapse
What if I have the S7 and Samsung Level wireless headphones along with the Samsung Level App and the uhq upscaler still is not accessible?
Hi,
Samsung's own UHQA BT audio codec, such as APTx HD or LDAC, has a link bandwidth of 24/96 (512 kbps), but when I connected my Level u pro to my S7 (Exynos) and check it from the developer's menu, it connect with scalable audio codec 16/44. (256 kbps). And I can not change it. in this case 24/96 flac music quality is reduced to cd. Can someone who knows explain?
Hi,
I send Feedback about it to Xiaomi and they said this:
"Dear user,
I am the Xiaomi user feedback group. The feedback about the Equalizer. Due to the adjustment of Xiaomi business, the Q version no longer provides this function, which is inconvenient for you."
So dont expect it on the future versions.
Solution for missing sound setup.
perfect_ said:
Hi,
So don't expect it on the future versions.
Click to expand...
Click to collapse
Not that the stock equalizer that came from Android Pie was any good. We just need people to try and revive the old DogsBark team (Noozxoide Laboratories) and make rootless DSP. I have nothing against Viper, don't get me wrong, on my other device I use Viper Audio, root and all that stuff... but sometimes you just need to stick to the old user/non-dev ways. I am sure it's possible, the problem is the financing and the will to do it. For me, the app developed by them and last updated in 2013 worked like a charm on many devices... except this one, since november update... That's when the problems started to appear.
Since then, I've been looking not just for an equalizer, but a self contained DSP pack that would work better and guess what, nothing's there... nothing except apps with built in function (which by definition are not system wide) and crappy adware.
As for the "Xiaomi business" this really shows me that Xiaomi really gave up on the development of this device, and ALL stock Xiaomi apps will be gone, replaced by Qualcomm's apps... and I don't ever recall seeing any DSP coming directly from Qualcomm.
----------Later addon----------
While the PRO version of Noozxoide EIZO-Rewire PRO has the problems mentioned it seems that the second software Noozxoide EIZO-Rewire Elemental which works even better is still compatible and working just fine on Android 10. Right now it's in testing and benchmarking... which is not an easy job to do, but as long as I love quality music I will do it and post results/download links for it.
-----Download Software-----
Download the Noozxoide EIZO-Rewire Elemental from HERE.
-----Testing abstract-----
For the following tests, were done using only hi-res audio (FLAC/ALAC 96khz 3mbps) files and 320kbps mp3 files so results may vary compared to what I tested here. Remember that streaming services use low bitrate/extremely compressed content.
---Test Speakers---
Internal audio speakers has a good response, bass is there audible, resolution is good, in this case I cannot post any reference to advanced graphs since they are irrelevant in this case.
The best settings (for me) are posted in the first screenshot here. While this is my recommendation, the software doesn't go overboard and keeps the audio quality in control. While testing all the test tracks which varies from Rock/Metal to Acoustic to a more aggressive dubstep there were absolutely NO cracks and pops in audio output from the speaker (which is a result of poor equalization/frequencies outside the speaker range).
---Test Line-Out/Amplified output---
Headphones (because of my current limitations of testing - a conclusive test would be source file vs. processed audio output and multiple headphone test - in ear, open back, ported, etc) were only tested with 3.5mm jack Apple EarPods which are well known to have the best consumer grade frequency response I found that the 2nd attached screenshot works best (for me). While some FLAC files with really deep bass (about 6-10Hz) totally overrun them (and not the Qualcomm audio processor) I would say that this DSP (VSP) works just fine on our devices.
I don't know if I should leave a placeholder here for the advanced, audiophile grade, passive amplified headphones.
---Test Wireless Audio---
Bluetooth and wireless media. Works just as expected. Test were done only with a Nokia BH-503 headset (couldn't test on the car, and neither did I want to spend time going to the car and test it on the BMW Pro-Logic system) but on those headset it made them literally vibrate on the ears, extremely good quality sound, deep bass, crystal clear trebbles and warm mid-tones. Again, I didn't manage to get a single crackle or pop on the speaker drivers which means the equalization done by this engine is sensible and perfectly limited/compressed. The settings I used are posted in the third screenshot.
-----Conclusion-----
The solution posted here works fine, while extensive testing the app still shows that is consumed 0% battery, so the battery drain is minimal.
The application works perfectly after reboot and closing from the recents screen, there were no modifications done/or excluded from the battery optimization screen.
This application is not a booster, this application is a DIGITAL SOUND PROCESSOR controlling the Qualcomm core (was built for this back in the day) and upscaling the audio resolution.
-----Q/A-----
Q: Does this app require any tampering with the system?
A: No, this app is installed as a normal app from the link provided (Play store link)
Q: Does this app work as a system wide equalizer and integrates in other apps?
A: Yes, yes it does, and from my testing it works with all media players (the equalizer option opens up the app), Youtube, Games, etc.
Q: Does this app consume system resources while processing?
A: Yes and no. Of course you need system resources for processing but they aren't that intensive at least for MP3 processing but for FLAC/ALAC processing things get a little more frisky as shown in the 4th screenshot attached.
Q: How's the battery drain overall with FLAC and MP3 playback?
A: Depending on the method of listening the drainage is different, but even on Bluetooth the consumption didn't affect my battery overall.
Q: Does this enable AptX?
A: No. This has nothing to do with that. But while AptX and SBC are not that different in base audio quality, this pushes the codec to 328kbps and upscales the audio to a resolution of 48khz which is ideed great for maxed out mp3 quality over Bluetooth, which again is based on the source files.
----------Thanks----------
If this problem helped you fixed a problem, press the thank you button.
It has been a bit frustrating trying to find an answer to something that I would think would be a common question (or not common since people with real surround systems are rare). Anyway, is it possible to output 5.1 surround sound (Dolby Digital Plus, DTS, etc) to an external device like a TV? If you can't mirror cast/screen cast that, is their a way to get that kind of audio output from some kind of usb-c to hdmi cord/adapter?
If the answer is no to both, and that it's impossible to do at all, why would such a seemingly basic thing never come to be supported?
The only possible way to retain full resolution is using the C port and keep the signal in the digital realm (minimum output should be 24/96 khz) to a quality reciever.
Normally Dolby, DTS, HDCD, etc is then decoded by the reciever and brought into the analog realm.
BT LDAC is the best bluetooth option available for this device, but this will degrade the image.
It lacks the bandwidth to fully support 24 bit/48 khz and higher resolutions.
A degraded image will be especially noticeable with a stereo image or more channels on a room sound system. They lower the resolution, the more of sound stage you lose. Mp3 have about none, CDs better, HDCDs much better, 24 bit and higher, best.
blackhawk said:
The only possible way to retain full resolution is using the C port and keep the signal in the digital realm (minimum output should be 24/96 khz) to a quality reciever.
Normally Dolby, DTS, HDCD, etc is then decoded by the reciever and brought into the analog realm.
BT LDAC is the best bluetooth option available for this device, but this will degrade the image.
It lacks the bandwidth to fully support 24 bit/48 khz and higher resolutions.
A degraded image will be especially noticeable with a stereo image or more channels on a room sound system. They lower the resolution, the more of sound stage you lose. Mp3 have about none, CDs better, HDCDs much better, 24 bit and higher, best.
Click to expand...
Click to collapse
Alright, so, I bought one of these https://www.amazon.com/dp/B07G2GJFF3/ref=cm_sw_r_cp_apa_fabc_KNVWFbWRMZRWP?_encoding=UTF8&psc=1 hooked it up to my TCL 75Q825 TV, and I was able to get a 4K 30fps connection. My TV has an HDMI ARC channel I use to bitstream audio to my Integra DHC-80.3 reciever so that I get Dolby Digital Plus and DTS output from my Smart TV app's shows and movies, but the Note 20 Ultra will only play 2.1 channels.
So if I directly connected the hdmi adapter to the reciever, and fed the video and audio through there to the TV, would I get the 5.1 channel sound? Or am I misunderstanding what you said and basically you can't really do it?
I'm actually going to be returning the hdmi adapter because I found out that there are better adapters that will allow me to have 4K 60fps from my ultra, but honestly, if I can't get HDR out of it and surround sound, I probably will forget the whole thing.
I'm not for sure what the 20 is outputting in the digital realm. It would need to preserve the digital DTS encryption for it to work. Same for Dolby 5.1
I doubt it will glean these though.
However as long as it outputs 24bit/48khz in the digital realm it will preserve the HDCD encoding subtext (my only interest at this point).
Sorry I never had use for this. The C port digital is how the get the highest possible resolution throughput from it.
The hardware/firmware/software must support formats like Dolby 5.1 or DTS.
Does Sammy even support Dolby 5.1 let alone DTS on this?
Sammy been pretty backward in this respect so I doubt it.
Best I can tell it doesn't.
https://www.samsung.com/us/support/answer/ANS00080318/
blackhawk said:
The only possible way to retain full resolution is using the C port and keep the signal in the digital realm (minimum output should be 24/96 khz) to a quality reciever.
Normally Dolby, DTS, HDCD, etc is then decoded by the reciever and brought into the analog realm.
BT LDAC is the best bluetooth option available for this device, but this will degrade the image.
It lacks the bandwidth to fully support 24 bit/48 khz and higher resolutions.
A degraded image will be especially noticeable with a stereo image or more channels on a room sound system. They lower the resolution, the more of sound stage you lose. Mp3 have about none, CDs better, HDCDs much better, 24 bit and higher, best.
Click to expand...
Click to collapse
blackhawk said:
I'm not for sure what the 20 is outputting in the digital realm. It would need to preserve the digital DTS encryption for it to work. Same for Dolby 5.1
I doubt it will glean these though.
However as long as it outputs 24bit/48khz in the digital realm it will preserve the HDCD encoding subtext (my only interest at this point).
Sorry I never had use for this. The C port digital is how the get the highest possible resolution throughput from it.
The hardware/firmware/software must support formats like Dolby 5.1 or DTS.
Does Sammy even support Dolby 5.1 let alone DTS on this?
Sammy been pretty backward in this respect so I doubt it.
Best I can tell it doesn't.
https://www.samsung.com/us/support/answer/ANS00080318/
Click to expand...
Click to collapse
Alright so this is what confused me about the audio capabilities https://www.samsung.com/us/smartphones/galaxy-note20-5g/specs/ just use find in page and put "Dolby" and you should find the sentence that throws me off. Makes it sound like it can at least decode those formats? From my perspective the whole thing just seems odd, I mean to give a piece of hardware those kind of capabilities, and then not be able to output that to something that could really make use of it, makes those capabilities a bit pointless. But to be fair, I do have a usb-c to aux adapter that allows 32 bit audio to pass from the phone to some high end equipment and I rather like it, just wish there was a way to bitstream that audio so as to have a solid surround sound playback.
dece870717 said:
Alright so this is what confused me about the audio capabilities https://www.samsung.com/us/smartphones/galaxy-note20-5g/specs/ just use find in page and put "Dolby" and you should find the sentence that throws me off. Makes it sound like it can at least decode those formats? From my perspective the whole thing just seems odd, I mean to give a piece of hardware those kind of capabilities, and then not be able to output that to something that could really make use of it, makes those capabilities a bit pointless. But to be fair, I do have a usb-c to aux adapter that allows 32 bit audio to pass from the phone to some high end equipment and I rather like it, just wish there was a way to bitstream that audio so as to have a solid surround sound playback.
Click to expand...
Click to collapse
If you go into the reciever in the digital realm and get a Dolby or DTS indicator light up you got your answer.
Don't think you'll see this but it be cool if you did
By the way for HDCDs you don't need a decoder; a reciever with high resolution DAC(s) will glean 90+% of the subtext and yield around a 22 bit image.
You must stay in the digital realm going in though to preserve that encoding.
Many CDs are HDCDs but not marked as such.
Example: B52's Time Capsule album is an HDCD.
blackhawk said:
If you go into the reciever in the digital realm and get a Dolby or DTS indicator light up you got your answer.
Don't think you'll see this but it be cool if you did
By the way for HDCDs you don't need a decoder; a reciever with high resolution DAC(s) will glean 90+% of the subtext and yield around a 22 bit image.
You must stay in the digital realm going in though to preserve that encoding.
Many CDs are HDCDs but not marked as such.
Example: B52's Time Capsule album is an HDCD.
Click to expand...
Click to collapse
Ok so I tried plugging in the hdmi from the adapter directly into the receiver, when I look at the audio information display from the receiver on that input, it shows as 2ch PCM audio as what's being received, tried different apps on my phone that I thought maybe support Dolby Digital Plus (Vudu, Anywhere Movies, and tried MX Player Pro with a couple movie trailers that contain and able to select Dolby Digital audio) but to no avail. And as I thought about it, I forgot something basic that I should have immediately remembered, I won't be able to get actual Dolby Digital Plus or DTS audio coming through to the receiver unless the phone and/or app allowed/had an option of bitstreaming audio. I was hoping though, that at the very least, the phone could send out 5.1 PCM audio. So either the phone just hasn't been given that ability or I need a certain adapter that would allow it.
It would be really awesome if they made the screen mirroring and/or USB-C outputs of a phone more customizable, like being able to adjust video resolution output, color format, bit depth, and of course audio options with bitstreaming and/or speaker channel options.
Make sure the phone's UHQ Upscaler is enabled/active after hook it up.
blackhawk said:
Make sure the phone's UHQ Upscaler is enabled/active after hook it up.
Click to expand...
Click to collapse
I'll try that when I get home, assuming that option becomes selectable, from what I read that option is for use with headphones, I guess I'll find out if that USB-C connection with the adapter allows it to be enabled. I assume it might, I'm sure my USB-C to aux cord would allow its enablement as that connection would be for headphones as well.
I guess this frustration is what I get for being part of that very tiny minority of audio/video "weirdos", lol. What I see as basic options that should be available considering the hardware capabilities of a device, most phone engineers will never think about.
At one point I had a Denon flagship 7.1 reciever driving all identical THX bookshelf speakers with two 400 watt subwoofers on the mains in a stereo configuration.
Excuse me while I kiss the sky
So... now I have this silly Note 10+
And yes Sammy's engineers have dropped the ball with sound so many times their faces are imprinted on the tarmac. Feel the wuv.
blackhawk said:
Make sure the phone's UHQ Upscaler is enabled/active after hook it up.
Click to expand...
Click to collapse
Was able to and enabled the UHQ Upscaler, checked my receivers audio display info, and what it did was change the sampling rate from 44kHz (or I think it was 48kHz) to 192kHz. It's possible that it also raised the audio bit depth, but my receiver didn't display that info.
Yeah best thing that could be done would be Samsung adding a bitstreaming capability, if it had that, a speaker channel option would be less of an issue, since bitstreaming would carry the speaker channel information built into the audio codec that is bitstreamed.
I would think something like that could be implemented through software alone, as whatever source is sending the audio doesn't need to decode it or anything, it just has to be sent untouched.
dece870717 said:
Alright so this is what confused me about the audio capabilities https://www.samsung.com/us/smartphones/galaxy-note20-5g/specs/ just use find in page and put "Dolby" and you should find the sentence that throws me off. Makes it sound like it can at least decode those formats? From my perspective the whole thing just seems odd, I mean to give a piece of hardware those kind of capabilities, and then not be able to output that to something that could really make use of it, makes those capabilities a bit pointless. But to be fair, I do have a usb-c to aux adapter that allows 32 bit audio to pass from the phone to some high end equipment and I rather like it, just wish there was a way to bitstream that audio so as to have a solid surround sound playback.
Click to expand...
Click to collapse
dece870717 said:
Was able to and enabled the UHQ Upscaler, checked my receivers audio display info, and what it did was change the sampling rate from 44kHz (or I think it was 48kHz) to 192kHz. It's possible that it also raised the audio bit depth, but my receiver didn't display that info.
Yeah best thing that could be done would be Samsung adding a bitstreaming capability, if it had that, a speaker channel option would be less of an issue, since bitstreaming would carry the speaker channel information built into the audio codec that is bitstreamed.
I would think something like that could be implemented through software alone, as whatever source is sending the audio doesn't need to decode it or anything, it just has to be sent untouched.
Click to expand...
Click to collapse
Excellent. It may support up to 32 bit certainly 24 bit.
Never looked into that as my music database is .wav and HDCD files. As long as I have 24 bit throughput they're good to go.
I know I wasn't able to rip DTS audio files to hard drive but since I only had one album at the time I dropped the issue.
The only reason I know as much as I do about HDCDs is Tony Harding at Denon* was kind and generous enough in 2004 to fully explain the technology and how to save/decode them. I have over 200 gb of .wav files on my 10+, my whole CD collection in my hand.
That's pretty cool.
Some of the high end audio sites would be good places to find answers. There are definitely people there that know.
*Denon gives near unconditional product support including hardware and firmware. They are on the bleeding edge of high end home audio.
Dollar for dollar they give you the most bang for the buck.
Their flagship receivers rival those costing thousands more including standalone audiophile products.
There devices always exceed their written specs and they support them for life.
Denon has even have issued hardware/firmware upgrades for their flagship recievers which is unheard of at this price point. They've been a industry innovator for over a century.
Rub up against them and you'll be pleasantly surprised.
Hello, I'm going to present to you a method to enable hi-res on the DAC of the Xiaomi Redmi Note 9' family.
The procedure will allow to you to use the full potential of the WCD9385 DAC present (at least) in the Snapdragon 720G.
Indeed, this chip can go up to 32 bits @ 192Khz for PCM stream and can decode natively DSD. Moreover, this chip have a THD+N (Total Harmonics Distortion + Noise) at a level of -108dB, but all audio tests of Xiaomi's phones mesures a THD+N about ~ -96dB, which is the noise floor of 16bits, logic cause by default, this chip is configured to only output in 16 bits mode.
I have setup, tested and experimenting myself on my own phone (Redmi Note 9 Pro - Global Version - MIUI 12.0.2.0 QJZMIXM) this method.
Due to some ROM similarity with other smartphone models in Xiaomi, it will probably works with other smartphones than the Note 9's family, but i will probably need some adjustments if your phone use a different DAC or scheme of audio configuration files.
Before anything :
I'm not responsible of any damage, malfunction or brick that you can do by applying the method. In general, if you don't know what are you doing, just don't do it !
Click to expand...
Click to collapse
Pre-requests :
1) Install ADB, Fastboot and Google ADB Drivers (if you are on Windows)
2) You need to unlock bootloader with Mi-Flash-Unlock (THIS WILL WIPE ALL YOUR PERSONAL DATA, MAKE A SAVE BEFORE STARTING ANYTHING !)
3) Install TWRP for Redmi Xiaomi Note 9
4) You need to root your smartphone with Magisk and install the boot image in fastboot mode that it will give to you.
5) Install ABD_ROOT and ENABLE_ENG Magisk's modules (it will give you the possibility to get root access in ADB) and turn them on for the next device reboot in Magisk App
6) Install MakeSysRW in TWRP (without it we can't remount /vendor partition in Read-Write, and can't touch system's files)
7) Strongly recommanded but not necessary : install Sample Rate Checker from Google Play (with this tool, you can check if the DAC has correctly been set in "HI-RES" mode)
Click to expand...
Click to collapse
Get your phone tuned for Hi-RES :
1) One all of those pre-requests are effectives, you need to get a terminal with adb working (smartphone connected to your PC and debug mode activated) and type :
adb shell mount -o remount,rw /vendor
If you get no errors, you just mounted the partition /vendor on your phone in Read-Write mode, this will allow you to get to the next step, otherwise, i strongly recommand to you to check if you have correctly done all the pre-requests i have described.
2) The next step will save the current audio configuration of your phone (in case you want to return to it for some reasons), still in a terminal window, type :
Code:
adb pull /vendor/etc/audio/audio_policy_configuration.xml ./saved_audio_policy_configuration.xml
adb pull /vendor/etc/audio_io_policy.conf ./saved_audio_io_policy.conf
This will download from your smartphone to your computer the current audio configuration files and save them under "saved_audio_policy_configuration.xml" and "saved_audio_io_policy.conf" in your current directory.
3) Now we will upload configurations files that i've tuned myself, in first case for my personal use.
What changes I've made from the OEM configuration ?
PRIMARY_OUTPUT was in 16 bits @ 48kHz => changed to 24bits @ 192 Khz
RAW_OUTPUT was in 16 bits @ 48 Khz => changed to 24 bits @ 192 Khz
DEEP_BUFFER was in 24bits @ 48 Khz => changed to 24bits @ 192 Khz
Wired Headset, Wired Headphones and Line comes from 16 bits @ 48 Khz, have all been tuned to 24 bits @ 192 Khz
Moreover, i have not touched the integrated speakers because they will not profit to go into 24 bits mode or with an higher sampling rate, and you will get more energy saving by let them as they currently are.
Click to expand...
Click to collapse
If you check the configuration, you will see at points that I tuned this : samplingRates="48000, 96000,192000"
EDIT 22-04-2021 - Few hours after the first release :
I have done this to let Android choose by it's own the sampling rate, because i have seen some sort of clipping on LINE output with OGG (vorbis) files (I assume it will be the same with destructive formats, such as MP3, but it's at least with OGG files) at max volume with very loud musics, i thinks if you set strict resampling at 96 or 192Khz, due to fast algorithms in Android Audio, it will generate some sort of distortion and, if your music is loud enough (and you are at the max volume), it will go over 0dB and clip. So I've maintained sampling rate at 48Khz, and it seems to be well, but if you have some clipping, please tell me in your reply, i will investigate further.
The clipping was effectively done by a resampling mismatches with two configurations files :
audio_policy_configuration.xml (the one that I modified originally)
audio_io_policy.conf
Sampling rates mismatches in audio_io_policy.conf because I left them to the OEM configuration, now it's fixed.
Click to expand...
Click to collapse
You can get my configuration file in the files attached to this post, unzip the files in the current directory where ADB running, then send them to your device :
Code:
adb push ./audio_policy_configuration.xml /vendor/etc/audio/audio_policy_configuration.xml
adb push ./audio_io_policy.conf /vendor/etc/audio_io_policy.conf
This command will overwrite your current configuration files, once again, please be sure to have saved OEM configuration file on your PC !
4) Reboot your phone, and enjoy ! Now you can check with Sample Rate Checker the configuration, you will see something like this (it can be slithly different depending on what is plugged to your phone when you're start the app, in my case i have plugged my phone to an amplifier, so LINE_ANALOG has appears):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see, AudioManager is in 192Khz mode, BUILTIN_EARPIECE correspond to the front top speaker usesed for private communications, and BUILTINT_SPEAKER is the bottom speaker, both of them have remain untouched.
The most interesting is LINE_ANALOG, corresponding to the phone plugged to a LINE output (a high impedance receiver, such as an amplifier), you can see the different Sample Rates supported, up to 192Khz, and Encodings is ENCODING_PCM_FLOAT corresponding to 24 bits (you can compare it with BUILTIN_EARPIECE and BUILTIN_SPEAKER that they are in 16bits mode).
EDIT : i can't attach the file to my post, anyway i sent it to mediafire and there is the download link
Download the Audio Configuration files tuned for HI-RES
If you have any comments, any remarks or want help, do not hesitate to ask.
22/04/2021 - Few hours after the first post :
I have discovered that the mysterious clipping isn't present when i plug/unplug the phone for few seconds, before appearing.
After some research, try and retries, I've found the problem : the file audio_io_policy.conf
In this file is listed all outputs present in the audio_policy_configuration.xml, but i found that all outputs have a fixed 48 kHz sample rate, which don't match with the concatenated ones in the tuned file.
Concretely, internally the sample rates don't matches, and streams (over)sampled above 48 KHz are some sort of clipped.
So I have concatenated samples also in audio_io_policy.conf, and now it works well with all types of musics.
The first post will be edited with modifications that you need to do with the file audio_io_policy.conf
06/13/2021 :
Xiaomi released an update (MIUI V12.0.1.0 - R****M) which introduce Android 11.
My mod is still perfectly working with this update and Android 11 without any modifications !
So, you can still follow this tutorial to enhance your device audio quality
_xenoxis_ said:
... (deleted)
EDIT : i can't attach the file to my post, anyway i sent it to mediafire and there is the download link
Download the Audio Configuration files tuned for HI-RES
If you have any comments, any remarks or want help, do not hesitate to ask.
Click to expand...
Click to collapse
Your audio_policy_configuration.xml has '<globalConfiguration speaker_drc_enabled="true"/>', and this means DRC (Dynamic Range Control) has been enabled on your all audio outputs. This is the reason the THD+N of your device is larger than that of usual hifi devices. Try replace the true with false in your configuration.xml file.
If you like, see maximizing the audio quality of bluetooth.
zyhk said:
Your audio_policy_configuration.xml has '<globalConfiguration speaker_drc_enabled="true"/>', and this means DRC (Dynamic Range Control) has been enabled on your all audio outputs. This is the reason the THD+N of your device is larger than that of usual hifi devices. Try replace the true with false in your configuration.xml file.
If you like, see maximizing the audio quality of bluetooth.
Click to expand...
Click to collapse
Thanks for your reply, i tried on my device but i don't know if I can hear a difference between before and now or if is it a placebo effect.
Android's audio configuration are poorly documented, what does exactly DRC ?
Thanks again for this tips, it will be added in the mod
The sample rate of AudioManager always 192kHZ, not fit the song dynamically.
Even we ignored energy saving(96kHZ, 48kHZ, etc), but how to handle 44.1kHZ case?
SRC still exist in this case right?
RlTd said:
The sample rate of AudioManager always 192kHZ, not fit the song dynamically.
Even we ignored energy saving(96kHZ, 48kHZ, etc), but how to handle 44.1kHZ case?
SRC still exist in this case right?
Click to expand...
Click to collapse
Yes it doesn't fit the song dynamically (at least them which are lossy formatted songs), but this is the android default behaviour, and instead of putting anything in 48kHz (which can be bad for all musics sampled over 48kHz), with my mod it resampling everything at 192Khz, which can avoid frequencies repliement (cf Shannon-Nyquist's theorem) and can be benefit for the DAC's internal logic and post-treatments.
Anyway, some music players on Android define the "passthrough" flag on lossless formats which tell to Android to not upsample.
In 24bits float, upsampling is very precise, and there's be no distortions audible (if there distorsion, it will happen only close to the noise floor, which is inaudible anyway), so you can consider your 44.1Khz to be EXACTLY the same if they are upsampling to 192Khz.
If it was 16bits, I will not tell you the same, in 16bits, the noise floor is at 96Khz, and there's much more conversions errors in Integer than floats, and much more in 16bits than 24 bits, so in this case, it can be destructive.
_xenoxis_ said:
Yes it doesn't fit the song dynamically (at least them which are lossy formatted songs), but this is the android default behaviour, and instead of putting anything in 48kHz (which can be bad for all musics sampled over 48kHz), with my mod it resampling everything at 192Khz, which can avoid frequencies repliement (cf Shannon-Nyquist's theorem) and can be benefit for the DAC's internal logic and post-treatments.
Anyway, some music players on Android define the "passthrough" flag on lossless formats which tell to Android to not upsample.
In 24bits float, upsampling is very precise, and there's be no distortions audible (if there distorsion, it will happen only close to the noise floor, which is inaudible anyway), so you can consider your 44.1Khz to be EXACTLY the same if they are upsampling to 192Khz.
If it was 16bits, I will not tell you the same, in 16bits, the noise floor is at 96Khz, and there's much more conversions errors in Integer than floats, and much more in 16bits than 24 bits, so in this case, it can be destructive.
Click to expand...
Click to collapse
Thanks!
Actually I am using Apple Music beta version which supporting lossless(even hi-res) resource. What can I do to "passthrough" upsample of Android? I saw a module called AINUR NARSIL in Magisk, is that work?
Two most common lossless formats in Apple Music are 16bit_44.1kHZ and 24bit_96kHZ. As you said, 16bit may cause serious problems? BTW, what's the difference between AUDIO_FORMAT_PCM_24_BIT_PACKED and AUDIO_FORMAT_PCM_24_BIT?
If 192kHZ works fine, how about 384？
RlTd said:
Thanks!
Actually I am using Apple Music beta version which supporting hi-res resource. What can I do to "passthrough" upsample of Android? I saw a module called AINUR NARSIL in Magisk, is that work?
Click to expand...
Click to collapse
You can't force to use the passthrough flag, it only depend on the music player implementation, how it use the Android's Audio layer. Apple Music can decode hi-res resources, but it not guaranteed that it use the passthrough flag behind. Anyway with my mod, even it doesn't use the passthrought flag, it will be upscaled to 192Khz which is sufficient for every hi-res listening.
Remember that the passthrough flag only tell to the Android Audio layer to not resampling the audio, which can be bad with music with a low sampling rate (as 44.1Khz or even 48Khz), cause there's no margin for audio processing in the DAC or high frequencies already in the audio source file.
I don't know about if the AINUR NARSIL mod can force the passthrough, the better is to test it yourself i would say
RlTd said:
Two most common lossless formats in Apple Music are 16bit_44.1kHZ and 24bit_96kHZ. As you said, 16bit may cause serious problems? BTW, what's the difference between AUDIO_FORMAT_PCM_24_BIT_PACKED and AUDIO_FORMAT_PCM_24_BIT?
Click to expand...
Click to collapse
Yes 16 bits may cause interpolations errors only if the destination rate isn't a multiple of the original rate and only if Android make the upsampling by maintaining the output level if the destination sampling rate is a multiple of the original one. This is a bit technical, and I don't know what Android decide and do, but in the worst case, yes, 16 bits integer sound makes more interpolation errors cause 16 bits is less precise than 24 bits float and makes more rounding errors.
For your last question, AUDIO_FORMAT_PCM_24BIT doesn't exist.
According to https://android.googlesource.com/platform/hardware/interfaces/+/master/audio/common/4.0/types.hal :
Code:
/* Subformats */
PCM_SUB_16_BIT = 0x1, // PCM signed 16 bits
PCM_SUB_8_BIT = 0x2, // PCM unsigned 8 bits
PCM_SUB_32_BIT = 0x3, // PCM signed .31 fixed point
PCM_SUB_8_24_BIT = 0x4, // PCM signed 8.23 fixed point
PCM_SUB_FLOAT = 0x5, // PCM single-precision float pt
PCM_SUB_24_BIT_PACKED = 0x6, // PCM signed .23 fix pt (3 bytes)
So there's just two different version of representing 24bits data.
You should take a look here, you'll probably learn some tips on how Android handle audio data
_xenoxis_ said:
You can't force to use the passthrough flag, it only depend on the music player implementation, how it use the Android's Audio layer. Apple Music can decode hi-res resources, but it not guaranteed that it use the passthrough flag behind. Anyway with my mod, even it doesn't use the passthrought flag, it will be upscaled to 192Khz which is sufficient for every hi-res listening.
Remember that the passthrough flag only tell to the Android Audio layer to not resampling the audio, which can be bad with music with a low sampling rate (as 44.1Khz or even 48Khz), cause there's no margin for audio processing in the DAC or high frequencies already in the audio source file.
I don't know about if the AINUR NARSIL mod can force the passthrough, the better is to test it yourself i would say
Yes 16 bits may cause interpolations errors only if the destination rate isn't a multiple of the original rate and only if Android make the upsampling by maintaining the output level if the destination sampling rate is a multiple of the original one. This is a bit technical, and I don't know what Android decide and do, but in the worst case, yes, 16 bits integer sound makes more interpolation errors cause 16 bits is less precise than 24 bits float and makes more rounding errors.
For your last question, AUDIO_FORMAT_PCM_24BIT doesn't exist.
According to https://android.googlesource.com/platform/hardware/interfaces/+/master/audio/common/4.0/types.hal :
Code:
/* Subformats */
PCM_SUB_16_BIT = 0x1, // PCM signed 16 bits
PCM_SUB_8_BIT = 0x2, // PCM unsigned 8 bits
PCM_SUB_32_BIT = 0x3, // PCM signed .31 fixed point
PCM_SUB_8_24_BIT = 0x4, // PCM signed 8.23 fixed point
PCM_SUB_FLOAT = 0x5, // PCM single-precision float pt
PCM_SUB_24_BIT_PACKED = 0x6, // PCM signed .23 fix pt (3 bytes)
So there's just two different version of representing 24bits data.
Click to expand...
Click to collapse
Much to learn.
One more question: your Sample Rate Checker showed that "LINE_ANALOG Encodings" is AUDIO_FORMAT_PCM_FLOAT. I got same result with my earphone. Our related setting should be AUDIO_FORMAT_PCM_24_BIT_PACKED. Thus i am confusing about that. Do you know why?
Here is my log and its screenshots. Some FLOAT words also appeared in it. Looks like Qualcomm handle audio by FLOAT format. I don't know if they have similar reason.
RlTd said:
One more question: your Sample Rate Checker showed that "LINE_ANALOG Encodings" is AUDIO_FORMAT_PCM_FLOAT. I got same result with my earphone. Our related setting should be AUDIO_FORMAT_PCM_24_BIT_PACKED. Thus i am confusing about that. Do you know why?
Here is my log and its screenshots. Some FLOAT words also appeared in it. Looks like Qualcomm handle audio by FLOAT format. I don't know if they have similar reason.
Click to expand...
Click to collapse
AUDIO_FORMAT_PCM_24_BIT_PACKED is the sub-format which is the float format in Android (as showed in my last reply), it contain only factional part and no integer part.
AUDIO_FORMAT_PCM_FLOAT is just a short alias which refer to it.
So, AUDIO_FORMAT_PCM_24_BIT_PACKED is strictly equal to AUDIO_FORMAT_PCM_FLOAT.
Apparently on your device, is it already setup to handle hifi audio in the record processing as well as the output, everything is in 24bits (float) @ 384KHz, which is very nice !
Which device is it ?
_xenoxis_ said:
AUDIO_FORMAT_PCM_24_BIT_PACKED is the sub-format which is the float format in Android (as showed in my last reply), it contain only factional part and no integer part.
AUDIO_FORMAT_PCM_FLOAT is just a short alias which refer to it.
So, AUDIO_FORMAT_PCM_24_BIT_PACKED is strictly equal to AUDIO_FORMAT_PCM_FLOAT.
Apparently on your device, is it already setup to handle hifi audio in the record processing as well as the output, everything is in 24bits (float) @ 384KHz, which is very nice !
Which device is it ?
Click to expand...
Click to collapse
Xiaomi mix2s with snapdragon 845.
Its integrated audio codec DSP is WCD9341, which has better dynamic range than WCD9385(snapdragon 888).
WCD9341 | Qualcomm
www.qualcomm.com
I carry it everyday as a "hi-fi" player.
RlTd said:
Xiaomi mix2s with snapdragon 845.
Its integrated audio codec DSP is WCD9341, which has better dynamic range than WCD9385(snapdragon 888).
WCD9341 | Qualcomm
www.qualcomm.com
I carry it everyday as a "hi-fi" player.
Click to expand...
Click to collapse
I can see the THD+N (Total Harmonics Distortions + Noise) is at -109dB for the WCD9341 and at -108 for the WWCD9385, which is exactly the same (you can't hear the difference, i dare anyone to tell me otherwise).
Don't refer to the "Playback Dynamic Range", which don't represent what is it outputted (you have to add the noise and the harmonics distortions).
You're very right to use it as a everyday hifi player ! I'm very surprise that Xiaomi has think to set the DAC in a hi-res mode by default. I'm wondering why they haven't do the same for their new devices .
_xenoxis_ said:
You're very right to use it as a everyday hifi player ! I'm very surprise that Xiaomi has think to set the DAC in a hi-res mode by default. I'm wondering why they haven't do the same for their new devices .
Click to expand...
Click to collapse
Actually I also changed configs as your mod and turn more items else to 24bit/384kHZ to ensure hi-res works. However, i don't know which features are essential for me.
RlTd said:
Actually I also changed configs as your mod and turn more items else to 24bit/384kHZ to ensure hi-res works. However, i don't know which features are essential for me.
View attachment 5361457
View attachment 5361459
View attachment 5361461
View attachment 5361463
Click to expand...
Click to collapse
"hifi_playback" is just an unused output which isn't routed to anything, so don't mind about it.
About your sampling rate change to 384kHz, this will not gonna set it to 384Khz cause you don't change the file "audio_io_policy.conf" where is the i/o configuration (currently, your configuration can cause some volume saturation as it done the first time I tried my mod on my device).
You need to set 384KHz as well in this file.
Moreover, is it useless to set the USB output over to 192Khz, I don't know a device in USB which can handle 384KHz audio on a USB connection.
However, I don't think there's a reel benefit to set the DAC to 384KHz, I mean the maximum sampling rate in PCM hi-res file is 192Khz (still rare actually) and I never seen anything beyond this value. Typically a hi-res file is in [email protected]
So what i'm trying to say, is that a change from [email protected] to [email protected] is beneficial, for many reasons (16-->24 bits, integer mode to float, increasing sampling rate), but passing from 192KHz to 384KHz is, in my opinion, completely useless.
Moreover, a value that high can increase the risk of causing some jitter (which normally can't happen even at 384Khz, but theoretically the risk increase).
And finally, you'll consume more power for nothing.
_xenoxis_ said:
"hifi_playback" is just an unused output which isn't routed to anything, so don't mind about it.
About your sampling rate change to 384kHz, this will not gonna set it to 384Khz cause you don't change the file "audio_io_policy.conf" where is the i/o configuration (currently, your configuration can cause some volume saturation as it done the first time I tried my mod on my device).
You need to set 384KHz as well in this file.
Moreover, is it useless to set the USB output over to 192Khz, I don't know a device in USB which can handle 384KHz audio on a USB connection.
However, I don't think there's a reel benefit to set the DAC to 384KHz, I mean the maximum sampling rate in PCM hi-res file is 192Khz (still rare actually) and I never seen anything beyond this value. Typically a hi-res file is in [email protected]
So what i'm trying to say, is that a change from [email protected] to [email protected] is beneficial, for many reasons (16-->24 bits, integer mode to float, increasing sampling rate), but passing from 192KHz to 384KHz is, in my opinion, completely useless.
Moreover, a value that high can increase the risk of causing some jitter (which normally can't happen even at 384Khz, but theoretically the risk increase).
And finally, you'll consume more power for nothing.
Click to expand...
Click to collapse
My system is MIUI11. A file called "audio_output_policy.conf" in same place which has the same content as a part of your audio_io_policy.conf. I've edited it and other file called "audio_policy.xml" in case.
Jitter looks getting higher in log but I don't know if I can hear it apparently.
Even I removed all energy-cost-optimizing-strategy on my music app to enhance stability of performance with 384kHZ. The battery cost is still acceptable.
Indeed, it makes me feel little bit weird when adopting 384kHz. All I do this is considering SRC from 44.1kHZ. Higher sampling may cause more reasonable curve in analog signal. However, it depends on algorithm and may cause other problems like harmonic wave and jitter. So it's an experiment and a trade-off. I will go back to 192kHZ if got nothing on 44.1kHZ files after comparing.
_xenoxis_ said:
"hifi_playback" is just an unused output which isn't routed to anything, so don't mind about it.
About your sampling rate change to 384kHz, this will not gonna set it to 384Khz cause you don't change the file "audio_io_policy.conf" where is the i/o configuration (currently, your configuration can cause some volume saturation as it done the first time I tried my mod on my device).
You need to set 384KHz as well in this file.
Moreover, is it useless to set the USB output over to 192Khz, I don't know a device in USB which can handle 384KHz audio on a USB connection.
Click to expand...
Click to collapse
I'm making a USB Sample Rate Changer script like bluetooth LDAC and usb-samplerate-unlocker (up to 386kHz and even 768kHz). If you like, see my github USB Sample Rate Changer and usb-samplerate-unlocker.
Update 08/07/2021 :
Hello guys, i have made a magisk module with this mod, it's currently on submission stage and it will be, normally, fully available in the magisk module repository (the "market").
With this magisk module, the mod will be systemless and will no require tricks to hard-modifying files on the device !
I'll keep you informed about this !
Great work.
I need to do the same in my K20 pro (Raphaelin), for the apple music lossless to use the inbuilt hifi dac