mrq
-
https://git.ecker.tech/ aims to provide a place to share my efforts while maintaining true ownership of my code, as I do not trust GitHub.
XMR: 4B9TQdkAkBFYrbj5ztvTx89e5LpucPeTSPzemCihdDi9EBnx7btn8RDNZTBz2zihWsjMnDkzn5As1LU6gLv3KQy8BLsZ8SG
- Joined on
2022-10-10
Block a user
5c876b81f3
Added small optimization with caching latents, dropped Anaconda for just a py3.9 + pip + venv setup, added helper install scripts for such, cleaned up app.py, added flag '--low-vram' to disable minor optimizations
Solving environment: failed with initial frozen solve.
I got a working setup with just Python 3.9 and pip in commit 0d8211e450044aaf240a15a33b65c7b940ced7f5 and updated the setup.bat to reflect it. I suppose it's not a true fix to the issue, but it…
0d8211e450
Added small optimization with caching latents, dropped Anaconda for just a py3.9 + pip + venv setup, added helper install scripts for such, cleaned up app.py
e8087e1c6b
Added small optimization with caching latents, dropped Anaconda for just a py3.9 + pip + venv setup, added helper install scripts for such, cleaned up app.py
Running out of memory despite being able to run the other gardio version?
Reverted the patch in commit 8f20afc18f8fe3be36daee99be591d302d54ac1f for now. I'll try and see about cramming in a way to toggle between using those optimizations or not. It should be easy.
Running out of memory despite being able to run the other gardio version?
Rats. I suppose that's why it wasn't merged in the original repo. Some anon(s) mentioned a small performance…
ea751d7b6c
forgot to copy the alleged slight performance improvement patch, added detailed progress information with passing gr.Progress, save a little more info with output
43f45274dd
Cleaned up the good-morning-sirs-dialect labels, fixed seed=0 not being a random seed, show seed on output
06183b494e
add extending settings to json, provided examples, so no more having to discard changes when pulling