Yes this is exactly what happen to me and I am unsure what config made the mic selectable.
run this in the terminal and check you can capture from both the mic's
arecord -Dhw:0,6 -c2 -r48000 -f S16_LE -d 10 /home/YOURUSERNAME/test-06.wav
arecord -Dhw:0,7 -c2 -r48000 -f S16_LE -d 10 /home/YOURUSERNAME/test-07.wav

You will get a 10 second recording so make some noises 😆

test-06.wav didn't record anything at all and test-07.wav recorded my voice just fine. why isn't the mic showing up on input settings on budgie and still creating that sound file?

As I said on github I have the following in a pulse audio modprob but since you don't have this I guess you could add the following line to a file in /etc/modprob.d/ I have one file called intel but not sure if I added it or the sof firmware added it 😆
load-module module-alsa-source device=hw:0,7

This is what my /etc/modprob.d/intel file says

# Do not load the 'snd_soc_avs' module on boot.
blacklist snd_soc_avs

You can try add both lines or just one line then power OFF and restart between each edit.

PS: Pulse Audio is what I used to make it selectable

    bigrammy I see, I tried both and one at a time of those commands and nothing showed up on sound input(greyed out). I was hoping someone had a solution that worked with pipewire. thanks for the help.

        darkserge try installing Pavucontrol from repo
        change the Profile on the Configuration tab from Analog stereo-output to Analog stereo duplex
        See what that does.

            Axios I have pavucontrol installed. configuration tab has no option for Analog stereo duplex or Analog stereo-output. The only options are: stereo output + Stereo input, Stereo output, Stereo input(unplugged)(unavailable), Pro Audio, and off.

                darkserge
                As I said I think you need this line
                load-module module-alsa-source device=hw:0,7
                added to a conf file for example /etc/modprobe.d/alsa-base.conf
                You can use nano to create and edit it.
                sudo nano /etc/modprobe.d/alsa-base.conf

                and what Axios has said.
                You can always uninstall Pules Audio later if another method is found using wireplumber.

                This may also take a couple of reboots to take affect. I tried all things but nothing seemed to work then boom it was their in the pavucontol so I selected it in there as the default and its worked ever since.

                I am not sure why our Asus devices seem to have so much trouble with the mic's.

                      bigrammy Ya I noticed alot of asus sound issues online
                      I think if he gets that setting it will work
                      I have no selection for (stereo output + Stereo input)
                      interesting

                          darkserge select Pro Audio for the profile then reboot and view the input devices tab and look to see if any of the "Hardware Input Devices" listed show any signs of life.

                              Axios I have 2 configuration profiles and all the various Analog and Digital profiles and the Pro Audio 😆 I have no idea how any of this sound stuff actually works it all seems over complicated to me. 😢

                              @darkserge I am going to get some sleep now let us know how you get on.

                                Kinda basic question we are talking internal mic and not a headset?

                                bigrammy that worked it shows up in sound input in budgie settings but it didn't get rid of that annoying f9 keyboard mute light

                                    darkserge Awesome so glad it's working!
                                    My keyboard didn't come with lights of any kind so that's a first world problem I can't help with. 😂
                                    Hopefully this internal Mic detection and loading problem gets solved officially one day. 🤞

                                      darkserge Yup glad its working also
                                      But hey thats what the forum is for we have enuf people something usually transpires out of things.

                                        As a possible Work around!
                                        According to https://www.alsa-project.org/main/index.php/Asoundrc
                                        It's possible to create a /home/.asoundrc file that can be modified to set your chosen hw device as the default.
                                        Could someone familiar with this sort of thing create a .asoundrc template we can easily edit adding our details
                                        from arecord -L and or arecord -l or aplay -L aplay -l

                                        Arch wiki gives some info about this and I think it would be useful for those with problem devices and SOF issues.
                                        https://wiki.archlinux.org/title/Advanced_Linux_Sound_Architecture/Troubleshooting#Setting_the_default_microphone/capture_device

                                        I would do it myself but I am not confident in my comprehension and coding skills sorry

                                          bigrammy I suck at coding myself and that info doesn't help me much.

                                          Something of note the mic is detected if you fresh install solus from the site, once you sudo eopkg up it doesn't detect the mic anymore unless you select pro audio from pavucontol

                                              darkserge Yes it's all a bit clunky but at least you can get it working using the pavucontol.
                                              Just for Info that unused S/PDIF in Alsamixer was for My HDMI when I un-muted it the Audio worked via HDMI which it didn't before but yours may well work fine but if it doesn't you know were to look first.
                                              It seems like Solus & SOF did a better job integrating your sound-card than it did with mine which is a bit of a hybrid system implementation it seems.