Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please support custom resolution and custom "alwayson_scripts" content #12

Open
aylz10 opened this issue Oct 24, 2023 · 2 comments
Open

Comments

@aylz10
Copy link

aylz10 commented Oct 24, 2023

I really like this project. You can use your phone to generate and process images without a PC, but you cannot customize the resolution and "alwayson_scripts" content (convenient to use other plugins, such as ADetailer)

The above content is translated using translation software

@jordenyt
Copy link
Owner

The resolution can be specified by "sdSize" parameters in custom mode JSON. If you want different aspect ratio other that 4:3 and 1:1, you can 1) create an image with your desired aspect ratio; 2) open it with this app; 3) do a txt2img on this image (with custom mode)

For the alwayson_scripts, it is a good idea and let me think about how to support it. You may also make a pull request if you figure out how to do it.

@aylz10
Copy link
Author

aylz10 commented Oct 25, 2023

Sorry, I don't know Java and I don't know how to modify the code to implement this function.But I have an idea for the alwayson_scripts, Perhaps a custom dialog box like custom mode can be designed to allow users to fill in the content themselves, and if the content is not empty, it can be inserted into alwayson_ Scripts.

for example,The API usage for ADetailer plugins is:

"alwayson_scripts": {
  "ADetailer": {
    "args": [
      {
        "ad_model": "face_yolov8n.pt"
      }
    ]
  }
}

Users can fill in

"ADetailer": {
      "args": [
        {
          "ad_model": "face_yolov8n.pt"
        }
      ]
    }

in the custom dialog box.Because new content is inserted in 'alwayson_scripts', it should not affect the original ControlNet functionality.

The above content is translated using translation software

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants