Brian Fitzgerald
commited on
Commit
•
8e606aa
1
Parent(s):
52c94ed
Update README
Browse files
README.md
CHANGED
@@ -48,15 +48,22 @@ Please note: This model is released under the [Stability Community License](http
|
|
48 |
|
49 |
### License
|
50 |
|
51 |
-
|
52 |
-
-
|
|
|
|
|
|
|
|
|
53 |
|
54 |
## Usage
|
55 |
|
56 |
For now, we recommend using the [standalone SD3.5 repo](https://github.com/Stability-AI/sd3.5) to use the ControlNets.
|
57 |
|
|
|
|
|
58 |
A full technical report on Stable Diffusion 3.5, with details on the ControlNet training, will be released soon as well.
|
59 |
|
|
|
60 |
### Using Controlnets in SD3.5 Standalone Repo
|
61 |
Install the repo:
|
62 |
```
|
@@ -106,42 +113,34 @@ img = F.interpolate(img, (h, w), mode='bilinear', align_corners=False)
|
|
106 |
```
|
107 |
|
108 |
### Tips
|
109 |
-
-
|
|
|
110 |
- Pass `--text_encoder_device <device_name>` to load the text encoders directly to VRAM, which can speed up the full inference loop at the cost of extra VRAM usage.
|
111 |
|
112 |
## Uses
|
113 |
|
114 |
-
|
115 |
|
116 |
-
|
117 |
-
* Generation of artworks and use in design and other artistic processes.
|
118 |
-
* Applications in educational or creative tools.
|
119 |
-
* Research on generative models, including understanding the limitations of generative models.
|
120 |
|
121 |
-
|
122 |
|
123 |
### Training Data and Strategy
|
124 |
|
125 |
These models were trained on a wide variety of data, including synthetic data and filtered publicly available data.
|
126 |
-
The data used is a subset of the Stable Diffusion 3.5 post-training dataset, and satisfies the same legal and safety requirements.
|
127 |
-
|
128 |
-
### Out-of-Scope Uses
|
129 |
-
|
130 |
-
The model was not trained to be factual or true representations of people or events. As such, using the model to generate such content is out-of-scope of the abilities of this model.
|
131 |
|
132 |
## Safety
|
133 |
|
134 |
-
|
135 |
-
For more about our approach to Safety, please visit our [Safety page](https://stability.ai/safety).
|
136 |
|
137 |
### Integrity Evaluation
|
138 |
|
139 |
-
Our integrity evaluation methods include structured evaluations and red-teaming testing for certain harms.
|
140 |
|
141 |
### Risks identified and mitigations:
|
142 |
|
143 |
-
* Harmful content:
|
144 |
-
* Misuse: Technical limitations and developer and end-user education can help mitigate against malicious applications of models. All users are required to adhere to our
|
145 |
* Privacy violations: Developers and deployers are encouraged to adhere to privacy regulations with techniques that respect data privacy.
|
146 |
|
147 |
### Acknowledgements
|
|
|
48 |
|
49 |
### License
|
50 |
|
51 |
+
Here are the key components of the license:
|
52 |
+
* Free for non-commercial use: Individuals and organizations can use the model free of charge for non-commercial use, including scientific research.
|
53 |
+
* Free for commercial use (up to $1M in annual revenue): Startups, small to medium-sized businesses, and creators can use the model for commercial purposes at no cost, as long as their total annual revenue is less than $1M.
|
54 |
+
* Ownership of outputs: Retain ownership of the media generated without restrictive licensing implications.
|
55 |
+
|
56 |
+
For organizations with annual revenue more than $1M, please contact us [here](https://stability.ai/enterprise) to inquire about an Enterprise License.
|
57 |
|
58 |
## Usage
|
59 |
|
60 |
For now, we recommend using the [standalone SD3.5 repo](https://github.com/Stability-AI/sd3.5) to use the ControlNets.
|
61 |
|
62 |
+
**Support in [ComfyUI](https://github.com/comfyanonymous/ComfyUI) and [🧨 Diffusers](https://github.com/huggingface/diffusers) is planned, and will be available very soon.**
|
63 |
+
|
64 |
A full technical report on Stable Diffusion 3.5, with details on the ControlNet training, will be released soon as well.
|
65 |
|
66 |
+
|
67 |
### Using Controlnets in SD3.5 Standalone Repo
|
68 |
Install the repo:
|
69 |
```
|
|
|
113 |
```
|
114 |
|
115 |
### Tips
|
116 |
+
- We recommend starting with a ControlNet strength of 0.7, and adjusting as needed.
|
117 |
+
- Euler sampler and a slightly higher step count (50-60) gives best results.
|
118 |
- Pass `--text_encoder_device <device_name>` to load the text encoders directly to VRAM, which can speed up the full inference loop at the cost of extra VRAM usage.
|
119 |
|
120 |
## Uses
|
121 |
|
122 |
+
All uses of the model must be in accordance with our [Acceptable Use Policy](https://stability.ai/use-policy).
|
123 |
|
124 |
+
### Out-of-Scope Uses
|
|
|
|
|
|
|
125 |
|
126 |
+
The model was not trained to be factual or true representations of people or events. As such, using the model to generate such content is out-of-scope of the abilities of this model.
|
127 |
|
128 |
### Training Data and Strategy
|
129 |
|
130 |
These models were trained on a wide variety of data, including synthetic data and filtered publicly available data.
|
|
|
|
|
|
|
|
|
|
|
131 |
|
132 |
## Safety
|
133 |
|
134 |
+
We believe in safe, responsible AI practices and take deliberate measures to ensure Integrity starts at the early stages of development. This means we have taken and continue to take reasonable steps to prevent the misuse of Stable Diffusion 3.5 by bad actors. For more information about our approach to Safety please visit our [Safety page](https://stability.ai/safety).
|
|
|
135 |
|
136 |
### Integrity Evaluation
|
137 |
|
138 |
+
Our integrity evaluation methods include structured evaluations and red-teaming testing for certain harms. Testing was conducted primarily in English and may not cover all possible harms.
|
139 |
|
140 |
### Risks identified and mitigations:
|
141 |
|
142 |
+
* Harmful content: We have used filtered data sets when training our models and implemented safeguards that attempt to strike the right balance between usefulness and preventing harm. However, this does not guarantee that all possible harmful content has been removed. All developers and deployers should exercise caution and implement content safety guardrails based on their specific product policies and application use cases.
|
143 |
+
* Misuse: Technical limitations and developer and end-user education can help mitigate against malicious applications of models. All users are required to adhere to our Acceptable Use Policy, including when applying fine-tuning and prompt engineering mechanisms. Please reference the Stability AI Acceptable Use Policy for information on violative uses of our products.
|
144 |
* Privacy violations: Developers and deployers are encouraged to adhere to privacy regulations with techniques that respect data privacy.
|
145 |
|
146 |
### Acknowledgements
|