![]() ![]() All I did was change the Audio Subsystem for Discord from Standard to Legacy and suddenly it's working over my audio cables again.Baron Lanteigne 2023 Computer generated virtual environment, screens, cables, synthetic grass.Ĭinématographie de la Matière Virtuelle is an installation made up of an arrangement of screens, whose contents were created in parallel with the virtual reality work Ascension. I don't know if I'm missing something or forgot a step.but as far as I know it's set up the same way as it was on my old PC.įor what it's worth, I fixed this particular issue. I know it's not the cable itself because if I set Teamspeak to Cable B it works just fine.my music player works just fine on Cable B.it's only Discord and it wont work on Cables A B or C.Īnyone else have this issue or know of any potential work arounds? I've searched and can't seem to find anyone with this specific issue (plenty of related, but none of the exact same and the other fixes don't really work). I even went into my Windows 10 Audio settings and made sure Cable B was selected there for Discord as well.but it still just doesn't work at all. When I change the output to the cable, I lose all sound from Discord. Two months ago I built a new computer so I have fresh installs of everything and now for the absolute life of me I cannot get Discord to work with the VB Cable. So I had Desktop Audio (games, and whatnot), Microphone, Cable A (Teamspeak), Cable B (Discord) and Cable C (Music players) and it has always worked perfectly. I've used it to separate all audio sources into separate channels for recording in OBS. For more than a year now I've had the audio on my PC set up with Voicemeeter Banana and VB Audio Cables (A B and C).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |