The object is working for me here with the same Max version , newer OS (10.11.5).

Maybe re-download the object: https://github.com/JulesFrancoise/myo-for-max/releases ? Also, make sure there's only one in your search path?

Hi and thanks for the suggestions,

tried downloading it again and made sure only one exists in the search path. The problem persists, though. Never had this happen before.

This thread might be helpful for you.

Thank you for the link. I did all they suggest, with no results. Wondering if it is my OS that is too old, even though it should be fine.

Hmm, I can confirm this problem. It worked fine earlier in the day, but now I'm getting the same "unable to load object bundle executable" thing.

Which OS are you running Rodrigo? I think I may have solved the issue after running the patch on four different Macs. Even though Max for Myo is supposed to run on 10.9.5, it did not work on any of the macs with this OS. However, the ones running 10.10.5 or later had no problem with the myo.mxo file. I haven't been able to upgrade yet, but hope to do so in the coming days.

I'm on 10.10.5.

It managed to work after I quit and reopened the Myo Connect thing a couple of times. I didn't do any rigorous testing beyond that though. But maybe it has something to do with a 'port' type issue where it has to be available to load the bundle? I've only really seen that error when something is wrong with the compiled external though (or trying to run in 32/64 bit when it's not made for that)

Still having the same issues. It worked one day, then not the next. I managed to get it to work again by switching Max to 32bit and then back again, but it must have been a fluke as now nothing I do gets it working.

I actually implemented some cool stuff around the external doing quaternion to eueler angle stuff, with scaling/smoothing and tare-ing the orientation. I also like the fact that you have the ability to send haptic feedback to the unit, which I was planning on using for gesture recognition, but with this level of inconsistency, it's not very promising...

I've posted an issue to Jules' github, so hopefully he picks up on it: https://github.com/JulesFrancoise/myo-for-max/issues/2

I also looked at a bunch of the other alternatives and it's not great. There's samyk's OSC bridge which appears to be working, but only one armband and no unit feedback. https://github.com/samyk/myo-osc

I did come across this: https://www.youtube.com/watch?v=B5xCrtpwcQE

But no info as to download it and googling his name turns up nothing.

Has anyone else found a good solution for using Myos in Max?

Hi Adam and Rodrigo,

Thank you for your emails. I just uploaded a new release on Github (v0.1.2) that should fix runtime errors on OS X 10.8.

@Rodrigo: You are saying that the object throws a "wrong architecture" error from time to time but not systematically? In this case, it must be a problem with Max opening in 32 bits instead of 64 bits. I have the same issue sometimes when I open Max from a patcher or from the dock, it opens in 32-bit mode even though "open in 32-bit mode" is disabled. In general, I try to always open max directly (not by opening a patcher), and I double-check in the "about" window that max is running in 64-bit mode.

Also, Myo Connect needs to be running before you create the object, or the object won't work.

Best, Jules

Ah great, I'll take a look.

And interesting. I hadn't thought to check the about window, but Max seems to be opening in 32bit (randomly) regardless of what the "open in 32-bit mode" tick box is set to. (according to the Max window anyways).

Hi Jules, finally had time to download the new version and yes, it seems to be working! Thanks so much. Best, Adam