#5 Parameter types

version 1
closed
5
2004-02-27
2003-02-28
No

Currently only their is no indication how a parameter is
used by a plugin.

Maye it would be usefull to give additional information, or
allow other types such as booleans and integers.

Also some plugins seem to use 0 and !0 for boolean
flags, maybe it should be standardized to 0-0.5 and 0.5-
1.

Discussion

  • Logged In: NO

    This is a good point. What info would be useful to hosts?
    We could define int and bool type parameters, but I think
    the actual data passed should stay standardised to float.
    This way plugins are less likely to break the host and we
    stay backwards compatible. We could let plugins 'hint' to
    the hosts that a parm is a bool, for example, so hostcan
    avoid complex, costly translation routines.
    Anyhow I reckon providing standard lookup tables in a
    freeframe_utils library would be a good start...

    The good thing about using 0 and !0 is that in the future !0
    can be a large range of error values, but remain back
    compatible. That's why we did it that way.

    We *do* need to start adding meaningful error codes to the
    spec though. I'm hoping these will start being requested by
    host/plug developers soon...

     
  • Logged In: YES
    user_id=142435

    Packing int values in a float is a bit weird when the call uses
    a dword for storage imho.
    Im using my midi keyboard with freeframe which works great
    except for booleans because its sometimes doesnt deliver a
    perfect zero when closed. (but thats my problem i guess :)

     
  • Logged In: YES
    user_id=644854

    After extensive discussion we have a parameter types sytem
    in FF 0.75 - we kept it fairly simple so as not to upset the
    'simple host' principle of one slider -> one FF parameter.

    All parameters for FreeFrame 1.0 are planned to be either
    the IEEE floats we already have from 0-1 or Text

    See spec for details

    Russell

     
    • milestone: 255847 --> version 1
    • assigned_to: nobody --> vjamm
     
  • Logged In: YES
    user_id=142435

    I cant seem to find the documentation on the site or in the
    mailling list.
    Does it solve my problem with using analog midi sliders for
    boolean signals?

     
    • status: open --> closed
     
  • Logged In: YES
    user_id=644854

    this has been done for 1.0 in a simple fashion

     
    • status: closed --> closed
     
  • Logged In: YES
    user_id=644854

    http://cvs.sourceforge.net/viewcvs.py/\*checkout*/freeframe/docs/specification.html?rev=1.2

    yes - boolean issues are clarified (your midi sliders you
    need to do the boolean detect cutoff in the middle of the
    range if you're worried about the slider not getting to the
    bottom - then translate that into FF bool)

    Nobody wrote:
    We could let plugins 'hint' to
    the hosts that a parm is a bool, for example, so hostcan
    avoid complex, costly translation routines.
    Anyhow I reckon providing standard lookup tables in a
    freeframe_utils library would be a good start...

    R: yeah wiked

    N: We *do* need to start adding meaningful error codes to the
    spec though. I'm hoping these will start being requested by
    host/plug developers soon...

    R: yes - anyone?