Question about Max/MSP runtime

    Dec 01 2008 | 1:10 am
    I noticed that none of my midi controllers seem to work with a patch a build when I run it with the max/msp runtime. Everything works fine when I run it in the normal max/msp. Additionally, if I take the same patch, build a standalone app which creates .mxf file the midi controllers do work.
    Before anyone asks, yes I checked the midi setup to make sure all the midi inputs were enabled.
    Is this a known bug or limitation?

    • Dec 03 2008 | 8:38 am
      hmm..., weird. did you check your midi setting in max runtime? sometimes runtime has its own mind about audio and midi.
    • Dec 10 2008 | 12:30 pm
      On 1. Dec 08, at 02:10 , emajcher wrote:
      > Is this a known bug or limitation?
      definitely not a known bug or a limitation. We use a huge patch ( regularly and there are several spots in the program where you can "learn" Midi-controls -- these work reliably in the software in Max and Runtime mode, so unfortunately your problem must lay somewhere else. Unfortunately I have no idea what it might be, or where to look..
    • Dec 10 2008 | 11:44 pm
      Ok, next question, is there any advantage to operating in runtime mode over the standard Max? I was under the assumption that it was less CPU intensive but does it just lack the editing functionality because I could not find actual statement either way.
    • Dec 10 2008 | 11:49 pm
      There's basically no difference between a locked patch in the full version and the same patch in the runtime.
    • Dec 11 2008 | 3:05 am
      i wonder if anyone did a benchmark test on this.
      i think runtime is less RAM intesive, so if you have a limited RAM space, runtime may perform better.
      for CPU, i doubt that if there would be a notable difference... but i'm really curious to see a benchmark test on this.