-
-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Potential enhancements for points editor #97
Comments
I have thought of all that, what's limiting me is my lack of JavaScript skills, everything I've done I've had to learn first as I have no previous experience. For the bg_image you can already use copy/paste with it so it's not that much trouble to just right click on an image, copy and paste it in. Alternatives I've thought of is possibly grabbing the image from the Loader node as it (or link to it) should be saved in the Loader node by same virtual link. I kinda wanted the results of the segmentation to be shown in the editor too, but that would make endless loop with how ComfyUI execution is setup... not sure how to tackle that, at least without more JavaScript. |
Negative points should now be in, also made the normalization a boolean rather as it's cleaner. |
Two more enhancement ideas: Ability to scale the size of the points editor node without losing functionality.
Ability to pull a specific frame from an input video.
Brilliant work! |
Shift+ left click for positive, shift+ right click for negative. |
I know it's still very early in development, and having tried it with your ComfyUI SAM 2 implementation, here are some thoughts I have that would help for that use case. I don't know where you plan to go with the node so pardon me if you have already considered these points and are already working towards something similar or have ruled them out for one reason or another.
I'm also not opposed to trying my hand at implementing some of these thoughts but I'll wait until its less work-in-progress. Regardless, really appreciate the work you're doing!
The text was updated successfully, but these errors were encountered: