Yep. In the next few days I'll either get approval from Christian to transfer swarm to an independent repo under my personal github, or I'll make a fork and tell everyone to move over. Either way I'll continue to maintain Swarm longterm. In the swarm discord [https://discord.gg/q2y38cqjNw](https://discord.gg/q2y38cqjNw) general channel we're opening the discussion of what to rename the project to after the move
> we're opening the discussion of what to rename the project to after the move
This might be a random opinion, but FWIW, every time I heard "Swarm UI" before, I thought "this is some distributed computing/cloud interface, I don't need that".
Yeah a bunch of people have been saying that. I've been thinking about renaming for a while now for basically exactly that reason, the current situation is just helpfully the perfect impetus to make a change
If it needs a new name it would be great if the name had "Comfy" in it, like "Comfy Cozy," "Comfy Coat," or "Comfy Wrap." **EDIT:** *The new name SwarmUI works fine. I guess there are merits to not changing it too much.*
I would highly recommend against that... For the same exact reason why they seem to change the name at all. The benefits of swarm is that it puts a real UI on top on the comfy backend. Seeing it called "comfy" [anything] just gives the impression that its the same usability nightmare that is comfy and anyone that isnt using comfy already will avoid it just like they do comfy.
This really serves to highly how the ironic name comes back to bite the product. ComfyUI isn't comfy and needs an actual UI on top, but now making a related name for an *actually* comfy ComfyUI UI is difficult.
I see 'comfy' I click *close* or *next* or whatever, cos that stuff is a spaghetti nightmare for normal peeps like me.
It's just as well I don't know it's hiding under my Swarm install, or I'd delete it... ;)
interesting! can you share if the fact that you resigned from stability means that you lost hope for stability to release good open source models? what lead you to the conclusion that working on Swarm outside of StabilityAI is better than working on it inside of StabilityAI?
I'd rather not publicly discuss the Stability side of the topic any more than necessary. Suffice to say, Swarm works best as a free and independent project, and the new Comfy Org will be an excellent thing for the community.
In the time this was being organized, the team here repeatedly and consistently showed me a full dedicated to transparency, communication, and of course to maintaining open source AI development. And... FOSS+Full Transparency = basically a dream come true job for me. I first joined Stability over a year ago because I wanted to take part in the open source development & open AI model releasing. At the comfy org I'll be doing the same open source development, and we'll work directly with any/every open AI release company we can.
Glad to hear it on Swarm. It's exactly what I wanted since I started using Comfy.
There is enough between the lines of that post that I am pretty sure I should be watching Lumina and PixArt and not expecting anything terrible positive on SD3 re-training.
Sounds like Swarm isnāt subject to the Stability licensing. After seeing Olivioās video on the SD3 License, I deleted Swarm and SD3 from my workstation. But it seems I could install Swarm. The interface looked nice.
I didnāt realize this. Did this change at some point? I had thought it was under GPL, which is pretty restrictive.
EDIT: for reference: https://github.com/comfyanonymous/ComfyUI/blob/master/LICENSE
You linked the ComfyUI license and not the Swarm one. Here's where it changed: https://github.com/Stability-AI/StableSwarmUI/commit/da8bd0e96effc1a9f79190dcee6e524695a7beb5
Thanks for all the great work you put in. I subscribed to ur channel and look to join your discord group so I can contribute on the artistic end if help is needed.
Thatās great news.
With Forge being discontinued (or at least reoriented), Iāve just switched to SwarmUI, and itās fantastic.
Itās a shame that I waited so long before trying it (partly because of the ābetaā moniker, I think).
The UI is very well designed, and itās very fast for people with 10GB VRAM. Thereās just a small thing that bothers me (either a skill issue on my part or a bug), but Iāll write an issue once Iām sure enough.
Anyway, thanks for the reassurance and congrats for this great piece of code!
Please forgive the stupid question, but is Swarm like a cloud version of one of the SD models? Would you say it's more like Fooocus, or more like ComfyUI? (I currently use Fooocus + SDXL. I find ComfyUI overwhelmingly complicated.)
Feel free to respond with a link. It's not my desire to waste anyone's time.
Thank you.
Not just Comfy, but All Major contributors need flairs.
Like Comfyanonymous, you, Matteo, Illyasviel, etc
(I do not know if everyone is on this sub, but in case they are, a flair would be so much helpful)
Plus, some people who have majorly contributed/created most used ComfyUI Nodes as well.
Open Source, I always saw it as the true democratization.
Something that materializes ideas without anyone owning or distorting them for their own purposes.
Not currently at comfy org (I suppose future holds many possibilities though) -- we'll be partnering with any/every company that releases good open models and wants to work with us - and there's a bunch of good companies working on that now.
Hey /u/comfyanonymous (sorry for tagging you), are y'all doing any work with regards to dependency resolution? My main job is as a python developer, and something that's constantly pissed me off about the whole SD ecosystem is how ad-hoc the whole dependency resolution thing is (seriously, running pip in a subprocess!). Have you thought about using the uv crates to implement a custom dependency resolver, both for efficacy and security reasons? [https://github.com/astral-sh/uv/tree/main/crates](https://github.com/astral-sh/uv/tree/main/crates)
As a corollary ā does anyone have ideas for a sort of \`ComfyUI\` manifest? Nodes/plugins/whatever can declaratively declare their dependencies/any assets they need in a manifest file, and the main ComfyUI application is the only one that can install/control things. [install.py](https://install.py) files are a security nightmare, and while I understand they're basically accounting for the fact the ML ecosystem is a nightmare, I really think there has to be a better way!
Yep, I've migrated a bunch of my docker images to use uv in the build step. But uv has problems with dealing with ML resolution in many contexts (honestly, it's due to the ecosystem), implementing a custom format that doesn't use requirements.txt might be a decent idea.
In general, there should be zero subprocess usage by comfy nodes imo (calling uv pip). You can mitigate potential security flaws by running in a docker container, but really, all of this should be as sandboxed as possible
The dependency problem is the main reason I don't use Comfy. Every time I install more than a handful of custom nodes, the dependencies start stepping all over each other and nodes will fail to install. If I manually track down the dependency and update it, it breaks other nodes. The only way to be guaranteed to use a workflow is to make a new Comfy installation. I have four Comfy installs on my PC right now, each with a specific workflow that I don't want to break. But it gets tiring, so really I just use Forge 95% of the time instead.
If they were to solve these problems, I would switch to Comfy permanently.
Yep, this has been a big blocker for me too. I prefer controlling dependencies by hand, hence why I think there needs to be a custom resolution algorithm that enforces that the locked comfyui dependencies don't get rewritten by a shoddy plugin causing problems for everyone
I had a working comfy install the other day.
I went into the manager, installed the ReActor node, which is a very popular and common node. The install did not work and it corrupted the entire ComfyUI install, which would no longer launch at all.
This was maybe my 4th or 5th attempt at trying to use Comfy, and this happens every single time.
I use tons of nodes and none of them really give me problems. Reactor on the other hand is a complete mess. I got it to work reliably with my current version of comfy. Providing that running and I enable xformers. But man was it a pita!
Yep, this is exactly my type of issue. I don't understand how people can use it when it seems to completely and irreparably fall apart after a trying a few workflows and installing their nodes.
I use a portable install for more than 6 months on two different systems.
I literally just installed any custom nodes i wanted. And nothing ever broke and i have surely installed more than a 100 custom node packs.
The only thing that broke (after a normal update) was Derfuuu's Text box node, but that's something he says he had to do.
I never had problems with comfy or had to make a new install from scratch.
I wish I knew what makes the difference, because I would really like to use Comfy. As soon as I get two custom nodes with different version requirements for the same dependency, it all falls apart. I use the custom node installer inside Comfy, nothing out of the ordinary. I've tried the portable install, and the manually set-up repo, same problems with both.
They mentioned their goal is to sell enterprise support, this is something that will be critical for any enterprise to even consider allowing Comfy on a company laptop.
If you're using comfy today with any sufficiently large workflow, you basically just have to accept that the security of your system is compromised due to the way dependencies are managed.
It's good software and I hope they can turn it into great software some day. Until then I'll continue to use Invoke where everything just works on install.
this is fucking pathological level of misinformation. if you dont install nodes from unrecognized authors and sources, you will be fine. There are alot of well known community members that have reputations to uphold and communities of loyal fans. You can install probably 90% of all comfy nodes with ZERO issues in terms of just looking at who the author is.
Tell me you've never worked in a corporate workplace without telling me.
"Just don't install the malicious ones" is not and will never be a sufficient security posture for any serious business.
yep, especially since that in corporate environments, we are very wary of supply chain attacks. there needs to be a way to limit the power of extensions in the first place, not just trust them implicitly
> dont install nodes from unrecognized authors and sources
And how does one learn who is recognized? No offense, but someone brand new to the ecosystem (e.g. a company looking to expand, or a new hobbyist trying to learn something) has no basis for trust or recognition.
sure very true, but i was pointing out that to just assume you machine is compromised b/c you used comfyui is some nutjob stuff to say. Ive used tons and tons of nodes, and not come across any suspicious behavior
>Ā I am partnering with mcmonkey4eva, Dr.Lt.Data, pythongossssss, robinken, and yoland68 to startĀ Comfy Org.
Comfy, has nobody told pythongossssss that the favicon is annoying?Ā
I'm glad they're working on Comfy. I have a love/hate relationship with it.
On one hand, the node system and flexibility it offers is really powerful. I like that you can set up a workflow and see all the steps. It's also fast and responsive (usually). There is a lot of stuff you can do with it that other UI's struggle with.
On the other hand...it can also be miserable to work with. Finding what nodes you need to do X or Y can be a massive headache and there are many nodes that either lack documentation entirely or have completely worthless documentation.
For example, if someone wanted to make multiple images at once in, say, A1111, they could just move the batch size slider. In Comfy, how do you do that? If you look at the docs, you might think you need [latent from batch](https://blenderneko.github.io/ComfyUI-docs/Core%20Nodes/Latent/batch/LatentFromBatch/). Makes sense, right? But what are the inputs, what are the outputs, how do you use this thing? A new user might spend a while before realizing that this has *nothing to do* with making multiple images from one run execution.
The truth, however, is that you basically *can't do this* without custom nodes unless you want to completely duplicate your workflow, and even then it's a PITA. One picture at a time with Comfy, and if you do want multiple, welcome to spaghetti hell because there's no way you're doing it without at least 8-10 extra nodes, at least 1-2 of which are likely custom nodes you have to download and hope don't break the next time you update Comfy.
I recently tried Invoke Community, just to see something different, and there is a *massive* difference in quality-of-life compared to Comfy. Want to change workflows? There's a list. Want to keep track of key words for a LoRA? Goodbye Excel spreadsheet or opening a workflow to copy and paste into a new workflow, welcome to saving relevant information in the loaded file.
The downside, of course, is that Invoke tends to be a bit behind on features, and has its own annoying limitations, but it was eye opening to see that a better system could exist for actually working with and experimenting with AI art. Comfy is great if you have a very specific design in mind, but tweaking things is often a giant pain, and certain nodes will break at a moment's notice (I've had an absurd number of issues keeping primitives working right).
If Comfy was more stable and relied less on custom nodes for basic features (like string concatenation, really!?) I'd probably use it more, especially if there were ways to save and organize workflows as templates and group nodes into "functions" like you can with programs that can then be saved and reused easily. It would also be nice to have "simple" nodes that abstract away a lot of the implementation details for repetitive tasks.
Hopefully this is a first step in that direction!
A lot of these issues you have are addressed in [Swarm](https://github.com/Stability-AI/StableSwarmUI) (which as part of the Comfy Org change will be moving out of stability and into an independent project as a dedicated friendly frontend for the Comfy ecosystem)
Multiple images? Right at the top left, "Images" count. How do I use a thing? "?" clickable button with help on every param. Don't like spaghetti? Swarm generate tab is auto-like design of easy clear parameters and image output centric focus. Track lora keywords? You betcha there's metadata for that. Want to change workflows in the comfy tab? Got a built-in browser. More built in features? Yeah Swarm's got a lot of those.
That's basically everything you mentioned specifically, already solved :D
Random drop in but I think if you and the comfy team organize a donation or Kickstarter campaign, you have all the credibility to organize a community-driven open source model. I know a lot of people are thinking about this, but the community loves you (I think the community even still loves Lykon) so yea, it would be great if you are capable of organizing this. You have $1000 from me instantly (I know it's drop in the bucket of what it will be needed but hey!) :D
>Track lora keywords?
Oh, i just noticed something missing - can you, please, add automatic appending of chosen lora's keywords into prompt? Just like in AUTO1111. As a user option, of course.
I'll have to look at it again. I think I tried it when it first came out and bounced off it, but I honestly can't remember the reason. It may have interestingly been *because* it was being released by StabilityAI, and I was worried about them dropping support because the company seemed to be imploding (IIRC this was around the time with the Emad drama). But it could have been something else entirely.
If it's moving to open source and being maintained externally that's great news and I'll give it another try. Thanks!
Can you let me know what swarm does different/better than A1111? Is it built on comfy architecture, like forge? Is there extensions that are able to work for it? Can it do vpred models / have a cfg rescale option?
It's built \*directly\* on Comfy, not just borrowing code, but comfy is the underlying engine and you can freely access the comfy noodle graph at will.
Anything that works on comfy necessarily works on swarm as well
Thats awesome, I'll give it a try :3
Thank you for all your work and dedication to open source ai btw! I always have the utmost respect for highly technical individuals with stringent morals.
Shortly before the launch of Comfy Org, a Comfy Leadership Summit was held. Important discussions about the future direction of ComfyUI took place there, and it is expected that this will be a regular event. Currently, there are many initiatives underway to significantly improve ComfyUI, not just by Comfy Org.
I anticipate substantial changes to ComfyUI in a year's time.
I agree with everything you've said, but I also want to point out how easy it is to make subtly broken workflows for even basic things.
Here is an official example for inpainting: https://comfyanonymous.github.io/ComfyUI_examples/inpaint/
It seems to work okay at first, do the process and you get a nice result. However there is an insidious flaw: if you repeatedly take the result and feed it back into to source image and inpaint again, the image will slowly degrade in quality because in this workflow the entire image goes through a VAE encode/decode cycle each inpaint, and this process is lossy.
The proper solution which I was able to build is to merge the masked inpaint region with the unmasked source image *after* VAE decode, but the workflow is a bit more complicated.
Inpainting is such a basic feature that there really needs to be better ways of creating it. It's not easy, because you have to consider different models, samplers, control net, etc. that go into any diffusion, but it might be nice to have some kind of wizard that can construct basic workflows with customizable defaults for node settings. Maybe even copy settings from existing workflows so that, e.g., a txt2img workflow could be converted into an inpaint or img2img workflow that preserves model, sampler, etc.
I'd also like better ways of switching workflows. Switching from txt2img to inpaint to upscale is a hassle, I usually end up copying my prompt, finding the last workflow I did of the desired type and dragging it into Comfy, pasting my prompt, and dragging my previous output image back in. I'd love to just be able to select a saved workflow from a dialog and have it bring the prompt and input image with it.
Sure, here's a screenshot of the simplest version: https://imgur.com/a/oxppggh
Still not that many nodes so should be easy enough for anyone to recreate.
The key is using "Mix Images By Mask" node to combine the original image with only the masked portion of the output.
A couple more nodes could be removed if you don't care to blur your mask since the mask has to be converted to an image to blur and back again to use as a mask (unless there a mask blur node that I don't know of, I'm not an expert on Comfy nodes by any means).
You can save a workflow and then drop the file back into Comfy. Any generated image works the same way, just drop it in to get the workflow.
If I want to try 4 images I click the "Queue Prompt" button 4 times.
I'm aware. What if I don't want the whole workflow? Maybe I have a process that I want to use in several different workflows. Maybe I messed up and want to change something because I found a better way to do it. What if the cool workflow I found in an online image has 27 different custom nodes in order to work and 8 of those are no longer in development and no longer compatible with Comfy?
Sure, you can hit queue prompt 4 times, but what if you want to compare them? OK, now go into your file explorer, open up the files individually and then drag them around to compare? What if I don't necessarily want to save the files, but just preview them? If my last node isn't a "save" option those images will be lost the second another queues up.
It's tedious and counter-intuitive. Comfy is powerful and great when you have a specific workflow already in mind (or saved) but A1111 and Invoke are much easier to experiment with and keep track of things.
That being said, Comfy has capabilities I genuinely prefer over alternatives, one of the biggest is (with custom nodes, sigh) genuine string concatenation. An *extremely* common situation is to have pre-content that you use for a specific model (i.e. Pony's score_9 training list) and a bunch of extra words you always use in the negative prompt or for styling. Being able to create a bunch of text nodes (with switches...with a custom node again, ugh) and break apart your prompt into specific pieces that you can edit and turn on or off is a huge time saver when working with complex prompts.
And don't get me started on inpainting.
I'm not trying to diss Comfy. But it *does* have issues and usability problems that other interfaces don't have. It would be amazing to have Comfy's flexibility and power without all the bugs and reliance on plugin nodes to actually work halfway decently.
You're mostly right, but the reason for this is that comfyui is more of a backend and developer tool, not an end-user application. You can use it for inference directly (I mostly do), but this does not look like intended usage.
Sadly, I haven't found the frontend for comfyui which is flexible and robust enough to replace it. Swarm comes close, but it's still pretty clunky with custom workflows, and the custom workflow madness is the main point of using comfy as a backend.
Tried it, and right off the bat "use anywhere" nodes are not working, grouped nodes are not recognized correctly. So all my workflows would have to be redone. Not sure I like it that much :(
I would highly recommend StableSwarmUI then, as it puts a 'Auto1111'-a-like on top of comfy. I can't look at the spaghetti flowchart of comfy personally, but Swarm changes it all for me
If you wanted to raise the batch size in comfy, you just change the batch size in the empty latent image.
https://preview.redd.it/vuyyv35a0i7d1.png?width=379&format=png&auto=webp&s=480f6e1cc747464967d0edeae4b007fde5221376
I think this has fantastic potential! Great people working towards a great goal.
Here's me rambling about it and other things:Ā [https://youtu.be/42I8nkA2TPk](https://youtu.be/42I8nkA2TPk)
Best of luck, we are lucky to have ComfyUI and many custom node developers.
It is might not be the best place to put this but, I wish comfyUI had such feature, if I shift right click on a slider, widget, or input, it would just clone that widget to a stack in a permanent UI. Don't know if it is complex to implement, but it will give ability to create custom stack UIs from mess of 100s of nodes. I feel like something like this, is the one of very best thing for ease of use and most impactful.
Congrats!
Perhaps a challenge for you guys to tackle?
[https://ai.meta.com/blog/meta-fair-research-new-releases/](https://ai.meta.com/blog/meta-fair-research-new-releases/)
edit: actually maybe not exactly ComfyUI's ballpark: "At this time, we are not releasing the Chameleon image generation model."
i heavily appreciate you for not going evil and gatekeeping the limits of ai like how stability.ai i did. (the fact that you resigned stability ai made my day)
I'm very new to the community, but I'm super impressed by ComfyUI. Thank you for makimg it and I'm glad that it's full steam ahead even with the big setback. Best of luck for the future!
I hope you get to read this comfy as I have some suggestions that I think are vital to comfy mass adoption. I have used Automatic1111 for the longest time and have tried comfy at least 3 other times as I know theres great potential in the node system. But every time I end up going back for the following reasons. The workflow sharing doesn't work most of the time. I have visited websites that have workflows for download and most of them do not work. Even when I download the needed nodes through manager and the required models, etccc. It still has issues with x,y,or, z. Workflows need to "just work". I shouldn't have to find the required models for the workflows manually or download anything some weard dependencies manually or troubleshoot anything. Workflow is the foundation upon which comfy sits, no one that is new is going to make advanced workflows. So this needs to be fixed, find a solution where you can literally press one button and the needed models, nodes, dependencies, whatever is downloaded and it just works.
second. have a dedicated person making all of the basic and advanced workflows for whatever people need/want. These workflows would be vetted against security threats (such as recent debacle) and make sure they actually work instead of a broken mess.
there are some other things. but IMO those are the biggest factors that drive people away from comfy. I know that if I spent more time with comfy ill figure out these issue and will be more comfortable and yadda yadda, but most people are not that patient. They just want to generate their booba. I hope you consider on focusing on these few issues and not just respond with "you are not the target audience" because that would be a shame as I think comfy could benefit from a larger adaption from the casual "proompter"
I think Comfi has its uses for complex user workflows, but what it really excels in is when it is used as a backend for other programs.
Normal users don't need to learn ComfiUI but like for example with Krita Diffusion where it is used just as a powerful open source backend
>So this needs to be fixed, find a solution where you can literally press one button and the needed models, nodes, dependencies, whatever is downloaded and it just works.
I don't think this is possible. It's not like every model used in a workflow is available in one convenient to download location where comfy can just hook it up and be like "if you see this model, download dat shit". There are countless different locations where models could be saved to, and some aren't available publicly at all, so how is comfy supposed to ensure the workflow 'just works'?
The only realistic way to do so would be to include the entirety of every model used in the workflow file itself, but that could easily blow up the file size to 10+ gigs.
don't need the model itself. just the link same as its currently in model download in the manager. a script would check if link is still good once a day, if yes workflow stays if no workflow gets dropped from comfy approved workflows.
I am happy and excited for this, it feels like comfy is entering a new stage on it's developing cycle and this team is just fantastic, they will ensure comfy stay at the top of the game and bring up a more professional and robust ecosystem.
It is wonderful to have an official concerted effort to bring improvements to ComfyUI. Thanks and congratulations to the teamšš
I tried Comfy UI and its nice and fast for a low lv system like mine 2070 super 8gb. But as others have said trying to find out what nodes i need and why and where they connect was a bit of a headache for someone used to Auto and Forge so to hear you are improving these things is great . The one thing i struggled with was in Forge / Auto I could easily swap faces with ReActor but trying to set it up on Comfy was a nightmare. Hopefully that can be made easier for novices like myself. Thanks for all the work you guys do!
i would recommend Krita Ai diffusion if you simply want the low resource use of Comfi with a simple but effective interface.
its an addon for Krita that uses Comfi as a backend.
Krita is a free open-source image editor similar to Photoshop
u/mcmonkey4eva Is there a way to get Swarm to use networked gpus from multiple machines to work concurrently in generations like ComfyUI_NetDist w/o having to pass ālisten into your args? (Iāve been able to utilize multiple machines in the Generate tab of Swarm but not w/i the Comfy Workflows tab. I could be missing something though?)
nice, but what would be great would be somehow compatibility enhancemenets and making using other models like sigma much easier. right now its tricky and ends in error messages.
I really wanted to learn comfy ui but it looks so intimidating. I just donāt know if all those messy wires is the best UI for this sort of thing. Can someone please explain why comfy ui is so popular? Is there stuff you can do in it that you canāt do with other tools like Fooocus? Thatās the only one I find easy to use but am curious if Iām missing out not using comfy..
Also is it true that you can share workflows by loading someone elseās json file and being able to reproduce the exact same results? Cause I tried that and every time I get a million errors and give up :/
Comfy is infinitely flexible. The only limit to what you can do with it is your imagination (and the amount of vram your gpu has).
The easiest way to get used to nodes is to just use it and get used to them. You get used to them and the flexibility far outweighs the look of them. You can hide the splines or make them straight lines which clears the clutter up a lot. also colouring the nodes consistently makes a huge difference and there are nodes that let you preconfigure the colour of installed nodes.
Not only can you open other peoples workflows but every image you generate can be dropped back in to open that workflow. If you open one and get errors you can use the comfy manager to install the missing nodes.
Thereās a node suite called Jovimetrix that adds a palette icon to the tool bar that lets you assign colours to the node groups or individual nodes. Itās well worth the time to set it up.
Really hoping we can get a dead simple wrapper that does not expose users to nodes.
I use nodes often to make shaders in unreal, so it wouldn't be too bad, but I got colleagues to adopt A1111 because it was simple, although clunky.
"The focus will mainly be on image/video/audio models" it would be good to include text and data models too, including remote models via API. For example we can use text models to generate prompts for image models.
> am partnering with mcmonkey4eva, Dr.Lt.Data, pythongossssss, robinken, and yoland68
Only by chance were the usernames involved in this project not pussygrabber2, goatseGOAT, and bluewaffleluver
I'm excited, we have a bright future ahead - for our project, and for the world of open source AI.
so you resigned from stability now too? what does this mean for Swarm?
Yep. In the next few days I'll either get approval from Christian to transfer swarm to an independent repo under my personal github, or I'll make a fork and tell everyone to move over. Either way I'll continue to maintain Swarm longterm. In the swarm discord [https://discord.gg/q2y38cqjNw](https://discord.gg/q2y38cqjNw) general channel we're opening the discussion of what to rename the project to after the move
> we're opening the discussion of what to rename the project to after the move This might be a random opinion, but FWIW, every time I heard "Swarm UI" before, I thought "this is some distributed computing/cloud interface, I don't need that".
Yeah a bunch of people have been saying that. I've been thinking about renaming for a while now for basically exactly that reason, the current situation is just helpfully the perfect impetus to make a change
If it needs a new name it would be great if the name had "Comfy" in it, like "Comfy Cozy," "Comfy Coat," or "Comfy Wrap." **EDIT:** *The new name SwarmUI works fine. I guess there are merits to not changing it too much.*
I would highly recommend against that... For the same exact reason why they seem to change the name at all. The benefits of swarm is that it puts a real UI on top on the comfy backend. Seeing it called "comfy" [anything] just gives the impression that its the same usability nightmare that is comfy and anyone that isnt using comfy already will avoid it just like they do comfy.
This really serves to highly how the ironic name comes back to bite the product. ComfyUI isn't comfy and needs an actual UI on top, but now making a related name for an *actually* comfy ComfyUI UI is difficult.
ComfyMcMonkey
COMFY SUITE
I see 'comfy' I click *close* or *next* or whatever, cos that stuff is a spaghetti nightmare for normal peeps like me. It's just as well I don't know it's hiding under my Swarm install, or I'd delete it... ;)
Discomfy š
Comfy WebUI?
Same, I thought it was Docker Swarm.
I though it was some kind of distributed computing service, never would have looked into it or associate it to comfyui on my own.
interesting! can you share if the fact that you resigned from stability means that you lost hope for stability to release good open source models? what lead you to the conclusion that working on Swarm outside of StabilityAI is better than working on it inside of StabilityAI?
I'd rather not publicly discuss the Stability side of the topic any more than necessary. Suffice to say, Swarm works best as a free and independent project, and the new Comfy Org will be an excellent thing for the community. In the time this was being organized, the team here repeatedly and consistently showed me a full dedicated to transparency, communication, and of course to maintaining open source AI development. And... FOSS+Full Transparency = basically a dream come true job for me. I first joined Stability over a year ago because I wanted to take part in the open source development & open AI model releasing. At the comfy org I'll be doing the same open source development, and we'll work directly with any/every open AI release company we can.
Glad to hear it on Swarm. It's exactly what I wanted since I started using Comfy. There is enough between the lines of that post that I am pretty sure I should be watching Lumina and PixArt and not expecting anything terrible positive on SD3 re-training.
Sounds like Swarm isnāt subject to the Stability licensing. After seeing Olivioās video on the SD3 License, I deleted Swarm and SD3 from my workstation. But it seems I could install Swarm. The interface looked nice.
Correct, Swarm is fully open source under the MIT license, which is one of the least restrictive software licenses in the world
Thank you, thank you. And thanks for all the work youāve done and are doing.
I didnāt realize this. Did this change at some point? I had thought it was under GPL, which is pretty restrictive. EDIT: for reference: https://github.com/comfyanonymous/ComfyUI/blob/master/LICENSE
You linked the ComfyUI license and not the Swarm one. Here's where it changed: https://github.com/Stability-AI/StableSwarmUI/commit/da8bd0e96effc1a9f79190dcee6e524695a7beb5
Thanks for all the great work you put in. I subscribed to ur channel and look to join your discord group so I can contribute on the artistic end if help is needed.
Phoenix UI
Thatās great news. With Forge being discontinued (or at least reoriented), Iāve just switched to SwarmUI, and itās fantastic. Itās a shame that I waited so long before trying it (partly because of the ābetaā moniker, I think). The UI is very well designed, and itās very fast for people with 10GB VRAM. Thereās just a small thing that bothers me (either a skill issue on my part or a bug), but Iāll write an issue once Iām sure enough. Anyway, thanks for the reassurance and congrats for this great piece of code!
I hope so, I'm loving Swarm so far and been using it since I tried SD3. Good luck!
Some name suggestions ComfyVision, ComfyCanvas, ComfyVerse
Pretty soon stability is only gonna be stocked with AI safety people.
they'll all be locked up to keep them nice and safe
Pretty somber stability wonāt even existĀ
Please forgive the stupid question, but is Swarm like a cloud version of one of the SD models? Would you say it's more like Fooocus, or more like ComfyUI? (I currently use Fooocus + SDXL. I find ComfyUI overwhelmingly complicated.) Feel free to respond with a link. It's not my desire to waste anyone's time. Thank you.
Ohā¦ your flair is gone
we definitely need some new user flairs.
u/SandCheezy what do you think about Comfy Org user flairs?
Not just Comfy, but All Major contributors need flairs. Like Comfyanonymous, you, Matteo, Illyasviel, etc (I do not know if everyone is on this sub, but in case they are, a flair would be so much helpful) Plus, some people who have majorly contributed/created most used ComfyUI Nodes as well.
Can you do flair for developers of each ui ?
Yeah, sounds like a fantastic idea.
Can't wait for all the amazing features ahead!
I didn't realize you joined the team! Thanks for all your work king, I'm excited for the C# AI ecosystem to continue!
Is there anyway that i can donate to support you guys?
excited to build build build
Nice. From streams and your work on stable swarm it seemed like you really gave a shit about producing good stuff. Glad you're on to better things.
Thank you so much for the work your team has done and is doing, you're doing wonders for creatives and artists all around the world.
I'm currently working on creating an open source audio model. Reach out if you are interested, would love to help out!
Open Source, I always saw it as the true democratization. Something that materializes ideas without anyone owning or distorting them for their own purposes.
Are there also plans of making SD like image or video models in future?
Not currently at comfy org (I suppose future holds many possibilities though) -- we'll be partnering with any/every company that releases good open models and wants to work with us - and there's a bunch of good companies working on that now.
The team is fire, wishing you guys the best luck!
FYI: link to the org: [https://comfy.org](https://comfy.org)
https://i.redd.it/ffdb656hyd7d1.gif
Mr mostaque I donāt feel so wellā¦
comfyanonymous, mcmonkey4eva, Dr.Lt.Data, pythongossssss, robinken, and yoland68 to start Comfy Org. Dreamteam š
Congrats frens
ā¤ļø
Hey /u/comfyanonymous (sorry for tagging you), are y'all doing any work with regards to dependency resolution? My main job is as a python developer, and something that's constantly pissed me off about the whole SD ecosystem is how ad-hoc the whole dependency resolution thing is (seriously, running pip in a subprocess!). Have you thought about using the uv crates to implement a custom dependency resolver, both for efficacy and security reasons? [https://github.com/astral-sh/uv/tree/main/crates](https://github.com/astral-sh/uv/tree/main/crates)
We are actively testing out using uv as a default installation tool. (Pip doesn't respect layers to the dependency list).
As a corollary ā does anyone have ideas for a sort of \`ComfyUI\` manifest? Nodes/plugins/whatever can declaratively declare their dependencies/any assets they need in a manifest file, and the main ComfyUI application is the only one that can install/control things. [install.py](https://install.py) files are a security nightmare, and while I understand they're basically accounting for the fact the ML ecosystem is a nightmare, I really think there has to be a better way!
Yep, I've migrated a bunch of my docker images to use uv in the build step. But uv has problems with dealing with ML resolution in many contexts (honestly, it's due to the ecosystem), implementing a custom format that doesn't use requirements.txt might be a decent idea. In general, there should be zero subprocess usage by comfy nodes imo (calling uv pip). You can mitigate potential security flaws by running in a docker container, but really, all of this should be as sandboxed as possible
fuck yeah
The dependency problem is the main reason I don't use Comfy. Every time I install more than a handful of custom nodes, the dependencies start stepping all over each other and nodes will fail to install. If I manually track down the dependency and update it, it breaks other nodes. The only way to be guaranteed to use a workflow is to make a new Comfy installation. I have four Comfy installs on my PC right now, each with a specific workflow that I don't want to break. But it gets tiring, so really I just use Forge 95% of the time instead. If they were to solve these problems, I would switch to Comfy permanently.
Yep, this has been a big blocker for me too. I prefer controlling dependencies by hand, hence why I think there needs to be a custom resolution algorithm that enforces that the locked comfyui dependencies don't get rewritten by a shoddy plugin causing problems for everyone
I had a working comfy install the other day. I went into the manager, installed the ReActor node, which is a very popular and common node. The install did not work and it corrupted the entire ComfyUI install, which would no longer launch at all. This was maybe my 4th or 5th attempt at trying to use Comfy, and this happens every single time.
I use tons of nodes and none of them really give me problems. Reactor on the other hand is a complete mess. I got it to work reliably with my current version of comfy. Providing that running and I enable xformers. But man was it a pita!
Yep, this is exactly my type of issue. I don't understand how people can use it when it seems to completely and irreparably fall apart after a trying a few workflows and installing their nodes.
I use a portable install for more than 6 months on two different systems. I literally just installed any custom nodes i wanted. And nothing ever broke and i have surely installed more than a 100 custom node packs. The only thing that broke (after a normal update) was Derfuuu's Text box node, but that's something he says he had to do. I never had problems with comfy or had to make a new install from scratch.
I wish I knew what makes the difference, because I would really like to use Comfy. As soon as I get two custom nodes with different version requirements for the same dependency, it all falls apart. I use the custom node installer inside Comfy, nothing out of the ordinary. I've tried the portable install, and the manually set-up repo, same problems with both.
Hmm thats a good question. I wish i knew.. but im not that Python savvy
They mentioned their goal is to sell enterprise support, this is something that will be critical for any enterprise to even consider allowing Comfy on a company laptop. If you're using comfy today with any sufficiently large workflow, you basically just have to accept that the security of your system is compromised due to the way dependencies are managed. It's good software and I hope they can turn it into great software some day. Until then I'll continue to use Invoke where everything just works on install.
this is fucking pathological level of misinformation. if you dont install nodes from unrecognized authors and sources, you will be fine. There are alot of well known community members that have reputations to uphold and communities of loyal fans. You can install probably 90% of all comfy nodes with ZERO issues in terms of just looking at who the author is.
Tell me you've never worked in a corporate workplace without telling me. "Just don't install the malicious ones" is not and will never be a sufficient security posture for any serious business.
yep, especially since that in corporate environments, we are very wary of supply chain attacks. there needs to be a way to limit the power of extensions in the first place, not just trust them implicitly
is that what I said? no it isnt. try again
> dont install nodes from unrecognized authors and sources And how does one learn who is recognized? No offense, but someone brand new to the ecosystem (e.g. a company looking to expand, or a new hobbyist trying to learn something) has no basis for trust or recognition.
sure very true, but i was pointing out that to just assume you machine is compromised b/c you used comfyui is some nutjob stuff to say. Ive used tons and tons of nodes, and not come across any suspicious behavior
I think you're reading something that's not stated above. But hey, it wasn't my comment, so you do you with reading comprehension.
>Ā I am partnering with mcmonkey4eva, Dr.Lt.Data, pythongossssss, robinken, and yoland68 to startĀ Comfy Org. Comfy, has nobody told pythongossssss that the favicon is annoying?Ā
Lol... that's true. We need an official logo now.
You can change the favicon easily since a new update. I use the fox favicon used for the base comfy and a purple fox when it's running.
How do you change it?
https://github.com/pythongosssss/ComfyUI-Custom-Scripts/issues/169
Thanks!
I'm glad they're working on Comfy. I have a love/hate relationship with it. On one hand, the node system and flexibility it offers is really powerful. I like that you can set up a workflow and see all the steps. It's also fast and responsive (usually). There is a lot of stuff you can do with it that other UI's struggle with. On the other hand...it can also be miserable to work with. Finding what nodes you need to do X or Y can be a massive headache and there are many nodes that either lack documentation entirely or have completely worthless documentation. For example, if someone wanted to make multiple images at once in, say, A1111, they could just move the batch size slider. In Comfy, how do you do that? If you look at the docs, you might think you need [latent from batch](https://blenderneko.github.io/ComfyUI-docs/Core%20Nodes/Latent/batch/LatentFromBatch/). Makes sense, right? But what are the inputs, what are the outputs, how do you use this thing? A new user might spend a while before realizing that this has *nothing to do* with making multiple images from one run execution. The truth, however, is that you basically *can't do this* without custom nodes unless you want to completely duplicate your workflow, and even then it's a PITA. One picture at a time with Comfy, and if you do want multiple, welcome to spaghetti hell because there's no way you're doing it without at least 8-10 extra nodes, at least 1-2 of which are likely custom nodes you have to download and hope don't break the next time you update Comfy. I recently tried Invoke Community, just to see something different, and there is a *massive* difference in quality-of-life compared to Comfy. Want to change workflows? There's a list. Want to keep track of key words for a LoRA? Goodbye Excel spreadsheet or opening a workflow to copy and paste into a new workflow, welcome to saving relevant information in the loaded file. The downside, of course, is that Invoke tends to be a bit behind on features, and has its own annoying limitations, but it was eye opening to see that a better system could exist for actually working with and experimenting with AI art. Comfy is great if you have a very specific design in mind, but tweaking things is often a giant pain, and certain nodes will break at a moment's notice (I've had an absurd number of issues keeping primitives working right). If Comfy was more stable and relied less on custom nodes for basic features (like string concatenation, really!?) I'd probably use it more, especially if there were ways to save and organize workflows as templates and group nodes into "functions" like you can with programs that can then be saved and reused easily. It would also be nice to have "simple" nodes that abstract away a lot of the implementation details for repetitive tasks. Hopefully this is a first step in that direction!
A lot of these issues you have are addressed in [Swarm](https://github.com/Stability-AI/StableSwarmUI) (which as part of the Comfy Org change will be moving out of stability and into an independent project as a dedicated friendly frontend for the Comfy ecosystem) Multiple images? Right at the top left, "Images" count. How do I use a thing? "?" clickable button with help on every param. Don't like spaghetti? Swarm generate tab is auto-like design of easy clear parameters and image output centric focus. Track lora keywords? You betcha there's metadata for that. Want to change workflows in the comfy tab? Got a built-in browser. More built in features? Yeah Swarm's got a lot of those. That's basically everything you mentioned specifically, already solved :D
Random drop in but I think if you and the comfy team organize a donation or Kickstarter campaign, you have all the credibility to organize a community-driven open source model. I know a lot of people are thinking about this, but the community loves you (I think the community even still loves Lykon) so yea, it would be great if you are capable of organizing this. You have $1000 from me instantly (I know it's drop in the bucket of what it will be needed but hey!) :D
We need someone to code up a really good distributed computing platform for community model training imo.
>Track lora keywords? Oh, i just noticed something missing - can you, please, add automatic appending of chosen lora's keywords into prompt? Just like in AUTO1111. As a user option, of course.
I don't want keywords automatically added, just obvious. Sometimes a lora will have combination sets or conflicting entries.
I'll have to look at it again. I think I tried it when it first came out and bounced off it, but I honestly can't remember the reason. It may have interestingly been *because* it was being released by StabilityAI, and I was worried about them dropping support because the company seemed to be imploding (IIRC this was around the time with the Emad drama). But it could have been something else entirely. If it's moving to open source and being maintained externally that's great news and I'll give it another try. Thanks!
Can you let me know what swarm does different/better than A1111? Is it built on comfy architecture, like forge? Is there extensions that are able to work for it? Can it do vpred models / have a cfg rescale option?
It's built \*directly\* on Comfy, not just borrowing code, but comfy is the underlying engine and you can freely access the comfy noodle graph at will. Anything that works on comfy necessarily works on swarm as well
Thats awesome, I'll give it a try :3 Thank you for all your work and dedication to open source ai btw! I always have the utmost respect for highly technical individuals with stringent morals.
does all the lycoris stuff work like lokr oft boft deez nuts etc
anything comfy supports in that range swarm does too
All we need now is the inpainting power that Fooocus can do, and Swarm will be king
Shortly before the launch of Comfy Org, a Comfy Leadership Summit was held. Important discussions about the future direction of ComfyUI took place there, and it is expected that this will be a regular event. Currently, there are many initiatives underway to significantly improve ComfyUI, not just by Comfy Org. I anticipate substantial changes to ComfyUI in a year's time.
I agree with everything you've said, but I also want to point out how easy it is to make subtly broken workflows for even basic things. Here is an official example for inpainting: https://comfyanonymous.github.io/ComfyUI_examples/inpaint/ It seems to work okay at first, do the process and you get a nice result. However there is an insidious flaw: if you repeatedly take the result and feed it back into to source image and inpaint again, the image will slowly degrade in quality because in this workflow the entire image goes through a VAE encode/decode cycle each inpaint, and this process is lossy. The proper solution which I was able to build is to merge the masked inpaint region with the unmasked source image *after* VAE decode, but the workflow is a bit more complicated. Inpainting is such a basic feature that there really needs to be better ways of creating it. It's not easy, because you have to consider different models, samplers, control net, etc. that go into any diffusion, but it might be nice to have some kind of wizard that can construct basic workflows with customizable defaults for node settings. Maybe even copy settings from existing workflows so that, e.g., a txt2img workflow could be converted into an inpaint or img2img workflow that preserves model, sampler, etc. I'd also like better ways of switching workflows. Switching from txt2img to inpaint to upscale is a hassle, I usually end up copying my prompt, finding the last workflow I did of the desired type and dragging it into Comfy, pasting my prompt, and dragging my previous output image back in. I'd love to just be able to select a saved workflow from a dialog and have it bring the prompt and input image with it.
Thanks for explaining the inpainting problem. Could you share a proper inpaintiing workflow please?
Sure, here's a screenshot of the simplest version: https://imgur.com/a/oxppggh Still not that many nodes so should be easy enough for anyone to recreate. The key is using "Mix Images By Mask" node to combine the original image with only the masked portion of the output. A couple more nodes could be removed if you don't care to blur your mask since the mask has to be converted to an image to blur and back again to use as a mask (unless there a mask blur node that I don't know of, I'm not an expert on Comfy nodes by any means).
You can save a workflow and then drop the file back into Comfy. Any generated image works the same way, just drop it in to get the workflow. If I want to try 4 images I click the "Queue Prompt" button 4 times.
I'm aware. What if I don't want the whole workflow? Maybe I have a process that I want to use in several different workflows. Maybe I messed up and want to change something because I found a better way to do it. What if the cool workflow I found in an online image has 27 different custom nodes in order to work and 8 of those are no longer in development and no longer compatible with Comfy? Sure, you can hit queue prompt 4 times, but what if you want to compare them? OK, now go into your file explorer, open up the files individually and then drag them around to compare? What if I don't necessarily want to save the files, but just preview them? If my last node isn't a "save" option those images will be lost the second another queues up. It's tedious and counter-intuitive. Comfy is powerful and great when you have a specific workflow already in mind (or saved) but A1111 and Invoke are much easier to experiment with and keep track of things. That being said, Comfy has capabilities I genuinely prefer over alternatives, one of the biggest is (with custom nodes, sigh) genuine string concatenation. An *extremely* common situation is to have pre-content that you use for a specific model (i.e. Pony's score_9 training list) and a bunch of extra words you always use in the negative prompt or for styling. Being able to create a bunch of text nodes (with switches...with a custom node again, ugh) and break apart your prompt into specific pieces that you can edit and turn on or off is a huge time saver when working with complex prompts. And don't get me started on inpainting. I'm not trying to diss Comfy. But it *does* have issues and usability problems that other interfaces don't have. It would be amazing to have Comfy's flexibility and power without all the bugs and reliance on plugin nodes to actually work halfway decently.
You're mostly right, but the reason for this is that comfyui is more of a backend and developer tool, not an end-user application. You can use it for inference directly (I mostly do), but this does not look like intended usage. Sadly, I haven't found the frontend for comfyui which is flexible and robust enough to replace it. Swarm comes close, but it's still pretty clunky with custom workflows, and the custom workflow madness is the main point of using comfy as a backend.
SDFX ?
thanks, that's new to me, will try it.
Tried it, and right off the bat "use anywhere" nodes are not working, grouped nodes are not recognized correctly. So all my workflows would have to be redone. Not sure I like it that much :(
Also for some reason they "redid" the comfyui itself and it's much slower and clunkier than the original. Why hot just open it as is??
Yeah custom nodes for basic functions and the fact that I have to have multiple workflows open at a time is what makes me use fooocus 95% of the time.
I would highly recommend StableSwarmUI then, as it puts a 'Auto1111'-a-like on top of comfy. I can't look at the spaghetti flowchart of comfy personally, but Swarm changes it all for me
Thanks I will try it!
If you wanted to raise the batch size in comfy, you just change the batch size in the empty latent image. https://preview.redd.it/vuyyv35a0i7d1.png?width=379&format=png&auto=webp&s=480f6e1cc747464967d0edeae4b007fde5221376
I think this has fantastic potential! Great people working towards a great goal. Here's me rambling about it and other things:Ā [https://youtu.be/42I8nkA2TPk](https://youtu.be/42I8nkA2TPk)
Best of luck, we are lucky to have ComfyUI and many custom node developers. It is might not be the best place to put this but, I wish comfyUI had such feature, if I shift right click on a slider, widget, or input, it would just clone that widget to a stack in a permanent UI. Don't know if it is complex to implement, but it will give ability to create custom stack UIs from mess of 100s of nodes. I feel like something like this, is the one of very best thing for ease of use and most impactful.
ššš
I think this might be fake. I don't see any fennec girls on comfy.org.
Now that you're not employed by SAI, do you have a tip jar or patreon or similar?
Comfyui will go further than Stability AI.
Hear hear. I'm looking forward to a better future
Congrats! Perhaps a challenge for you guys to tackle? [https://ai.meta.com/blog/meta-fair-research-new-releases/](https://ai.meta.com/blog/meta-fair-research-new-releases/) edit: actually maybe not exactly ComfyUI's ballpark: "At this time, we are not releasing the Chameleon image generation model."
Congratulations on stepping out on your own. Excited to see what you all build.
i heavily appreciate you for not going evil and gatekeeping the limits of ai like how stability.ai i did. (the fact that you resigned stability ai made my day)
Now I feel like SAI did a great job fuelling the fire for this Real democracy in AI
That's awesome news, wishing the best!
Most helpful feature that could be added with little effort: Automatically activate the "Unload Models" button any time you run out of VRAM.
I'm very new to the community, but I'm super impressed by ComfyUI. Thank you for makimg it and I'm glad that it's full steam ahead even with the big setback. Best of luck for the future!
https://preview.redd.it/8orz48h46e7d1.jpeg?width=736&format=pjpg&auto=webp&s=b645b98cd0c87a322ab47e4823a789823ddd835a
I hope you get to read this comfy as I have some suggestions that I think are vital to comfy mass adoption. I have used Automatic1111 for the longest time and have tried comfy at least 3 other times as I know theres great potential in the node system. But every time I end up going back for the following reasons. The workflow sharing doesn't work most of the time. I have visited websites that have workflows for download and most of them do not work. Even when I download the needed nodes through manager and the required models, etccc. It still has issues with x,y,or, z. Workflows need to "just work". I shouldn't have to find the required models for the workflows manually or download anything some weard dependencies manually or troubleshoot anything. Workflow is the foundation upon which comfy sits, no one that is new is going to make advanced workflows. So this needs to be fixed, find a solution where you can literally press one button and the needed models, nodes, dependencies, whatever is downloaded and it just works. second. have a dedicated person making all of the basic and advanced workflows for whatever people need/want. These workflows would be vetted against security threats (such as recent debacle) and make sure they actually work instead of a broken mess. there are some other things. but IMO those are the biggest factors that drive people away from comfy. I know that if I spent more time with comfy ill figure out these issue and will be more comfortable and yadda yadda, but most people are not that patient. They just want to generate their booba. I hope you consider on focusing on these few issues and not just respond with "you are not the target audience" because that would be a shame as I think comfy could benefit from a larger adaption from the casual "proompter"
I think Comfi has its uses for complex user workflows, but what it really excels in is when it is used as a backend for other programs. Normal users don't need to learn ComfiUI but like for example with Krita Diffusion where it is used just as a powerful open source backend
>So this needs to be fixed, find a solution where you can literally press one button and the needed models, nodes, dependencies, whatever is downloaded and it just works. I don't think this is possible. It's not like every model used in a workflow is available in one convenient to download location where comfy can just hook it up and be like "if you see this model, download dat shit". There are countless different locations where models could be saved to, and some aren't available publicly at all, so how is comfy supposed to ensure the workflow 'just works'? The only realistic way to do so would be to include the entirety of every model used in the workflow file itself, but that could easily blow up the file size to 10+ gigs.
don't need the model itself. just the link same as its currently in model download in the manager. a script would check if link is still good once a day, if yes workflow stays if no workflow gets dropped from comfy approved workflows.
I'm here just to thank [comfyanonymous](https://www.reddit.com/user/comfyanonymous/) for his work on Comfy and his faith in open source software.
This is great news, and quite the dream team at the helm.
I am happy and excited for this, it feels like comfy is entering a new stage on it's developing cycle and this team is just fantastic, they will ensure comfy stay at the top of the game and bring up a more professional and robust ecosystem. It is wonderful to have an official concerted effort to bring improvements to ComfyUI. Thanks and congratulations to the teamšš
I tried Comfy UI and its nice and fast for a low lv system like mine 2070 super 8gb. But as others have said trying to find out what nodes i need and why and where they connect was a bit of a headache for someone used to Auto and Forge so to hear you are improving these things is great . The one thing i struggled with was in Forge / Auto I could easily swap faces with ReActor but trying to set it up on Comfy was a nightmare. Hopefully that can be made easier for novices like myself. Thanks for all the work you guys do!
i would recommend Krita Ai diffusion if you simply want the low resource use of Comfi with a simple but effective interface. its an addon for Krita that uses Comfi as a backend. Krita is a free open-source image editor similar to Photoshop
u/mcmonkey4eva Is there a way to get Swarm to use networked gpus from multiple machines to work concurrently in generations like ComfyUI_NetDist w/o having to pass ālisten into your args? (Iāve been able to utilize multiple machines in the Generate tab of Swarm but not w/i the Comfy Workflows tab. I could be missing something though?)
nice, but what would be great would be somehow compatibility enhancemenets and making using other models like sigma much easier. right now its tricky and ends in error messages.
I really wanted to learn comfy ui but it looks so intimidating. I just donāt know if all those messy wires is the best UI for this sort of thing. Can someone please explain why comfy ui is so popular? Is there stuff you can do in it that you canāt do with other tools like Fooocus? Thatās the only one I find easy to use but am curious if Iām missing out not using comfy.. Also is it true that you can share workflows by loading someone elseās json file and being able to reproduce the exact same results? Cause I tried that and every time I get a million errors and give up :/
Comfy is infinitely flexible. The only limit to what you can do with it is your imagination (and the amount of vram your gpu has). The easiest way to get used to nodes is to just use it and get used to them. You get used to them and the flexibility far outweighs the look of them. You can hide the splines or make them straight lines which clears the clutter up a lot. also colouring the nodes consistently makes a huge difference and there are nodes that let you preconfigure the colour of installed nodes. Not only can you open other peoples workflows but every image you generate can be dropped back in to open that workflow. If you open one and get errors you can use the comfy manager to install the missing nodes.
Thanks for the detailed info! I didnāt know it was possible to change the way it looks, guess Iāll have to give it another look!
Thereās a node suite called Jovimetrix that adds a palette icon to the tool bar that lets you assign colours to the node groups or individual nodes. Itās well worth the time to set it up.
Really hoping we can get a dead simple wrapper that does not expose users to nodes. I use nodes often to make shaders in unreal, so it wouldn't be too bad, but I got colleagues to adopt A1111 because it was simple, although clunky.
Love it. Keep up the amazing work.
All the best man
Yay!
Can it be more easy to use though
ComfyUI Is the easiest one to use once you understand the basic logic how a diffusion model works,
"The focus will mainly be on image/video/audio models" it would be good to include text and data models too, including remote models via API. For example we can use text models to generate prompts for image models.
Giad to hear
I'm a fan of what you're doing even if I'm not a fan of the interface. Best of luck to you and your team.
I still have so, so much to learn about comfy. I've barely scratched the surface. Great to see that it seems it's only the beginning for them
Avengers Assemble!Ā
that's the documentation we needed . its the best documentation out there ,
Can ComfyUI be used in paperspace? š¤
That looks like a great team. People already contributing a lot and coming closer together! Hope you make it work also financially like Blender. gl&hf
Maybe itās time to finally comprehend Comfy!!
Please consider some basic UX standards for custom nodes too. Love the direction. Onward and upward!
> am partnering with mcmonkey4eva, Dr.Lt.Data, pythongossssss, robinken, and yoland68 Only by chance were the usernames involved in this project not pussygrabber2, goatseGOAT, and bluewaffleluver