今さら聞けないStable Diffusion webUI AUTOMATIC1111の更新方法【Stable Diffusion】
TLDRAutomatic1111のStable Diffusion WebUIの更新方法について解説。既存のバージョンを維持しつつ新しいバージョンを別にインストールする方法と、現在使用中のバージョンにドラッグ＆ドロップでアップデートする方法の2つ存在。git cloneコマンドとgit pullコマンドを使用し、前者は環境を維持しながら新しいものを構築し、后者は既存の環境に追加する。アップデートにはリスクがあるため、エラーを自分で対処できる人向け。また、事前にバックアップをとることが重要。
Takeaways
- 🔄 今回はStable DiffusionのWeb UI Automatic1111の更新方法について解説します。
- 📦 更新には2つの方法があります：既存のバージョンを維持して新しいものを別にインストールする方法と、現在使っているバージョンにドラッグ&ドロップで更新する方法。
- 🛠️ git cloneメソッドは環境を維持しながら新しいものを構築する方法で、比較的安全で信頼性が高いです。
- 📂 更新前には、既存のWeb UIを起動し、インストールしているエクステンション機能のURLをコピーしてメモを取る必要があります。
- 🔄 git pullコマンドは、既存の環境に加えて新しい環境を構築する方法で、モデルやROLAsを移動する必要がありません。
- ⚠️ git pullメソッドでは、環境に依存するエラーが発生する可能性があり、自分でエラーを解決できる方が良いです。
- 🔙 git resetコマンドを使用することで、過去のバージョンに戻ることができますが、手動で変更した設定（例えばdot badge）は初期化されます。
- 📊 git reflogを用いて、Web UIの変更履歴を確認することができます。
- 🎉 プレリリースバージョン（1.4rcなど）を利用するには、メインブランチではなく、特定のブランチを指定してgit cloneを実行する必要があります。
- 💡 更新は、エクステンション機能が最新のものに合わせられるため、本体も更新することが望ましいです。
Q & A
What is the main topic of the video?
-The main topic of the video is about updating the Stable Diffusion Web UI Automatic1111.
Why is it necessary to update the Automatic1111?
-Updating the Automatic1111 is necessary because using an old version can lead to errors, and the web UI functions are updated according to the main body, requiring regular updates for both.
What are the two ways to update the Stable Diffusion Web UI Automatic1111 mentioned in the video?
-The two ways to update the Stable Diffusion Web UI Automatic1111 are: 1) maintaining the existing version and installing a new one separately, and 2) performing a drag and drop update to overwrite the current version.
What is the advantage of using the git clone method for updating?
-The advantage of using the git clone method is that it is a stable and reliable way to update, as it does not affect the existing environment and allows you to continue using the old version if the new one does not work.
How does one proceed with the git clone method for updating Automatic1111?
-To proceed with the git clone method, one should launch the web UI, copy the URL of the extension function, and paste it into a notebook. Then, create a new folder, open the command prompt, and use the git clone command from the Automatic1111 GitHub page. After copying, launch the .bat file to check the operation.
What are the potential drawbacks of using the git pull method for updating?
-Using the git pull method can potentially cause errors that may prevent the startup of the web UI, and it might generate so-called Omakan errors depending on the environment. This method is recommended for users who can handle errors by themselves.
How can one avoid moving models and ROLAs when updating with git pull?
-To avoid moving models and ROLAs when updating with git pull, one can make use of the .bat argument. By referring to the GitHub wiki of Automatic1111, one can set up arguments to call models and ROLAs from other folders, making the update process easier.
What is the process for reverting to a previous version using the commit hash?
-To revert to a previous version using the commit hash, one should start the command prompt in the install folder, use the git log to hide the commit hash of the current version, then use git reset --hard followed by the hash value to return to the designated version. Finally, apply the changes with git stash apply.
How can one check the change history of the web UI?
-To check the change history of the web UI, one can enter git reflog in the command prompt while in the install folder. This will display the history of changes made to the web UI.
What is a pre-release version and how can one access it?
-A pre-release version is a version that is not yet officially implemented and is intended for enthusiastic researchers. To access it, one needs to specify the branch from the GitHub release notes, copy the URL, and use git clone with the branch repository argument to clone the version from the Release Candidate branch.
What is the recommendation for updating the main body and expansion functions?
-The video recommends updating the main body and expansion functions according to the latest version, as the expansion function will be updated accordingly. It suggests weighing the cost of moving and the risk of error to decide whether to use git clone or git pull for the update.
Outlines
🚀 Introduction to Updating the Automatic1111
The paragraph introduces the issue of an outdated extension and the necessity of updating it. It discusses the two primary methods for updating the Stable Diffusion Web UI Automatic1111: cloning a new version alongside the existing one or overwriting the current version with a git pull command. The speaker explains the advantages and drawbacks of each method, highlighting the importance of regular updates to maintain functionality and the potential issues that may arise from using outdated versions. The speaker then provides a step-by-step guide on how to perform the git clone method, emphasizing its reliability and the ability to maintain the current environment while testing the updated version. The process includes copying the extension URL for later use, launching the command prompt, and using the git clone command from Automatic1111's GitHub repository. The speaker also touches on the use of .bat arguments for a smoother transition and the importance of reviewing and managing unused models and extension functions.
🛠️ Updating with GitPull and Version Management
This paragraph delves into the second method of updating the Automatic1111, which is using the git pull command. The speaker explains that this method leverages Git's version management capabilities to update the local environment while preserving the existing models and ROLAs. The process involves navigating to the installation folder and using git log to identify the current commit hash, which is crucial for reverting to previous versions if needed. The speaker then demonstrates how to execute the git pull command to update to the latest version and verify the update's success by checking the version information on the web UI and command prompt. The paragraph also addresses potential issues that may arise from updating, such as incompatibilities with updated libraries and the risk of encountering errors. The speaker advises weighing the costs and risks of updating before proceeding and shares personal experience with the git clone method for its reliability. The paragraph concludes with instructions on how to revert to a previous version using git reset and git stash, as well as how to review the change history with git reflog and introduce a pre-release version by specifying the branch during cloning.
🔄 Exploring Pre-Release Versions and Final Thoughts
The final paragraph discusses the availability of pre-release versions, such as the 1.4rc version mentioned in the script. These versions are not yet officially implemented and are intended for enthusiastic researchers who are willing to troubleshoot potential issues. The speaker explains that to access these pre-release versions, one must specify the branch from which they are derived, as they do not reside on the main branch. The process involves copying the URL of Automatic1111, identifying the commit hash of the pre-release version, and cloning the repository while specifying the Release Candidate branch. The speaker warns that pre-release versions are not for everyone and should be used only by those familiar with troubleshooting and discussion. The paragraph wraps up with a reminder that updating the main body and expansion functions is essential to keep up with the latest developments and a farewell to the viewers, expressing gratitude for their attention.
Mindmap
Keywords
💡Stable Diffusion
💡Web UI AUTOMATIC1111
💡更新方法
💡git clone
💡git pull
💡エクステンション
💡バージョン管理
💡模型
💡ローラ（ROLA）
💡GitHub
💡Pre-release version
Highlights
Introduction to updating the Stable Diffusion Web UI Automatic1111
Two methods of updating: maintaining the current version and installing a new one, or overwriting the current version with drag and drop updates
The importance of regular updates for both the main body and screen function of the UI
Detailed explanation of the git clone method for a stable and reliable update
How to copy the URL of the extension function and paste it into a notebook for easier reset later
Instructions on building the latest version alongside the existing version without affecting the old system
The process of transferring manually installed files like VAE and learning files to the new version
Using .bat arguments to avoid moving models and ROLAs for an easier update
Explanation of the git pull command for updating the current environment without needing to move models and ROLAs
Risks associated with git pull, such as potential errors and loss of image generation environment
How to confirm the change history and version updates using git log and git reflog
The process of rewinding to a past version using commit hash values with git reset
Introduction to pre-release versions and how to access and use them
The concept of branching on GitHub and how to use it to access pre-release versions not on the main branch
Weighing the cost of moving and the risk of error to decide between cloning or pulling for updates
The author's preference for building a new environment with git clone for each video to ensure stability and reliability
Final advice on updating the main body and expansion function according to the latest version for optimal use