Forums > MaxMSP

[bug?] seq~, noteout or me ?

September 25, 2010 | 12:53 pm

Hello,

I have a strange problem when feeding noteout with note on and note off
messages from seq~.

Please use the embedded patcher and open the attached .txt file with seq~.

The messages do seem to have the right syntax and if I translate them
for midiout everything is OK. But if I send them directly to noteout no
MIDI message is coming out from noteout.

So, is it noteout, seq~ or me ? I got no answer from C74′s support…

Thank you in advance.

Roald Baudoux

– Pasted Max Patch, click to expand. –
Attachments:
  1. sequence.txt

September 25, 2010 | 1:32 pm

You just need to unpack the list coming from seq~.
(Notice that noteout has 3 inlets).



MIB
September 25, 2010 | 7:36 pm

This might be a bug(?). You should be able to send a list to noteout but it seems the channel info breaks the functionality. If you unpack the message it works fine… weird. And just to be totally confusing you can send it pitch/velocity as a pair and set the channel separately and it works…

– Pasted Max Patch, click to expand. –

September 25, 2010 | 9:45 pm

@MIB

"You should be able to send a list to noteout.."

Can you point to a reference section where this is described?



MIB
September 25, 2010 | 10:00 pm

sorry, don’t really know where the reference is. but I do remember that any list sent into the left inlet of a multi-inlet object will be distributed over the inlets from left to right…


September 26, 2010 | 9:17 am

Interesting. I wasn’t aware of the "distribution rule".
Is it documented somewhere officially?


September 26, 2010 | 2:18 pm

Hello maxers,

It seems that [seq~] outlet isn’t a true list (comment is _anything_) ;
if you put a [trigger l] between [seq~] and [noteout] that works ;

– Pasted Max Patch, click to expand. –

HTH.



MIB
September 26, 2010 | 10:58 pm

that’s interesting. wonder why it’s not defined as a list…
never occurred to me to check the outlet type!!! definitely going into my bag of tricks now ;)

cheers


September 27, 2010 | 8:03 am

Hello MIB,

"… wonder why it’s not defined as a list …"

Actually it is.
I did a test with CNMAT’s [printit] external ;
from [seq~] you get a LIST with 3 LONG exactly like from [t l]‘s outlet ;

so what’s happened ?


September 28, 2010 | 7:41 pm

Yes, I ran the printit test and I got the same results as pizza olives.

I also thought it could come from several events having exactly the same position in the sequence but even by moving events slightly to avoid this it doesn’t solve the problem.


September 28, 2010 | 8:47 pm

Looks like a timing problem. The channel info needed from noteout to calculate the status byte (144 etc.) probably arrives too late relative to the first inlet. But in my opinion the "distribution rule" is questionable anyway.


September 29, 2010 | 9:05 am

> But in my opinion the "distribution rule" is questionable anyway.

Well, even the noteout’s helpfile shows its use.

I’d like a comment from C74 on this topic…


September 29, 2010 | 7:01 pm

Roald, I never saw an email from you in Support regarding your original posting, perhaps it lost the battle with a spam filter on one of our sides? Regardless, apologies for the delay.

The issue here is a little more complex and general as it relates to what happens with things being sent out an outlet ‘anything’ and sending that to an inlet that expects a list. We will take a closer look.

In the meantime, sending it through a [t l] or something similar should work.

Regarding the ‘distribution rule’, I wouldn’t count on it unless the object explicitly states that it does this.

-Ben


October 1, 2010 | 6:53 pm

Hi Ben,

Glad to know my message wasn’t put aside. I suspect that some people with a brutele.be send spam, it might explain the filtering.

Curious to know what causes seq~’s/noteout bug anyway…

Best regards,

Roald


Viewing 14 posts - 1 through 14 (of 14 total)