[bug]: Could not read metadata

[apfelnymous]

Is there an existing issue for this?

• [X] I have searched the existing issues

OS

Linux

GPU

cuda

VRAM

6GB

What happened?

Can't read metadata ?!

invoke> !fix /home/apfelkomplott/Pictures/beautifulvampirewoman.png --outcrop top 128
>> fixing /home/apfelkomplott/Pictures/beautifulvampirewoman.png
>> could not read metadata
Traceback (most recent call last):
  File "/home/apfelkomplott/InvokeAI/ldm/invoke/args.py", line 1036, in metadata_loads
    images = [metadata['sd-metadata']['image']]
KeyError: 'image'

Screenshots

Additional context

No response

Contact Details

No response

[lstein]

This is fixed in release 2.1.3, which should be released imminently.

[apfelnymous]

This is fixed in release 2.1.3, which should be released imminently.

Thanks, can't wait :)

[downj05]

Had a similar issue, when no metadata is provided and I am using my own prompt (in my case with outcropping) it still excepts metadata and throws an uncaught error that crashes the entire script.

[psychedelicious]

@lstein Looks like there are still some issues with this

[apfelnymous]

What I forgot to mention: In this case an old dalle2 picture was used, but the error is the same when passing the --new_prompt tag along with it. Trying the same with a picture created with invoke works (except I run out of vram when it starts to generate)

So, anyone knows a handy metadata editor to initialize the needed attribute manually on the terminal ?

[lstein]

I'm afraid I can't reproduce the issue when I choose a random picture from the Internet that has no metadata in it. Here's a JPG of Beyonce accepting a Grammy nomination earlier this week:

And here's the outcropped image after extending 128 pixels at the bottom using --outcrop 128:

This was using 2.1.3 and the inpainting-1.5 model. I didn't even add a prompt or seed and let it use its default seed of 0 and prompt of "". Can @apfelnymous and @downj05 confirm that you are both experiencing the problem in the new release? Maybe you could post images that are causing the bug to appear?

[apfelnymous]

@lstein I tried it with one random jpeg which worked, but then also 2 png which didn't. I pulled just now and updated the env, but how can I output the version to check ? This one doesn't work for instance: Can you reproduce it with that one ?

[lstein]

I've made a pull request that will fix this bug, and it should appear in the next point release sometime this week.

Here is your outcropped vampire. I reduced her in size a bit for the purpose of debugging. For best results on a non-InvokeAI-generated image, please use the inpainting-1.5 model.

[apfelnymous]

Thx, I can avoid the matter until then by extending the pictures canvas and import it to inpaint the empty borders.

[apfelnymous]

Tested this in the 2.2 unified canvas webui and the CLI, works.