Falcosc / enable-loudness-equalisation

automatically adds and enables loudness equalisation to any playback device
GNU General Public License v3.0
57 stars 9 forks source link

Admin Error with Admin PowerShell #29

Open prodbyeagle opened 3 months ago

prodbyeagle commented 3 months ago

I dont really know why im getting this?

image

ArtIsWar commented 3 months ago

You're need to run Equalizer APO as LFX/GFX FIRST, then run the falcosc's command. Not an issue with his work at all.

Falcosc commented 3 months ago

Interesting that there are usecases where an admin ha no access.

https://github.com/Falcosc/enable-loudness-equalisation/blob/f4de655353da0c3d9a28840e845f305e053539a4/EnableLoudness.ps1#L76-80

$devices = Get-ChildItem "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Render\*\Properties"
if($devices.length -eq 0) {
    exitWithErrorMsg "Script does not have access to your Audiodevices, try to run it as Admin."
}

I guess Equilizer APO does change the visibility of the registry keys from System to admin.

Thats why I habe the hack in the PS file, to overwrite System write only Keys. But on most devices properties are at least readable by admins.

I probably won't add the hack on this check, because it is ugly as hell. @prodbyeagle could you screenshot the permissions of your Audio renderer registry keys before you run the other tool please? HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Render*\Properties

Maybe we can change permissions without equilizer apo

prodbyeagle commented 3 months ago

You're need to run Equalizer APO as LFX/GFX FIRST, then run the falcosc's command. Not an issue with his work at all.

i did i used your setup but this came

ArtIsWar commented 3 months ago

This GitHub is not the place for this, my community discord is.

@Falcosc apologies, unique to a setup of mine, not sure why they trickle over here.

prodbyeagle commented 3 months ago

i reinstalled everything and i came back image

here are the permissions image

ArtIsWar commented 3 months ago

@prodbyeagle Again, these issues aren't with Falcosc's work but with how you're following my guide.

Please take this issue to my discord and not crowd the Git with issues that aren't related to Falcosc's work.

prodbyeagle commented 3 months ago

Please take this issue to my discord and not crowd the Git with issues that aren't related to Falcosc's work.

Alright.

Falcosc commented 3 months ago

Screenshot of admin permission of any device below renderer would be interesting

We need any properties folder. Best if you could find your Sound device hidden behind the folder id to screenshot the admin permissions of it's properties folder

prodbyeagle commented 3 months ago

image

Screenshot of admin permission of any device below renderer would be interesting

We need any properties folder. Best if you could find your Sound device hidden behind the folder id to screenshot the admin permissions of it's properties folder

prodbyeagle commented 3 months ago

Screenshot of admin permission of any device below renderer would be interesting

We need any properties folder. Best if you could find your Sound device hidden behind the folder id to screenshot the admin permissions of it's properties folder

Oh my bad i read that wring imma do that soon

lucr80 commented 1 month ago

1 - Is the command in powershell definitive, after restarting the PC the audio settings will be there or do you need to do the scheduled part of tasks? 2 - Do these commands depend on gpedit group policy? In this case they would not work on Windows home. 3 - A note I noticed that even activated in the audio control the Bass settings do not change, you change, but do not change anything in the audio, only when you install the bass and the equalizer. Is that right?

Falcosc commented 1 month ago

Depends on how your driver is implemented. So trial and error on every device