This feature was secondary from the start. I mostly wanted to observe the input streams without trashing the console output (especially when sending at a high-rate).

We could add a library function to crow that sets up a metro & sends the stream message

One solution would be to add a library function that creates a metro which transmits the input values always. :

scope_metro = {} -- need a global to store whether we're sending
function scope(active)
  if active and scope_metro == {} then
    scope_metro = metro.init{ time = 0.1 }
    scope_metro.event = function()
      _c.tell('stream',1,input[1].volts) end
      _c.tell('stream',2,input[2].volts) end
    end
    scope_metro:start()
  elseif not active and scope_metro ~= {}
    scope_metro:stop()
    metro.free(scope_metro.id)
    scope_metro = {}
  end
end

I guess my point is, implementation is easy, it's much more of a design issue.

Is it even useful to have the raw floats / bools printed? I've been thinking a visual fader might make it more communicative. Alternatively we could scrap the input vals being printed, and instead have some kind of scope / histogram thing.

input values not at top of the repl #13

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions