Facilitate ASIO(4All) sound setup on Windows

[ann0see]

Setting up ASIO4All correctly can be quite challenging (see survey #534 (comment)). The setup should be made easier.

This GitHub issue should focus on how to make the audio setup process easier for new users.

What has already been done or is in process:

• Wiki explains ASIO4All setup in a generic way
• New website will link wiki more prominently to get more users through the wiki (Link descriptions from llcon.sourceforge.net to GitHub Wiki and new website #581)

What has not been done yet:

• Guidance in Jamulus specifically for new users. Suggestion: If ASIO4All is detected show a link to the windows audio setup page in the wiki. (Doing it via new installer now)
• Some aid if there's no connection to a server yet and asio4all is found (maybe show helping text if the mixer board is empty)
• ?
  Also see Integrate sound check #534

[gilgongo]

It's hard to know what the main cause of setup problems is on Windows, but I suspect it's knowing which device to enable/disable in the ASIO4All control panel, since the names of these devices are often obscure. This is an example of trying to clarify what needs to be done: https://www.sweetwater.com/sweetcare/articles/installing-and-using-asio4all-for-windows/

(BTW in the install video it shows the selection of "offline settings" - I wonder what that is?)

The animated gif showing the input and output device selections being highlighted is interesting. We could maybe re-create that and add it to the wiki?

[ann0see]

Off line settings is a way to access the control panel without a ASIO host, I think. #305 (comment)

The link could be quite good.

An other problem I heard about is the MS wavetable synth which could block A4A.

[ann0see]

I've edited the windows page and added some more help and structure

The animated gif showing the input and output device selections being highlighted is interesting. We could maybe re-create that and add it to the wiki?

I don't know, if it helps. Maybe I can make a small video although I'd prefer to link a video like https://www.youtube.com/watch?v=EFOMPsCSXLY But it wasn't specifically made for Jamulus.

Edit: I've made a few changes to the wiki to streamline the installation and setup process for new users.

[gilgongo]

The thing that's interesting about the gif is that it attempts to help with what (I think!) is the central problem: which input and which output from which device (assuming you have more than one) do you choose (and how do you choose them? You can select the "parent" or the "child")?

[ann0see]

What if we just link the site and declare it as "further help"?

The html ID of the setup is #asio4allsetup so we can directly send the user to the correct section

[gilgongo]

The trouble is that section mentions a few potentially confusing things like talking about a DAW (do they need a DAW to use Jamulus? What is a DAW? Etc.), Offline (What if they didn't install that? You don't need it for Jamulus), and adjusting buffer size (which we're silent on - should we tell people to set to 128 at first?). Also, what about "always resample 44.1kHz to 48Hz"? I don't actually know what the advice is on those things and that link doesn't really help on those.

Perhaps we should just add the following to the setup steps and that will cover it? Assuming this is the correct advice:

6 . Set the "buffer size" slider to 128 (if you can)
7 . Set "always resample 44.1kHz to 48Hz" (if you can)

[ann0see]

I don’t think that any of these options are actually needed (only in special situations)?

Buffer sizes are (at least for me) set via jamulus.

[trombonepizza]

New here. Not new to audio and computers.

ASIO has been a real pain when trying to get people up and running on telepresence apps like Jamulus. I did make a video on using it with Soundjack. It may only add to the confusion. Here it is : https://youtu.be/G49yCO11XGs

I might make another one on using it with Jamulus. I think one of the biggest problems people run in to with Windows and ASIO4All is that whichever app grabs the microphone first will lock to it, and then other apps will not be able to access it. This becomes a really slippery issue because many Windows setups have uncounted hidden apps grabbing the microphone (Cortana, etc).

[trombonepizza]

Here's a rather lengthy video on implementing ASIO4ALL with Jamulus. I've tried many times to make videos that are concise and exciting, but always failed. Generally, my videos are somewhat easy to follow, if you have a long attention span. If anyone wants to try to make a concise version of what I am saying here, feel free to do so.

https://youtu.be/_GzOsitVgLI

[ann0see]

The video looks quite good. We could link it with a sentence like: "Can't work out ASIO4All? Look at this video form @trombonepizza which gives more detailed setup information on ASIO4All!"

Edit: updated wiki

[trombonepizza]

Cool with me.

[ann0see]

@gilgongo?

Nevertheless, it might solve the problem for people who find the wiki. I'd actually include some aid in the Jamulus app too.

[gilgongo]

No problem with linking to a video (I've yet to watch it though). When you say "include some aid in the Jamulus app too" we have links to the wiki already in the help menu. Do you mean elsewhere in the UI?

[ann0see]

Yes. I mean a link or whatever which shows up if ASIO4All is detected. I'd prefer to link it right in the main window (where the sliders are) and/or next to the sound setup in settings.