cbranje

If I manually change a number box to 1, or toggle on a toggle with the mouse, the right message gets sent.

But if the number box gets changed to 1 automatically by the patch, the message underneithe does not get sent . .

message-only-sent-when-manually-banged

When you say 'automatically' how do you mean? loadbang? If you post an example patch it would make things a lot easier.

by automatically I mean during the normal operation of the patch . . . so I have a midi device feeding in numbers to the patch . . . if the number box i'm talking about is set by the midi keyboard, then there is no action, but if I manual set that box to 1 by click it then the message sends fine.

in the file I included check out the first subpatch . . . I'm trying to send /digitalout/0/value 1 . .

in the file I included check out the first subpatch  . . . I'm trying to send /digitalout/0/value 1 . . 

On May 1, 2008, at 10:39 AM, Carmen Branje wrote:

Without sharing it here, it makes it very difficult to help.

On May 1, 2008, at 10:39 AM, Carmen Branje wrote:
> I have a patch . .

Chris Muir
cbm@well.com	
http://www.xfade.com

it seems only the right most message box works . . .?

So please look at the pdf I've included . . .

Only the right most message gets sent to mc.usb . . . if I delete the rightmost connection the next one down the line starts to work . . .

So please look at the pdf I've included . . . 

Only the right most message gets sent to mc.usb . . . if I delete the rightmost connection the next one down the line starts to work . . . 

poly only takes one argument. Did you intend for the extra arguments to do something?

Your "midi" subpatcher could be made simpler, I think, by using a series of "split" objects instead of all the == >=

I'm a little suspicious of how you're routing the poly output and velocity value to the midi subpatcher. I think you should just unpack the list output from route in your midi subpatch.

All that said, this is a solution to the specific question you asked:

Your "midi" subpatcher could be made simpler, I think, by using a series of "split" objects instead of all the == >= 

I'm a little suspicious of how you're routing the poly output and velocity value to the midi subpatcher. I think you should just unpack the list output from route in your midi subpatch. 

Thanks for your responses . . . . I've fixed one problem and found another . . .

this initial problem was that the message was being sent when ever a change in value was sent, so from 0-1 or 1-0, so both where being sent I believe.

I've fixed that, but now I am only able to get the right most message to fire as per my post above.

this initial problem was that the message was being sent when ever a change in value was sent, so from 0-1 or 1-0, so both where being sent I believe. 

I think you have some fundamental misunderstandings about Max. The way your patch is set up ALL of the logic for decoding MIDI notes will change state with EVERY note that comes in. If you are sending messages with each change, lots of messages will be sent. Add bang messages hanging off of all your && objects to see what I mean.

At this point I'll reiterate my advice about using split instead of a lot of your logic. With split, only a given range will respond to a change.

BTW, Posting images is not as useful as posting patches.

I think you have some fundamental misunderstandings about Max. The way your patch is set up ALL of the logic for decoding MIDI notes will change state with EVERY note that comes in. If you are sending messages with each change, lots of messages will be sent. Add bang messages hanging off of all your && objects to see what I mean. 

Don't hand this homework in until you understand how it 

Don't hand this homework in until you understand how it  
works:

am I missing something . . . it seems from you post like you posted a max patch but all I'm getting is this text . .

On May 1, 2008, at 7:31 PM, Carmen Branje wrote:

> am I missing something . . . it seems from you post like you posted 

> a max patch but all I'm getting is this text . .

And go to Max 5.0.1 or greater and select New From Clipboard.

On May 1, 2008, at 7:31 PM, Carmen Branje wrote:
>
> am I missing something . . . it seems from you post like you posted  
> a max patch but all I'm getting is this text . .

Yeah, copy the lines starting with
----------begin_max5_patcher----------
   and ending with
----------end_max5_patcher----------

Message only sent when manually banged