Split pitch_ namespaces into note_ and contour_
See original GitHub issueAs discussed in #91 starting here, currently the pitch_hz
and pitch_midi
namespaces are overloaded in a bad way, supporting both note-style annotations (where a note has a start time, duration, and pitch) and continuous f0 (contour)-style annotations (where contours are specified by timestamped pitch values with 0 duration).
Apart from being confusing, this causes a number of problems e.g. for sonification and visualization.
The proposed solution is to split “pitch” into “note” and “contour”, keeping the hz/midi distinction as well:
note_hz
note_midi
contour_hz
contour_midi
Note that the only difference between hz and midi here is how pitch values are represented (on a Hertz scale or as MIDI note numbers), but the two are otherwise equivalent: neither implies any sort of pitch quantization, and both can be used to represent sparse (note) annotations and dense (contour) annotations.
Finally, we need to decide whether to use the aforementioned namespace names as is or add a pitch_
prefix to each of the 4 (the former means shorter/cleaner namespace names, the latter is less ambiguous).
Issue Analytics
- State:
- Created 7 years ago
- Comments:20 (20 by maintainers)
Top Results From Across the Web
Namespaces · Issue #13 · marl/jams - GitHub
I'm starting a new issue to manage namespace definition/schema ... need to discuss/sort-out the whole melody/note/pitch/f0 ambiguity stuff ...
Read more >Virtual Hosts - Project Contour
This CLI flag accepts a comma separated list of namespaces where HTTPProxy are valid (e.g. --root-namespaces=default,kube-system,my-admin-namespace ). HTTPProxy ...
Read more >Speech Synthesis Markup Language (SSML) Version 1.1 - W3C
A document is a Conforming Stand-Alone Extended Speech Synthesis Markup Language Document if it meets both the following conditions: It is a ...
Read more >Ingress is dead, long live ingressroute - Dave Cheney
Contour exists to fulfil the requirements I just described. I want to be clear that this talk isn't a product pitch — well...
Read more >Maya User's Guide: Adding a contour to your scene - Autodesk
In the Attribute Editor of the shading group node for your material shader, select Enable Contour Rendering under the Contours section. · In...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Right – I’m talking about the old (deprecated) namespaces where that was implicit, not the new
note_*
namespaces.I just wanted to make sure that we’re agreed that implicit voicing does not exist in midi space. I think we’re 👍 though. Thanks for clarification!
If I recall correctly the assumption was that
pitch_hz
would be used for time series andpitch_midi
would be used for notes, where voicing is indicating implicitly by the absence of a note. But in practice either namespace could be used to represent both a frequency time series or a set of notes.Long story short, yeah, I guess we didn’t support unvoiced frequencies for midi namespaces. Won’t be a problem with the new namespaces, for conversion I guess lets just say unvoiced is not supported for midi.