Not change communications devices

[Bl41rw1tch]

Hello,

The bug I encounter concerns audio device changes, when I switch from one configuration to another via the Display Magacian software, it keeps the other sound card as the default communication device. I check the box when I create the profile "also set this as the communication audio output" on the output and the microphone.

But when I run the script it applies the correct sound card to the output but leaves the output and the microphone on the sound card of the other layout. I don't know if I can make myself understood well, I don't communicate easily in English.

I would like the sound card to be active as a non-default device (that's good) and as a default communication device.

Enviroment (please complete the following information):

• Windows Version: Windows 10
• DisplayMagician Version 2.5.0.352
• Video Card: RTX 3080
• Number and make/model of monitors: One Group 1x Samsung G9 LC49G95TSSPXEN + 1x Samsung SMS24A650 and Second group 1x MSI mag301cr2 + 1x Samsung SMBX2440
• Date of last video driver update: 2023-11-09
• Date of last windows update: 2023-12-03 (Build 19045.3693 Version 22H2)

There may not be a bug but simply a problem of understanding on my part.
In any case thank you for your work, it saves me a lot of time when I have to change layouts. Keep it up, it’s really great!
Thank you in advance for your help

Sorry for my english, I get help from Google translate.

[terrymacdonald]

@Bl41rw1tch if I understand correctly, you want to set up a Desktop Layout Game Shortcut that will let you change your display layout, as well as permanently change your default audio output and default microphone, as well as your communications audio output and communications microphone. I'm assuming you leave have the 'Game to Start' set to 'don't run a game'.

If that's the case, then how you have configured it is correct. That is one of the use cases that I had in mind when I designed DisplayMagician.

It seems like there is a logic bug within DisplayMagician based on what you have described.

In order to know where the issue lies, can you please help me with some testing? Can you please update the Desktop Layout shortcut to actually open a game? This will pause DisplayMagician logic whilst it waits for the game to shut down, which will let you do some testing for me while the game is running.

Then, just before you start the Desktop Layout Game Shortcut, can you please record the:

• Default Audio Output Device
• Default Audio Microphone Device
• Default Communications Output Device
• Default Communications Microphone Device

Next, start the Desktop Layout Game Shortcut, and leave the game running. Then can you please record the:

• Default Audio Output Device
• Default Audio Microphone Device
• Default Communications Output Device
• Default Communications Microphone Device

Finally, close the game, which should make DisplayMagician perform it's last tasks. Then can you please record the:

• Default Audio Output Device
• Default Audio Microphone Device
• Default Communications Output Device
• Default Communications Microphone Device

Then please send all the 3 groups of information to me. This will let me see where the bug lies in the audio handling logic. I need those details to be able to understand if the logic bug is in the part where it first changes the audio devices, or in the part where it changes the audio devices back.

Thanks
Terry

[terrymacdonald]

Hi @Bl41rw1tch,

Thanks to you input and some local testing, I've found a bug in the code that I've now rectified. I'd accidentally set the comms microphone to be the default microphone when it was being rolled back after game closure. This effectively broke the microphone rollback. This has been fixed in the code, and the patch will be included in the next release of DisplayMagician.

For this reason I'll close this issue at this time. Closing an issue when I've fixed the code helps me keep track of which other bugs I still have to fix. You can always reopen this issue if you find the functionality is still broken when you test the next release.

Thanks
Terry