Related
[MOD SOUND] ViPER4Android FX & XHiFi ANDROID 2.3/4.0/4.1/4.2 (GB & ICS & JB)
ViPER4Android
FX 2.2.0.7 & XHiFi 2.1.0.0
2.3/4.0/4.1/4.2 (GB & ICS & JB)
Short description:
Equalizer with a variety of effects.
Description:
V4A FX version: Adds a variety of sound effects (visualization of sound).
V4A XHiFi version: Restores sound quality.
V4A FX and XHiFi together: More sound settings, the cat. make the sound quality is much nicer.
Specifications
Codename: (FX version) Beautiful / (XHiFi version) X-Factor
Supported OS: Android 2.3 / 4.0 / 4.1 / 4.2
Supported hardware: ARM (ARM15, Cortex A8/A9 or higher).
FX min. requirements (Convolver off): A8 300MHz or ARM11 500MHz.
FX min. requirements (Convolver included): A8 single-core 800MHz, recommended dual-core or quad-core 1.2GHz.
XHiFi min. requirements (all effects included): A8 dual-core 1GHz or higher, Tegra2 processor supported.
Supported languages: English (United States) / Simplified Chinese / Traditional Chinese.
Screenshots
{
"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"
}
Download FX-version:View attachment ViPER4Android_FX_2207_en.zip
Download XHiFi-version:View attachment ViPER4Android_XHiFi_2100_en.zip
IRSamples for Convolver:View attachment IRSamples.rar
Recommended settings from the author
ViPER4Android_FX
<Headset>
1. Master Power: ✔
2. Playback Gain Control
(1) Enable checkbox: ✘
(2) Select Effect Strength: Slight
(3) Max Gain: 4x
(4) Max Output: -1.9dB
3. FIR Equalizer
(1) Enable checkbox: ✘
(2) Select Preset: Acoustic
(3) Linear Equalizer graphic: default
4. Convolver
(1) Enable checkbox: ✔
(2) Impulse Response: PopEQ // DBX 160SL Blue - Medium Ratio // JoeMeek SC2 Impulse
5. Field Surround
(1) Enable checkbox: ✘
(2) Select Field Surround Strength: Extreme
(3) Select Mid Image Strength: Extreme
6. Reverberation
(1) Enable checkbox: ✘
(2) Room Size: 25m2
(3) Sound Field: 5m
(4) Damping Factor: 0 Percent
(5) Wet Signal: 0 Percent
(6) Dry Signal: 50 Percent
7. Dynamic System
(1) Enable checkbox: ✘
(2) Select Listening Device: Common Earphone(v2)
(3) Select Dynamic Bass: 0 Percent
(4) Tube Simulator(6N1J): ✘
8. Master Gate(Limiter)
(1) Ouput Gain: 0dB
(2) Limit Threshold: 0dB
<Phone Speaker>
1. Master Power: ✔
2. FIR Equalizer
(1) Enable checkbox: ✘
(2) Select Preset: Acoustic
(3) Linear Equalizer graphic: default
3. Convolver
(1) Enable checkbox: ✔
(2) Impulse Response: Studer +1dB Updated
4. Reverberation
(1) Enable checkbox: ✘
(2) Room Size: 25m2
(3) Sound Field: 5m
(4) Damping Factor: 0 Percent
(5) Wet Signal: 0 Percent
(6) Dry Signal: 50 Percent
5. Extra Loud
(1) Enable checkbox: ✘
(2) Select Effect Strength: Slight
(3) Max Gain: 4x
(4) Max Output: 0dB
6. Master Gate(Limiter)
(1) Ouput Gain: 0dB
(2) Limit Threshold: 0dB
ViPER4Android_XHiFi
1. Master Power: ✔
2. Playback Gain Control
(1) Enable checkbox: ✔
(2) Select Effect Strength: Slight
(3) Max Gain: 4x
(4) Max Output: -1.9dB
3. FIR Equalizer
(1) Enable checkbox: ✔
(2) Select Preset: Acoustic
(3) Linear Equalizer graphic: default
4. Audio Reconstruction
(1) Enable checkbox: ✔
(2) Hi Clarity: 50
(3) Lo Contour: 70
5. Master Gate(Limiter)
(1) Limit Threshold: 0dB
installation
1) Download and unzip the IRSamples.rar the root of the SD-card (SD-card\Viper4Android\Kernel\*.irc)
2) Set the selected ank (FX or XHiFi) of acc. file - can be both, because they get along well together
3) apk run and follow the instructions appearing on the screen
And for other system Poweramp music players (e.g., MIUI music player, Apollo, etc.
From version: FX v2204, XHiFi v2007:
To make it work with V4A Poweramp correctly, you have to both applications (FX and XHiFi), switch to Compatible Mode and then reboot the phone.
CODEC CHOOSE WHAT?
NEW! Starting with version FX 2207:
ZTE U880 or same CPU (PXA920), choose - "PXA920 without VFP" (Convolver disabled)
Tegra2 or any CPU with freq equal / less than 800MHz, choose - "ARM with VPF"
Qualcomm of freq higher than 800MHz - single core, choose - "A8 with NEON"
ALL other Dual-core, Quad-core, Octa-core, choose - "A9/15 with NEON"
NEW! Starting with version: XHIFI 2100
Tegra2, choose - "NVIDIA Tegra2"
ALL others, choose - "CortexAx with NEON"
Homepage: Original theme author on XDA <-> Original theme author's Chinese website
IRS samples for convoluters (convolver)
IRS samples for convoluters (convolver) thanks tranceman111
So what is the convolver (Convolver), and what it eats? try to understand
Start by asking the concept - "Reverb"
"Reverb - a reflection of sound from the different items that surround it (walls, floor, ceiling, windows, bookshelves, trees, houses and even people.) Any sound that we hear in life, is not a pure signal, and contains themselves more and their reflections on the various surfaces. "
Convolution reverb or just convolver
It is also called convolution reverb and pulse. It uses impulse responses of the various processing facilities or equipment (other reverbs), repeats the distribution of fluctuations in the original.
More information can be read: here and here
IRS (Impulse Response) - is an impulse response in the form of short Wave files that are loaded into convoluter, through which he recreates a mathematical model of a room, reverb, devices, etc. from which recorded (shot) pulse! (ie the impulse response contains a linear response of your system (ie frequency response), and does not include the non-linear characteristics (ie distortion / color).
PULSES
Technics Vintage IRS
[Pulses with vintage equipment Technics (1978 issue) preamp and power amp.
Technics+Vintage+v4
Presets+Technics+Equ
Version for those who do not pull the processor (wheezing, stuttering, delay, etc.)
Technics+SU-9011(Preamlifier)+&+SU-9021(PowerAmplifier)+LITE+IRS
Presets+Technics+Equ+Lite
SuperLight Technics Vintage v4
SuperLight Preset Technics Equ
later
WORK Beats Audio, SRS, Dolby mobile, xLOUD + ViPER4Android FX & XHiFi
To work sound effects Beats should be laid out in this thread I've found (system / etc / audio_effect.tsonf) before installation and after installation. I made the necessary Changes to your firmware.
audio_effect.conf to put the replacement in
/ system / etc / audio_effect.conf
Restart the phone.
Full work
[ROM][Sense 4.1][20.01] Team Venom presents: ViperS 1.6.3 - welcome to the future.
View attachment audio_effects.rar
FAQ Reserv
Q: What makes this program?
A: This program is a conventional equalizer with a wide list of options, working with almost all the players.
Q: How do I install?
A: Set yourself ank, run and follow the instructions poyavivscheysya. If the default setting does not help, use FLASHABLE-version.
Q: Why the program needs ROOT?
A: Then, what driver (library) that are required to operate the program prescribed (set) in the section: system / lib /
Q: What kind of CPU to choose for my device?
A: Table of compliance processors, see the cap under the spoiler.
Q: Where to copy files (samples) for Convolver'a?
About: SDCard/ViPER4Android/Kernel / - Case of letters dlozhen be strictly adhered to!
Q: I downloaded a new impetus to the device for the convolver, and the device does not see them, why?
A: Advice to all who do not work convoluter, make sure that the files pulses *. Irs you have piled up in a heap in the folder ViPER4Android/Kernel rather than sorting into folders.
Q: What is the format (extension) to be in the sample?
A: Since version 2.2.0.3 (2.0.0.6) and further, the file extension "Nonlinear processing" (aka Convolver) with. Wav replaced by. Irs
Q: How to make the new drivers? After all, there is laid only apk.
A: Install the program and open it, it will offer to update the driver.
Q: How do I use different pulses are then laid out? I put a version XHiFi, but there is no any choice of these same effects ...
A: The pulses are designed to convoluter (convolver), cat. there is only a version of the FX! At the root of the memory card create a folder: / ViPER4Android/Kernel / and there throws impulses. Now, where in the program choose the right impetus.
Q: I have a program does not work with PowerAmp'om. What to do?
A: To get to work with V4A Poweramp correctly, you have to both applications (FX and XHiFi), switch to Compatible Mode and then reboot the phone.
In: Switch from Normal to Compatible and still with PowerAmp does not want to. Maybe something else to turn on or off in PowerAmp? Prompt?
A: PowerAmp need to go to Settings-> Sound-> Advanced Settings-> put a checkbox on musicfx. Then tab tone / volume set compulsory treatment by activating point musicfx (in this case in the system settings must be activated V4A), long press on musicfx otkryvaetsya equalizer that are currently using the system.
Q: When installed a program, and tried to find the driver Toli Toli update I wrote this: "please comfirm your phone has been rooted and busybox installed". What do I do?
A: First, the program will necessarily need ROOT-law, and secondly, we must also install Busy Box. It select the smart installer and reboot.
Q: What's the difference between versions XHiFi?
About: V4A XHiFi version is mainly to restore the sound quality and detail. This is the main feature of XHiFi, making detailed and high frequencies to restore losses to MP3 audio files.
In install the latest version of V4A through AIC. Install both the equalizer. On the second why you do not have the settings for the speaker. This is as it should be or cant install?
About: XHiFi intended only for the headset (headphones) / BT, but if you want to use XHiFi for the speaker, then simply activate the lock effect mode in XHiFi application.
Q: Can I use them both at the same time or just individually?
A: You can either - they get along well together and complement each other perfectly.
Q: I installed both versions, but activate only one of them, and in the process both hang. Why is that?
A: It does not matter which version you have activated - FX or XHiFi, they will still always be run together (provided that they are installed both).
Q: If fx is the driver, should be put hifi, whether or not the driver put it?
A: Yes, on the first run, the program will prompt you to update draver.
Q: There are significant differences from the DSP Manager is available?
About: V4Android partly based on the source code of the DSP Manager, that is, in fact, it is more advanced (improved) version of it.
Q: And now all in one file? Previously, there was also a manager. Explain.
A: Since version 2.2.0.4 (2.0.0.7) and further, manual installation is now - will not be as program itself will update the driver at startup.
Q: Unpacked impulses for convoluters, but the application of sound stutters. Tell me what's the problem?
A: The processor is unable to cope. Disconnect convoluter.
Q: How to use this non-linear processing? Which of this heap of files in the format. Irs stand for improvement?
A: Anyone, what you enjoy. They are all in their own way alter the sound, so only you can choose what you like.
Q: Can me more about the actual samples? Everything can be put right? And at some specified phone model, what is it?
A: Yes, you can throw all the samples in a single folder. If on a sample contains the model number, so this phone has some kind of his trademark uluchshayzer (such BeatsAudio from HTC), while the use of which was filmed sample (using the spec. Equipment).
Q: What is the mode of Safe Mode (Safe Mode), and what is it for?
A: If you V4A not work with any player, then try switching to Safe Mode, cat. and is designed to work with almost any music player with a cat. V4A does not work in Normal Mode (works only with the Android 4.X and above).
Q: What is the mode Compatible Mode (compatibility mode) and what is it for?
About: Compatible Mode supports a larger number of both system and third-party music players and players with their own sound effects or EQ (works only with the Android 4.X and above).
In: Switch to Compatible Mode, and I wrote that the Driver status: NO
About: Driver status in V4A FX Compatible Mode will always show - NO. YES will show only in Normal Mode - this is a bug of the program.
In: Switch to Compatible Mode, reboot, but nothing changed ... (Option 1)
A: If you want to use Compatible Mode, then you need to switch to this mode, both applications (ie, both XHiFi and FX).
In: Switch to Compatible Mode, reboot, but nothing changed ... (Option 2)
A: For those who still remained a problem with effects in Compatible Mode, even after a reboot, do the following: Locate the file - / system / build.prop and change the line with: Ipa.decode = true on lpa.decode = false
Q: Why ViPER4Android FX always leads to FC when headphones?
A: Most likely you have not write to the partition / system / on the device, so the drivers were not installed. Allow entry to the system partition and reconfigure the automatic installation of drivers or install them manually.
Q: Why ViPER4Android FX creates unexpected sound effects, cat. not observed (or different) from other users?
A: First, try to clean the data ViPER4Android FX, and if that is unsuccessful, then make sure you do not stand the sound of the amplifier.
Q: Why ViPER4Android FX will not boot after boot device?
A: Check your antivirus, or else V4A was off the list of startup.
Q: Why do missing V4A effect after using task-killer'a?
A: Just add ViPER4Android FX to the list of excluded task-killer'a.
Q: Why V4A effect suddenly disappears?
A: Because the Android system kills some processes due to memory limitations. Just set ViPER4Android.apk as system application (move it to / system / data / and reboot the device.)
Q: Why there is background noise when using v4a effects?
A: This error Android, cat. they will all sound modes (BeatsAudio, etc). Try to rename the file: / system / lib / SoundFX / libbundlewrapper.so in libbundlewrapper.so.bak, and reboot the device.
Q: I'm trying to install the program, wrote that the driver is not installed. Check for root and biziboks. Both are found in the catch, I do not understand ...
A: Perhaps you should not permit entry in the system, so the driver and did not put. Try to install the drivers manually for this instruction.
Q: Tell me, in the status of the driver, the value of treatment - no, it's that it does not work or does not work?
A: Status: Processing - NO (if the music is not playing); Processing - YES (if the music is playing).
Q: What is the Cure +?
A: When listening to music, with a normal audio system for more than three hours, you'll start to feel fatigue, dizziness, tinnitus, irritation and other ailments. This is a normal reaction of the body, as heavy bass and loud sound can cause permanent damage to the human auditory system. But from these symptoms can easily get rid of - just enough, just relax a bit. Viper is also the professional tool for listening to music, so we decided not to ignore the problem. We put a lot of effort to develop a more "innocent" technology listening to music, and have achieved little success. But think about how to give users the opportunity to experience it. It is this "little success" and is a technology - Cure +. But we are still working on how to better present this technology to the user.
Which music player that you recommended except Power AMP?
baronzelan said:
To work sound effects Beats should be laid out in this thread I've found (system / etc / audio_effect.tsonf) before installation and after installation. I made the necessary Changes to your firmware.
audio_effect.conf to put the replacement in
/ system / etc / audio_effect.conf
Restart the phone.
Full work
[ROM][Sense 4.1][20.01] Team Venom presents: ViperS 1.6.3 - welcome to the future.
View attachment 1978979
Click to expand...
Click to collapse
thanks should i change permission after replacement in
/ system / etc / audio_effect.conf
Rvl7 said:
Which music player that you recommended except Power AMP?
Click to expand...
Click to collapse
I use HTC music player. You can use any player, only need to turn on in the settings ViPER4Android:
And for other system Poweramp music players (e.g., MIUI music player, Apollo, etc.
To make it work with V4A Poweramp correctly, you have to both applications (FX and XHiFi), switch to Compatible Mode and then reboot the phone.
mamdouhn said:
thanks should i change permission after replacement in
/ system / etc / audio_effect.conf
Click to expand...
Click to collapse
Yes
- Go to: / system / lib / soundfx / a RootExplorer
- Make this folder writable
Come-in: / system / etc / a RootExplorer
- Make this folder writable
- Manually put the file there - audio_effects.conf (from the archive below)
- Reboot the device.
baronzelan said:
Yes
- Go to: / system / lib / soundfx / a RootExplorer
- Make this folder writable
Come-in: / system / etc / a RootExplorer
- Make this folder writable
- Manually put the file there - audio_effects.conf (from the archive below)
- Reboot the device.
Click to expand...
Click to collapse
thanks
so / system / lib / soundfx will be rwxr-xr-x
and audio_effects.conf will be rw-r--r--
is it right ?
thx
Very nice thank you
This Mod works perfectly with ViperS 1.6.3 within Htc Music Player (better than any other mod). And please refer to @zhuhang original thread for latest updates.
is there any iinterference with Beats, or it works along with Beats?
DarkLP said:
is there any iinterference with Beats, or it works along with Beats?
Click to expand...
Click to collapse
Works with Beats
Pretty nice....thanks.
"I wanna be the apex of predators in my backyard"
Joe Rogan
Thanks, one question do we need to create folder on sd card ? to copy IRsample.rar there? I cant see any folder created by application after running it. can some one provide exact path with exact name of folders if we need to create manually.
Also how to use these IRsample?
Sent from my Micromax A116 using Tapatalk 2
Works perfect with vipers 3.0.2 along with beats audio. It's amazing, thanks
can i use this on xperia device?
khamim said:
can i use this on xperia device?
Click to expand...
Click to collapse
Yes but goto original thread for more info and latest version. Link in OP and in my Sig.
Sent from my HTC Sensation
How can I make this work on viper jb rom?
Sent from my HTC Sensation Z710e using xda app-developers app
Does it works on ViperS 5.1.0 sense 5 ???
Here is the audio effects that i ever feel the greatest.
It is
ViPER4Android [V4A]
Here is official page http://forum.xda-developers.com/showthread.php?t=2191223
{
"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"
}
Version: FX version 2.2.1. 1/ XHiFi Merged
Operating environment: Android 2.3 / 4.0 / 4.1 / 4.2 / 4.3
★ Android 4.3 Support ★
ViPER4Android supports Android 2.3 Ginger bread, 4.0 Ice Cream Sandwich and 4.1 upto 4.3 Jelly bean firmwares.
★ NEW Channel Pan ★
Controls left/right channel output. Its not very useful unless your headphone is imbalance or faulty one side. It will be a cure for you.
★ NEW Differential Surround / Haas Effect ★
This is an old feature which ViPER520 had removed from FX in early days.
But after many users requesting it, ViPER520 bring it back to FX
More info on Haas Effect: http://www.mixcoach.com/creating-dep...haas-effect-2/
★ NEW ViPER Fidelity Control ★
★ ViPER Bass ★
With 2 bass mode, you can have greater bass experience than before! This requires a little bit better headphone.
★ ViPER Clarity ★
With the latest Clarity mode selection, you can balance up heavy bass with high clarity audio that you can never imagine before!
★ NEW Headphone Surround Engine+ ★
★ NEW Cure Tech+ ★:
With normal audio system, listening for more than three hours will feel fatigue, dizzy, tinnitus, irritated and other symptoms. This is a normal reaction, heavy bass and high volume could cause permanent damage to the human auditory system, but other phenomena can restore through resting.
Viper as a listening experience professional will not ignore this problem. Therefore put a lot of effort to study how to make a "Healing" sound technology, just a small success. But thinking on how to let users experience it.
★ NEW In-App Installation ★:
With this in-app installation, users just have to follow the instructions when first run V4A app and the app will install everything for you.
In order to use this feature successfully, full Busybox must be installed.
★ NEW Compatible Mode (Only in 4.x) ★:
Compatible Mode supports large variety of music players and the players' own EQ/sound effects (system-provided/third party)
Therefore, you don't have to select V4A in Sound Settings > Music Effects, choose anything other than V4A. Just run V4A app and the effects will be working with anything else.
1. In option, switch to Compatible Mode. Reboot, done.
2. In Sound Settings > Music Effects, choose other than V4A.
3. Run V4A app and configure the settings then the effects will work together with the one you chose in Sound Settings.
★ NEW Safe Mode (Only in 4.x) ★:
If V4A dont work on many players, try switching to Safe Mode to work with almost any music player.
1. In option, switch to Safe Mode. Reboot, done.
Bugs/Issues:
1. Driver status in FX Compatible Mode always NO. Driver status will show YES in normal mode.
Latest Version Changelogs
FX version: v2.2.1.1
1.Add differential surround (Haas effect).
2.Add channel pan setting.
3.More settings for field surround.
4.Support android 4.3.
FX version: v2.2.1.0
1.Added XHiFi Clarity mode.
2.V4A XHiFi stopped development.
For your information:
XHIFI Hi Clarity = FX Viper Clarity > XHiFi Clarity Mode.
XHIFI Lo Contour = FX Viper Bass > Natural Bass Mode.
FX version: v2.2.0.9
1.Add fidelity control system.
2.Optimize Headphone Surround Engine+ for VFP platform.
3.Fix some bugs.
4.Add update check.
FX version: v2.2.0.8
1.Add Headphone Surround Engine+.
2.Fix some bugs.
XHiFi version: v2.1.0.2
1.Support speaker effects.
2.Fix some bugs.
Click to expand...
Click to collapse
DOWNLOADS
FX version v2.2.1.1 : http://www.mediafire.com/download/7t1c73wsz4qiygu/ViPER4Android_FX_2211_en.zip
XHiFi version v2.1.0.2 : http://d-h.st/4WM
Sony Xperia New S.Enhance IR Samples Rev2: http://forum.xda-developers.com/showthread.php?p=41320703
Creative ZEN X-Fi IR Samples: http://forum.xda-developers.com/show....php?t=2308239
IRSamples for Convolver(Updated 15Apr) : http://www.mediafire.com/download/9am1sogfq9lm31d/en_IRSamples_331+IR.zip
For more IR samples, visit V4A IR Sample Index Thread with Official Mirror, all new IR samples were uploaded here : IRSamples
HighDefinition Impulse Responses Samples (IRS) - (stereo, 24bit, bitrate: 2823 kb/s, 44100 Hz, 2 channels)
BBE 1-5
Unofficial V4A Tool by a vipersaudio member - Fix FX not working for many players below 4.3:
http://d-h.st/c4Z
Click to expand...
Click to collapse
INSTALLATION
Require Rooted,BusyBox
Which to install? FX or XHiFi or Both?
A: FX has many audio effects, where as XHiFi restores audio quality. If you like many effects(reverb, bass, surround) then choose FX, if you like clear audio/vocal and you have a good headset, choose XHiFi. You can also install both, more CPU usage, that's all.
[FX/XHiFi version]
1. Extract zip
2.Choose correct android version & Install ViPER4Android.apk
2. Run app, when prompt, choose Yes to "install/update".
3. Choose correct CPU Type. (Instructions include in your downloaded zip)
4. Reboot device.
Option1. Choose V4A(either fx or xhifi) in sound settings > music effects (Don't worry, both fx and xhifi wil run together)
Option2. Dont touch sound settings, open up both(fx and xhifi), in option, switch to FX Compatible Mode, reboot.
Update To Latest Version
1. Download latest FX and XHIFI apks
2. Copy to system/app to overwrite // OR // Install like normal and replace previous version.
3. Open up FX and XHIFI, Choose "Install/Update"
4. Reboot, done.
UNINSTALLATION
1. In both FX and XHiFi app, go option and choose uninstall driver.
2. After that, uninstall the apk itself.
3. Reboot.
Click to expand...
Click to collapse
For IR Samples (Impulse Response)
1.Download it and extract to sdcard/Vi4PERAndroid/kernel (if folder does not there,jump to step 2 and then step 1)
2.Open Vi4PERAndroid,check box "impulse response"
3.Select desire samples
Changed Driver List (Corrected 20/May)
For Galaxy S Advance,Choose Cortex A9/15 with NEON
NEW FX 2208+
ZTE U880 or same CPU(PXA920), choose "Without VFP (PXA920)" (Convolver and Surround+ disabled)
Tegra2, ARM or any CPU with freq equal/less than 800MHz, choose "With VFP"
All Qualcomm/Snapdragon of freq higher than 800MHz, regardless of cores, choose "CortexA8 with NEON"
All other Dual-core,Quad-core,Octa-core, choose "CortexA9/15 with NEON"
NEW XHIFI 2101+
ZTE U880 or same CPU(PXA920), choose "Without VFP (PXA920)"
Tegra2, ARM, choose "With VFP"
ALL others, choose "CortexAx with NEON"
Click to expand...
Click to collapse
★★★For those having problems with effects in compatible mode even after rebooting. Try this:
1.Open up /system/build.prop (If you can't find this line, you have to solve in other way)
2.Change the line Ipa.decode=true to lpa.decode=false
Trouble Shooting
When V4A is not working for you. (Really No effect for all options, NOT BY CHECKING driver status)
0. MAKE SURE YOU HAVE CHOSE THE CORRECT DRIVER. Refer OP.
1. MAKE SURE YOU HAVE BUSYBOX INSTALLED
2. Uninstall, reboot. Reinstall, Choose correct driver, reboot.
3. Don't use compatible mode yet, go to sound settings>music effects> and choose v4a(either fx or xhifi). Test.
4. If not working, switch to compatible mode, reboot, go to sound settings>music effects> and select previous effect. Test.
5. If not working, activate safe mode, reboot. Test.
Click to expand...
Click to collapse
CREDIT
ViPER520(creator) and zhuhang
FX & XHiFi Settings Explained & Recommended Value
FX Settings
V4A FX version mainly for rendering audio effects, by controlling various parameters to achieve the purpose of audio effect adjustment.
<Headset>
1. Master Power. This option defines whether to enable V4A headset sound effects, also known as main switch.
2. Playback Gain Control :
It is mainly used to dynamically control the audio volume, to amplify or to attenuate.
(1) Enable checkbox : Whether the effect is enabled.
(2) Select Effect Strength : Effect Strength is the speed of amplification or attenuation, the stronger the faster the speed and the higher the final volume, the weaker the slower the speed, the closer to the original volume. Recommended medium.
(3) Max Gain : When the volume of the note is too small, in order to uplevel the sound, there may be very large magnification. The higher the value, the louder the volume. But too large will also amplify the noise within the song. Recommended 4 times.
(4) Max Output : This value defines the maximum volume of the PlaybackAGC sound in decibel value, the greater the value the greater the volume, 0 db is the maximum. In order to make the sound softer recommended -1.9 dB.
3. FIR Equalizer
511-order 10 bands FIR linear equalizer.
(1) Enable checkbox : Whether the effect is enabled.
(2) Select Preset : Here you can select default equalizer presets. When choosing custom, it will follow the user-defined lines drawn.
(3) Linear Equalizer graphic : Will pop up when you touch the graphic equalizer, you can manually adjust the levels of amplification and attenuation of the 10 bands.
4. Convolver
When an impulse response(IR) sample is loaded, music will show the same characteristics of the loaded sample, for example equalizer, surround, reverberation, tube etc.
Make sure SD Card has /ViPER4Android/Kernel/ folder, IR samples will be located there. If folder not exists, you can download latest V4A FX and extract SDCard_V4A.zip.
(1) Enable checkbox : Whether the effect is enabled.
(2) Impulse Response : Here you can select and load IR Samples inside /ViPER4Android/Kernel/ folder.
5. Field Surround
It is mainly used to create sound field surround effects. The sound field can be understood as mono field or stereo field.
(1) Enable checkbox : Whether the effect is enabled.
(2) Select Field Surround Strength : This value defines the strength of the field surround effects. The stronger, the stereo effect will be more obvious, the sound will come from left and right sides. Recommended medium.
(3) Select Mid Image Strength :This value defines the central vocal intensity. More strongman sound more clear, the weaker the more ethereal sound.
6. Reverberation
It uses mathematical methods to simulate the environmental feeling sensation. Example a song can be felt playing inside the auditorium, living room, bathroom, and so on.
(1) Enable checkbox : Whether the effect is enabled.
(2) Room Size : This value defines the virtual environment area size. The larger the value, the sound is wider and more echoes.
(3) Sound Field : This value defines the width of the room above, in meters. Assumed that the above room size is 100 square meters, here to set a width of 14 meters, then the length of the room will be 7.14 m.
Therefore, the room size and width defines the aspect ratio of the virtual environment.
The larger the value, the sound coming from both sides will felt more obvious.
(4) Damping Factor : This value defines the humidity of air in the above virtual environment, the moisture vapor in the air will easily absorb the echoes.
So the bigger this value, the less echoes heard.
(5) Wet Signal : This value defines the volume of the simulated environment effect.
(6) Dry Signal : This value defines the volume of the original sound.
For environments with low air humidity such as living room, auditorium and other indoor environment, you can use room size and sound field to define the area of the virtual environment, water vapor content values from 0 to 20, the reverb signal values 20 to 50, the proportion of the original signal to take value of about 50.
For environments with high air humidity such as bathroom and other indoor environment that contains a lot of moisture, you can use room size and sound field to define the area of the virtual environment, water vapor content values of 50 to 100, the reverb signal values 40 to 80, the proportion of the original signal value of about 50.
7. Dynamic System
It handles the dynamic range of the sound. In other words the bass, treble, and limiting.
(1) Enable checkbox : Whether the effect is enabled.
(2) Select Listening Device : This value defines the headset type connected to the audio jack. If you cannot get the right device for good bass tone, then select Common earphone. Common earphone is a common choice. Recommend Common earphone.
(3) Select Dynamic Bass : This value defines the average dynamic bass, the greater the stronger bass. Recommend 33%.
(4) Tube Simulator(6N1J) :This option defines whether to enable tube simulator effect. V4A tube simulator uses a simplified mathematical simulation of tube effect.
If turned on, will greatly reduce high-frequency odd harmonic distortions, while increases even-order harmonic distortions of tube simulator.
8. Master Gate(Limiter)
This option is V4A output limiter, its used to prevent overloud clipping distortion.
(1) Ouput Gain : This value defines the main output volume. Its something like a volume control.
(2) Limit Threshold : This value defines the limits of waveform amplitude by the limitor, 0 dB is the maximum value.
The smaller the value, the easier to experience audio frequency compression(the smaller the volume), will lose sound details, but can effectively control the final output volume. Recommend 0 db.
<Phone Speaker>
1. Master Power : This option defines whether to enable V4A speaker sound effects, also known as main switch
2. FIR Equalizer : Same as headset equalizer.
3. Convolver : Same as headset convolver.
4. Reverberation : Same as headset reverberation
5. Extra Loud
eXtra-Loud further amplifies the sound, but is controlled to protect the speaker, will not overload.
(1) Enable checkbox : Whether the effect is enabled.
(2) Select Effect Strength : Effect Strength is the speed of amplification or attenuation, the stronger the faster the speed and the higher the final volume, the weaker the slower the speed, the closer to the original volume. Recommended medium.
(3) Max Gain : When the volume of the note is too small, in order to uplevel the sound, there may be very large magnification. The higher the value, the louder the volume. Recommend infinity.
(4) Max Output : This value defines the maximum volume of the EL sound in decibel value, the greater the value the greater the volume, 0 db is the maximum. Recommend 0db.
6. Master Gate(Limiter)
Same as headset limiter.
XHiFi Settings
V4A XHiFi version mainly for restoring audio quality and details.
1. Master Power
This option defines whether to enable V4A headset/bluetooth sound effects, also known as main switch.
2. Playback Gain Control : Same as FX version's PlaybackAGC.
3. FIR Equalizer : 2047-order 10 bands, quality much better than FX version. Method of adjusting same as FX version.
4. Audio Reconstruction
It is XHiFi's core feature, it does the detailing and treble restoring for lossy mp3 audio files. (Currently in adjustment phase, different device may have different experience.)
(1) Enable checkbox : Whether the effect is enabled.
(2) Hi Clarity : This value defines the detailing and treble restoration percentage, the larger the value, the more details of the sound and stronger treble.
For low-end/common earphones, this is not recommended as you may experience high frequency shrills.
For better earphones such as Monster,Philips,Zombie,Sennheiser, recommended value = 30 ~ 50.
For high-end headphones, value depands on headphone cable length. Start with value = 40, value +10 for every 80cm cable length.
For preamp/amp connect to phone. Start with value = 60, value +10 for every 80cm cable length.
For tube amplifier, directly use value = 100.
(3) Lo Contour : The value defines the percentage of bass contour reconstruction over total band. The larger the value, the stronger the bass, but midrange and details will slightly lost.
For earphones recommend value = 50 ~ 70.
For headphones recommend value = 20 ~ 30.
5. Master Gate(Limiter)
This option is V4A output limiter, its used to prevent overloud clipping distortion.
(1) Ouput Gain : This value defines the main output volume. Its something like a volume control.
(2) Limit Threshold : This value defines the limits of waveform amplitude by the limitor, 0 dB is the maximum value.
The smaller the value, the easier to experience audio frequency compression(the smaller the volume), will lose sound details, but can effectively control the final output volume. Recommend 0 db.
Recommended FX Settings (will differ with official post)
<Headset>
1. Master Power: ✔
2. Playback Gain Control
(1) Enable checkbox: ✔
(2) Select Effect Strength: Slight//Moderate
(3) Max Gain: 4x//8x
(4) Max Output: -1.9dB
3. FIR Equalizer
(1) Enable checkbox: ✔
(2) Select Preset: Acoustic
4. Convolver
(1) Enable checkbox: ✔
(2) Impulse Response: PopEQ // DBX 160SL Blue - Medium Ratio // JoeMeek SC2 Impulse
5. Field Surround
(1) Enable checkbox: ✘
(2) Select Field Surround Strength: Extreme
(3) Select Mid Image Strength: Extreme
6.Headphone Surround +
(1) VHS+ : ✘
(2) Select Effect Quality: Normal
7. Reverberation
(1) Enable checkbox: ✘
(2) Room Size: 25m2
(3) Sound Field: 5m
(4) Damping Factor: 0 Percent
(5) Wet Signal: 0 Percent
(6) Dry Signal: 50 Percent
8. Dynamic System
(1) Enable checkbox: ✔
(2) Select Listening Device: Common Earphone(v2)
(3) Select Dynamic Bass: 30 Percent
(4) Tube Simulator(6N1J): ✘
9.Auditory System Protection
(1) Cure Tech+ : ✔
(2) Select Binaural Level : Slight
10. Master Gate(Limiter)
(1) Ouput Gain: 0dB
(2) Limit Threshold: 0dB
<Phone Speaker>
1. Master Power: ✔
2. FIR Equalizer
(1) Enable checkbox: ✔
(2) Select Preset: Acoustic
3. Convolver
(1) Enable checkbox: ✔
(2) Impulse Response: Studer +1dB Updated
4. Reverberation
(1) Enable checkbox: ✘
(2) Room Size: 25m2
(3) Sound Field: 5m
(4) Damping Factor: 0 Percent
(5) Wet Signal: 0 Percent
(6) Dry Signal: 50 Percent
5. Extra Loud
(1) Enable checkbox: ✔
(2) Select Effect Strength: Slight
(3) Max Gain: 4x
(4) Max Output: 0dB
6. Master Gate(Limiter)
(1) Output Gain: 0dB
(2) Limit Threshold: 0dB
Recommended XHIFI Settings
1. Master Power: ✔
2. Playback Gain Control
(1) Enable checkbox: ✔
(2) Select Effect Strength: Slight
(3) Max Gain: 4x
(4) Max Output: -1.9dB
3. FIR Equalizer
(1) Enable checkbox: ✘
(2) Select Preset: Acoustic
4. Audio Reconstruction
(1) Enable checkbox: ✔
(2) Hi Clarity: 80
(3) Lo Contour: 70
5. Master Gate(Limiter)
(1) Output Gain: 0dB
(2) Limit Threshold: 0dB
Click to expand...
Click to collapse
Development Progress (Updated 5-Jun-2013)
FX version: v2.2.0.9 (Estimated date: )
1. Optimise Surround Engine+ for VFP CPUs.
XHiFi version: v2.1.0.3 (Estimated date: )
-
TODO List:
1. ViPER4Android driver auto install/update [Done]
2. Increase compatibility for Android 4.x [Done]
3. EQ user-defined slot [Deprecated, use Sound Effect Profile]
4. Sound Effect Profile [Done]
5. XHiFi support Tegra2 [Done]
6. Convolver support ARMv5TE CPU [Done]
7. Improve Convolver process [Done]
8. Convolver support IR Sample of any length [Done]
9. FX Field Surround Upgraded [Done]
10. FX Virtual Headphone Technology added [Done]
11. Fix the sound delay caused by convolver. [Done]
12. Import IR samples from external storage. [WIP]
13. Optimize audio reconstruction module. [Done]
14. Upgrade the bass effect of audio reconstruction module. [Done]
15. Use RootTools to install driver. [Done]
16. Cure Tech+[Done]
17. Add Natural Bass to FX [WIP]
18. Add clarity settings [WIP]
19. Combine FX and XHIFI [WIP]
20. Add Effect Calibration to suit one's ear [WIP]
Effect Calibration:
Every human's auditory systems are not the same, some people experience Left-Right asymmetries, while some with high-frequency phobia. Each individual has a different concept of the sound field. Therefore "Hearing Calibration" was introduced.
Through a simple calibration wizard, V4A system benchmark will be adjusted according to the calibrating result. "Hearing Calibration" feature will make sure every V4A user experience its ultimate effects up to par.
Of course, due to huge "Hearing Calibration" variety, its impossible to cook all the features at once, allow ViPER520 to experiment slowly, as the first edition could only achieve Left-Right symmetric and high frequency calibration.
Click to expand...
Click to collapse
V4A FX GUI Design (Not ready)
thanks:good:
What improvements make this more precise?
Is this better than AC!D Sound Engine?
Sent from my phone, because I'm away from my PC right now
Sami Kabir said:
Is this better than AC!D Sound Engine?
Sent from my phone, because I'm away from my PC right now
Click to expand...
Click to collapse
I've tried both and AC!D sounds better for me.
Sami Kabir said:
Is this better than AC!D Sound Engine?
Sent from my phone, because I'm away from my PC right now
Click to expand...
Click to collapse
For me "YES". I tried almost all song engines such as Acid,DSP,Awesome Beat,Pure Audio& this.I love this more.
Try using different convolvers
I'm sorry for such silly question
But what is IRSamples?
Do i need them?
fongandy said:
I'm sorry for such silly question
But what is IRSamples?
Do i need them?
Click to expand...
Click to collapse
It is Impulse Response.It is optional
1.Download it and extract to sdcard/Vi4PERAndroid/kernel (if folder does not there,jump to step 2 and then step 1)
2.Open Vi4PERAndroid,check box "impulse response"
3.Select desire samples
hermeshhn said:
thanks:good:
Click to expand...
Click to collapse
Please press "THANKS":smile:
Grady22 said:
What improvements make this more precise?
Click to expand...
Click to collapse
OP updated for detail
More IR Samples added:good:
Yeah ! I'm using this mod really cool ! Best working with Google Play Music.. choose setting -> equlizer to viper4android
edit -> I faced some problem with that I think this help to others.
When Activate Mod Sound not wotking with poweramp and some apps (Headset also). for get sound back need to disable Viper4android .
quality sound but need more fixes i think.
Yes,that's right dude
Rom : Umbrella Corporation V2
Kernel : CoCoE 6.2
4cylturbo scripts + CrossBreeder
imcoolsj said:
Yeah ! I'm using this mod really cool ! Best working with Google Play Music.. choose setting -> equlizer to viper4android
edit -> I faced some problem with that I think this help to others.
When Activate Mod Sound not wotking with poweramp and some apps (Headset also). for get sound back need to disable Viper4android .
quality sound but need more fixes i think.
Click to expand...
Click to collapse
To use Viper4android with Poweramp, you must :
- go to settings (of Poweramp)
- go to Audio Engine
- go to Advanced Tweaks
- uncheck "Direct Volume Control"
Envoyé depuis mon GT-I9070 avec Tapatalk
Letin69 said:
To use Viper4android with Poweramp, you must :
- go to settings (of Poweramp)
- go to Audio Engine
- go to Advanced Tweaks
- uncheck "Direct Volume Control"
Envoyé depuis mon GT-I9070 avec Tapatalk
Click to expand...
Click to collapse
yep but i also got ringing problem aswell
Edit - ok working nicely no problem.. I dont know wht happen
imcoolsj said:
yep but i also got ringing problem aswell
Click to expand...
Click to collapse
I never get any problems since the 1st time i used.
WOW! View count nearly 1,000 in my first post. Thank you all
anyone using jetaudio try this out yet?
FX Version 2.2.0.9 update :laugh:
What audio driver un first start i need install ?
Enviado desde mi GT-I9070 usando Tapatalk 4 Beta
MX Player Pro user here; I use Kodi to stream shows for my kids to watch and it supports EDL files that I use to cut out commercials, certain scenes, mute language, etc. It would be great if this could be added to MX Player as well for when they want to stream on their tablets.
Kodi functionality came from MPlayer EDL and Kodi supports the following types of edits:
Cut - the content is completely removed from playback as if it were never in the original video.
Mute - the audio is muted, video continues playing.
Scene Marker - these can be used to seek to points of interest within a video similar to how chapter seeking works for DVDs.
Commercial Breaks - each commercial break is automatically skipped once during playback.
The name of the file must be the same as the video file but with a file extension of .edl.
The file contains the start and end times of the edits along with the type of action associated with each edit. The file format is:
[start time] [end time] [action]
Start and end times can be defined as seconds, HH:MM:SS.sss, or frames. To specify frames precede the frame number with the # symbol. Supported actions are:
0 - Cut
1 - Mute
2 - Scene Marker (if start and end times are specified, the end time is used)
3 - Commercial Break
For example, the following .edl file content will skip from second 5.3 to second 7.1, mute at 15 seconds, unmute at 16.7 seconds, and commercial skip from 420 seconds to 822 seconds. There will be two scene markers. The first at 255.3 seconds and the next at 720.1 seconds.
5.3 7.1 0
15 16.7 1
420 822 3
1 255.3 2
720.1 2
Full Kodi examples here
Thanks,
Ranbato
+1
Alright, I'm not an audiophile & I wouldn't know what those many sliders in equalizer apps do, but one of the first things I do when I setup windows in a new laptop is tick the Loudness equalization option. What it does is it reduces the volume of incredibly loud videos, increases the volume of low volume videos and I never have to fiddle around with the volume settings from video to video just to get it equally loud. Is there any similar mod for android that would allow me to normalise volume systemwide? I'm using a rooted Kenzo Xiaomi redmi note 3 with MiUI lollipop 5.1.1.
I need it too!
Use Dolby Atmos. It has a volume leveler feature. I'm using the Magisk module Dolby Atmos r6.5b by Yash98. Worked extremely well.
I used these settings.
imgur.com/a/UIg8a
{
"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 on April, 2023 there are following methods:
The avialble applications can be categorised as follows'
I) Real Time Normalization
(a) Across the system: Viper4Android-Android, Realtek driver v6.0.1.6767, Date 30-10-2012-Windows, Realtek-Dolby Audio
(b) Application level: AIMP-Android, AIMP-Windows, double Twist v3.2.1-Android, Cloud Player v1.8.5-Android, many online streaming services
II) Replay Gain identification, linking and saving as separate file without even disturbing meta data: Neutron Audio Player - Android
III) Replay Gain Normalization (Replay gain writing at Meta Data it can be undone, if player is not compatible it will ignore Replay gain): mp3gain, foobar2000, R128Gain_1.0.11_win64_gui.
IV) Loudness conversion (can not be undone to original, such processes generally cannot be lossless): Audacity, etc many apps for windows as well as android.
Note: Perceived volume level or Digital “loudness” is measured as LUFS and it’s negative. Mp3gain 89dB = -18LUFS
--------------------------------------------
I.a.1 The following is experience sharing of Android with Viper4Android 2.7.2.1 on spare phone Xiaomi mi5 lineage 17.1 (Android 10) (Phone Volume 40 to 70%)
i) Enable "Master limiter"
Output -0db
Output pan 50:50
Threshold limit 0dB
ii)Enable "FET Compressor" with the following settings
operator threshold to -60dB (or -50 to -60dB)
Compression ratio to 10.00:1, (or higher like 20:1 upto infinite)
Automatic Knee untick it,
inflection: 10.8dB
inflection point gain 2.00x,
Automatic Gain-Untick,
Automatic Gain 25.6dB (or 20 to 40dB it will be more effective but in relation with operator threshold )
Automatic attack, untick
Attack to 10ms. (0.1 to 12ms)
Max attack 200ms, (10 to 250ms)
Automatic Release untick
Release 20 ms (0.2 to 25 ms)
Max Release 250 ms (2 to 300ms)
Crest 20dB,
Adapt 2639
Clipping prevention Tick
it is able to normalize loudness automatically tested qith audio volume 88.8dB (-14LUFS) and 105.2 db (-3LUFS), -36LUFS (dB as identified by MP3Gain PC software).
As normalization standard is available so many parameters are not required for audio normalization, once selected it can target -18 LUFS like Foobar plug in /double Twist.
Note:
(i) Even after Audio Modification libraries (AML) is installed, a4v needs SoundFX to be disabled. It is working on Legacy Mode. it works along with Dolby Atmos also.
(ii) James DSP is having Dynamic Range Compressor, but not having options to provide necessary inputs /it is not having them built in, it is not able to work as auto volume normalizer.
(iii) Any DSP expected to impure or introduce artifacts to the audio, we may not be able compensate by tweaking with v4a etc to the original. If you enjoy your own way, you may like it. Further if the function of Auto loudness / Auto volume level /auto volume normalization is at top priority , it succeeds to great extend android across the system. Tested with pink noise with digital loudness from -3LUFS to -23LUFS. It is noticed if bass is very high in original the above settings may not be suitable or difficult to adjust to universal setting.
(iv) There is no auto loudness normalization in "Dolby Atmos" in current versions. Dolby Audio is effective which is available at speaker control panel on windows 10.
in my case:
The Viper4Android 2.7.2.1 rootless type installed from TWRP (as magisk module is infinitely trying for installation of driver) even after installing Selinux 11, AML 4.2, Lineage's SoundFX disable or all in one type available at Github.
at present UNINSTALLER for above rootless type is not readily available.
There is noticeable deterioration in sound quality of low frequency with fet compressor of v4a.
I.a.2. or If you are on windows 10 with Realtek audio , install 2012 driver v6.0.1.6767, Date 30-10-2012 (old driver) it will give options “Enhancements" select loudness equalization ’ (sometimes it miss few milliseconds at start of track). This is real-time type as well as across the system, but it's effectiveness cannot be checked with pink noise. It is also noticed that later drivers having Dolby Audio , when made it on , it is also acting as loudness normalizer. However Dolby Atmos is not having any such feature.
---------------
I.b.1 or use "double Twist v3.2.1.apk" (i.e classic) Android {for real-time normalization: Settings>Loudness Normalization>on} but it is not able to recognize all folders / audio files.
I.b.2. or "Cloud Player v1.8.5" for Android by double Twist Corp {for real-time normalization: Settings>Loudness Normalization>on (after buying)} but it is not able to recognize all folders / audio files.
I.b.3. Or use "AIMP" for Android or PC {for Real-time auto loudness normalization: options >sound effects > options > Volume Normalization> Replay Gain > select / Tick Replay Gain, Untick at Use values from tags (as not required for real time mode) , Tick on the fly Analysis> tick (=ok)}. Some times it misses by a few milliseconds at new track.(PC version's UI is not user friendly at present)
I.b.4 or Jet Audio HD Player Android {for Real-time auto loudness normalization: Menu > Preferences > Playback> select "Adjust Replay gain with AGC"}
I.b.5 Foobar2000 PC
Use "EBU or R128 Normalizer" plugin for Real-time auto loudness normalization ( install the plug in , add the same at DSP from preference. It is working ok. Tested with pink noise with digital loudness from -3LUFS to -33LUFS. Working perfectly when started with -33LUFS and going up , it's output was normalized to -18LUFS and verified with Youlean_Loudness Meter 2 vst3 plug-in installing to Foobar.
I.b.6 PC through installation of VST adapter: adding this adapter to DSP compnent to Foobar and using available VST plug in. At present volume normalizer for play purpose yet to be developed.
I.b.7 Many online streaming services
---------------------
II.1 "Neutron Audio Player" Android It writes replay gain information to a separate file with a reference for location and file name, so even meta data is also preserved. However getting into folder browsing is outdated {Neutron v2.12 Menu (3 horizontal lines) icon> Sources (do not select folders available in options, the following folders will linked /show up at the folders of neutron at later stage )> + > File system > Devices > SD card> now it will come to nearly modern browser mode..browse to required folder having music files...., select folder > select Tick > it will scan files}
(i) Addition of music folder to Neutron
{Neutron v2.12 Menu (3 horizontal lines) icon> Sources (do not select folders available in options, the following folders will linked /show up at the folders of neutron at later stage )> + > File system > Devices > SD card> now it will come to nearly modern browser mode..browse to required folder having music files...., select folder > select Tick > it will scan files
, if not hold on folder to get option to scan.(The files inside above folder is not responding/not scanning , delete above folder in above settings of neutron click and hold to get delete option (it is not real deletion at internal drive) , make back and forth , to get refreshed and re-create. If required
select other than previously used folder or super folder or some other sub folder. For using any other than sub folder you have to repeat above process.
{Neutron v2.21.9 Menu , just after fresh installation : select Audio Source as Manual>File System> + > Audio files folder or subfolder (as per your plan and scheme how you want them appear later) >Use This folder > ALLOW >select this folder > click on Tick Icon> Folder on drive will be added to folders of Neutron, if not successful add another folder or subfolder consisting audio files.
if above skipped or at later stage some more folders to be added : (3 horizontal lines with arrow) icon> Sources > + > File system > + > now it will come to nearly modern browser mode..browse to required folder having music files...., select folder > >Use This folder > ALLOW > select Tick >.....
(ii) (i) Deletion of music folder to Neutron
To delete folder in neutron app (No physical deletion on inernal drive) : (3 horizontal lines with arrow) icon> Sources > tap and hold on the folder > delete
(iii)Normalize the volume level all files in a folder to -18LUFS
{Menu> Sources> Folders > Click and hold on the required folder to get normalize option >+EQ Preset> Normalize > select Tick}
(Source file will not be affected , even metat data)
(iv) To remove above normalization
To delink above Neutron assigned Replay Gain through Normalize: {Menu> Sources> Folders > Click and hold on the required folder >click again on +EQ Preset}
Note: Some times icons /menu are relocated, please find them to get navigation options.
-----------------------------
III.1 mp3gain.exe {It is the most compatible with Windows as well as Android apps, it is a defacto standard for Replay Gain, until mp3 normalization standard is formed}
or III.2 Foobar2000 v1.6.16 {compatible with Foobar2000 player v.1.16.16, AIMP v3.30.1250 and VLC player v3.5.4 , Jet Audio HD v11.2.3, both windows / Android , USB Audio player pro trial 6.0.3 (Android) but not v6.1.0.0, Power Amp v3b957 (Android), FIIO Music v3.1.7 (Android) }
or III.3 R128Gain_1.0.11_win64_gui {compatible with AIMP and VLC player both windows / Android, USB Audio player pro trial 6.0.3 (Android) but not v6.1.0.0, Power amp v3b957 (Android)} program on PC (freeware) to write replay gain data at meta data of track (or album) without changing any music data i.e music will be as original. If the player is compatible with this replay gain, data stored at metadata will play the music file with normalized volumes.
----------------------------------
IV.1 Normalization open freeware DAW like Audacity etc.
Procedure to Loudness Normalization by Audacity
1)file>Browse to the required files > Open all required files,
2)Select all files,
3)Effect > Volume & Compression>Loudness Normalization>Perceived Loudness (Digital)>.....LUFS>Apply
4)File > Export >...... (processed file will be outlet folder)
IV.2 PC through VST3 for 5.1
Install VST3 plug-in e.g The Normalizer by FinalLoud by TBPro Audio VST3 manager. They are in advanced audio creation (DAW) etc. It will do permanent changes to music.
-----------------------------------------
In case of real time loudness normalizer, if it is not programmed to know track to track to information or analysis of sufficient length of buffer etc , it may intervene in between / intermittently causing a feeling of unnaturalness or distortion. Same difficult is similar with across system loudness normalizer.
--------------------------------------------
Due to any reason , if you don't want to listen to full length of song, but initial few seconds (like 30 sec or 120 sec or 180 sec or any) , automated preview of various varieties are available at "Automate Community" a forum of Automate by llamalab.
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