Brian Fitzgerald commited on
Commit
9ed59eb
1 Parent(s): 488bcbe

Update README

Browse files
Files changed (1) hide show
  1. README.md +18 -19
README.md CHANGED
@@ -48,15 +48,22 @@ Please note: This model is released under the [Stability Community License](http
48
 
49
  ### License
50
 
51
- - **Community License:** Free for research, non-commercial, and commercial use for organizations or individuals with less than $1M in total annual revenue. More details can be found in the [Community License Agreement](https://stability.ai/community-license-agreement). Read more at https://stability.ai/license.
52
- - **For individuals and organizations with annual revenue above $1M**: please [contact us](https://stability.ai/enterprise) to get an Enterprise License.
 
 
 
 
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
  ```
@@ -97,42 +104,34 @@ blurred_image = gaussian_blur(image)
97
  ```
98
 
99
  ### Tips
100
- - Euler sampler and a slightly higher step count (50-60) gives best results.
 
101
  - 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.
102
 
103
  ## Uses
104
 
105
- ### Intended Uses
106
 
107
- Intended uses include the following:
108
- * Generation of artworks and use in design and other artistic processes.
109
- * Applications in educational or creative tools.
110
- * Research on generative models, including understanding the limitations of generative models.
111
 
112
- All uses of the model must be in accordance with our [Acceptable Use Policy](https://stability.ai/use-policy).
113
 
114
  ### Training Data and Strategy
115
 
116
  These models were trained on a wide variety of data, including synthetic data and filtered publicly available data.
117
- The data used is a subset of the Stable Diffusion 3.5 post-training dataset, and satisfies the same legal and safety requirements.
118
-
119
- ### Out-of-Scope Uses
120
-
121
- 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.
122
 
123
  ## Safety
124
 
125
- As part of our safety-by-design and responsible AI deployment approach, we take deliberate measures to ensure Integrity starts at the early stages of development. We implement safety measures throughout the development of our models. We have implemented safety mitigations that are intended to reduce the risk of certain harms, however we recommend that developers conduct their own testing and apply additional mitigations based on their specific use cases.
126
- For more about our approach to Safety, please visit our [Safety page](https://stability.ai/safety).
127
 
128
  ### Integrity Evaluation
129
 
130
- 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.
131
 
132
  ### Risks identified and mitigations:
133
 
134
- * 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.
135
- * 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](https://stability.ai/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.
136
  * Privacy violations: Developers and deployers are encouraged to adhere to privacy regulations with techniques that respect data privacy.
137
 
138
  ### 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
  ```
 
104
  ```
105
 
106
  ### Tips
107
+ - We recommend starting with a ControlNet strength of 0.9, and adjusting as needed.
108
+ - Euler sampler and a slightly higher step count (50-60) gives best results, especially with Canny.
109
  - 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.
110
 
111
  ## Uses
112
 
113
+ All uses of the model must be in accordance with our [Acceptable Use Policy](https://stability.ai/use-policy).
114
 
115
+ ### Out-of-Scope Uses
 
 
 
116
 
117
+ 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.
118
 
119
  ### Training Data and Strategy
120
 
121
  These models were trained on a wide variety of data, including synthetic data and filtered publicly available data.
 
 
 
 
 
122
 
123
  ## Safety
124
 
125
+ 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).
 
126
 
127
  ### Integrity Evaluation
128
 
129
+ 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.
130
 
131
  ### Risks identified and mitigations:
132
 
133
+ * 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.
134
+ * 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.
135
  * Privacy violations: Developers and deployers are encouraged to adhere to privacy regulations with techniques that respect data privacy.
136
 
137
  ### Acknowledgements