loadbang not activating message "port from Max 1"?
I am using Max 6 and mac Lion, on a brand new 15 inch mac book pro, and I am using a loadbang with send/receive around my patch. Everything seems to be ok, except it does not seem to activate the message " from Max 1" with noteout object in order to change from "AU DLS Synth" to " port from Max 1" when the patch starts. I have to do it manually every time ? I tried various forms such as…port from Max MSP 1… port from Max 1,,, from max 1 etc as it says port is optional. I am new to this and I did search, so sorry if this has been asked before. I am sure it is something really simple.
i’m having this same issue. max v6.0.2 (51770) on os x 10.7.2
hmmm. well we are not alone as I spoke with a friend at college this evening, as we are all doing projects at college using max, and he has the same problem. Perhaps just a bug then? I read a few post where people said they just don’t trust load bang on the whole and suggested ways to initiate things. I think for now I will just use something else in the patch to initiate this message. I presume I can take a bang from something else that initiates and send that bang to the port message.
Thanks for the reply, now there is a few people saying this I know its not just some stupid thing I did.
i can’t even get it to work by manually triggering the message. can you? i think it’s a bug.
Having tried everything the message simply does not work. your right. shit. then its a bug for sure what now should we send a report to the people here. I am so new to this I have never address a bug with cycling 74? any suggestions here?
----------begin_max5_patcher---------- 368.3ocwTsjSCCCDcsyovxqKUwNkBEwUfsrgVgbRl1ZThcI1QDnpRbG3FxIg lIIkzOKLYCarkmY7Lu2KOmsADVroBrL5czmnDx1.BACUGfzdlvxkUIYRKVFK wjmCZGaTSNGT4v32+8meQ0FGPesb+psq.cYtozkAN75gsQUo3kLwub0ztJWZ zNsLGvLOBEoRsrK2FoKYsRu54BHw0.WQT33vQTwsh5Md3D7DebHcQuFZUefM jWW0ADozc.hWGaWPP8xHOk.M71dfelBjYjowR8pKyb94LehOLuoEt22.Mzlg i3.GufvvC4nTDgJxzo+25RsoXOK71PDMPCQKuiZ7EWeyf3cz.3cNXsxUvYDe iovQmyVVXxoOHqn74Lu8FhA4M7xWz9fgOC2l8GEHQOABuHKSoO8WH3zqierp YMkEIcXs8E.82wmBVmRKcJitWMhipYsJMEz8cNoJqLNCPoK7he87EMBOPSz. QCcQvtfe.XoZCgH -----------end_max5_patcher-----------
----------begin_max5_patcher---------- 179.3ocSOFjCBBCDEcc6oXxrVIzhtwcd.7DHFSAKZMzVCThMR3taaARXyL4+ l+7mLiTBVY8xdDNAWABYjRHITDPVzDTK70sh9jMzH+Zqdi6lG4jd2L15j1AG ThMcVMbQ3AVItZyLnCCaktTF4KzFqw0q9IiLFOaEqdjRLbk8LbiUiPmrhm6T h1MQqLqIWr.+Hb0uTlm26j0t4uiWbLbAfeH0XbdRkmkC2h6LQowRPLQ+CHAZ AsJ -----------end_max5_patcher-----------
Also, you can double-click on the noteout (or midiout, or ctlout) object to see which port it is sending to presently. I believe this works for all midi port-related objects (meaning the inputs also).