Fooocus Private Log #160
Replies: 16 comments 17 replies
-
|
This log is missing the seed. Without that information, the log defeats its purpose. |
Beta Was this translation helpful? Give feedback.
-
|
fixed in 1.0.32 |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for all the effort you've put into this repository. Much appreciated! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for implementing private logs. I agree with Fooocus's philosophy of protecting user privacy and not writing hidden data in the generated images, and the way you have implemented it. |
Beta Was this translation helpful? Give feedback.
-
|
Would it be possible to record the version of "Fooocus" in this log? This would make it easier to track information in the future when new features are added. Such as the 'Sharpness' feature. |
Beta Was this translation helpful? Give feedback.
-
|
Great solution. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
will there be a easy way to get the prompt etc from the log into Fooocus like copy a section from the log and input it somewhere? |
Beta Was this translation helpful? Give feedback.
-
|
I've created a Tampermonkey script that converts the plaintext log file into a gallery app. It won't solve all the problems talked about here but certainly makes browsing created images and finding settings used much easier! Find it here -> https://github.com/mattmarkwick/fooocus-gallery
|
Beta Was this translation helpful? Give feedback.
-
|
I love the project feature and wish a gallery was part of the main Fooocus project but i dislike the use of browser extensions like you used.. wish it was just part of fooocus :( |
Beta Was this translation helpful? Give feedback.
-
|
this is to be upviewed ,as it is faster and easier to review images in small thumbs than in a big scrolling images log as today. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Illya, first of all: You did a really great job! Finally I can play around with the SDXL even on my small RTX-3070 card with only 8GB VRAM. Thanks for that! 😊 I have a small suggestion for improvement: The Log.html is a good solution, but I it will be better to write each file a seperate log.html with the same filename as the image.png. So it will be easier to find old generations. I switch often and play around with the prompt and sometimes i would like to reproduce older prompts. So at the moment I first need to find the image in the expolorer what is quick but then I need to search in the .html for the filename and the prompt. And that takes more time. Best regards from germany, |
Beta Was this translation helpful? Give feedback.
-
|
Can we imagine a way to copy/paste the text of an image's log file into Fooocus to automatically re-parameterize Fooocus? |
Beta Was this translation helpful? Give feedback.
-
|
maybe, we will "ReGenerate" some finished images at another version of Fooocus: https://github.com/metercai/SimpleSDXL |
Beta Was this translation helpful? Give feedback.
-
|
"ReGenerate" is ok, can try it: https://github.com/metercai/SimpleSDXL |
Beta Was this translation helpful? Give feedback.
-
|
What I would like is the private log to fully show the negative and positive prompt that gets fed into the generation. When you select styles for example it will mention the style name but not the prompt resulting from them. |
Beta Was this translation helpful? Give feedback.
-
|
Would be cool if the log would also keep track of the image prompts used, maybe by file name and weight? |
Beta Was this translation helpful? Give feedback.
-
|
Absolutely. Image Prompt generation are not reusable in the log. |
Beta Was this translation helpful? Give feedback.
-
|
If one of the developers could point me to where the image prompt parameters get stored, I can create a PR to add the info to the private log. |
Beta Was this translation helpful? Give feedback.
-
|
I view images via built-in photo apps on both PC and a mobile device. A simple txt file alongside each image would be easier to locate using built-in device file explorer apps. Currently, i need to open an HTML file which isn’t supported on mobile devices (e.g. via OneDrive sync, images don’t appear in log depending on file viewer), use CTRL-F (not available in file previews on all sync apps), and in some cases after a file is moved, identify and navigate to the original folder. It would be easier to search for and open a txt file sitting alongside each image using a preferred file viewer rather than a more prescriptive log format. This would also make it easier to copy files along with their metadata when moving them. and hopefully would involve less effort on your part to maintain what i’ll note is a pretty nicely formatted log/gallery file. |
Beta Was this translation helpful? Give feedback.
-
|
Hello |
Beta Was this translation helpful? Give feedback.
-
|
@toutjavascript that's pretty neat. I may give it a try on my fork. |
Beta Was this translation helpful? Give feedback.
-
|
Just for reference: you can find the meta data PR in #1940 (also compatible with A1111 SD WebUI). |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! Yes, I saw that they said they would never merge it. If it instead was an option to save it as a separate txt file with a matching filename they might consider it. |
Beta Was this translation helpful? Give feedback.
-
|
I am trying to generate the images with metadata include with my Fooocus Log Viewer |
Beta Was this translation helpful? Give feedback.
-
|
@toutjavascript I may try to integrate your code in my fork when I get a chance. |
Beta Was this translation helpful? Give feedback.
-
|
"Fooocus is committed to protect user privacy and will never write any hidden data in your generated images." I love Fooocus, and I am grateful for all of the time and work put into it. The prompt information is not "hidden data". It is data about the image. Concealing the prompt is concealing essential information about the image. Allowing a user to choose to include the image metadata (prompt, model, seed, etc.) of the images they generate is no more an invasion of privacy than is the image itself. (It may be helpful to refer to GDPR for a useful definition of "personal data".) Please allow users to include the image data in the image files they generate. Thank you for your time. |
Beta Was this translation helpful? Give feedback.
-
|
Please find the metadata feature in https://github.com/lllyasviel/Fooocus/releases/tag/2.2.0 and the latest version 2.2.1. You can activate it using the config or the UI (Developer Debug Mode). |
Beta Was this translation helpful? Give feedback.
-
|
And it has a choice between text and ison! Thank you and thank lllyasviel. 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
It should be great if we can add our signature/website/nickname in the metadatas with a free text zone (customizable in config.json) |
Beta Was this translation helpful? Give feedback.
-
|
@toutjavascript you can already do so, please use the metadata_created_by config! |
Beta Was this translation helpful? Give feedback.
-
|
You are the best! |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
|
The log file or prompt is tracker on net. |
Beta Was this translation helpful? Give feedback.
-
Fooocus is committed to protect user privacy and will never write any hidden data in your generated images.
The option “write hidden meta data” does not even exist in Fooocus, so that you do not need to constantly check if you have forget to turn it on/off, or constantly using some tools to check it.
Once you are in Fooocus, you can just trust that everything is absolutely private and clean without any hidden things.
Nevertheless, we also appreciate community feedbacks with the demand to track history generation.
We propose “Fooocus Private Log”, a balance between user privacy protection and tracking flexibility.
After you generate images, you can have a log in the folder “Fooocus/outputs/XXX”, with all detailed parameters in your user interface.
Fooocus is also committed to eliminate the barrier between different software and we encourage users to directly copy prompts as pure texts when sharing them. We will not implement any “fooocus-only” meta data reading functionality to bind users with Fooocus, and users can always try different software directly by copying and pasting your prompts. Those logs are friendly to all other software.
Below is a screenshot of an example log:
Another advantage is that this log can do "Ctrl+F".
Beta Was this translation helpful? Give feedback.
All reactions