I'm just going to
give you the gist for now.

Stereograms need to be somewhat simple to be effective so when
you're modeling your scene think simple big shapes and use depth
with strong foreground and background elements.

We are aiming to obtain something called a depth map.
Essentially, that is data that can be stored in an image where black
represents something at the very furthest point (height = 0) and white is the most near. (height = 1)

The trick to obtaining good depth maps for stereograms is to
adjust the Camera Clipping settings.(Clipping Start/End )
They are values you find on your camera object.
Make sure that the End: setting just barely captures your furthest
element without cutting it off. This will insure that your model
spans the entire range of values for the depth map.

Thus, objects will really 'pop'.

Next, you need to Use Nodes and set up something like this.

Basically, we run our Z depth buffer through a Normalizing vector node
and then invert that to obtain our depth map.
I used an output File node to pull it directly to a file, but you
need not do so. You can simply route it to the Compositor node
and hit the Render button.

It might take a bit of work to get the image just right.
You're aiming for a lot of shading variation like so.

Once you have that...
Run the openstereogram java project

And set Hidden Element to Depth map.
Set your file and click Generate.

And then try to see if it worked.
I must say I had to quickly get good at seeing these
in order to test my output.

Best of luck, and remember this is just the gist.
I'll be motivated to do a more detailed guide when
I'm healthy and thinking straight again.
... and who knows how many more months 'that' will be.
Sheesh.

I like this site because they tend to run statistical queries over
the population of data and tell me about the state of the human condition
in a quantitative sort of manner.(oktrends)

Regardless, I found a rather odd message in my inbox this
morning.

What the h$%^ll?
If this is spam it's pretty amazing spam.

Anyway, I trust this site a bit more given that,
"All four of OkCupid’s founders were math majors"
And their system for analyzing data is quite intriguing.
Regardless, it's a bit vague on the details here.

It says, 'top half of' the users.
The actual number might be slightly above average
I have no idea what the confidence interval or dataset size was.

*I'm perfectly fine meeting people in real life but I'm not about to
pass up any chance to find perfection in a world with nearly 4.5 billion choices.
Nor can this small town really provide the necessary selection. Double hence
wait for the movie. It ought to be a delight.

A few months is a long time to not be able to think straight.
Especially for someone who really enjoys being able to think straight.
And so it's all the more worse to be living through this.
And I do hope that it is through it because I'm not ready to accept
that this is how I have to spend the rest of my life.

I've been over all the hypotheses. I've been trying to narrow it
bit by bit. The most likely thing I can think of is my lung are still
just not 100% back from the abyss. Since the brain requires a lot of oxygen
any fall short of need probably manifests itself as what I'm feeling.
That would also explain why just moments after I awaken in the morning I feel
fine. And that's the only time I feel fine. I kiss those moments good bye
as soon as the day begins.

All my mental tasks are that much more difficult to pull off.
And since my job requires a high performing mind my work suffers.
And so I suffer.

Now, I have been keeping track. And I do know that from what i've ready it
takes between 1 and 3 months to really get over pneumonia. And I was sort of hoping
that my short week of clarity was going to last. But it did not.
It turned out to be a short blip in the graph.

And so I wait, in a purgatory with walls of broken alveoli.

Recorded today
By the Burning Sea

Version 2 (Ethereal)

It's a bit about being lovelorn but still thinking someone could
be out there.

Enjoy.

I've stepped up my production value as of late.
The mission was to spend whatever it took to get better quality
audio and cleaner mattes.

So far, I'm pretty excited about having my voice actually sound
like my voice for once.

This is all in preparations for a larger series of videos covering
compiling, blender, web dev, ray tracing etc.

Stay tuned.

I should probably take the time aside to say this.
I was able to take a simple .c file that had to include external
libs and things and configure it into a Xcode project with the cmake build system.
That means I'm now able to debug my project effectively in Xcode.
I thought it would take a lot longer but I'm glad it didn't.

I've got enough to worry about with this strange program output.
I seem to continually have an issue with my programs working... but
not quite well enough to be helpful. So I wind up with images
like the one you see above.

Basically, I'm processing a movie and the data you see is the location
of a pattern in the movie file that it's suppose to use to help track
the camera position. .. . Seems my program can't spot the pattern until
half way through the movie. And then it can't see it after that either
because the numbers aren't changing.

