Pack without Element 1 to Bang

    Aug 21 2018 | 7:33 am
    Hi Guys,
    I have multipul Dials that need to be sent as one list and then output'd as the list again. However when changing for Example dial two, you must send a bang through "Element 1/Input 1" for Dial twos data to go through.
    Is there a way I can pack items into a list without having to use Element 1 as bang? And just have them all bang?
    Sidenote: I realise I can attach a button as well on each other input but this messes up a-lot other variables in my patch.

    • Aug 21 2018 | 8:00 am
      try pak hth zzz
    • Aug 21 2018 | 10:26 am
      Hey Cheers Mizu!
      However is there a way to remove Bang completely? I will be using buttons after the unpack and unfortunately this will trigger them, when they aren't supposed to be.
      I attached another Version if this makes sense. Basically whenever I use another dial, it sends a bang or signal through to the unpacked button.
      Basically I want to combine a bunch of data send it as one signal and then unpack it at the other end and use it exactly the same as it goes in?
    • Aug 21 2018 | 2:17 pm
      use the [join] object with @triggers, so you can set which input triggers the output
    • Aug 21 2018 | 5:35 pm
      Basically I want to combine a bunch of data send it as one signal and then unpack it at the other end and use it exactly the same as it goes in?
      You can't, because you've transformed the original data by packing it into a list. When a list is triggered, all individual elements are triggered. If you want to treat them separately, what was the point of joining them into a list in the first place? Do you really need to group your data in a list? Personally, I think you would be best served with naming the parameters (prepend) and routing them at the other end, and if you really need to send a list somewhere (e.g. outside Max) do it separately.
    • Aug 21 2018 | 10:57 pm
      Ahh I see, cheers! Thanks for your help, this worked much better than sending a list.
      The reason being is I'm using Max for live to communicate to a Max Patch. Ableton is automating these parameters. So I'm using UDPSend and receive for data. However I'll be using 4 sets of UDPsends and don't want to have 20 sends for different ports.
    • Aug 22 2018 | 9:20 am
      This way you only need one udpsend because the individual messages are tagged/described (e.g. "scale 0.5").
    • Aug 22 2018 | 12:45 pm
      + 1 imho it depends of the way you need to update your data. With a list, you can have the hand on the order of the parameters. I don't know how UDP respects that, and how fast it packets the data, regarding the charge of your computer. A way to "detrigger" a list with change object. - nb: use the (reserved?) word "bang" makes me perplex inside Max hth michel
    • Aug 22 2018 | 11:11 pm
      Yeah Prepend works much better, as essentially I'll be using x4 of my original patch. If I send each parameter independently I will need to use 8+ UDP sends. Each time I load this patch it will try and link each port.
      However now that I'm routing all data too one UDPSend. I can send 20+ parameters and only need one send for that specific patch.
      This meaning that I only actually need 4 UDPsends altogether for affecting all parameters and all patches.
      Only real reason was to make things easier when patching really haha. Appreciate all your guys help though.