disco-diffusion-1
disco-diffusion-1 copied to clipboard
entmike
``` cd docker docker build -t disco-diffusion . Sending build context to Docker daemon 19.97kB Step 1/39 : ARG base_image Step 2/39 : FROM ${base_image} as base base name (${base_image})...
- Installed via `docker pull entmike/disco-diffusion-1` - When running test job ``` docker run --rm -it \ -v $(echo ~)/disco-diffusion/images_out:/workspace/code/images_out \ -v $(echo ~)/disco-diffusion/init_images:/workspace/code/init_images \ -v $(echo ~)/disco-diffusion/models:/workspace/disco-diffusion-1/models \ -v...
it just runs `python disco.py` instead
when i change the prompt of my disco diffusion 4. Diffuse! jusy jump out this infomation ``` Starting Run: TimeToDisco(3) at frame 0 Prepping model... --------------------------------------------------------------------------- EOFError Traceback (most recent...
I'm trying to use this actually on replicate.com https://replicate.com/nightmareai/disco-diffusion but I get the zeroth frame which is just perlin noise, and then for follow on images, nothing. Is it safe...
``` def createVideo(args): .... image_path = f"{args.batchFolder}/({run})_%04d.png" ``` changing to ``` image_path = f"{args.batchFolder}/{args.batch_name}({run})_%04d.png" ``` results in correct behavior. Maybe i will fix this with a PR
Hi, so I'm not sure if the notice is relevant anymore, but I have a temporary solution for this. First, downgrade `torch`: `!pip install torch==1.11.0 --extra-index-url https://download.pytorch.org/whl/cu113` Then just install...
### Replication: ```bash python disco.py --config_file=./examples/configs/artstudy2.yml --width_height="[256, 256]" ``` ### Problem 1: The first problem that shows up immediately is that [split_prompts](https://github.com/entmike/disco-diffusion-1/blob/da528b4e5f17cc1f6fc8d3224923ea9ae5e916e5/dd.py#L983-L989) errors because it's always expecting a multi valued...
Tested using YAML version with this config: https://gist.github.com/seandearnaley/2859612e30c76ad2a13e4c9e5ec99353  UPDATE: 5/30/22: some findings, weirdly the colab YAML wasn't actually pulling down repo updates, I don't know whether this was because...
