Mostly scrambling to finish a paper, but this looks interesting…
From Intel Software Adrenaline:
And they have some nifty video to go along with it. Watch the volume though. It’s silent until the gunshots…
The addition of the processing might have an interesting effect on how effectively users get direction cues.
Not a good week for development.
The headgear is done, the divers are in, and I was ready to start doing a serious dive into the Java3D sound capabilities (as per Section 2 of the plan “Develop codebase for testing haptic rendering”). Then my father got sick and landed in the hospital for a week. Which kinda shot productivity to hell.
Anyway, I’m picking up the pieces. The (official) java3d.java.net site was down for most of yesterday, so I’ve only just connected to it again. So far I’ve downloaded and installed the AMD64 version of the jar files, hooked up my Eclipse IDE to the J3d-examples subversion repository (https://svn.java.net/svn/j3d-examples~svn).
The downloaded code compiles and runs as an ant file, but the structure doesn’t accommodate Eclipse’s code navigation for some reason. To fix this, I created a new Java project and copied the entire “resources” tree over and the tree that starts under “classes” in the original file. Here’s a screenshot:
This still didn’t compile though. I got an “Access restriction on class due to restriction on required library“, which I’ve never seen before. Poking around led me to StackOverflow, where there was this suggestion:
“go to java build path and under Library tab, remove JRE System Library. Then again Add Library –> JRE System Library”
Well, that makes no sense. It is just deleting and re-adding the system library. On the other hand, that’s exactly the kind of senseless thing that fixes weird errors, so I gave it a shot. Worked like a charm.
Anyway, now I’m having problems locating files that are right where the code says they are, but the loader’s can’t find them. Regardless, it’s time to go take care of Dad.
So I have this project that might be a really interesting, though somewhat dark excursion into CSCW. I’m not quite sure what to do with it, but when I hear things like this on Morning Edition, I really wonder if I just shouldn’t figure out a way to go all in. The question is – is a solution that winds up with fewer people getting killed in a war always better?
And here’s something that matters for this: http://securityledger.com/mobile-phone-use-patterns-the-new-fingerprint/. This is the paper the article references: http://www.nature.com/srep/2013/130325/srep01376/fig_tab/srep01376_F1.html
A few more useful links:
After a frustrating couple of days trying to get my Vantec USB Dolby 7.1 unit working, I gave up and sent it back to Amazon. Who, I must say, in their vast, impersonal way, really did a good job. The new replacement unit was on its way and arrived the day I sent the old unit back on their dime. Pretty impressive.
After letting the device sit in its box for a while as I worked up the energy to try something that I suspected would not work, I finally tried it this morning, and it works like a charm. Yay! Now I noticed something different, so it’s possible that the old unit worked fine.
When I plugged in the new controller, I happened to notice that there was a new icon in my system tray:
Clicking the icon brought up a tool that I hadn’t seen before:
Note that the System input seems to default to 2 CH, though 8 are available. More importantly, on the right side of the screen note that the “DSP Effect” seems to be getting 2CH data that it then sends to all the speakers. This was the behavior that I was getting that I couldn’t seem to fix.
Selecting “8 CH” in the combobox has the following effect:
After making that change, I clicked on each of the speaker icons in the lower right image and was rewarded by a synthetic voice coming out of the appropriate helmet speaker. Hooray!
Now this configuration tool must have been installed with the device, but it wasn’t mentioned anywhere in the documentation and didn’t pop up in the install procedure. It looks like you just have to know that it’s there. I guess that’s not surprizing, in that all these USB systems use the same chipset, made by C-Media, and they wrote the driver.
Anyway, I now have a functioning system. I need to play around with the best way to have the actuators contact the user’s head, but I think that’s the last remaining hardware task.
I’ve also finished getting the correct speaker lead to go to the correct amplifier, and cleaned up the wiring harness. Here’s a picture of the leads coming off the helmet:
I’m sure that no one would look twice at me walking down the street wearing that and four glowing amplifiers strapped to my back…
Today’s job was twofold – get all the speakers wired up and test everything as a unit, and if that works, get a cheap bike helmet to mount them all to.
Testing was a breeze – it turns out that Windows has a nice control panel for configuring speakers:
Anyway, everything works. The next picture should be looking something like Rick Moranis in Ghostbusters:
Ok, I’ve got the actuators mounted in the helmet and they work pretty well. The only problem is that the Dolby until is locked into stereo mode and I can’t seem to get it to think that it’s 7.1. Sigh. Guess that’s the problem for tomorrow…