Oh, I forgot, there are different contexts in which the term "step" is used
as well. Sometimes it's step within an octave - in which case it's C = 0 -
but there is also an absolute version that incorporates octave as well.
On Mon, May 4, 2015 at 4:35 AM, Jim Newton wrote:
> Is this defined some
Is this defined somewhere in the code?
I.e., which step value corresponds to which note, A,B,C etc?
My first investigation shows 0 = A, not 0 = C.
> - step is normally an integer 0 = C, 1 = D, 2 = E, etc - basically, note
> name, not considering key or accidental
--
View this message in cont
Thanks. That is a helpful document.
Note the sentence from the document:
The Segment object (segment.h) is perhaps the most important data structure to
understand in MuseScore.
> On 03 May 2015, at 19:07, Marc Sabatella [via MuseScore Developer]
> wrote:
>
> Oh, sorry, I didn't realize that
Oh, sorry, I didn't realize that. Segment is a very fundamental concept in
MuseScore - it refers to a vertical time slice of the score. See
https://docs.google.com/document/d/1BmjPqk9j4-zSFaiFsUjYSURDk98MHSgrHjfhMJ1Q9gg/edit?usp=sharing
for information on these sort of basics.
On Sun, May 3, 201
Yes thanks, it is making more and more sense.
But I still haven’t understood what a segment is.
I see a way of getting it of this and that object, but I still don’t know what
it represents.
> On 03 May 2015, at 18:52, Marc Sabatella [via MuseScore Developer]
> wrote:
>
> On Sun, May 3, 2015 a
On Sun, May 3, 2015 at 11:59 AM, Jim Newton wrote:
> Great that is very enlightening. But I think I don’t yet understand “line”.
> Is line some sort of iterator or index into the staff or measure when read
> from left to right?
Are you looking at the code? It's a simple integer. 0 for the top
Great that is very enlightening. But I think I don’t yet understand “line”.
Is line some sort of iterator or index into the staff or measure when read from
left to right?\
Or is line really referring to the 5 lines of a staff and the 4 spaces?
I ask this because it seems that I can calculate the
I don't know that there is documentation on this, but I can try to answer
the specific questions here according to my understanding
- staffIdx is indeed the index into the array of staves
- some note input functions use a concept of position to indicate where the
note is to be placed, the details
Hi Marc, thanks for pointing out that issue. I was beginning to wonder
something very similar from looking at the code.
The puzzling thing that I've found so far is this.
Given a Note object, I can call findAccidental on it. However, if the note
has not yet been created, it is not clear to me h
FWIW, there is an open issue that I think also relates to this in some way:
https://musescore.org/en/node/54691. Maybe it's only related in my head
:-). But I think they perhaps both have to do with not having enough
context at the point where it is needed.
On Sat, May 2, 2015 at 4:34 AM, Lascon
Off the top of my head, I would check Measure::findAccidental()
lasconic
2015-05-02 10:25 GMT+02:00 Jim Newton :
> As some of you may know, I'm working on an enhancement to musescore which
> implements ornament articulations such as trills (and others). I'm making
> heavy use of the function di
As some of you may know, I'm working on an enhancement to musescore which
implements ornament articulations such as trills (and others). I'm making
heavy use of the function diatonicUpDown, which looks at a key and
calculates intervals restricted to the key signature.This works great,
but is l
12 matches
Mail list logo
