今さら聞けないStable Diffusion webUI AUTOMATIC1111の更新方法【Stable Diffusion】
TLDR今回紹介するのは、Stable Diffusion WebUI AUTOMATIC1111の更新方法です。既存のバージョンを維持して新しいものを別にインストールする方法と、現在使っているバージョンにドラッグ＆ドロップでアップデートする方法の2つがあります。git cloneコマンドを使用する前者は安定して信頼性が高く、モデルやROLAsを移動することなく、新しい環境を構築することができます。一方、git pullコマンドを使用する後者は、環境に加えることでアップデートを行いますが、エラーが発生した場合、解決するまで画像生成環境を失うことがあります。また、事前にコミットハッシュを確認し、以降のバージョンに戻るために必要な情報を保存することが重要です。
Takeaways
- 📂 Two methods exist for updating the Stable Diffusion Web UI Automatic1111: cloning a new version alongside the old one or overwriting the current version with git pull.
- 🛠️ The git clone method is stable and reliable, preserving the existing environment while building a new one, but it resets the extension function settings.
- 🔄 When using git clone, manually transfer files like VAE and learning files, and re-enable the extension function to maintain your custom settings.
- 📋 Use the .bat file arguments to specify different model and ROLA paths, easing the transition and reducing manual moving of these files.
- ⚙️ The git pull method updates the current environment directly, which is convenient but can cause errors and requires manual troubleshooting if issues arise.
- 🔍 Before updating, record the commit hash of the current version to easily revert back if necessary.
- 🔄 Use git reset --hard with the commit hash to revert to a previous version, but be aware that manual changes will be lost.
- 📈 Understand the use of git reflog to review the change history of your web UI and to ensure the update process is as expected.
- 🎉 Pre-release versions like 1.4rc can be accessed by specifying the branch during git clone, catering to users eager to test new features.
- 🤖 Regular updates to both the main body and extension functions are essential to maintain compatibility and access to the latest features.
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 need to be updated regularly to ensure proper functioning.
What are the two methods mentioned for updating the Stable Diffusion Web UI Automatic1111?
-The two methods mentioned for updating are: 1) maintaining the existing version and installing a new one separately using the git clone command, and 2) using the git pull command to update the version you are currently using.
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 approach that does not affect the existing environment. It allows you to continue using the old version if the new one does not work, and it helps avoid potential issues with the extension function being reset.
What should you do before updating with the git pull method?
-Before updating with the git pull method, you should check the commit hash of the version you are currently using, as this will be necessary if you need to revert back to the previous version.
What is the risk associated with updating using the git pull method?
-The risk with the git pull method is that if the update causes an error and prevents startup, you could lose your image generation environment until the issue is resolved. Additionally, this method may be prone to causing so-called Omakan errors depending on the environment.
How can you avoid moving models and ROLAs when updating with git pull?
-To avoid moving models and ROLAs when using git pull, you can make use of the .bat argument options for setting up. These options allow you to call models and ROLAs from other folders, eliminating the need to move them during the update process.
What is the pre-release version mentioned in the video?
-The pre-release version mentioned in the video is 1.4rc. It is a version that is still in the testing phase and not yet officially implemented, intended for those who are enthusiastic about research and familiar with troubleshooting.
How can you check the change history of the web UI you are using?
-You can check the change history of the web UI by entering 'git reflog' in the command prompt. This will display the history of updates, resets, and other changes made to the environment.
What should you do if you want to revert back to a previous version?
-To revert back to a previous version, you can use the 'git reset --hard' command followed by the commit hash value of the version you want to return to. After resetting, you can apply your stashed changes using 'git stash apply'.
Outlines
🚀 Introduction to Updating the Automatic1111
This paragraph introduces the issue of an outdated extension and the necessity of updating it. The speaker, Robin, discusses the process of updating the Automatic1111, highlighting two methods: maintaining the current version and installing a new one separately, or overwriting the existing version with a drag and drop update. The paragraph emphasizes the importance of regular updates to ensure compatibility and functionality, and outlines the steps to update using the git clone method, which is considered stable and reliable. It also mentions the potential need to reset extension functions and the process to transfer models and ROLAs for a seamless update.
🛠️ Git Pull Update Method and Its Risks
In this paragraph, the speaker demonstrates the use of the git pull command to update the version 1.30 to 1.32 of the Automatic1111. The git pull method is described as a version management function that updates the local environment by illuminating the differences between the GitHub environment and the local environment. The speaker warns about the risks associated with this method, such as the potential loss of the image generation environment if startup errors occur. The paragraph also discusses the possibility of encountering 'Omakan' errors and suggests that this method is best suited for those who can handle errors independently. Additionally, the speaker shares personal preference for using git clone for updates due to its stability and reliability.
🔄 Advanced Techniques: Rewinding and Pre-Release Versions
This paragraph delves into more advanced update techniques, including how to rewind to a previous version using the commit hash value and how to check the change history with git reflog. The speaker explains the process of reverting from version 1.32 back to 1.30 and emphasizes the importance of saving changes locally using git stash. Furthermore, the paragraph introduces the concept of pre-release versions, such as the 1.4rc version, and explains how to access and use these versions from a branch that is not on the main branch. The speaker advises that pre-release versions should be used by those who are knowledgeable and capable of troubleshooting, as they may not be as stable and are intended for research purposes.
Mindmap
Keywords
💡Stable Diffusion
💡Web UI
💡AUTOMATIC1111
💡git clone
💡git pull
💡extension function
💡version management
💡commit hash
💡pre-release version
💡GitHub
💡branch
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 for later reset.
Instructions on building the latest version alongside the existing one.
The process of transferring manually installed files like VAE and learning files.
Using .bat arguments to avoid moving models and ROLAs for an easier update.
Explanation of the git pull command for version updates.
Advantages and risks of using git pull for updates.
How to confirm the commit hash and version update history.
Introduction to rewinding to a past version using the commit hash.
Checking the change history with git reflog.
Accessing pre-release versions not on the main branch.
Instructions for cloning the 1.4rc pre-release version.
Considerations for using pre-release versions.
Conclusion on the necessity of updating both the main body and expansion functions.
