今さら聞けないStable Diffusion webUI AUTOMATIC1111の更新方法【Stable Diffusion】
TLDRStable Diffusion Web UI（AUTOMATIC1111）のアップデート方法について解説。既存のバージョンを維持しつつ新しいバージョンを別にインストールする方法と、現在使用中のバージョンにドラッグ＆ドロップでアップデートする方法の2つ存在。git cloneコマンドとgit pullコマンドを使用し、前者は環境を維持しながら新しいものを構築する方法で安定性が確保され、後者はエラーが発生しやすく、自己解決能力のある方が良い。また、アップデート時のエラー対応法や、事前にコミットハッシュを確認してバージョンを戻す方法も紹介。
Takeaways
- 🔄 The video discusses two methods for updating the Stable Diffusion Web UI Automatic1111: cloning a new version alongside the existing one or overwriting the current version with git pull.
- 💻 Cloning a new version ensures a stable and isolated environment, but requires reconfiguring extensions and resetting the state.
- 🛠️ When using git clone, it's important to copy the extension function URL for easy reset later and to transfer manually installed files like VAE and learning files.
- 📂 The git pull method updates the current environment, which is convenient but can lead to errors if the new version is incompatible with the old setup.
- 🚨 Risks of using git pull include potential 'Omakan' errors and loss of image generation environment until resolved.
- 🔙 To revert to a previous version, use the git reset command with the commit hash value obtained before updating.
- 📊 The git reflog command can be used to check the history of changes made to the web UI.
- 🔍 For those interested in the latest features, the pre-release version (1.4rc) can be accessed by specifying the Release Candidate branch.
- 🌐 To clone the pre-release version, use the branch URL and repository from the GitHub page of Automatic1111.
- 📝 It's recommended to weigh the cost of moving and the risk of error when deciding between cloning or pulling for an update.
- 🎥 The video creator suggests building a new environment with git clone for each video to ensure stability and reliability.
Q & A
What is the main topic of the video?
-The main topic of the video is how to update 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 function is 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 current environment and allows you to continue using the old version if the latest 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 GitHub of Automatic1111. After copying, launch the .bat file to check the operation.
What are the potential risks of using the git pull method for updating?
-The potential risks of using the git pull method include the possibility of encountering errors that prevent startup, and the chance of generating so-called Omakan errors depending on the environment.
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 and refer to the wiki of the GitHub of Automatic1111 for various options. This allows calling models and ROLAs from other folders, making the update process easier.
What should one do to confirm the commit hash value before updating with git pull?
-Before updating with git pull, one should enter 'git log' in the command prompt to hide the commit hash of the version currently in use. This hash value represents the current version and will be necessary for reverting to a previous version if needed.
How can one revert to a previous version using the commit hash value?
-To revert to a previous version, one should enter 'git reset --hard' followed by the commit hash value that was previously hidden. This will return the environment to the designated version. Afterward, 'git stash apply' can be used to restore any manual changes made to the environment.
What is a pre-release version and how can one access it?
-A pre-release version is a version that is still in the testing phase and not yet officially implemented. To access a pre-release version like 1.4rc, one must specify the branch 'Release Candidate' when using the git clone command and follow the steps to clone from that specific branch.
What is the main branch in GitHub and why is it important for updates?
-The main branch in GitHub is the primary branch where all the stable and official updates are merged. All the differences replicated with git clone and pulled with git pull so far have been brought from the main branch. To use a version that is not on the main branch, one needs to specify the branch when cloning or pulling.
Outlines
🔄 Introduction to Updating the Automatic1111
The paragraph introduces the process of updating the Automatic1111 extension. It begins with a conversation between two individuals discussing the issues with an outdated extension. The speaker then explains that updating is necessary due to the constant changes in the web UI and the need for regular updates to the main body. Two methods for updating are presented: one involves maintaining the current version and installing a new one separately, while the other is a drag-and-drop update over the existing version. The speaker provides a detailed guide on using the git clone command for a stable update and discusses the advantages and drawbacks of each method, including the potential for errors and the need to reset extension functions.
🚀 Updating with GitPull
This paragraph delves into the second method of updating the Automatic1111, which is using the git pull command. The speaker demonstrates how to update the current version to the latest one using Git's version management function. The process is shown to be relatively quick and straightforward, with the speaker noting the importance of recording the commit hash of the current version before updating. The speaker also cautions about the potential for errors when updating from older versions, especially if there are significant changes in library dependencies. The paragraph concludes with advice on weighing the risks and costs of updating, and the speaker shares their personal preference for using git clone for each new video to ensure stability.
🌐 Exploring Pre-Release Versions and Advanced Git Techniques
The final paragraph discusses the availability of pre-release versions of Automatic1111 for enthusiastic researchers. It explains that these versions are not on the main branch and require specifying the branch when cloning. The speaker guides the audience through the process of accessing and cloning a pre-release version, known as 1.4rc, from the Release Candidate branch. The paragraph also covers advanced Git techniques, such as using git reflog to check the change history and git stash to save local changes. The speaker advises that pre-release versions should be used with caution and are best suited for those familiar with troubleshooting and discussion within the community.
Mindmap
Keywords
💡Stable Diffusion
💡Web UI
💡Automatic1111
💡git clone
💡git pull
💡エクステンション
💡アップデート
💡GitHub
💡コミットハッシュ
💡ブランチ
💡プレリリースバージョン
Highlights
介绍了Stable Diffusion Web UI Automatic1111的更新方法。
更新Automatic1111有两种方法：克隆新版本或拉取现有版本进行更新。
克隆新版本可以避免旧系统无法访问新版本时的问题。
克隆新版本时，扩展功能将从1开始重置。
通过使用git clone命令来克隆新版本。
使用git pull命令可以更新现有版本，但可能会遇到错误。
使用git pull更新时，不需要移动模型和ROLAs。
更新时可能会遇到所谓的Omakan错误，这取决于环境。
使用commit hash值可以回退到旧版本。
使用git reflog可以查看变更历史。
介绍了如何使用git stash来保存本地环境的更改。
介绍了如何引入预发布版本。
预发布版本可能不适合所有人，只推荐给熟悉它的人使用。
在更新前应权衡迁移成本和错误风险。
介绍了如何通过.bat文件参数调用其他文件夹中的模型和ROLAs。
在更新到新版本时，可能会更新Torch和Gladio等库。
如果从较旧版本更新，可能会遇到各种错误。
介绍了如何检查Web UI的版本信息。
介绍了如何使用git clone和git pull来复制和更新版本。