Feature idea: have a menu to choose a mode of cssrule/sound equivalence. #33

New issue

Open

opened 2021-10-20 11:59:27 +00:00 by e-lie · 4 comments

e-lie commented

2021-10-20 11:59:27 +00:00

(Migrated from gitlab.com)

Since there are several possible associations between rule kinds and sound properties and that this equivalence is not always obvious a menu could:

Clarify the association for a performance audience (not always desirable maybe)
Make it possible to switch between several modes

Since there are several possible associations between rule kinds and sound properties and that this equivalence is not always obvious a menu could: - Clarify the association for a performance audience (not always desirable maybe) - Make it possible to switch between several modes

raphaelbastide commented

2021-10-20 12:17:44 +00:00

(Migrated from gitlab.com)

Clarify the association for a performance audience (not always desirable maybe)

I agree, a graph or visual table could be automated to map visual / sound properties together. A text version of such a table is currently visible in the README. But it’s too static and not visual enough

Make it possible to switch between several modes

Exactly, the idea in the long term is that the performer chose its own links between visual and sound props. That could be nice to have something like:

  var cascade = new Cascade '.splide' );
  cascade.options.pitch = "x-axis";
  cascade.options.pulseTime = "y-axis";
  cascade.options.bpm = "window-width";

The only thing is that values have to be compatible technically. E.g. BPM can’t be mapped on a boolean value.

> Clarify the association for a performance audience (not always desirable maybe) I agree, a graph or visual table could be automated to map visual / sound properties together. A text version of such a table is currently visible in the README. But it’s too static and not visual enough > Make it possible to switch between several modes Exactly, the idea in the long term is that the performer chose its own links between visual and sound props. That could be nice to have something like: ``` var cascade = new Cascade '.splide' ); cascade.options.pitch = "x-axis"; cascade.options.pulseTime = "y-axis"; cascade.options.bpm = "window-width"; ``` The only thing is that values have to be compatible technically. E.g. BPM can’t be mapped on a boolean value.

raphaelbastide commented

2021-11-02 11:22:08 +00:00

(Migrated from gitlab.com)

mentioned in issue #10