Comments (9)
If you use the standard definition of above and below, these positions remain constant
whether the stem is above or below the notehead.
Exactly. The position of the number is independent of the stem direction.
Am I correct in assuming that what you're looking for is a way to create a dependency between the stems and the tuplet numbers? That is, if the stems are flipped, then so is the position of the numbers?
We might be able to accommodate both by allowing @num.place
to use 2 sets of values: "above" and "below" for absolute placement and "head" and "tail" for relative placement.
I think you meant tuplet/@numplace
, but in any case, for stemless notes or in the case where stem directions aren't specified, stem direction has to be assigned.
from guidelines.
Am I correct in assuming that what you're looking for is a way to create a dependency between the stems and the tuplet numbers? That is, if the stems are flipped, then so is the position of the numbers?
Yes
We might be able to accommodate both by allowing @num.place to use 2 sets of values: "above" and "below" for absolute placement and "head" and "tail" for relative placement.
Here are the possible cases:
A, C, F, G: "below"
B, D, E, H: "above"
A, E: "tail"
B, F: "head"
tail/head assignments are confusing for C, D, G, and H. Perhaps they can be defined by the direction of the first note in the beam group.
Typically music style uses head/tail system. Modern editions like using "tail", but 19th century editions prefer "head". When dealing with music that have lyrics, a possible preference would be for "above" so that the tuplet is not getting in the way of the words.
from guidelines.
Makes sense. But, how should Verovio / other processor deal with mixed stem direction AND relative number placement? For instance, a value of "head" or "tail" for case G? Should "head" and "tail" be disallowed by Schematron when stem directions are mixed?
from guidelines.
For "head"/"tail" mapping to "above"/"below" in the case of a mixed-direction beam:
Perhaps they can be defined by the direction of the first note in the beam group.
So:
C, H: "tail"
D, G: "head"
from guidelines.
Sorry, missed that sentence. The exact mapping strategy doesn't matter as long as Verovio is consistent.
Is this something that should be in 4.0 or can it wait 'til the next revision?
from guidelines.
There is no hurry, so it can wait until the next version.
from guidelines.
This also applies to [email protected]
. See issue rism-digital/verovio#987
from guidelines.
@ahankinson transferred this issue from music-encoding/music-encoding on Apr 12
Should discussions about new features (or changes in features) be placed here (music-encoding/guidelines) or in (music-encoding/music-encoding)? I am going to submit a new issue for <key>
, which I will start in this repository...
from guidelines.
@ahankinson transferred this issue from music-encoding/music-encoding on Apr 12
Should discussions about new features (or changes in features) be placed here (music-encoding/guidelines) or in (music-encoding/music-encoding)? I am going to submit a new issue for
<key>
, which I will start in this repository...
new features please to the music-encoding repo, not the guidelines
from guidelines.
Related Issues (20)
- Add include tag for module descriptions HOT 2
- Styling of figure captions HOT 5
- Captions for code examples HOT 2
- multirest.md block description HOT 8
- Guidelines miss styling in Safari HOT 3
- Misleading content model info HOT 2
- Chapter 05 (dev): MEI examples to be rendered in Verovio are not shown HOT 8
- Update Verovio version HOT 3
- Last note of one MEI example file not being displayed HOT 1
- verovio example chopped off HOT 4
- Refer to TEI Guidelines HOT 6
- version folders HOT 3
- guidelines dev is missing index.html HOT 5
- Wrong menu for the devlopment version HOT 3
- Links to TEI guidelines still broken HOT 7
- tabs in dev not working on firefox
- Javascript error when displaying full description of attributes HOT 4
- Typo in v.4 Guidelines Ch. 3 HOT 1
- deprecate wiki HOT 1
- Deactivate issues in this repo
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from guidelines.