Next, I plan to make a small starter module to which you can connect the individual modules in order to build your own small, compact special tool. What do you think, does that make sense? Best regards and thank you for your comment
hey thanks as always, I just came across something that kinda buggs me, whenever i use flux i like to also use the optimize with latent upscale SDXL part, to give the image a stylised look, but the saved image is always the flux direct one not the one after the latent upscale, in previous versions of ur workflow this didnt happen, I'm now using a image_save node to save the wanted output but its kinda weird thats all. is there an ez way to adjust the saved image?
@salomahal7287 Hi, thanks for your message. I just looked into this, with my new workflow that isn't released yet and also with the V2.0 that is on CivitAi. I can't recreate it. Did you remember that there are 3 Save nodes that you can turn on. The blue one is always just for the start image. The green and brown ones are for the final image. The final images are saved in a different directory than the start image. You can freely define the directories and, if you want, enter the same one twice. I think I'll upload the current workflow at the end of the week, but first I want to install a Lora trigger for the latent SDXL. I just noticed when checking that I had forgotten that. ;-). There are also 15 small workflows with a different memory module. Not as convenient but much faster. You can add it pretty easily. The workflows are finished and the video instructions are in progress. But I can only continue a little after work.
Thank you for this info. I tested these nodes about 2 weeks ago and also implemented one of these nodes, but haven't published the workflow yet. I think on Friday there will be the new video and several small and the new big workflow with this node.
Great work again Murphy, lots of options as usual 😊
Next, I plan to make a small starter module to which you can connect the individual modules in order to build your own small, compact special tool. What do you think, does that make sense? Best regards and thank you for your comment
@@murphylangathat would be appreciated
Sounds good to me. Not everyone likes very complicated workflows, and there's alot to be said for different workflows or modules for different tasks.
ok, then I will do that soon, I'm currently playing with text to speech F5TTS cool stuff :-)
Great work!
Many thanks
This is my goto workflow! I have modified it to my needs but this is my base.
In my last picture on CivitAI the latest Ultimate workflow is embedded, I hope I can upload it officially and create the video for it by the weekend
I loaded it and would an adfitional 30 or so new nodes to me this work!! Do you havd a simplified verdion just for creative flux upscaling?
@@WhySoBroke Hello, I'm currently building a collection of simple workflows that I will publish soon. Flux upsale can then be easily assembled.
hey thanks as always, I just came across something that kinda buggs me, whenever i use flux i like to also use the optimize with latent upscale SDXL part, to give the image a stylised look, but the saved image is always the flux direct one not the one after the latent upscale, in previous versions of ur workflow this didnt happen, I'm now using a image_save node to save the wanted output but its kinda weird thats all. is there an ez way to adjust the saved image?
@salomahal7287 Hi, thanks for your message. I just looked into this, with my new workflow that isn't released yet and also with the V2.0 that is on CivitAi. I can't recreate it. Did you remember that there are 3 Save nodes that you can turn on.
The blue one is always just for the start image. The green and brown ones are for the final image. The final images are saved in a different directory than the start image. You can freely define the directories and, if you want, enter the same one twice. I think I'll upload the current workflow at the end of the week, but first I want to install a Lora trigger for the latent SDXL. I just noticed when checking that I had forgotten that. ;-).
There are also 15 small workflows with a different memory module. Not as convenient but much faster. You can add it pretty easily. The workflows are finished and the video instructions are in progress. But I can only continue a little after work.
@@murphylanga Ah yea I was using the 1.0 version the one in the 2.0 works nicely thx
@@murphylanga btw dunno if its already somewhere in there but the detailer daemon node is really nice and an ez implementation just for the futur mb.
Thank you for this info.
I tested these nodes about 2 weeks ago and also implemented one of these nodes, but haven't published the workflow yet.
I think on Friday there will be the new video and several small and the new big workflow with this node.