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
In Kohya SS GUI previously I could go into Utilities->Manual Captioning and select an existing folder on a drive on my PC that has existing images and .txt caption files in, and I would edit all those .txt files in Kohya.
Currently my caption .txt files and images for captioning are stored on drive D (though they get copied to another drive & formatted folder when training). Now when I select the D drive and folder with the images and .txt captions in in the Kohya Flux branch the cmd window shows:
gradio.exceptions.InvalidPathError: Cannot move D:\Pics\[folder I use to store lora and dreambooth training images & captions main folder]\...filename.jpg to the gradio cache dir because it was not created by the application or it is not located in either the current working directory or your system's temp directory. To fix this error, please ensure your function returns files located in either the current working directory (G:\Kohya-Flux-Training-for_Lora-and-Dreambooth-v16\kohya_ss), your system's temp directory (C:\Users\[username]\AppData\Local\Temp) or add D:\Pics\[full folder name of that specific folder with those captions in that I'm trying to edit] to the allowed_paths parameter of launch().
So this new version of gradio is stopping the Kohya Flux branch from working as it did before in allowing captions to be manually edited. The GUI doesn't give any info on what is best to be done by the user.
Ideally it could just work and allow me to select any drive and folder on my PC and allow me to use that for a source folder to edit the captions at (like I could previously and can still with an old version of Kohya GUI that hasn't been updated for a while). Or if it needs specific ones, maybe there could be something in the installation section where the user could specify which drives and folders it should allow access to.
The text was updated successfully, but these errors were encountered:
TechScorpion
changed the title
Manual Captioning (editing) with latest version, with the updaed gradio now doesn't work properly/as it did before
Manual Captioning (editing) with latest version, with the updated gradio now doesn't work properly/as it did before
Nov 25, 2024
In Kohya SS GUI previously I could go into Utilities->Manual Captioning and select an existing folder on a drive on my PC that has existing images and .txt caption files in, and I would edit all those .txt files in Kohya.
Currently my caption .txt files and images for captioning are stored on drive D (though they get copied to another drive & formatted folder when training). Now when I select the D drive and folder with the images and .txt captions in in the Kohya Flux branch the cmd window shows:
gradio.exceptions.InvalidPathError: Cannot move D:\Pics\[folder I use to store lora and dreambooth training images & captions main folder]\...filename.jpg to the gradio cache dir because it was not created by the application or it is not located in either the current working directory or your system's temp directory. To fix this error, please ensure your function returns files located in either the current working directory (G:\Kohya-Flux-Training-for_Lora-and-Dreambooth-v16\kohya_ss), your system's temp directory (C:\Users\[username]\AppData\Local\Temp) or add D:\Pics\[full folder name of that specific folder with those captions in that I'm trying to edit] to the allowed_paths parameter of launch().
So this new version of gradio is stopping the Kohya Flux branch from working as it did before in allowing captions to be manually edited. The GUI doesn't give any info on what is best to be done by the user.
Ideally it could just work and allow me to select any drive and folder on my PC and allow me to use that for a source folder to edit the captions at (like I could previously and can still with an old version of Kohya GUI that hasn't been updated for a while). Or if it needs specific ones, maybe there could be something in the installation section where the user could specify which drives and folders it should allow access to.
The text was updated successfully, but these errors were encountered: