That's the one I use.If you have Magisk, use that version instead. It's updated with Oreo and SELinux support is also included.
Yes, I've had 44.1k IRS files for quite some time now, after an XDA discussion that left me with the impression that the sampling rate has to match the file being played back rather than V4A's output rate in order to work.Are you using a convolver or anything that would change the samplingRate? Some are 44100 and some are 48000. I'm curious if only convolvers with the same samplingRate defined in the file you modified work
Scroll up and read a few posts above yours, maybe? )When i plug my usb audio card via otg .
It goes abnormal and unsupported.. any solution guys ?
Hoping that it will get fixed by an update on Magisk.Yes, I've had 44.1k IRS files for quite some time now, after an XDA discussion that left me with the impression that the sampling rate has to match the file being played back rather than V4A's output rate in order to work.
But since you asked, I created 48k copies of all of them and also copied over 44.1 and 48k versions of Joe0Bloggs' "3D" IRS thingies for "vivid" and "widefield" and switched back and forth while the music was playing and... I'll be damned if I could hear a difference between 44.1 and 48k for any of them. They all differ a lot from no-convolver, as they should, but from eachother between sampling rates... not that I could hear. So either it's intelligently resampling the IRS to match the stream being played back or resampling both to 48k, but anyway it's making it transparent for the user, which is OK I guess. (I'd like to minimize resampling if possible, but I guess this is better than it going from working to not-working as I switch from 44.1k music to 48k video and back.)
Scroll up and read a few posts above yours, maybe? )
I have that aswell but so far iv had no issues or warnings from my malware app or even the built in antivirus from samsung only playstore that notice comes up so dont be to worried
Sent from my BadBwoi-S9+ using XDA Labs
Try to flash Audio Modification Library after viper. That worked for me on Oreo and pie.
Nope. It doesn't work. I'm guessing this issue is only happening with msTry to flash Audio Modification Library after viper. That worked for me on Oreo and pie.
Not a solution, but it may help diagnose the problem and hopefully follow on with a cause, and possible provide a path for a solution.The driver is working fine in Spotify but it keeps working and stopping. When I'm on a song it's working fine when I change the song it stops (processing goes to no), then if I change a song again it starts working again and it keeps doing this (processing and not processing).
I already tried to install Viper through Magisk, flash as a zip even do a manual install, set kernel to permissive, use Audio Modification Library and Audio Compatibility Patch.
Then later trying to fix this first issue now Viper is also failing to detect the drivers (drive installs then I reboot and it asks to install driver again).
Checking Viper's files it's installing the .so file with the effects and even alterning the audio_effect.conf (and all paths to the .so files seem fine) but somehow it can't detect the driver.
The only Viper version that kinda works for me is the Viper FX material design 2.6 but even then I have to use it on compatible mode which causes stutters at every song's start.
Not a solution, but it may help diagnose the problem and hopefully follow on with a cause, and possible provide a path for a solution.
When its in an almost working state, I would try setting the nice and the oom values for both the audio player and Viper, to their max (which is actually the lowest number:silly You can do it manually within the shell, or you could use the App i built at: https://xdaforums.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260
You can find "nice" in the menu, at: Application Info / Manage > Manage State > Nice >Nice an app to highest [-20] > *APP ID*
and OOM in the menu at: Application Info / Manage > Manage State > OOM > OOMM an app to Superman [-17] > *APP ID*
Set both of the above for both Viper and your music player (ie "*APP ID*"), and see if that helps.
Play music and you should see yes.
See my reply before your repeated post.
v4a_fx {
path /system/lib/soundfx/libv4a_fx_xxx.so
}
#NECESSARY FOR XHIFI
v4a_xhifi {
path /system/lib/soundfx/libv4a_xhifi_xxx.so
}
v4a_standard_fx {
library v4a_fx
uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b
}
#NECESSARY FOR XHIFI
v4a_standard_xhifi {
library v4a_xhifi
uuid d92c3a90-3e26-11e2-a25f-0800200c9a66
}