Audio devices iterates in Windows when Jamulus starts and when joining to a server

[alekeyspiano]

Describe the bug

When I run Jamulus or when I join to a new server, selected audio device in windows changes and iterates selecting all available devices and a few seconds later returns to the initial device selected.

To Reproduce

I have a BehringerXAIR in my PC that have 4 devices, XAIR 1 2 | XAIR 3 4 | XAIR 5 6 , etc. I assign 3 4 one to Jamulus and 1 2 to windows, but when I start Jamulus or join to a server. The device selected in windows change and iterates became crazy and I lose all sound except Jamulus during a few seconds or a minute, causing losing audio in OBS, Google Chrome, Spotify, etc...

Expected behavior

To don't iterate this and keep the same device selected in windows.

Screenshots

This place becomes crazy

This is ok

Operating system

Windows 10 22H2

Version of Jamulus

Jamulus 3.11.0

Additional context

This don't allow me and other colleagues to stream our Jamulus performance on Twitch and it is very annoying for us

[softins]

Can you show us the display when you click on Configuración Dispositivo ASIO?

[alekeyspiano]

Yes Sure!

Also a screenshot of all my devices

[softins]

@alekeyspiano could you try something and let us know the result? (Not something to fix it, but to help us know where to look)

1. Make a Jamulus connection to a server, and wait for the audio device to stop iterating.
2. While still connected, open the Settings window, and change one of the settings: Calidad Audio, Retardo Buffer or Buffers Red Pequeños, while watching the audio device in Windows.

Does the audio device start iterating when you change one of those settings? Or not?

Also, you mentioned the iteration issue causes loss of sound in OBS, Chrome, Spotify, etc. Do you still get the device iteration if nothing else is running except Jamulus?

[alekeyspiano]

Hello, I did some tests:

1- Applying "Calidad Audio": iterates on Windows main devices: several cuts of sound during 45 secs
2- Idem applying "Buffers Red Pequeños"

This occurs when I open or connect Jamulus after I have the other softwares opened.

When I open Jamulus before, audio cuts are during 4 or 5 secs. But if I leave a server and try to connect other one, then we are in the first scenario.

If nothing else is running I can't check it because I have no audio to view if I have cuts or not. Always Jamulus is sounding because is always well assigned and well routing in all cases, but I have been using Jamulus for 4 years and this issue appeared since the last year. Probably a Windows updating or Jamulus updating that include changes in the audio management.

Other colleagues presents the same issue. We are almost 10 people streaming music on twitch and collaborating by Jamulus.

[softins]

OK, thanks. Those tests help narrow down where to look in the code. No ideas yet as to the cause.

[teseo]

Same issue here.

Thanks for opening this issue.

[softins]

It would be very helpful if anyone who is experiencing this issue has the time to try older versions of Jamulus such as 3.10.0 or 3.9.1, and let us know whether they exhibit the same problem.

That would help us to identify whether this is a new problem or one that has always been there.

Also @pljones, you probably have the most complex PC-based setup out of the team members. Could you see if you can observe the same issue as described?

[pljones]

There was something done to try to find a working Audio device (i.e. one that said OK when asked to open at 48000 samples per second). I'd check whether any such device exists first.

[softins]

@alekeyspiano sorry, more questions, since I don't have a setup that can demonstrate the issue, and am currently just looking for clues in the code.

• When the devices iterate, do they do so too fast to see, or at a slower rate?
• Can you see whether the iteration includes the non-ASIO devices, or just the ASIO ones?
• Are you able to video the iteration on your phone (from before it starts until after it stops), and post a link to the video?

You said it only started doing this in the last year or so. It would be hugely helpful to us if you can identify an earlier version that does not show the problem, as mentioned above.

[alekeyspiano]

I am going to test with Jamulus 9.0 and say conclusions in the following post.

[alekeyspiano]

Hello, the same issue with older versions.

1- The iteration is very fast, in this case only iterates between 2 devices (same device different channel inputs) I will attached a video recorded from my cellphone.
2- In this test does not occured but other times, I could see my webcam audio device that is not an ASIO device.

In the next post I will attach the video to see more details about the test.

[alekeyspiano]

This is the video link (expires in 7 days)

https://we.tl/t-a80RBBbPbX

In this video you can see that I have open Spotube (similar to spotify, and same behaviour that happens in OBS too) with audio routing to my OUT 7-8 BEHRINGER AIR.

Jamulus is routed to OUT 3-4 BEHRINGER AIR
Main windows audio as you can see in the video is routed by default, and have OUT 1-2 BEHRINGER AIR

When I connect to a server (as you can see in the video) spotube audio stop, and devices iterates fast some seconds. Also my main windows device switches from 1-2 to 5-6 several times.

Moreless 20-25 secs after, audio returns and everything is OK.

The more apps I have open the more time audio cut I have.

Tested in the 9.0 version but also happens in 11.0. I evidence this issue after some Windows updates last year but I am not sure if this is the cause or is only coincidence.

A colleague that have Jamulus in MAC evidence the same Issue. Other people who I asked told me that the audio cut is only 1 sec. This happen to me when only jamulus is opened, but more time when open more apps that manage audio.