Razer hydra

Small update

I have managed to get the x vector out of the hydra, using midiparse and this midi learn subpatch made by mr_mapes that I found on the forum;

https://cycling74.com/forums/gui-objects-wishlist

btw. thanks mr_mapes :)

But I can only get one control parameter, if I try to have two midilearn subpatches (differently named (saved)) then I always just get the same parameter , using the midi app from sixense

I cant understand why they would build a midi app for such a precise controller (Why not OSC or just HID) - midi sucks balls :)

`
mr_mapes subpatch:

Hi Edsonedge,

Sixense recently published a tutorial video for setup of the MIDI app on youtube. As I am unaware of the linking rules of this forum I'll have to ask you to Google "sixense MIDI app setup", this should yield the video as the first result.

If you have any additional questions or need further assistance please post on the Sixense forums, we'll get one of our MIDI app specialists connected with you immediately. Thanks :).

_________________
Dan Paullus
QA/Production Manager, Sixense MotionCreator
Lead Production Artist
Sixense Entertainment Inc.

thanks for the reply

Yeah I did see the video before - and made it work with massive

If the Midi specialist can help to get this to work in max, thats well appriciated

But midi vs OSC is sort of what VGA vs HDTV is in sound controller terms. The one parameter (x position) that I got to work proberly in Max - still I was getting just 127 steps - and with a controller that has the range of over 2 meters, with 1 mm precisioan accuray, I could use those extra steps

Just saying, it would be awsome if you could take the raw data from the SDK and pack it into OSC (I would do it myself if I had gotten passed page 100 of C++ for dummies)

all the best

Hey there, I'm the guy who wrote the Sixense MIDI app. I'm going to take a pass at getting it working with OSC, are there any Max samples or documentation you could point at to help get me started? There doesn't seem to be much in the documentation about it.

Awsome! thanks alot :)

If you want to make an external for max I guess you need the Max msp SDK

https://cycling74.com/products/sdk/

But maybe it is simpler, and more generally usful just to make an OSC exacutable with the Razer Hydra SDK and a library such as this: http://code.google.com/p/oscpack/

If the motion paramters and trigger floats, along with the button int´s can be packed as OSC and sent out as data to 127.0.0.1 on a specific port, then the Hydra can be used with loads of programs (not just Max but also PD, Proccessing, Supercollider and many others) and it is real easy to get a feed of the data using the Osc-route object http://cnmat.berkeley.edu/patch/4029

Thanks again :)

Oh and P.s dont forget to include the Analog sticks as OSC messages - they could be very usefull I think

Thanks, that helps a lot. Should I define my own messages like /sixense/joystick/x and /sixense/position/x or are there specific messages that Max is expecting?

I am pretty sure you define them yourself

then one just writes in the osc route object a "/" followed by a defenition of each parameter (that is what you define them as)

Here is an example of a OSC exacutable someone did for the emotiv BCI headset

http://www.emotiv.com/store/apps/applications/119/1446

and here is an example Max patch for it

Here is a picture of the patch if you dont have Max