3dproger
AxelChat Client not the application source for new message sound
The client doesn't seem to be the source of the new message sound, which makes audio routing really annoying. The sound always goes through the system default audio output device regardless of what my audio settings are. I can manually set the output device of AxelChat to be a different device in the Windows audio settings, but it does nothing. Same goes for setting the volume of the application via the mixer. It's probably just going through system sounds or something, not really sure. I even checked to see if it was going through the widget in OBS, but it is not.
I don't want my viewers to hear the new message sound, so I was going to route it to my virtual device that doesn't go through to the stream. Now I've had to reconfigure my whole setup to not send system sounds to stream, meaning I have to manually set every game or app to route to a different virtual device just so the stream can hear them.
Hi! Thanks for reporting the issue. I'm planning to add the ability to customize the audio output device, the volume of the sound and choose the sound itself. I think this will solve the problem. But I can't name the implementation dates yet, unfortunately.
Hi! The sound notification for a new message is now located in an external file <app_folder>/deps/audio/notifications/default1.wav. This means that by replacing this file, you can change the notification sound. Only the wav format is supported. After replacing the file, restart AxelChat. I still haven't created a proper interface for customizing this notification, sorry. This works since 0.41.2. You can try: https://github.com/3dproger/AxelChat/releases
If you are using Streamer Bot, Axel Chat is able to connect with it via Websocket. Then, in Streamer Bot you will be able to script New Message notification and even select output device.
