Download Jamulus

0 views
Skip to first unread message

Lynne Pruskowski

unread,
Aug 5, 2024, 5:05:26 AM8/5/24
to compsinemi
Iinstalled Jamulus on my Windows 10 PC, and tried to optimize the audio settings.

Unfortunately i closed with a configuration where no audio output was working.

When i try to start Jamulus now,

i get an error "No usable ASIO audio device (driver) found" , "ASIO4ALL v2:The audio device does not suppport the requirde sample rate. The required Sample rate is 48000 Hz."


I have had the same problem today but reinstallation of both jamulus and ASIO4all didn't work. It took me several hours to figure out what the problem was. I had to use another ASIO host to enable the ASIO4all controlpanel in order to set the sample rate from the wrong 44.1kHz on the right 48kHz. There are soundcards that use 44.1 kHZ for standard but you can't correct this before ASIO4all has started. The problem is that Jamulus stops without giving the user any access to the ASIO driver controlpanel when it doesn't match the 48kHz and ASIO4all doesn't show up its panel when there is no ASIO request from a running host like Jamulus. It is a circlulair problem.

Question: Is it possible to offer the Jamulus ASIO settingspanel in case of and ASIO ERROR so that the user get access to the jamulus settings panel and ASIO controlpanel button, despite the wrong actual ASIO settings?


Hello Luuk, That is true in the case the user has actively checked the online settings box during installation, this menu wil be available. In default the box is uchecked during installation and ASIO4ALL is installed without settings menu option. For most client users, it isn't obvious to check this box on forehand except when you know why.


I have not this problem for me as I'm with Linux, but the case interrests me for my friends on Windows. Xamp, was it not possible to set A4A from without Jamulus, e.g. from A4A Windows Programs menu and/or Windows Control Panel's Sound applet ? Or is there something stored in jamulus (ini file ?) ?


I encountered the same problem as the original poster, and thanks to Xamp's post from 04 Apr, I at least was able to get to the ASIO4ALL control panel. In the Windows Sound Controls, I have deactivated all devices but the microphone and the speakers (as I use a headset), and have switched the mic to 48000 Hz. These two devices are the only ones showing up in the ASIO control panel; unchecked everything else. The A4A control panel gives no options to adjust sample rate or anything. Jamulus keeps showing "No usable ASIO audio device (driver) found - ASIO4ALL v2:The audio device does not suppport the required sample rate. The required sample rate is 48000 Hz." on startup.

Any ideas or suggestions? All help is appreciated.


Hello Roland, First you have to enable all the soundcards inside the windows sound menu in order to let ASIO4ALL to find the cards. I read you did. Then open the ASIO4ALL setting panel. In case you can't see it in the menu (just as Luuk posted above), you have to reinstall ASIO4all with the settings box checked now. After opening you have to select the right soundcard. To see the properties you have to press the icon right down in the panel to see the card settings. In case your cards don't support 48kHz or 24 bit, you can force ASIO4ALL to resample 44.1 to 48kHz and to use 16 bits, but be careful with these You can also tune the buffer to the right value Start with 512 sample and reduce when you experienced that it works without dropouts in Jamulus. I added a picture with some screenshots. I hope this can help you. Regards, Rob


Rob, thanks for the advise. After some more testing last night and today and a ton of Youtube videos, I found out that my webcam (a Microsoft LifeCam VX-1000; driver dates from 2010, but is indicated as being up to date) and Jamulus / Asio4All seem not to be getting along. See Screenshot of what A4A says (thanking also Luuk; that "Offline-Settings" checkbox went totally unnoticed). Jamulus still won't start, same message.

What does get past Jamulus and A4A is deactiving the webcam in the device manager, i.e. as if removing from the system, i.e. not just in the Windows sound controls. That is unfortunate as our rehearsals would probably benefit from having the video in parallel (sound over Jamulus, video over Skype, Zoom etc.).

So with your help I got the Jamulus client going. Thanks. [How to do the video in parallel should rather feature in separate thread, IMHO.]

Roland


I am having similar problems. I managed to select something not working in ASIO Setup (via Jamulus -> Settings -> ASIO Setup) and get stuck on Jamulus not starting - the same as Helmut reports in the first post. The only way to get out of this is uninstall/reinstall ASIO4ALL. The Offline-Settings tool did not help. Even selecting the originally working settings didn't help. I just noticed the installer claims the tool to be useless:


