ctlin bug


    Jun 10 2014 | 1:43 pm
    either a doc mistake, or a [ctlin] bug :
    in the reference of ctlin, the following (about the set message) is wrong :
    "This message is appropriate only if a specific controller number was originally typed in as an argument; it is ignored by ctlin if no controller number argument was originally typed in."

    • Jun 10 2014 | 2:57 pm
      Looking at ctlin help and I can't see what you're referencing to. What version are you on? What message on the object is giving you this?
      By reference you do mean the help file? If you type ctlin -1 4 you get all messages on channel 4, if you type in ctlin you get all messages on all channels. If you double click the ctlin you can select the midi device you want to read from. If you type in ctlin 16 1 you will read the value of CC16 on channel 1.
      Also did you ever think it might be an easter egg for people who cracked a version of their software? Or just update your version, as mine doesn't have it and am on max 6.
    • Jun 10 2014 | 3:23 pm
      !!!?? my version is not cracked, and i'm running the last version. and thanks, but I don't need an explanation about how ctlin works.
      I'm just saying that if you send "set 5" to a [ctlin] which does not have any argument, it is not ignored : the ctlin will only listen to the controller number 5. This is not the expected behavour, as the reference clearly states that if the ctlin did not have an controller number argument, then "set $1" will be ignored.
      FYI, what we call "reference" is that : https://cycling74.com/docs/max6/dynamic/c74_docs.html#ctlin you can find it by going to an help patch, click on the "?"->open reference.
    • Jun 10 2014 | 3:34 pm
      Edit: nevermind. Misunderstood the original post in that I assumed the issue was the set did not work when a controller number was added as an argument (it does - though the reported controller number doesn't change). But rather the issues appears to be that set works when a controller number is *not* added as an argument in initialisation...
    • Jun 10 2014 | 3:40 pm
      Ahh right ok I just tested and you are right. Cheers for clearing it up on the ref vs. help file that's very handy. And for explaining the problem in more detail, I was able to replicate your conundrum like you described.
      Does this bug affect what you're trying to create by the way? I can't see it being a massive problem.
    • Jun 10 2014 | 3:47 pm
      Does this bug affect what you’re trying to create by the way? I can’t see it being a massive problem.
      no, not at all. I'm just reporting it so that cycling fixes it. I guess the best thing to do is to change the doc, not the code, so that existing patches won't be affected.
    • Jun 10 2014 | 4:10 pm
      ahh excellent good to hear! Don't suppose you're an absolute boss at MAX and can help me solve this problem:
      Been tearing out my hair this week and been checking this forum every five minutes, so I've been an unusual pest around here lately, so apologies for the ignorance shown by me in this thread!