Xbox Controller Interface

Hi! Any pointers on doing something similar for the Xbox One controller?

Thanks :D

Scratch that, this does! You should add Xbox One to the tags, thanks so much for sharing this!

Hi! Thanks, it looks so useful.

I'd like to purchase a controller and use it with your patch. I got a question :

Which model should I buy now in 2017 to work with it ?

Is it working as well with generic controllers ?

Thanks!

Hello, I'd love to try this, but unfortunately the file is missing... Too bad! :p

Hello!

Is there any chance this would work on MAC OSX? If not, would there be an easy way for me to make this happen? Thanks in advance.

Hi this is great!

I can't seem to get it to work with an Xbox One controller. Having read further up the comments it seems that people have got it to work with their Xbox One controllers, am I doing something wrong??

Thanks

Hi, everybody I'm a total beginner on jitter, so I'll try to be as clear as possible. I want to map the joystick keys to trigger some premade vizzie objects. Let's say I just want to control the crossfade between two videos with the left trigger of the controller. How can I do this?

Doing this is similar to any basic Max patching question. You need to know three things (one of which you already know, if you're at all familiar with Vizzie).

1. What range of values doe the XFADR module in Vizzie expect to work with. Answer: floating point values in the range of 0. - 1.0.

2. What range of values does the joystick controller put out? You can check that out by either looking at the patch itself, or by sticking a floating point number box on the output.

3. What Max object or technique can I use to convert the output range of values from the video controller part of my patch to the 0. - 1.0 range that all Vizzie modules expect for data (Hint: the scale object)?

That's it, basically. Good luck.

Thanks a lot, Gregory! Trying to figure out now a bunch of new stuff :)

I have this driver installed to connect the xbox controller to my macbook. The hi object recognizes that the controller is connected but won't read any input from the controller. Any ideas on how to get the hi object to read from the controller on a mac?

I've noticed the rt and lt controls are indexed with the same number, so if you hold both triggers down [hi] outputs the same value as when both triggers are up. Is there any way to distinguish the right trigger from the left trigger?

Hi, I'm taking a look at this in response to some support inquiries. I'm currently trying a recent Xbox wireless controller (Series X/S) with the macOS version of 'hi' (and without the 360Controller driver, which doesn't work with this controller). It's working fine and all of the controls are registering uniquely and providing data. Are the reported problems ONLY with the older 1708 controller via XINPUT? Or only on Windows? Thanks for any info you can provide.

Hi @Jeremy Did you make any progress on this topic since last year? Apparently the triggers problem is specific to Windows (according to this thread), and several, if not all xbox controllers are affected (same issue with a Xbox One controller connected trough USB). Maybe a workaround could be to use another driver than the one provided by default by Windows, but I don't know how to do that.

We added an XINPUT mode to hi a while ago. Have you tried it?

I wasn't aware of this, no. How do you switch mode? Maybe I missed it because I'm still on Max 7...

Sorry, it's Max 8 only (grab the demo if you want to try it). I can't remember the syntax offhand, but it's probably something like 'xinput N' where N is a device id from 1-4.

Ah yes thanks! Just found it was added in 8.2.0. Well, that's one more reason for me to upgrade. Will wait for the next deal! For now I found a workaround with a custom xbox controller driver.