Aug 13, 2016
It’s funny how the process goes...the timing here just happened to be right so that when I came off the pole, the colors changed. It was a coincidence, but I liked the effect so much I ended up coding it in!
seen from United States
seen from United States
seen from United States
seen from United States
seen from United States
seen from Russia
seen from United States
seen from United States
seen from Brazil
seen from Türkiye
seen from Bangladesh
seen from Chile
seen from United States
seen from Australia
seen from United States
seen from Türkiye
seen from United States
seen from United States
seen from United States
seen from Türkiye
It’s funny how the process goes...the timing here just happened to be right so that when I came off the pole, the colors changed. It was a coincidence, but I liked the effect so much I ended up coding it in!
Meredith Burgess is where pole dancing collides with computer science. You might not put the two together, but for the Boulder woman, the combination of her two seemingly disparate passions has brought her to the largest pole dancing competition in the world.
So my project ended up getting coverage in the local newspaper! Sweet!
The link to this blog was mentioned at the end which is funny because I never brought that up and have sadly not been staying up to date here as much as possible.
Sooo gonna try to do that. Yea.
Been working as much as possible this past week, amidst circus and work madness.
Reworking detection to work on a gradient rather than just discrete values, as reflected by the color changes. This was hardest for the hand gestures, as there really is nothing built for in between gestures. While doing this I discovered my velocity calculations were all kinds of incorrect, so hopefully it’s more accurate now. Also trying to take account for relativity due to distance from the camera. There’s been a lot of hacky math going on in my notebook.
I also have started incorporating a particle system! Hooray!
Also, timing. It’s happening! The appearance of the squares is set to the musical tones at the beginning of the song. I’m going for a little bit less interactive with a few things just to make sure they happen no matter what. Gotta leave room for some error up there, I only get one shot. :/
A little stressed because I still haven’t done a full run through of anything yet. It’s very unlike my process to leave things up in the air. I like it locked down by now. I just keep telling myself I’m good at improvising and spontaneity is half the point of this piece sooo.... Agh! This is an experience all right.
Whoa!
I actually made all of my goals! It’s Tuesday and I already have all the detection systems I said I would by now. They could be more refined yes, but I’m still proud of myself. I have not looked into mapping yet. Will do for the rest of the week.
But! All this work gave me an idea. Give me a day and we’ll see if it works out.
I restarted some things, got a basic layout of an overall motion sensing/detection demo going. I got caught up in trying to figure out data binding for text for awhile. It seems straight forward enough with the sensor status included in the sample code, but once I got to the hands I became very confused. I decided since I don’t actually care about text showing up on screen, just feedback on hand state, I’d keep it simple with colored rectangles. If I wanted to I could probably make images that showed up with text in them. Somehow I think that’d be easier than data binding a string to a text box.
I swear to god, some things are so hard for no reason.
Tomorrow I’ll try to add in velocity again.
Back from vacation this week.
Feeling like I’m starting to understand this stuff a bit better. Set up some code that tracks left, right, upper, and lower extreme points, plus the average center point. Also figured out how to take the silhouette data and make it just an outline. I think this will open up some avenues. I don’t have to rely on the sketchy and sensitive kinect algorithms for finding specific body points, but can still use the outline and basic shape of my figure, which will be good for the convoluted movement I intend to have.
After my revelation yesterday I finally have silhouettes coming in unobstructed by background pixels (hooray little endian!). Working on some image transformations...I gave myself backup dancers! There are currently some memory leaks causing huge lags in my program. I never paid attention to lectures on memory leaks in class because I’d never encountered problems with them before. Derp. Guess it’s time to learn.
Going on vacation next week, but I’ll have my hands on a projector soon so I can start tackling the mapping of it all and seeing what it actually looks like on top of me.
Some developments with body index (silhouette) stuff.
I find the following things infuriating:
1. System.Drawing vs. System.Windows.Media.Imaging libraries.
Why are there two ways to use a bitmap?!? Do you know how difficult this makes googling shit?? “Oh, this says right here there is a MakeTransparent method for my bitmap...wait, nevermind, that is for the other type of bitmap”
Rage face.
2. Bitmaps in general.
Why the hell is it so difficult to take the human body data and JUST write those pixels in? Why must I have a background? I don’t know.
3. Canvases vs Viewboxes
Actually, just the GUI crap in general. So many options to display things. I don’t know which tool I am supposed to be using. The middle here is a viewbox. The right is a canvas. Getting the two to sync up in terms of size is insane.