Could I replace o.message and o.prepend with Max default objects?

    Jun 16 2017 | 7:43 am
    Hi, I am wondering if there is a way to replace o.message and o.prepend with Max default objects, as it helps Windows users to open my patch.
    This is the patch I would like to modify.
    Many thanks,

    • Jun 16 2017 | 10:28 am
      Can't you simply connect your number to [prepend /sine/sine67/pan ] ?
      If your OSC message depends on #1, #2, etc., arguments then you could use [combine #1 #2 /pan 1] to create the message.
    • Jun 19 2017 | 6:07 pm
      Thanks a lot for your advice.
      I just tried out your approach, but it seems not working as you can see in this screenshot.
      Comparison between prepend and o.message
      Comparison between prepend and o.message
      It seems o.message does something more than simply prepending. The help file of o.message says 'o.message behaves like the standard Max message box except that it converts its data to OSC packets.' I am not very sure what this means in practice.
    • Jun 19 2017 | 9:49 pm
      i'm not sure but if i remember correctly, udpsend by default is supposed to convert messages to OSC packets, so you should be able to send full OSC packets this way (you would'nt see it inside Max). But i'm not sure. It's something to test.
    • Jun 20 2017 | 7:40 am
      Vichug is right, udpsend will send the OSC messages correctly. There are some explanations in udpsend's help file (CNMAT compatibility tab).
    • Jun 23 2017 | 3:40 pm
      Thanks a lot.
      I just read the CNMAT compatibility tab of udpsend's help file . Do you know what 'FullPacket' message is? In what situation do we benefit from that, compared to using only Max standard objects?