macOS#
Invoke AI runs quite well on M1 Macs and we have a number of M1 users in the community.
While the repo does run on Intel Macs, we only have a couple reports. If you have an Intel Mac and run into issues, please create an issue on Github and we will do our best to help.
Requirements#
- macOS 12.3 Monterey or later
- About 10GB of storage (and 10GB of data if your internet connection has data caps)
- Any M1 Macs or an Intel Macs with 4GB+ of VRAM (ideally more)
Installation#
Homebrew
First you will install the "brew" package manager. Skip this if brew is already installed.
Conda Installation
Now there are two different ways to set up the Python (miniconda) environment:
- Standalone
- with pyenv
If you don't know what we are talking about, choose Standalone. If you are familiar with python environments, choose "with pyenv"
Create the environment & install packages
# Activate the environment (you need to do this every time you want to run SD)
conda activate invokeai
Info
export PIP_EXISTS_ACTION=w is a precaution to fix conda env
create -f environment-mac.yml never finishing in some situations. So
it isn't required but won't hurt.
Download the model weight files
The configure_invokeai.py script downloads and installs the model weight
files for you. It will lead you through the process of getting a Hugging Face
account, accepting the Stable Diffusion model weight license agreement, and
creating a download token:
Run InvokeAI!
IMPORTANT
Make sure that the conda environment is activated, which should create
(invokeai) in front of your prompt!
To use an alternative model you may invoke the !switch command in
the CLI, or pass --model <model_name> during invoke.py launch for
either the CLI or the Web UI. See Command Line
Client. The
model names are defined in configs/models.yaml.
Common problems#
After you followed all the instructions and try to run invoke.py, you might get several errors. Here's the errors I've seen and found solutions for.
Is it slow?#
python ./scripts/orig_scripts/txt2img.py \
--prompt "ocean" \
--ddim_steps 5 \
--n_samples 1 \
--n_iter 1
Doesn't work anymore?#
PyTorch nightly includes support for MPS. Because of this, this setup is inherently unstable. One morning I woke up and it no longer worked no matter what I did until I switched to miniforge. However, I have another Mac that works just fine with Anaconda. If you can't get it to work, please search a little first because many of the errors will get posted and solved. If you can't find a solution please create an issue.
One debugging step is to update to the latest version of PyTorch nightly.
If it takes forever to run conda env create -f environment-mac.yml, try this:
Or you could try to completley reset Anaconda:
"No module named cv2", torch, 'invokeai', 'transformers', 'taming', etc#
There are several causes of these errors:
-
Did you remember to
conda activate invokeai? If your terminal prompt begins with "(invokeai)" then you activated it. If it begins with "(base)" or something else you haven't. -
You might've run
./scripts/configure_invokeai.pyor./scripts/invoke.pyinstead ofpython ./scripts/configure_invokeai.pyorpython ./scripts/invoke.py. The cause of this error is long so it's below. -
if it says you're missing taming you need to rebuild your virtual environment.
- If you have activated the invokeai virtual environment and tried rebuilding it, maybe the problem could be that I have something installed that you don't and you'll just need to manually install it. Make sure you activate the virtual environment so it installs there instead of globally.
You might also need to install Rust (I mention this again below).
How many snakes are living in your computer?#
You might have multiple Python installations on your system, in which case it's important to be explicit and consistent about which one to use for a given project. This is because virtual environments are coupled to the Python that created it (and all the associated 'system-level' modules).
When you run python or python3, your shell searches the colon-delimited
locations in the PATH environment variable (echo $PATH to see that list) in
that order - first match wins. You can ask for the location of the first
python3 found in your PATH with the which command like this:
Anything in /usr/bin is
part of the OS.
However, /usr/bin/python3 is not actually python3, but rather a stub that
offers to install Xcode (which includes python 3). If you have Xcode installed
already, /usr/bin/python3 will execute
/Library/Developer/CommandLineTools/usr/bin/python3 or
/Applications/Xcode.app/Contents/Developer/usr/bin/python3 (depending on which
Xcode you've selected with xcode-select).
Note that /usr/bin/python is an entirely different python - specifically,
python 2. Note: starting in macOS 12.3, /usr/bin/python no longer exists.
If you installed python3 with Homebrew and you've modified your path to search for Homebrew binaries before system ones, you'll see the above path.
If you have Anaconda installed, you will see the above path. There is a
/opt/anaconda3/bin/python3 also.
We expect that /opt/anaconda3/bin/python and /opt/anaconda3/bin/python3
should actually be the same python, which you can verify by comparing the
output of python3 -V and python -V.
The above is what you'll see if you have miniforge and correctly activated the invokeai environment, while usingd the standalone setup instructions above.
If you otherwise installed via pyenv, you will get this result:
It's all a mess and you should know how to modify the path environment variable if you want to fix it. Here's a brief hint of the most common ways you can modify it (don't really have the time to explain it all here).
- ~/.zshrc
- ~/.bash_profile
- ~/.bashrc
- /etc/paths.d
- /etc/path
Which one you use will depend on what you have installed, except putting a file in /etc/paths.d - which also is the way I prefer to do.
Finally, to answer the question posed by this section's title, it may help to
list all of the python / python3 things found in $PATH instead of just the
first hit. To do so, add the -a switch to which:
This will show a list of all binaries which are actually available in your PATH.
Debugging?#
Tired of waiting for your renders to finish before you can see if it works? Reduce the steps! The image quality will be horrible but at least you'll get quick feedback.
OSError: Can't load tokenizer for 'openai/clip-vit-large-patch14'#
"The operator [name] is not current implemented for the MPS device." (sic)#
example error
... NotImplementedError: The operator 'aten::_index_put_impl_' is not current
implemented for the MPS device. If you want this op to be added in priority
during the prototype phase of this feature, please comment on
https://github.com/pytorch/pytorch/issues/77764.
As a temporary fix, you can set the environment variable
`PYTORCH_ENABLE_MPS_FALLBACK=1` to use the CPU as a fallback for this op.
WARNING: this will be slower than running natively on MPS.
The InvokeAI version includes this fix in environment-mac.yml.
"Could not build wheels for tokenizers"#
I have not seen this error because I had Rust installed on my computer before I started playing with Stable Diffusion. The fix is to install Rust.
How come --seed doesn't work?#
Information
Completely reproducible results are not guaranteed across PyTorch releases, individual commits, or different platforms. Furthermore, results may not be reproducible between CPU and GPU executions, even when using identical seeds.
Second, we might have a fix that at least gets a consistent seed sort of. We're still working on it.
libiomp5.dylib error?#
You are likely using an Intel package by mistake. Be sure to run conda with the
environment variable CONDA_SUBDIR=osx-arm64, like so:
CONDA_SUBDIR=osx-arm64 conda install ...
This error happens with Anaconda on Macs when the Intel-only mkl is pulled in
by a dependency.
nomkl
is a metapackage designed to prevent this, by making it impossible to install
mkl, but if your environment is already broken it may not work.
Do not use os.environ['KMP_DUPLICATE_LIB_OK']='True' or equivalents as this
masks the underlying issue of using Intel packages.
Not enough memory#
This seems to be a common problem and is probably the underlying problem for a
lot of symptoms (listed below). The fix is to lower your image size or to add
model.half() right after the model is loaded. I should probably test it out.
I've read that the reason this fixes problems is because it converts the model
from 32-bit to 16-bit and that leaves more RAM for other things. I have no idea
how that would affect the quality of the images though.
See this issue.
"Error: product of dimension sizes > 2**31'"#
This error happens with img2img, which I haven't played with too much yet. But I know it's because your image is too big or the resolution isn't a multiple of 32x32. Because the stable-diffusion model was trained on images that were 512 x 512, it's always best to use that output size (which is the default). However, if you're using that size and you get the above error, try 256 x 256 or 512 x 256 or something as the source image.
BTW, 2**31-1 = 2,147,483,647, which is also 32-bit signed LONG_MAX in C.
I just got Rickrolled! Do I have a virus?#
You don't have a virus. It's part of the project. Here's Rick and here's the code that swaps him in. It's a NSFW filter, which IMO, doesn't work very good (and we call this "computer vision", sheesh).
My images come out black#
We might have this fixed, we are still testing.
There's a similar issue
on CUDA GPU's where the images come out green. Maybe it's the same issue?
Someone in that issue says to use "--precision full", but this fork actually
disables that flag. I don't know why, someone else provided that code and I
don't know what it does. Maybe the model.half() suggestion above would fix
this issue too. I should probably test it.
"view size is not compatible with input tensor's size and stride"#
File "/opt/anaconda3/envs/invokeai/lib/python3.10/site-packages/torch/nn/functional.py", line 2511, in layer_norm
return torch.layer_norm(input, normalized_shape, weight, bias, eps, torch.backends.cudnn.enabled)
RuntimeError: view size is not compatible with input tensor's size and stride (at least one dimension spans across two contiguous subspaces). Use .reshape(...) instead.
Update to the latest version of invoke-ai/InvokeAI. We were patching pytorch but we found a file in stable-diffusion that we could change instead. This is a 32-bit vs 16-bit problem.
The processor must support the Intel bla bla bla#
What? Intel? On an Apple Silicon?
Intel MKL FATAL ERROR: This system does not meet the minimum requirements for use of the Intel(R) Math Kernel Library. The processor must support the Intel(R) Supplemental Streaming SIMD Extensions 3 (Intel(R) SSSE3) instructions. The processor must support the Intel(R) Streaming SIMD Extensions 4.2 (Intel(R) SSE4.2) instructions. The processor must support the Intel(R) Advanced Vector Extensions (Intel(R) AVX) instructions.
This is due to the Intel mkl package getting picked up when you try to install
something that depends on it-- Rosetta can translate some Intel instructions but
not the specialized ones here. To avoid this, make sure to use the environment
variable CONDA_SUBDIR=osx-arm64, which restricts the Conda environment to only
use ARM packages, and use nomkl as described above.
input types 'tensor<2x1280xf32>' and 'tensor<*xf16>' are not broadcast compatible#
May appear when just starting to generate, e.g.:
invoke> clouds
Generating: 0%| | 0/1 [00:00<?, ?it/s]/Users/[...]/dev/stable-diffusion/ldm/modules/embedding_manager.py:152: UserWarning: The operator 'aten::nonzero' is not currently supported on the MPS backend and will fall back to run on the CPU. This may have performance implications. (Triggered internally at /Users/runner/work/_temp/anaconda/conda-bld/pytorch_1662016319283/work/aten/src/ATen/mps/MPSFallback.mm:11.)
placeholder_idx = torch.where(
loc("mps_add"("(mpsFileLoc): /AppleInternal/Library/BuildRoots/20d6c351-ee94-11ec-bcaf-7247572f23b4/Library/Caches/com.apple.xbs/Sources/MetalPerformanceShadersGraph/mpsgraph/MetalPerformanceShadersGraph/Core/Files/MPSGraphUtilities.mm":219:0)): error: input types 'tensor<2x1280xf32>' and 'tensor<*xf16>' are not broadcast compatible
LLVM ERROR: Failed to infer result type(s).
Abort trap: 6
/Users/[...]/opt/anaconda3/envs/invokeai/lib/python3.9/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 1 leaked semaphore objects to clean up at shutdown
warnings.warn('resource_tracker: There appear to be %d '
Created: August 31, 2022