float isn't float ?


    Jun 08 2007 | 8:09 pm
    Hi list,
    If I send a message "ceiling .5 .5" to [unpack s f f] I get "ceiling .5 .5"
    it's ok !
    So, could somebody say to me why jit.freeframe message can't be unpacked (precisely the second float(sometimes it is an int but same problem)) when I send it a "getparam ceiling" (or getparam currentparam) message ?
    the second float given by jit.freeframe isn't a float ?
    max v2;

    • Jun 12 2007 | 6:50 am
      No, but there is no second float. The message is "param paramname/
      paramid paramvalue". So, "param 0 0.5" or "param truthiness 1.0".
      jb
      Am 08.06.2007 um 22:09 schrieb derrickgiscloux:
      > the second float given by jit.freeframe isn't a float ?
    • Jun 12 2007 | 7:16 pm
      Sorry but depending of which freeframe plug in is loaded you can have several parameter values (several floats) for one parameter name.
      It seems we can't unpack the second value with [unpack] object consecutively to a getparam message to jit.freeframe
      Could someone confirm.
    • Jun 12 2007 | 9:11 pm
      Sorry but that's incorrect.
      The subsections beginning with the word Parameter would be of
      particular relevance here.
      I quote from ParameterValue():
      ParameterValue
      (32-bit float value OR 32-bit pointer)
      Definition:
      ParameterValue:
      Float value from 0-1 or pointer to null terminated string. (See remarks)
      Remarks:
      Apart from text parameters, FreeFrame parameter values are always 32-
      bit floats, and the range of values permitted is STRICTLY 0-1 (0 ParameterValue of values over a standard range, so the host can run up sliders or
      similar for the plugin. The Use of any values outside this range will
      result in hideous incompatibilities. The ParameterDisplayValue can be
      used to display whatever actual values the plugin likes e.g. 0-255,
      0-767, 1-256 or whatever. The plugin should translate the standard
      0-1 float range into the values it needs for its processing.
      For text parameters, this 32-bit value represents a pointer to a null
      terminated string.
      jb
      Am 12.06.2007 um 21:17 schrieb derrickgiscloux:
      > Sorry but depending of which freeframe plug in is loaded you can
      > have several parameter values (several floats) for one parameter name.
    • Jun 13 2007 | 9:02 am
      A corrective note: the "getparam" message _does_ report a 2nd value,
      as documented here in the Jitter reference:
      getparam: Sends a list out the object's right outlet containing the
      current value of the parameter specified by the param argument
      (either by name or by index into the list returned by getparamlist).
      The list is formatted as 'param "param" "param-val" "param-display"'.
      The "param" argument is the name of the parameters, the "param-val"
      the value, and "param-display" is an alternate display value, for
      parameters whose "real value", as understood by the parameter, lies
      outside of the range 0-1.
      This "param-display" value is probably what you're talking about.
      Sorry for the miscommunication. "param-display" is a symbol, not a
      float, since the freeframe spec reports this information as a string,
      rather than as a number.
      Best
      Jeremy
    • Jun 14 2007 | 5:08 pm
      Yes, this was the problem :
      When you ask for a getparam to jit.freeframe, and if the plugin has 2 values for this params :
      - the first is given as a float
      - the second as a symbol (in float "form")
      It's right.
    • Jun 14 2007 | 5:44 pm
      Sorry, but I have to correct you here: it's not that the plugin has 2
      values for the param. It's that there is a "real" value and a
      "displayed" value. They are the same value, but the "real" value is
      what the plug-in is really set to and the "display" value is what the
      plug-in wants you to think it's set to. There is only one value for
      the parameter. This is important. Each parameter has only one value.
      jb
      Am 14.06.2007 um 19:08 schrieb derrickgiscloux:
      >
      > Yes, this was the problem :
      > When you ask for a getparam to jit.freeframe, and if the plugin has
      > 2 values for this params :
      > - the first is given as a float
      > - the second as a symbol (in float "form")
      >
      > It's right.