swatch turns to grey when controlling from Mira

    Apr 22 2015 | 11:52 am
    I'm sure this is a feature and I"m just missing the trick... When I control a swatch object from my Ipad through Mira, the palette turns grey. Turning on the inspector I see the saturation is changing. Is it some kind of movement or hot corner that causes that? I have no problems when controlling it from my Mac
    I saw this problem in an older thread which apparently was related to versions - but I don't believe that is the issue for me.
    I'm on Max 7.0.3, below the Mira version details.
    I still have a Max 6.1 folder which also has a Mira package, I checked it just in case but it's the latest version there too: 6.1.3 I don't use Max 6 anymore, it shouldn't really matter right?
    "mira" : { "name" : "Mira", "type" : "package", "author" : "Cycling '74", "description" : "Mira automatically connects to Max and mirrors your interface.", "version" : "1.1.8", "major_version" : "1", "minor_version" : "1", "min_max_version" : "7.0.2", "path" : "McBas13:/Applications/", "vol" : -371
    Thank you! Bas

    • Apr 22 2015 | 6:27 pm
      you can set the saturation, store it in a message box and bang that when outputting from the swatch?
    • Apr 23 2015 | 3:43 am
      good idea - That at least allows me a 'recover' option. But why does it change in the first place?
    • Apr 24 2015 | 1:27 pm
      anybody? I'm I the only one with this problem?
    • Apr 26 2015 | 2:32 pm
      Ok I've raised it with support. I've done a little more troubleshooting, it seems related to using 'compatibility mode' (outputs RGB in 0-255 instead of floats) which is what I want to use because these bytes control LED colors through an Arduino.
      You can reproduce the effect if you put the swatch in compatibility mode, and move your finger back and forth a few times along the top edge of the swatch object.
      When you do this on the Mac interface, no problem. If you do it on the swatch object on the Ipad, it gets locked in the top left corner.
      Code below:
    • Feb 20 2016 | 6:40 pm
      I should have mentioned, this, here's is Cycling's response (April 2015): "Engineering are aware of this, thanks for reporting"