piper-audio / ugly-duckling

Technology demo for Piper components using Waves-UI
4 stars 0 forks source link

limitations in note rendering (was: can't represent notes) #11

Open cannam opened 7 years ago

cannam commented 7 years ago

We don't have a working representation for note-type outputs.

cannam commented 7 years ago

There is now a PianoRollLayer in wavesUI.helpers. Its implementation may change (at the moment it converts note structures to something understood by the segment shape), but we can start using it all the same.

The next two problems:

I would also like to make the pianoroll accept a colour mapper like that used for the matrix shape. Later.

cannam commented 7 years ago

Also, as with all the other layers, the piano roll has no vertical scale or labels yet (see #6).

LucasThompson commented 7 years ago

I've got a pending pull request for this, which also contains some work regarding #34.

Is this issue far enough along to merge those changes and close for now? A vertical scale and labels may be separate issues. There is also the desire for sonification.

cannam commented 7 years ago

I'm not sure we should close it until we actually have note-feature-type metadata being carried along. The current bodge is a nice bodge but it is, after all, a bodge. Also it's no bad thing to have a reminder to handle the vertical range/scale stuff.

(Perhaps we should rename the issue and remove the priority tag.)

cannam commented 7 years ago

Definitely should merge it though!

LucasThompson commented 7 years ago

Okay, I've changed the comment in the pull request so it won't close this issue automatically on merge. About to merge!

cannam commented 7 years ago

Thinking again about how to attach an output type URI to a Piper extractor. This wiki page https://code.soundsoftware.ac.uk/projects/vamp-js/wiki/Adding_Plugin_Output_URI_to_Existing_Piper_Schema lists six (!) options. What do you think?