s-ol’s avatars-ol’s Twitter Archive—№ 764

    1. Today I decoupled the MIDI and Time logic from Shader uniforms. The uniforms now have metadata attached in a comment to specify extra options like uniform sampler1D p; // @expose{type=float,history=100} which defines a float parameter with 100 frames of history.
  1. …in reply to @S0lll0s
    @.exposed parameters can be bound to different “Controllers”, so far there is a UI slider, the Midi-stuff and a time ramp thing. Right now yhey are re-assignable at runtime by shanging the params in the shader (live-reloading!) but actually I want the association to be done in UI
    1. …in reply to @S0lll0s
      This might eventually turn into a full node-based system but I’ll see. Either way I need a way to save state soon; it’s annoying enough having to set up the JACK midi connections on each start
      1. …in reply to @S0lll0s
        ofxGui was also a bit of a pain, I think I will switch to ofxImGui soon. Makes more sense anyway since I store my state myself already.
        1. …in reply to @S0lll0s
          tl;dr & nontechnical: a lot of cool workflow changes today, none of which are nice to show or cool to see :P