[BUG] Unable to scan .png files
Describe the bug Hi, I saved my images from SwarmUI or ComfyUI into png format but they do not appear in Diffusion Toolkit. When I switch to jpg files, they turn up.
Both .png and .jpg are file extensions set for the Toolkit
Version: 1.6.1, 1.7, 1.7-FIXED
Tool: ComfyUI, SwarmUI
To Reproduce Generate PNG images on ComfyUI or SwarmUI
Expected behavior The images appear in the folders but they do not turn up in scans of the folders by Diffusion Toolkit.
Affected Image(s) PNG type images
Hi, sorry for the late reply.
Are you still having problems with this? Can you post sample images?
I'm having a similar issue with pictures generated by SwarmUI v0.9.5-Beta and DiffusionTookit v1.8. For me, they are showing up, but they've got a red exclamation point, no metadata, and an error. Here's an example image:
This is the error shown in DiffusionToolkit:
The given key was not present in the dictionary.
at System.Text.Json.JsonElement.GetProperty(String propertyName)
at Diffusion.IO.Metadata.ReadFooocusParameters(String data)
at Diffusion.IO.Metadata.ReadRuinedFooocusParameters(String data)
at Diffusion.IO.Metadata.ReadFromFileInternal(String file)
at Diffusion.IO.Metadata.ReadFromFile(String file)```
Thank you for the image. I have a fix in place that will be included in the next release, hopefully soon.
Thank you for the image. I have a fix in place that will be included in the next release, hopefully soon.
Amazing, thanks!
A new stable build is up, please try this:
https://github.com/RupertAvery/DiffusionToolkit/actions/runs/14348000145/artifacts/2908080007
The stable build seems to be working, at least for me (I had the same issue).
I am still getting the red exclamation points, though there is metadata and the workflow is present to the point it can be pulled into comfy and it works.
Thanks so much for the fix! I was seeing the same thing as @f-rank at one point, but I'm not any more. Not sure if there was another update I missed or perhaps I'm forgetting that I rebuild the metadata (or something else entirely). Anyway, no issues on my end at this point! IMHO this can be closed out