Individualising a patch


    Nov 28 2021 | 8:17 pm
    Hello, I'm only new to max and i am having trouble trying to 'individualize' my patch. The problem occurring is when i paste the patch into a parent patch, the midi interacts with all the duplicated sub patches. With pictures i will try to explain more clearly,
    Sub Patch - Midi data comes in, gets locked and compared to the raw data. This then allows the velocity/value only to output when the two locked midi data values are in play
    Sub Patch - Midi data comes in, gets locked and compared to the raw data. This then allows the velocity/value only to output when the two locked midi data values are in play
    So, when this sub patch is brought into a parent patch the two sub patches interact with eachother even tho the locked midi values are in play in one sub patch(The left 'Mapper')
    So, when this sub patch is brought into a parent patch the two sub patches interact with eachother even tho the locked midi values are in play in one sub patch(The left 'Mapper')
    I've thought maybe cloning the patch and naming them differently is an option, but not quite sure? Any suggestions Thanks

    • Nov 28 2021 | 8:52 pm
      Try a small addition to your send/receive objects inside the abstractions. Instead s name / r name use s #0name / r #0name - this should make s / r connections local (restricted to single instance of the abstraction).
    • Nov 28 2021 | 9:19 pm
      Thank you very much, that worked perfectly!!