Conversation
| @@ -10,7 +10,8 @@ permalink: "/wiki/Installation-for-Windows" | |||
| # Installation for Windows | |||
| Make sure you read the [Getting Started](Getting-Started) page. | |||
| 1. **Download and install an ASIO Driver**. It is recommended to use a sound card/interface with a native ASIO driver. If you don't have an external sound card, you probably need to install [this free ASIO driver (ASIO4ALL)](https://www.asio4all.org){: target="_blank" rel="noopener noreferrer"} before installing Jamulus. | |||
There was a problem hiding this comment.
Can this also note that "It's well worth installing the ASIO4ALL Off-line Settings tool when installing ASIO4ALL", as well? It lets people set up before running Jamulus - i.e. not having Jamulus make wrong decisions about what devices are available. Indeed, I'd even say this is the point to say "If you're installing ASIO4ALL and haven't used it before - go read this" and link to something that will explain what's going on... Once we have it.
There was a problem hiding this comment.
If you're installing ASIO4ALL and haven't used it before - go read this
Yes. That's a good suggestion. Can you open a PR to the changes branch with this proposal?
Concerning the off-line settings, I'm not exactly sure if that helps. I think there was a discussion somewhere that it doesn't do what we thought it would do: You can't setup the A4A in/outputs with off line settings since A4A saves configuration on per app basis.
There was a problem hiding this comment.
You can't setup the A4A in/outputs with off line settings since A4A saves configuration on per app basis.
Oh - OK, no point then, agreed. I wonder why it exists? (Maybe that's why it's so hard to install....)
pljones
left a comment
pljones
left a comment
There was a problem hiding this comment.
So this shouldn't be merged until after the latest tag gets moved?
Yes it should! If we merge it to changes, it will not go live instantly. jamulus.io is built on the files on the release branch. Once a Jamulus release is planned, release will be merged into translate and once the translations are finished and Jamulus gets released, translate will be merged into release which then "publishes" the site. |
|
Ah, right... Is there a document for maintaining the jamuluswebsite, i.e. with the process needed to make changes and release them? (Not related to this, of course.) |
|
Not exactly, but see https://github.com/jamulussoftware/jamuluswebsite/blob/changes/CONTRIBUTING.md and probably #31 and #14 But information seems to be cluttered everywhere. |
|
Merged. Sure, we might need to move to another solution soon. |
2 participants
Solves: #307
Probably still worth a discussion. This is a quick and easy approach.