InvokeAI icon indicating copy to clipboard operation
InvokeAI copied to clipboard

[bug]: can't import new models

Open 2refocus opened this issue 3 years ago • 4 comments

Is there an existing issue for this?

  • [X] I have searched the existing issues

OS

macOS

GPU

cuda

VRAM

32

What happened?

Importing new models didn't work. It didn't found the path. The model is in the right folder. InvokeAi is started using the CLI.

(I also tried with the complete path with the same result)

from my terminal:

invoke> !import_model models/ldm/stable-diffusion-v1/robo-diffusion-v1.ckpt ** models/ldm/stable-diffusion-v1/robo-diffusion-v1.ckpt: file not found

invoke> !import_model /Users/xxx/invokeai/models/ldm/stable-diffusion-v1/robo-diffusion-v1.ckpt ** /Users/xxx/invokeai/models/ldm/stable-diffusion-v1/robo-diffusion-v1.ckpt: file not found

Screenshots

No response

Additional context

No response

Contact Details

No response

2refocus avatar Dec 08 '22 16:12 2refocus

The first thing to double check is whether the file is actually there. In a terminal: ls -l /Users/xxx/invokeai/models/ldm/stable-diffusion-v1/ and see if the robo file appears in the listing

nelsonre avatar Dec 09 '22 15:12 nelsonre

Same problem....

bach777 avatar Dec 09 '22 15:12 bach777

The first thing to double check is whether the file is actually there.

In a terminal:

ls -l /Users/xxx/invokeai/models/ldm/stable-diffusion-v1/

and see if the robo file appears in the listing

That's what i already said. It is there. I used a lot of different models in automatic 111 and stable diffusion without any problems. So there must be a different path / config / import problem.

Thanks for taking time.

2refocus avatar Dec 09 '22 19:12 2refocus

No worries. I was suggesting checking the directory because I also had a similar (file not found) issue. I just had the wrong path. I had mixed up models/ldm with ldm/models. But that doesn't sound like it was your issue.

nelsonre avatar Dec 09 '22 21:12 nelsonre

There has been no activity in this issue for 14 days. If this issue is still being experienced, please reply with an updated confirmation that the issue is still being experienced with the latest release.

github-actions[bot] avatar Mar 16 '23 06:03 github-actions[bot]