-
Notifications
You must be signed in to change notification settings - Fork 12
About supported resolution. #24
Comments
Yes the module can provide maximum output shape. Input names are available, and maximum input shape is exported from the module but the code for maximum input shape is not present in the interface, I can add this if required Get outputs with:
|
Is it correct that the size is limited to multiples of 64, ranging from a minimum of 64 to a specific maximum size? |
Current modules support 8px increment. |
Size reported by module for unet is in latent size, so multiply or divide by 8 if you're working with pixel size. |
Based on a quick test, it appears that pixel size of the image doesn't need to be a concern. Since it gets truncated to a multiple of 8 when converted to latent, I don't need to worry about it. |
Should the size of the manageable max resolution in the module be obtained from the name? Anyway, if AITemplateLoader pass the |
Yes The AITemplateLoader does not actually load the module, it only signals to sampler that it should use AIT, loading unet modules happens in sample and module is selected based on sizes etc Could you share more details of your use case? Maybe you can just detect the module to use from within your node |
In the detailer, a specific part of the image is upscaled and then encoded using VAE for KSample. If the upscale size exceeds a certain limit, an error occurs. I'm trying to impose an additional restriction here in the form of a maximum resolution. When the model is passed to the Detailer and resolution constraints are enforced by the model, having the maximum resolution information somewhere within the model would allow me to utilize this information. |
This plugin overrides If you could share any links to relevant code sections, details on how you're integrating, etc and with regards to |
When I tried just simple T2I with 1024x1024 on SD1.5 model. The generation is failed. This issue will break Detailer's behavior. |
Could you please share any relevant code sections where you are attempting to integrate, and any errors you are receiving? |
I thought this error is normal behavior. Since 1024x1024 caused an error in SD1.5, and there were no issues even with 2048x2048 in SDXL, I was searching for a basis on which to establish the max resolution setting.
|
I am currently trying to incorporate size restrictions here. |
There will be some additional error message above the traceback. The maximum you should set there would be 4096, at this is the largest module supported currently. Other than that, you should not need to set restrictions based on loaded module, because module selection is automatic, and AITemplateLoader does not pass the module itself, only a flag that AITemplate should be used. vae encode here can use code from AIT vae encode, then module selection is automatic |
So, if setting a resolution exceeding 768 results in KSample failure, that wouldn't be considered a normal situation, right?
|
Thank you for providing the error message, it is important to provide all error messages to assist in diagnosing the issue. linux/sm80/bs1/768/unet_v1_768.so.xz had the same sha256 as 1024, this resulted in 768 being selected instead of 1024. |
Oh... There was an issue with module selection due to hash collisions. I misunderstood that error as a limitation of the AIT approach. Thx. |
Ensure you delete the current file otherwise the correct module will not download. |
Oh.. should I delete that file? |
It works well :) |
I'm contemplating how to support AIT in the Detailer node, and it seems quite challenging to apply in a different way.
So, when the model passed to the Detailer is an AIT model, I intend to approach it by restricting the upscale factor to the resolution supported by AIT.
To achieve this, I need to determine the supported resolutions from the model passed to the Detailer. Is it possible for the model to provide such information?
The text was updated successfully, but these errors were encountered: