mhamilt

Last month Cycling '74 very kindly added my 

 to the Max Package Manager and to my surprise some people have actually downloaded it.

The Max Hardware Library was born out of my frustration that no creative programming application currently provides an easy interface for Bluetooth Low Energy devices. Hopefully others find it useful, but is is very much designed around the way I think both with Max and BLE, which is something I'd like to change.

At the moment the only avenue for feedback I have is via the 

, which I think may be raising the barrier of entry to give feedback and flag issues.

I thought it might be a sensible idea to carve out a small space on the Cycling '74 forums to make it easier for others to get in contact and open the floor to discussion a little more.

Any problems, feedback or points for discussion please add to this thread and I should at least get a notification in my inbox.

Last month Cycling '74 very kindly added my Max Hardware Library to the Max Package Manager and to my surprise some people have actually downloaded it.

At the moment the only avenue for feedback I have is via the GitHub repository issues, which I think may be raising the barrier of entry to give feedback and flag issues.

Last month Cycling '74 very kindly added my Max Hardware Library to the Max Package Manager and to my surprise some people have actually dow

max-hardware-library

I just became aware of your object as I’ve been trying to access data from the Waves NX head tracker. There is currently an app for Mac (NxOsc), but nothing for Windows. 

I got into a conversation on Facebook MaxMsp group about this, and someone mentioned your object but said that it works but it doesn’t have a WRITE feature yet, so the device has to be initiated in a separate app first for it to work. Is that the case? Is there a way around this? Will you be adding this feature? I haven’t had a chance yet to play around with it myself, so I’m still unsure how it works.

https://www.facebook.com/groups/983057392109423/permalink/1383383042076854/

I just became aware of your object as I’ve been trying to access data from the Waves NX head tracker. There is currently an app for Mac (NxOsc), but nothing for Windows. 

I got into a conversation on Facebook MaxMsp group about this, and someone mentioned your object but said that it works but it doesn’t have a WRITE feature yet, so the device has to be initiated in a separate app first for it to work. Is that the case? Is there a way around this? Will you be adding this feature? I haven’t had a chance yet to play around with it myself, so I’m still unsure how it works.

Writing to a characteristic is very doable. I'd initially left it out as I didn't have anyone to help shape the workflow and test, though 

. Writing to characteristics has only been implemented on macOS so far. If you have any suggestions on what you would like the process to be in Max, then let me know here, or better yet in the issue 

https://github.com/mhamilt/maxmsp-ble/issues/14

 . If the current workflow sounds good, great! I can start implementing it for windows (if you don't mind doing some testing)

Writing to a characteristic is very doable. I'd initially left it out as I didn't have anyone to help shape the workflow and test, though that has been partially covered. Writing to characteristics has only been implemented on macOS so far. If you have any suggestions on what you would like the process to be in Max, then let me know here, or better yet in the issue https://github.com/mhamilt/maxmsp-ble/issues/14 .  If the current workflow sounds good, great! I can start implementing it for windows (if you don't mind doing some testing)

I’ve tried using the ble object, and it crashes Max. I see on the GitHub page that it a known issue. Has there been any progress on this front? I’d like to implement this into my M4L device if I can get it to work reliably on Windows and Mac.

https://maxforlive.com/library/device/7669/headtracked-binaural-e4l-mod-of-master-bus

I’ve tried using the ble object, and it crashes Max. I see on the GitHub page that it a known issue. Has there been any progress on this front?  I’d like to implement this into my M4L device if I can get it to work reliably on Windows and Mac.