Through the looking glass, one subsystem at a time.

Y’all grok?

with 5 comments

Not to be greedy, but a comment or two today would be nice. It’s boring musing to an empty room. =)


Written by bzerk

February 16, 2009 at 7:44 am

Posted in Uncategorized

5 Responses

Subscribe to comments with RSS.

  1. Ok here is your comment 🙂 . So how OpenFramework is better than OpenCV ?


    February 16, 2009 at 7:57 am

    • OF is a C++ framework including a set of useful libraries, mostly oriented towards generative visualization, physical computing, etc. OpenCV is one of them. OpenFrameworks with OpenCV is better than Processing with JMyron or Processing’s OpenCV-derived libraries. I was just saying that I’m behind the curve in not using OpenCV. But machine vision isn’t what I’ve been focusing on. I just put Myron in to make a point. It just labels and numbers color blobs in boxes. It isn’t anything you can’t do by working directly with the pixel matrices, but like I said, not my focus. And I’m colorblind, so coding anything with color values confuses the hell out of me. And I haven’t made the jump to OF because I’m still building on the Processing sketch.


      February 16, 2009 at 11:36 am

  2. So OF is just another OpenCV middleware layer. I was hoping someone rewritten OpenCV with better API. IMHO OpenCV API as it is now is butt ugly. cvCreate/cvRelease for such simple thing as matrix multiplication, no operator overload…


    February 17, 2009 at 12:16 am

  3. I’d hardly say that it is “just” a middleware layer for OpenCV. More like a middleware layer that wraps a lot of APIs, and is suited for a particular development niche. I’m afraid that your complaints with regards to OpenCV go over my head. I haven’t touched it yet myself, am using JMyron, and am using it for nearly nothing at that. Proof-of-concept to demonstrate the principle of inline machine vision fused with other AR types. I’m looking at the CxCore reference, but I’m not savvy enough to understand why allocating the memory structures to do the calculation is a problem. Is it something that should be more or less abstracted? Is it a memory management thing?

    And call me what you will, but “<<” stuff annoys me when I’m trying to think with OOP abstractions and pointers and such already. I’m a wuss when it comes to polymorphism so far. I’m no pro coder, homey.

    And I don’t really know or really care about the most efficient way of doing what I’m doing right now. For machine vision I’d need to, but I’m not even using image analysis in the current branch. Somebody will rewrite it when it needs to be rewritten. Just a hack to drive my hardware.

    Clearly, I’m not somebody qualified to pass judgement on the ugliness of the API. Check out the OF reference, and let me know if there is actually another layer in there. I was under the impression that the mappings were literal, but haven’t looked yet.


    February 17, 2009 at 1:28 am

  4. LOL 😀 You totally got me off on a code tangent when I was supposed to be coming up with a generalist’s narrative on AR. I just had to ask for comments. 😉 Would love to continue the conversation in a couple of days, since it isn’t one that I can have off-the-cuff and intelligently, and I’m the distractible sort. I’m happy that your comment was one that got my nose into another reference I’ve been avoiding. Thank you.


    February 17, 2009 at 1:45 am

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: