It's Mira Time

    Today we released our first product in the app store, officially known as Mira Controller for Max (but hereafter referred to as Mira). It works on any iPad and we’re selling it for around $50. A couple of years ago, we contacted the main developer of Mira, Sam Tarakajian, on the basis of his creative tutorials that I highly recommend you check out. We asked, “Dude837 -- if that’s your real name/number -- what would you want to do?”
    Sam expressed interest in something mobile.
    Mira is the result of a long conversation about the process of using mobile devices with Max. The result of this conversation is the simple idea that your iPad should just give you back your patch. (It’s yours after all.)
    There’s no separate UI to build, no OSC messages to deal with, no networking to configure (OK, sorry, it’s networking, there will always be something to configure).
    The initial release of Mira is aimed at people interested in creating new Max projects with mobile control. In addition to the iPad app, there is a package of Max objects for our recently released version 6.1.3 you’ll need to download. The process is simple: you arrange UI elements (sliders, buttons) on top of a new object called mira.frame that represents the screen of your device. Every mira.frame in every patch gets its own tab on the iPad. In the coming months, we’ll be adding more Max UI objects and optimizing Mira support for Max for Live users.
    There’s a lot more going on here than I can explain in a few paragraphs. We’ve made a couple of videos for two perspectives on the Mira workflow. Internally we’ve been referring to these as the East Coast and West Coast videos. See if you can figure out which is which.

    Alex and Leslie Play with Mira

    Introducing Mira for the iPad

    To learn more about Mira, head on over to the app store or check out our Mira product page.

    • Jun 21 2013 | 12:33 pm
      Exciting. I'm looking forward to using it with Max for Live.
      mira.frame appears not to work in Max 6.0 (and hence not with Live 8). Can you please confirm/deny this before I rush out and upgrade to Live 9?
    • Jun 21 2013 | 1:02 pm
      Yes. Mira requires Max 6.1.3, and Live 9 for M4L usage.
    • Jun 22 2013 | 5:00 am
      I already own M4L 5.1.9.
      Is the version of M4L that comes with Live 9 Suite any different?
    • Jun 22 2013 | 1:21 pm
      Live 9 Suite requires/authorizes Max 6.1 for use within Live. So, yes, you would need to have Live 9 suite to use Mira in M4L.
    • Jun 23 2013 | 2:22 pm
      Max For Live without the suite also requires/authorizes Max 6.1 for use within Live. So, no, you would not need to have Live 9 suite to use Mira in M4L.
      (There is no difference between the Live 9 version of Max For Live and the Live 9 Suite version of Max For Live)
      Meanwhile, Live 9 is only a requirement if you don't also own a non-m4l license of Max/MSP. Which, granted, is most users. (Live 8 can be configured to run any version of Max that you've paid for separately, but will only bypass the "paid for separately" for Max 5. )
    • Jun 24 2013 | 12:28 pm
      Does Mira currently work with the M4L Step Sequencer? A comment was posted in another forum that Mira couldn't display patches with sliders. Is that correct? Any other limitations with respect to M4L devices in Mira?
    • Jun 24 2013 | 2:03 pm
      live.step is not currently supported. There are several sliders that are currently supported with mira including multislider and slider, so a mira interface to live.step could be hacked together, but it would be better if mira simply supported live.step.
    • Jul 12 2013 | 1:05 am
      I hope the umenu object will be integrated soon