...When I saw this result I was debating whether or not the program had
actually worked....
I mean it proves that it has pulled of it's purpose at least once.

It's just that I need to find out why it's not spotting the pattern in
every frame.

Anyway, that aside I realize I'm aiming for 3 really big projects this year.
The Match Motion Blender Augmentation (this thing I'm working on now)
The realtime digital puppetry system and a proof of concept implementation of the
Construction Algorithm.

#
# Building a simple project that needs to include external libs
#
# Chris B Stones
# April 6, 2010
#
# Cmake build system
# 	http://www.cmake.org/cmake/help/documentation.html
# Function Documentation:
# 	http://www.cmake.org/cmake/help/cmake-2-8-docs.html#command:cmake_minimum_required

cmake_minimum_required (VERSION 2.8)
project (ctest)
set (Ctest_VERSION_MAJOR 1)
set (Ctest_VERSION_MINOR 0)

# Must ADD link directories BEFORE you add your target *shrug*

# Find Libaries (.a)'s
link_directories( /Users/admin/Desktop/ARtest/ar/lib )
link_directories( /Users/admin/Desktop/ARtest/ffmpeg/lib )

# Find Headers
include_directories( "/Users/admin/Desktop/ARtest/ar/include"
                     "/Users/admin/Desktop/ARtest/ffmpeg/include")

add_executable(test test.c)

# Must be after you define the executable
target_link_libraries(test   -lAR  -lARMulti  -lARgsub  -lARgsubUtil  -lARgsub_lite
                             -lARvideo -lz  -lbz2  -lavutil  -lswscale  -lavcodec  -lavformat)

If you have ever wanted to jump right into blender
development and have your own unique fun place to play
with your code right away.
This may be your answer.

That is if you can compile blender form source and you
want a little SPACE_TYPE playground to frolic in. And can
apply a patch.

I made this patch because I need to separate my code
for creating a space type and the work I'm doing for
Match Motion.

I thought it would be an insightful file for those whom
have a bit of background with source code.

Thus, review the code changes in this patch file and you'll
get some idea for what it takes to add a new SPACE_TYPE
in Blender 2.5.
Maybe it will take you less than the X number of days it took me.
(I had to painstakingly
figure it all out by hunting, testing changes, debugging, analyze revision histories... It took a few days really.)

But Lucky you. You can benefit from my time and hard work.

To instantly have a new space in which to write your own
code and make your own dreams a reality. Download and place
my patch in the /blender/ source directory and run:

patch -p0 < NEW_SPACE_TYPE_PATCH.txt

Then compile the source and voila!

Notes about my patch
1
The patch involves changes to 16 files.
M source/blender/blenkernel/intern/context.c
M source/blender/blenkernel/BKE_context.h
M source/blender/makesdna/DNA_space_types.h
M source/blender/makesrna/intern/rna_userdef.c
M source/blender/makesrna/intern/rna_space.c
M source/blender/makesrna/RNA_access.h
M source/blender/windowmanager/WM_types.h
M source/blender/editors/screen/screen_ops.c
M source/blender/editors/screen/area.c
M source/blender/editors/include/ED_space_api.h
M source/blender/editors/include/ED_screen.h
M source/blender/editors/space_api/spacetypes.c
A source/blender/editors/space_matcher
A source/blender/editors/space_matcher/space_matcher.c
A source/blender/editors/space_matcher/space_matcher.h

2
This patch is HACKISH and I don't claim that it's fit for anything
but helping someone to understand what it takes to add a
space type to blender 2.5.

3
The rna code is absent or wrong and there is no save/restore
code.

4
I had to put my name in there sporadically
so I could find all my changes later. It was quite a process
to figure it all out in the first place so I had a lot of changes
I was making and then un-making.

In other news... I got blender to compile with FFMPEG
turns out that if you try to compile with with FFMPEG you need
to compile it with SDL and openAL. So, I spent about 3.5 hours
getting all that to run. Finally, I was able to move on to
studying how to get AR talking to blender. I also managed to
cement in my head how to get Xcode to recognize new libs.
But more on that topic later.

Download the patch: new_space_type_patch