There is a word for smell (like when we smell roses) and a word for taste (mmm… ice cream). But there should be a word for the combination of them. As I have identified the deficit, I will use smelltaste until someone gives me a better term.
There are times when the smelltaste is exceedingly different from the smell or the taste of something. Take Japanese sake as an example, if you smell good sake, it is often floral. If you drink it, the tastes ranges but is often fruity. If you take a whiff and then a drink, it tastes like tears of happiness. Errr… I mean it is a combination of fruity and floral that reminds me of honey without sweetness (yeah, I know that makes no sense, but still).
On the other hand, if you sample the smelltaste of cheap whiskey, it is a sinus burning phenomenon followed by coughing pain.
As much as I love champagne, its smelltaste is not often as good as its taste (which, I think, is why I like the less yeasty, less scented sparkling wines).
When you want to learn about an alcohol, one of the first things you need to figure out is if it should be tasted or smelltasted.
Fresh-baked chocolate chip cookies and hot coffee are two items that are almost all smelltaste. The smell can be wonderful but the taste by itself is not as good as you might expect (yes, I did just give you an excuse to make cookies this afternoon, its for SCIENCE).
I got to thinking about this last night… while neither the smell nor the taste is reminiscent of anything particular, the black licorice smelltaste of Pastis reminds me of my childhood.
I mentioned that I’m working on a Raspberry Pi project with video. It wasn’t going well.
I started with Python + SimpleCV because it looked easy and fun but then determined that frame rates of six frames per second would make it hard to show moving things. So I went a more native option: cross compiled C with OpenCV.
The problem with this path is that it feels like work.
While I strongly believe in life outside tech, I do some personal engineering-related projects. I consider the podcast my main personal project. But Element 14 has graciously been sending me hardware and the occasional check to write for them. This arrangement lets me learn new things and share my enthusiasm. It is pretty cool (zOMG, you guys, they pay me to goof off! If I whine enough, they send me even neater hardware! This is such a scam!)
But I do have a day job. Oh, don’t get me wrong, my billable hours are not totaling anywhere near 40. But I could be gardening, reading a book, writing a novel, designing my Halloween costume, or painting the ceiling; I could be doing other amusing things but I’ve opted to work on a technical project because I find it interesting. Getting paid is nice and directs my (often scattered) attention but it is not a large portion of my income (thus it is not motivation enough).
Having a project lose the joy of discovery and become a grind is not good for its prospects of completion. (Though I am excited about the end widget. But maybe it would be easier to do on my laptop. But then it isn’t embedded. Maybe there is an 8-bit microcontroller out there that needs me to do something with it. You know, my Halloween costume is likely to be pretty technical…)
Doing a project in Python on the Raspberry Pi is fun: hack it together, do a little experimentation, call it done enough, maybe revisit in a few weeks. But it didn’t work, too slow. And then cross compiling and C felt workish, especially the starting over part. I actually had some things working in Python. I fought the evil of Linux video drivers. I learned about computer vision libraries too. It was fun in Python.
It was less fun in C. Though, realistically, I haven’t gotten to do much C, mostly build nonsense. But SimpleCV looks friendlier than OpenCV.
Imagine my disappointment to read that I can only expect ten frames per second in the C+OpenCV version. I don’t know how I missed that. It seems impossible. There is rasppivid video that is 30 fps, why can I get to something like 25? Oh, I know there is hardware acceleration and blah. blah, blah. But I want it. I want it more than they do. (Hey, you did read my Guardians review, right?)
So now I’ve found a different Python package, one with better Pi Camera integration. It is even linked from the Raspberry Pi Camera page. (Was it there before and I missed it? The idea of that makes me feel slightly insane. I looked around A LOT for Pi Camera stuff before deciding to leave Python).
The Camera Modes documentation shows some high frame rates. The text later talks about all the interesting ways users can mess that up. And there is a section for rapid capturing and processing though I wasn’t clear that I could display them too. It would be interesting to try.
Ok, I think that, yes, I am going to restart the project but back to Python. All the paths are frustrating. But Python has the most potential for amusement and the chance that I’ll get beyond fighting tools and back to playing with gear. I hope.
I’ve seen Guardians of the Galaxy. Twice.
I was excited about the movie, I loved the trailers, even the teasers. I was pretty sure they’d taken all the good pieces and left the movie bereft of jokes. I was wrong, happily, happily wrong.
I’ve been trying to figure out why I adored GotG so much. Was it the really good plot? Was it the awesome number of quotable lines? Was it the fact that they had that meeting I have had at least once a week where a decision was made and then someone said “what? I wasn’t listening. I was thinking about something else”? (That is officially called “draxing” now, so you know.)
I love the point where one of them completely embarrasses himself, just to stall for a bit of time. I wish I was that brave. And I don’t know why I wouldn’t be. Embarrassment is not fatal. I love that he had the faith that his team would fix it.
It made me happy that at the end of the movie, the characters were relatively unchanged, except they were happier, more confident.
Let me recall my review of Thor (the first one). I could have sworn I posted a review of Thor here but can’t find it. Anyway, I thought Thor was a good movie but I found it difficult to watch. At the beginning, Thor is happy: happy to be a prince, happy to be a warrior, happy to be Thor. Then he get tricked, loses his hammer, falls in love, saves our world, goes home a man burdened by responsibilities, a dysfunctional family, and a long distance relationship. The movie was a story of a boy maturing to a man. He grew up and growing up sucked.
There is (or should be) a point in growing up where you have all this freedom and potential and energy: you can save the world and you want to but you don’t have to. It is a wonderful point. I remember the night after high school graduation as being fairly incandescent with possibilities and lacking in responsibilities.
There have been other points like that but, more often, the reward for a job well done is a more difficult job. That’s good but can get exhausting, even damaging as the difficult job becomes impossible.
There was none of that in the movie. The reward for a job well done in Guardians was the gratitude of a planet, a rebuilt space ship named after an 80s celeb, a new family, and a galaxy of possibilities.
If I could watch any movie this afternoon, it would be GotG. Again. It made me happy.
I just cross compiled an application for Raspberry Pi: camcv combines the Pi’s camera program raspivid with OpenCV.
It took hours and hours. Not just to build the cross compilers (though that did hours) and figure out cmake and figure out what code I needed, it took hours of tweaking and fiddling to make it work.
I suppose now I’m supposed to write up how I accomplished it, so you can reproduce it, glossing over the tricky bits and making it sound like a walk in the park.
First, I must give credit to
- Kitware for the lengthy, detailed and mostly still correct instructions on how to set up cross compiling for the RPi
- Stuff about code for (native) compiling raspivid
- ThinkRPi for the exhaustive (but native) write-up of OpenCV and Pi Camera
- ThinkRPi’s commenters for their suggestions for OpenCV & Pi Step 3: create you own project
Well, and to be fair, I’m still at Step 3 of OpenCV and Pi Camera’s instructions (of 7 (and a half)). I finally got the program to compile but I have a new Raspberry Pi board and haven’t even powered it on. Oh heck, if I’m reading step 4 correctly, I haven’t actually managed to pull in OpenCV.
I had this neat plan for what to do with the Pi, a camera (two maybe!), and a small display. But I’ve been so battered by compiling something that already existed and isn’t even really what I meant to compile anyway.
I find that many Linux projects have this exponentially expanding scope. My initial initial plan was to play with the camera in python using the actually pretty simple SimpleCV computer vision tools. But it was horrifically slow (a known issue to people who have tried the python and camera but a new issue to a newbie like me).
Worse, I don’t know cross-compiling has been truly worth it. Is multiple hours of setup worth many times two minutes of recompile time? Also, the RPi Compute doesn’t have an Ethernet port so it isn’t as easy to set up a tftp that would all my device access to the cross compiled executables without even a scp copy.
So I’m not going to give you the “here’s how I did it”… I’m not even sure how to post my trees. And I went through so many strange turns, I’m not sure my results will be useful (“and then at step 1123, spin in your chair, clockwise three times, the next cmake .; make instruction will then work”).