Skip to content
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

[Feature] Channel selector #50

Closed
dishmint opened this issue Nov 28, 2022 · 3 comments · Fixed by #85
Closed

[Feature] Channel selector #50

dishmint opened this issue Nov 28, 2022 · 3 comments · Fixed by #85
Assignees

Comments

@dishmint
Copy link
Owner

    Could be interesting to have agents for each color channel.  imagine sending out a green agent, where the seed image is preserved, but only the green channel is affected.

Originally posted by @dishmint in #42 (comment)

Choose which channels to apply filtering to. r,g,b or a.

@dishmint dishmint self-assigned this Nov 28, 2022
@dishmint dishmint added this to the ArcanePropagation App milestone Sep 21, 2023
@dishmint
Copy link
Owner Author

Or, grayscale the image and put that gsc value in one of the channels.

to keep the original image in one of the channels, and use the others to observe the propagation of the filter.

@dishmint
Copy link
Owner Author

An ArcaneProcess takes the pixel and applies the filter to all channels.
Might need to refactor ArcaneProcess that takes in a pixel, then internally can decide how to process the channels. Not sure how it would work with built-in filters like BLUR, maybe this is where mask() would be useful?

@dishmint
Copy link
Owner Author

What I really want is an overlay, so I can see the filter propagation on top of the original image.

Otherwise showing the filter on a single channel wouldn't actually demonstrate the affect on the whole image.

dishmint added a commit that referenced this issue Sep 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant