Firebot icon indicating copy to clipboard operation
Firebot copied to clipboard

[Bug] Play Sound ignores output device setting (global and individual) when nested in Random Effect

Open Pigmess opened this issue 3 years ago • 7 comments

Is there an existing issue for this?

  • [X] I have searched the existing issues

Current Behavior

I think "Play Sound ignores output device setting (global and individual) when nested in Random Effect" pretty much covers it, but please feel free to ask for clarification.

Expected Behavior

No response

Steps To Reproduce

No response

Version

5.53.3

What operating system are you using Firebot on?

Windows 10

Relevant log output

No response

Contact Details (Optional)

Pigmess#7403

Pigmess avatar Sep 08 '22 22:09 Pigmess

I created a command, added a Random Effect to the command, then added two Play Sound effects that are each set to a different audio device inside the Random Effect playlist. Mine reliably played them randomly on their respective devices. Unfortunately, I was unable to reproduce the bug on 5.53.3.

Are you able to reliably reproduce this? If so, could you include exact steps if they differ from what I did?

zunderscore avatar Sep 09 '22 01:09 zunderscore

Steps to reproduce:

  1. Create new Command or Effect List.
  2. Add a Play Sound effect.
  3. Set the output for that Play Sound effect to a virtual audio device, or set to "app default" and set the default output in Firebot settings to a virtual audio device.
  4. Playing the sound will send it to the system default audio device regardless of selection.

I realized that the issue is tied to the use of virtual output devices - and that the Random Effect and Effect List are not necessary to reproduce it. Setting the output to a physical device circumvents the issue.

Note, I have used a virtual device as the app default in the past with no issue. My system default - where the sound is sent instead - is actually itself a virtual device.

The virtual devices in this case are created using a program called Virtual Audio Cable.

Pigmess avatar Sep 10 '22 02:09 Pigmess

Note, these latests tests I ran on Firebot 5.54.0.

Also of note, I think this behavior started after a somewhat recent update to Windows, as I found I had to re-assign my audio outputs in OBS and other programs at that time. (I have tried doing the same for Firebot - unselecting then reselecting the virtual output - to no avail. Perhaps there is a settings cache or similar that I can clear, without actually losing my settings/commands/etc?)

Pigmess avatar Sep 10 '22 02:09 Pigmess

This sounds very much like an issue with the sound devices refreshing after the Windows update and potentially needing to be reset on the effects.

Have you tried opening one of the effects that aren't working as desired, changing the output, saving and closing it with the different output, then reopening it, changing it back, and saving it a second time before testing that it works?

zunderscore avatar Sep 10 '22 03:09 zunderscore

Yes, and reconfirmed - this has no effect on the issue.

Pigmess avatar Sep 10 '22 22:09 Pigmess

Let me know if there's anything else that would be helpful to know, or whether you'd like me to provide logs/screenshots/settings.json/etc.

Pigmess avatar Sep 11 '22 04:09 Pigmess

Would you mind creating a thread in the Discord's #issues channel and referencing this issue? It might help us better troubleshoot.

zunderscore avatar Sep 13 '22 20:09 zunderscore

Checking back in. Has this been resolved? If so, I'll close the issue.

zunderscore avatar Dec 16 '23 22:12 zunderscore