search

RupertAvery / DiffusionToolkit

Metadata-indexer and Viewer for AI-generated images
MIT License
743 stars 46 forks source link

[BUG] Can not find generated images (NovelAI) #175

Open yifeifrank opened 9 months ago

yifeifrank commented 9 months ago

Describe the bug Toolkit browser unable to find generated pictures.

Version: version 1.5 & 1.5.1 version 1.4 works fine.

To Reproduce the main filepath settings, other settings not changed. image

Expected behavior Generated files should be listed in the toolkit browser. After porting v1.4 database to v1.5, the files show up in the library, but clicking cause the following error. image

Source Image All generated images, be it from webui or NovelAI. I think the problem is about metadata, png files from danbooru can be listed.

Source Image or Screenshots image

RupertAvery commented 9 months ago

Can you attach a sample image that raises the error?

yifeifrank commented 9 months ago

aris_blue_archive,eluthel,naga_u,tyakomes,baku_p,healthyman,yuizaki

generated via NovelAI

RupertAvery commented 9 months ago

Looks like this was caused when I added support for FooocusMRE which also uses a "Comment:" tag.

NovelAI uses a Comment: tag as well, but also has a "Software: NovelAI" tag.

RupertAvery commented 9 months ago

Let me know if this version fixes your issues

(non-working link removed)

yifeifrank commented 9 months ago

Running main exe shows error: Unable to load DLL 'sqlite3' or one of its dependencies. (0x8007007E)

Let me know if this version fixes your issues

(non-working link removed)

RupertAvery commented 9 months ago

Sorry about that. This one has the DLL.

(non-working link removed)

yifeifrank commented 8 months ago

Sorry about that. This one has the DLL.

(non-working link removed)

Thank, you! Update: the error is fixed, much thanks

RupertAvery commented 8 months ago

Turns out some code changes made it work on my machine but not others. Hopefully this should work.

Diffusion.Toolkit.v1.6 beta.zip

toshi-miura commented 8 months ago

Thank you for the correction. I was facing a similar issue, but I have confirmed that the problem has been resolved in my environment