You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi.
Let me start by saying this project is great. Using it to generate larger images using cpu after experimenting to find interesting texts with gpu (limited by RAM). So far so good.
But for some reason the files I get are always very "blocky" (the slightly burned woodgrain-ish texture permeating the image)
even after 500 or 1000 iterations. I seem to be unable to get "clear" images.
The above was generated with python generate.py -cd cpu -s 600 294 -opt Adamax -p "sea Tri-X 400 TX" -o sea_trix_Adamax.png
but neither the "Adamax" nor the "Tri-X 400 TX" nor the use of cpu is the culprit (I am using lots of permutations to find the cause)
Anyone out there with an idea ?
Regards, Gert
The text was updated successfully, but these errors were encountered:
Also unable to get clear images, all results have a characteristic blocky texture. I'm using the stock model checkpoint from the readme setup instructions. Here's an example, prompt was something like: "silhouette of a man watching sunset over mountain city." Running on 32 GB Nvidia GPU setup per instructions.
i third this. i was on a RTX A6000 was using the following command: python generate.py -p "sunset" -s 1250 1250 -o output/a_beautiful_sunset.png. i found the max resolution you can use without getting the blocky effect is 850x850
Hi.
Let me start by saying this project is great. Using it to generate larger images using cpu after experimenting to find interesting texts with gpu (limited by RAM). So far so good.
But for some reason the files I get are always very "blocky" (the slightly burned woodgrain-ish texture permeating the image)
even after 500 or 1000 iterations. I seem to be unable to get "clear" images.
The above was generated with python generate.py -cd cpu -s 600 294 -opt Adamax -p "sea Tri-X 400 TX" -o sea_trix_Adamax.png
but neither the "Adamax" nor the "Tri-X 400 TX" nor the use of cpu is the culprit (I am using lots of permutations to find the cause)
Anyone out there with an idea ?
Regards, Gert
The text was updated successfully, but these errors were encountered: