-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
1b288dd
commit 073fc0e
Showing
2 changed files
with
33 additions
and
48 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,68 +1,53 @@ | ||
| # a1111-setup | ||
| **Simple and easy way to install Automatic1111 WebUI or Forge on Mac** | ||
| # Install Stable Diffusion WebUI on Mac | ||
| **Simple and easy Automatic1111 and Forge install script for macOS** | ||
|
|
||
| By default, this script will install A1111 in `stable-diffusion-webui` inside your home directory, but you can change the location if you want. | ||
| By default, this script will install **Stable Diffusion WebUI** (Automatic1111) in `stable-diffusion-webui` inside your home directory, but you can change the location if you want. | ||
|
|
||
| The script will apply some recommended fixes and install the required libraries. If there is already an installation in that folder, the script will purge the pip cache, remove venv, and force using the latest version of A1111. A new venv will be created, and you should be able to use A1111 on your Mac without any problems. | ||
| The script will apply some recommended fixes and install the required libraries. If an installation is already in that folder, the script will purge the pip cache, remove venv, and force the latest version of Stable Diffusion WebUI to be used. A new venv will be created, and you should be able to use Stable Diffusion WebUI on your Mac without any problems. | ||
|
|
||
| Simply run `bash a1111-setup.sh` or `chmod 755 a1111-setup.sh && ./a1111-setup.sh`. Wait a few minutes (depending on your computer and internet speed) until you see WebUI opened in your default browser. | ||
| Run `sh a1111-setup.sh` or make the script executable with `chmod 755 a1111-setup.sh` and then run `./a1111-setup.sh`. Wait a few minutes (depending on your computer and internet speed) until you see WebUI opened in your default browser. | ||
|
|
||
| Command line parameters: | ||
|
|
||
| ``` | ||
| [-t stable|develop] stable or develop version of PyTorch | ||
| [-f all|errors|none] apply all fixes, only fixes for errors or none | ||
| [-d folder_name] specify the destination folder for A1111 installation | ||
| [-o a1111|forge] install A1111 or Forge | ||
| [-b] update Homebrew | ||
| [-h] display help | ||
| [-r] dry run, only show what would be done | ||
| [-b] update Homebrew | ||
| [-t] use development version of PyTorch | ||
| [-i] show debug info and exit | ||
| [-f all|none] apply all fixes or none | ||
| [-d folder_name] specify the destination folder for WebUI installation | ||
| [-o forge] install Forge | ||
| [-c red|green|yellow|blue|magenta|cyan|no-color] use specified color theme for messages | ||
| ``` | ||
|
|
||
| The [latest stable release](https://github.com/pytorch/pytorch/releases) of PyTorch will be installed by default, which is now recommended for Macs. It is still possible to use the development version using the `-t develop` option, but it is not necessary anymore. | ||
| The recommended version of PyTorch will be automatically installed. At this moment, it is 2.3.1 for ARM and 2.1.2 for Intel. The development version of PyTorch can still be used with the `-t develop` option, but only on ARM Macs. | ||
|
|
||
| Only errors will be fixed by default, but you can also apply command line param tweak using `-f all`. Based on my tests, those parameters give a better and faster performance of A1111 WebUI than those provided by the A1111 team. | ||
| *PyTorch dropped support for Intel Macs. The last version of PyTorch that properly works on Intel Macs with MacOS 14.4+ is 2.1.2* | ||
|
|
||
| Use option `-d` to specify the destination folder for A1111 installation or the folder where A1111 is currently installed. | ||
| Fixes for very rare errors will not be applied by default. You can use `-f all` to apply them. | ||
|
|
||
| Use option `-o` to specify which webui to install. You can choose between A1111 and Forge. | ||
| Use option `-d` to specify the destination folder for WebUI installation or the folder where WebUI is currently installed. | ||
|
|
||
| Since some people might not want to update their installation of Homebrew, the update is disabled by default, but you can update brew using the `-b` option. | ||
| Even though [the Forge team advised users to change back to A1111](https://github.com/lllyasviel/stable-diffusion-webui-forge/discussions/801), it is still possible to install Forge using `-o forge` if you need it. | ||
|
|
||
| **Additional Notes** | ||
| Since some people might not want to update their Homebrew installation, the update is disabled by default, but you can update it using the `-b` option. | ||
|
|
||
| In some extremely rare cases, default command line parameters provided by the A1111 team might not work correctly, for example, with some Macs with eGPU. | ||
| By default, script use a blue color theme, but you can change it using `-c` option. For example, you can use `-c green` to use green color theme. | ||
|
|
||
| You can try and see which of the command line parameters below works the best for you. | ||
| The new `-i` option will show debug info and exit. This information might be helpful when you report a problem. | ||
|
|
||
| Args for Macs implemented by the A1111 team: | ||
| ``` | ||
| export COMMANDLINE_ARGS="--skip-torch-cuda-test --upcast-sampling --no-half-vae --use-cpu interrogate" | ||
| ``` | ||
| **Additional Notes** | ||
|
|
||
| My recommendation for most Macs: | ||
| ``` | ||
| export COMMANDLINE_ARGS="--skip-torch-cuda-test --opt-sub-quad-attention --upcast-sampling --no-half-vae --medvram-sdxl --use-cpu interrogate" | ||
| ``` | ||
| In some extremely rare cases, WebUI might produce only noise with `--no-half-vae`. *I have never noticed that, but some people with external GPUs and two nonstandard AMD GPUs had that problem.* | ||
|
|
||
| My recommendation for Macs with 36GB or more RAM: | ||
| ``` | ||
| export COMMANDLINE_ARGS="--skip-torch-cuda-test --opt-sub-quad-attention --upcast-sampling --no-half-vae --use-cpu interrogate" | ||
| ``` | ||
| If you experience that problem, you can try one of those command line args: | ||
|
|
||
| In some extremely rare cases, WebUI might produce only noise with `--no-half-vae`. *I have never noticed that, but some people with external GPUs and two nonstandard AMD GPUs had that problem.* | ||
| ``` | ||
| export COMMANDLINE_ARGS="--skip-torch-cuda-test --upcast-sampling --no-half --use-cpu interrogate" | ||
| export COMMANDLINE_ARGS="--skip-torch-cuda-test --opt-sub-quad-attention --upcast-sampling --no-half --medvram-sdxl" | ||
| ``` | ||
|
|
||
| Those combinations also worked without error on my Macs: | ||
| ``` | ||
| export COMMANDLINE_ARGS="--skip-torch-cuda-test --opt-split-attention-v1 --opt-sub-quad-attention --upcast-sampling --no-half-vae --medvram-sdxl" | ||
| export COMMANDLINE_ARGS="--skip-torch-cuda-test --upcast-sampling --no-half-vae --medvram-sdxl" | ||
| export COMMANDLINE_ARGS="--skip-torch-cuda-test --opt-split-attention-v1 --upcast-sampling --no-half-vae --medvram-sdxl" | ||
| export COMMANDLINE_ARGS="--skip-torch-cuda-test --opt-sub-quad-attention --upcast-sampling --no-half-vae --medvram" | ||
| ``` | ||
|
|
||
| *All comments and suggestions are welcome* | ||
|
|
||
| 3 min read |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters