Experimenting with augmented reality and Max

    Feb 12 2021 | 9:07 pm
    I want to explore augmented the idea of integrating Max and an augmented reality platform like Magic Leap.

    Magic Leap | Demos: Everyday Magic with Mixed Reality

    Ideally it would be awesome to be able to create a jit.world with objects in it and send it to the Magic Leap device and see the jitter world around you. Or be able to place interactive musical interfaces in the augmented reality space. I also envision instruments like Reactable being shared by multiple users wearing a Magic Leap devices
    https://www.youtube.com/watch?v=0h-RhyopUmc My question for Cycling74 and developers is what are the ways that third party apps can connect to Max? Can you create send 3d objects or matrix data across TCP/IP to be rendered on the Magic Leap device? Likewise any interaction in the Magic Leap world would be conveyed to Max. Is this the way Mira does things on iOS or is there a better way to do this?
    Thanks, Anthony

    • Feb 16 2021 | 5:26 pm
      Any ideas?
    • Feb 22 2021 | 5:06 pm
      Okay let me rephrase my question. What is the best way to send data from Max to another app (iOS, or VR Headset)?
    • Feb 22 2021 | 5:51 pm
      OSC is the only thing i can think of (ha, i have been thinking of answering this here for days, but didn't because i don't know anything about VR or this particular platform you're using...) i've been learning Unreal4 lately, and prior to that dabbled in Unity, and to get data of any kind from Max to these two environs, it seems the only way, other than creating your own file-protocol and developing your own bridge between Max and the platform(or using some 3rd party stuff, that probably doesn't even work with 3D/CGI environs but deals more with streaming audio/video or a set frame-by-frame capture of something... with all the problems of dropout which accompany that type of system), is to send OSC... this probably means you wouldn't send the exact visual data, but 'specification data' for the platform to render something similar. i don't know much about the current capabilities, though... i feel like the .OBJ/.DAE/.FBX file formats are actually small enough that it would be easy to send across a network, but i've not seen anything like this used anywhere(i think i probably don't understand how complex those objects can get, too: i do notice when creating face-groups to color different parts of an object differently, the size of a .dae file can increase, even though the polygon-count/shape was never changed).
      ๐Ÿ‘†all that to basically say, i have no idea ๐Ÿ˜‚ (but hopefully at least offered some food for thought and bumps the thread for others to chime in)
    • Feb 22 2021 | 7:20 pm
      texture sharing via Syphon or Spout, and matrix sharing via NDI are also possibilities to explore for inter-app communication.
    • Feb 24 2021 | 8:23 pm
      Thanks guys for feedback, I will research these options.