Goldfish64 / AudioPkg

Audio stack for UEFI. Currently supports HD audio controllers/codecs. WIP

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

can we use clover nvram?

Sher1ocks opened this issue · comments

  • // BootChime variables stored in Clover GUI
  • { L"Clover.SoundDevice", &gEfiAppleBootGuid }, { L"Clover.SoundVolume", &gEfiAppleBootGuid },
  • { L"Clover.SoundIndex", &gEfiAppleBootGuid },

audiopkg use this nvrams
{ L"Device", &gBootChimeVendorVariableGuid }, { L"Volume", &gBootChimeVendorVariableGuid },
{ L"Index", &gBootChimeVendorVariableGuid }

to set, we have to enter shell to set nvram to use audiopkg.
now clover can set nvram in gui.
can we consider this nvram without command in shell?

thanks in advance

I would prefer to keep this project as separate from Clover as possible, but the BootChimeDxe driver probably could be changed to use Clover's NVRAM variables if the AudioPkg ones don't exist.

right. BootChimeDxe need it.
also i suggest one more.
BootChimeDxe volume size is max.
i always listen 100% sound volume. my laptop demaged speaker with noise.
can you reduce default volume size?
also if there are no nvram(ex. clover.sounddevice or device), can you consider no gernerate sound like clover setting in BootChimeDxe?

so, if user dont't want bootsound with BootChimeDxe in Driver64UEFI folder, just dont need remove file, we just clear nvram with F11 key in CLOVER GUI