You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are images downloaded through the Gligen-GUI 'Download Image' button supposed to contain workflow metadata?
Images I queue myself from ComfyUI contain workflow metadata which I can load with either Drag-and-drop or the Load dialog button, and they appear in the ComfyUI/temp folder.
Images I queue from the GUI and downloaded using the 'Download Image' button don't appear to contain metadata. I checked the ComfyUI/temp folder hoping to find temp files that might contain metadata but they don't appear there.
I'm not sure if github removes metadata or not, but this is an image I made using the GUI that I can't load back into ComfyUI as a workflow.
The text was updated successfully, but these errors were encountered:
Thanks for posting this. I'll take a look at his. But meanwhile, you can take the generated images from "\ComfyUI\output\gligen" and drop them into ComfyUI and they should load the workflow just fine.
That works for me - I missed that folder until now because I have quite a few subfolders in there, a few of which also have gligen in the folder name. All the images are there and they do load properly.
Are images downloaded through the Gligen-GUI 'Download Image' button supposed to contain workflow metadata?
Images I queue myself from ComfyUI contain workflow metadata which I can load with either Drag-and-drop or the Load dialog button, and they appear in the ComfyUI/temp folder.
Images I queue from the GUI and downloaded using the 'Download Image' button don't appear to contain metadata. I checked the ComfyUI/temp folder hoping to find temp files that might contain metadata but they don't appear there.
I'm not sure if github removes metadata or not, but this is an image I made using the GUI that I can't load back into ComfyUI as a workflow.
The text was updated successfully, but these errors were encountered: