![]() NET earlier than 4.0, you will need to modify and insert the following into the section: NET is your thing, you can interact with the RtkCfg COM library by creating an interop DLL for it using TlbImp - in my case, from the Windows "v7.0A" SDK's bin folder, but other versions of TlbImp probably work. For my particular device, the relevant COM-accessible DLL is RtkCfg64.dll, RtkCfg.RtkCfgApi.1. Some Realtek drivers come with DLLs that allow you to change Fx Properties and have it take effect immediately (without disabling/re-enabling the whole device). View attachment ToggleLoudnessEqualization.zip ToggleLoudnessEqualization.exe and RTPolic圜onfigClientLib.dll are the only files necessary for the application to execute. Just an example usage, and the way I use it myself. If you have Nir Sofer's wonderful nircmd installed, that command will announce whether you've just turned Loudness Equalization on or off. The above command is useful in a batch file. So yes it could be done by batch script provided you have all the required keys (and would need to get the new GUID key names and values each time you reinstalled Windows), and change the permissions on the key to be able to toggle the value.Īll in all, it might not be worth the hassle. the registry change was all that was needed. There was no need to start/stop the audio service. then I was able to toggle the value without issue. ![]() I had to use Windows registry editor to change the permission of the key to full access for admins. Changing the permissions didn't seem to work from RW either. I was using Registry Workshop and my changes were denied. apparently these keys are protected from change by the user. you can have that key open when you change the setting and then refresh the screen and see which key has changed. it's another unique GUID label key, the value is 0 for off and 1 for on. Once you find the right key for Speakers, then you go back into the FxProperties subkey and that's where the setting is stored. ![]() My PC has 2 for some reason and changing the setting only affects one of the keys. you might only have one so it would be easy to find. In each GUID named key there are 2 sub keys named FxProperties and Properties, in the Properties key you will be looking for a key whose value is Speakers. You can take a snapshot of your registry and then change the setting in volume control, then compare the active registry to the snapshot to see which key was changed, so you know for sure. then from there it's a unique GUID key for every computer and every audio device. Murphy is correct, that's where the setting is.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |