Phr00t commited on
Commit
833297d
·
verified ·
1 Parent(s): c2ce1ba

Update Custom-Advanced-VACE-Node/README.md

Browse files
Custom-Advanced-VACE-Node/README.md CHANGED
@@ -13,6 +13,6 @@ It adds two new parameters to the node: "control_strength" and "control_ease".
13
  **control_ease**: How many frames to "ease in" the control_images motion? Starting too quickly can cause a strange early jump to try and match the motion to your start image. This is to give more time for your start frame to line up with the control_images motion. If your starting frame is very close to the motion start, try low values (like 8). If you have a very different motion from your starting frame, go with 24 to 48.
14
 
15
 
16
- Replacing this file could break your WanVideoWrapper with future updates. It might be smarter to just replace the 'class WanVideoVACEStartToEndFrame:' code with this one.
17
 
18
  I should probably have a fork and offer a pull request for this, but for now, I'm just providing the file if you want to use it. If Kijai or anyone wants to bring this over if y'all find it useful, it is much appreciated.
 
13
  **control_ease**: How many frames to "ease in" the control_images motion? Starting too quickly can cause a strange early jump to try and match the motion to your start image. This is to give more time for your start frame to line up with the control_images motion. If your starting frame is very close to the motion start, try low values (like 8). If you have a very different motion from your starting frame, go with 24 to 48.
14
 
15
 
16
+ **Replacing this file could break your WanVideoWrapper with future WanVideoWrapper updates**. It may be more compatible just replacing the 'class WanVideoVACEStartToEndFrame:' code with the class code from my file.
17
 
18
  I should probably have a fork and offer a pull request for this, but for now, I'm just providing the file if you want to use it. If Kijai or anyone wants to bring this over if y'all find it useful, it is much appreciated.