Hello, I have similar problems as mentioned before. The same message as Helmut .

"No usable ASIO audio device (driver) found" , "ASIO4ALL v2:The audio device does not suppport the required sample rate. The required Sample rate is 48000 Hz."

Here attached the error msg and also the ASIO4all configuration.

I've ticked on Always Resample 44.1 kHz to 48 kHz with no success.

Any idea will be welcome

Thanks in advance


I am in the same boat with one of my collaborators, and have not gottenanywhere so far but am also finding some 44KHZ devices working fine so I am not sure whey some can scale up and not others, did you come to any resolution here?


Hi, trying not to create a new thread, but running into issues with resampling that, frankly, I am disappointed in myself for just discovering. The idea that 44KHZ microphones are unsupported is creating a significant barrier with the people I am trying to get on it as many of them invested in usb microphones that can't run at a higher rate. Some seem to be working fine, users on the same microphones on Macs are working, people on PCs have their devices getting rejected (and they are using the same Snowball iCE mics on both platforms). Obviously, there are variations in OS but is there any straight forward advice for this, or can the script get ammended or an add for 44KHZ support with the caveat that it will be lower quality? In trying to resample 44KHZ to 48KHZ in ASIO4 Jamulus still wouldn't accept the input.


Jamulus is a reasonable way to continue to interact with fellow musicians and actually broaden the network. I've been using it to play with the jazz band that I had recently joined just before Covid-19. It's kept some of us going - learning new stuff, even. Last week, I had a jam on sax, blowing through some standards with a bunch of complete strangers and we all said we would do that again this week. A couple of us (kb and sax) started it off in a 'room' and when other people saw that there was something going on, they joined us so that we ended up with a full band.


Delay and sound quality issues could put some people off. I found on occasions, playing busier riffs, that the sound coming back to my ears late made it almost impossible. The drummer in our jazz band doesn't listen to himself through the system, for this reason, though that is not advised. I've noticed that he tends to slow down through a number, because we're coming through late in his ears. Apparently the brain does eventually adjust as long as the delay isn't too high. My set-up operates at between 40 - 50ms which isn't great but it's not terrible. 20ms is good. If you lower the buffer size, you get a lower delay, but the sound quality goes, so it's a juggling act.


Every week, there's a group who hold an online streamed 'WorldJam' which is often excellent and involves random musicians from all over. I joined last week briefly on sax and again this week. Because they had technical hitches this week, they were pushed for time and didn't talk to each of the jammers. That's why I was called by the wrong name and missed the start of my solo and also why I hadn't noticed I had my 'mute myself' box checked and therefore couldn't be heard anyway! What an idiot! Still, I noticed that the eminent professors in the iSage conference kept forgetting to turn on their mics, so I'm not alone.


Yep, lots of bass players on the public servers. Perhaps bassists are more inclined to try new things, and more persistent in getting things to work?



Personally only have good things to say about using jamulus. Sound quality is sometimes not great, but I found the overall experience is great.


Yep. It's getting better and better all the time with each update. A gift of a piece of software that isn't widely appreciated. I can see how it can become very useful for pre rehearsal rehearsals. Thrash it out on jamulus so that everyone knows the form etc. and then when it's more or less sorted, get together for the full rehearsal. Would save on fuel, time, studio fees etc. (when we eventually get back to in-person rehearsals)


Interesting point. I would recommend the opposite, which is to only turn off direct monitoring and only hear the return signal from your instrument. In that way you can adjust your playing to compensate for latency. Of course that doesn't work for singing or acoustic instruments


Agreed. You should try to hear the return signal if you can. The brain compensates for latencies after a while. The trick is to hang into the drummer. Even when I play sax, I try to turn up the return to drown out the live sound. I don't use the 'solo' button any more because I've been caught out in a live jam with people entering the room who I'd previously put on solo. It cuts out all the other feeds and everything goes silent. Now you can set new entrants to the room to come in at 0% or something which won't deafen you. Most recently I've played with a violinist in the states. He was using electric violin and managed to totally compensate for 140ms+ latency!

3a8082e126
Reply all
Reply to author
Forward
0 new messages