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

Give PixyMon a graphical editor for color signatures. #24

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

jessecrossen
Copy link

This PR adds a dialog to PixyMon which maps colors from the incoming raw video onto the UV plane and allows drag and drop editing of color signatures as rectangles in UV space. This allows for more precise visualization and editing of signatures. I'm happy to make adjustments or correct any areas where I haven't properly understood the "pixy way".

The UI is fairly straightforward, recognizing the following gestures:

  • Drag the middle of a signature box to move it.
  • Drag any edge or corner of a signature box to resize it.
  • Drag on the background to create a new signature.
  • Click a signature box and press delete or backspace to remove it.

To simplify control of the signature area, when a signature is edited in this dialog its range is set to 1.0 and its (u,v) mean is placed at the center of the box. The range can later be adjusted as normal, but there's less need to do this when you can precisely place the signature area itself.

Changes are previewed in real time, and the dialog buttons have the same meanings as the ones on the config dialog. I've included a screenshot below:

sigedit-1

@richlegrand
Copy link
Contributor

nice --- thanks so much Jesse! We'll take a look....

Are you working on anything else? (just curious...)

thanks!
--rich

@jessecrossen
Copy link
Author

@richlegrand I'm looking into some small spatial accuracy improvements, but that might reach into the firmware, which I'm unlikely to compile until it's possible with gcc. I have only a vague understanding of the blob algorithm so far, so I'll need to do a bit of reading before finding a direction to go in. Honestly, I'm just trying to make pixy work better for my application, which is a MIDI drum sequencer controlled by colored ball-bearings on a turntable.

@richlegrand
Copy link
Contributor

Hi Jesse, note, we have a gcc version of the firmware here:
https://groups.google.com/forum/#!forum/pixy_firmware_sdk (you can request
a membership).

Happy to help -- let me know if you need anything.

thanks,
--rich

On Tue, Jan 19, 2016 at 8:25 PM, Jesse Crossen notifications@github.com
wrote:

@richlegrand https://github.com/richlegrand I'm looking into some small
spatial accuracy improvements, but that might reach into the firmware,
which I'm unlikely to compile until it's possible with gcc. I have only a
vague understanding of the blob algorithm so far, so I'll need to do a bit
of reading before finding a direction to go in. Honestly, I'm just trying
to make pixy work better for my application, which is a MIDI drum sequencer
controlled by colored ball-bearings on a turntable.


Reply to this email directly or view it on GitHub
#24 (comment).

Charmed Labs
www.charmedlabs.com

@jessecrossen
Copy link
Author

@richlegrand Awesome, thanks!

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 this pull request may close these issues.

2 participants