AUTOMATIC1111
[Bug]: macOs open local env using --nowebui mode, the request of txt2img api return base64 str,production of image is wrong in confusion。。。
Is there an existing issue for this?
- [X] I have searched the existing issues and checked the recent builds/commits
What happened?
- stable diffusion open api mode :python launch.py --nowebui --skip-torch-cuda-test --no-half
- http post request:txt2img
- stable diffusion return result base64 str arr,i got this result to parse image ,but image is out of expect, like above pic... production of image result is wrong...i also print the res on python source code ,the base64 format string output of this api make me suck...is it my mac config is wrong,but on the webui mode anything is ok ^/^
Steps to reproduce the problem
- stable diffusion open api mode :python launch.py --nowebui --skip-torch-cuda-test --no-half
- http post request:/txt2img
- stable diffusion return result base64 str arr,i got this result to parse image ,but image is out of expect, like above pic...
What should have happened?
production of image result is wrong...i also print the res on python source code ,the base64 format string output of this api make me suck...
Commit where the problem happens
master
What platforms do you use to access the UI ?
No response
What browsers do you use to access the UI ?
No response
Command Line Arguments
python launch.py --nowebui --skip-torch-cuda-test --no-half
post req
List of extensions
No
Console logs
no
Additional information
No response
Happening here as well. Have found only a couple of other references to the problem. Something new?
i have same problem
just try this command with args: python launch.py --nowebui --skip-torch-cuda-test --upcast-sampling --no-half-vae --use-cpu interrogate fix my problem
That didn't resolve it.
I did have the problem that I was not using python 3.10, however starting over with python 3.10.11 has the same problem.
That didn't resolve it.
I did have the problem that I was not using python 3.10, however starting over with python 3.10.11 has the same problem.
my running python version is 3.10.6