Difference between Max8 and Max9 with line~ in a poly~
Hey, I think I've discovered a difference between Max8 and Max9.
I've tried to break it down into a as-simple-as-possible patcher.
Just turn on audio and click the bang in the ez-synth_debug_main.maxpat patch in max8 and then in max9.
I'm getting a different output, can somebody confirm?
Ok I think I've narrowed down the problem:
So what I have is a voice loaded in poly~, which has an additional parameter in to glide:
I then send the synth 2 notes and on each note a glide command.
I want both notes to glide on each command, so I do [t l b] where the bang sends a "target 0" message telling the poly to target all voices:
In max 8 this works fine and as i would expect. In max 9 however the first note does not get the second glide command. I can fix this using [deferlow] to defer the glide command which leads me to believe that the threading of the inlets was somehow changed between max8 and max9. I think my example shows that the bevaviour is more inconsistent in max9 so I would probably consider this a bug.
Could I get a confirmation if this is considered a bug?
target message should be sent to leftmost inlet of poly object.
when you use target message, don't use note messages.
talking about threading... while this is not the case in the current situation... those [del] could easily break the patch when they would be attached to something left from other branches without a del.
@Roman
This was just an example patch, the easiest I could come up with. It's not a thing that i'm really using. I got the bug in a larger patch and tried to break it down.
@Source
my original patch didn't use the note message, I just used it for this demonstration. Normally pretty much all my patches involving poly~ only use target + (frequency, velocity) messages to the left inlet for notes and target 0 + (parameter, value) messages to the right inlet for parameters. Never had problems with it. Can you explain why I shouldn't use target messages to the right inlet?
I don't have much time right now but as soon as I'm able I'll create another patch to demonstrate the bug, maybe one which makes more sense.