t; Sent from: http://dev-list.musescore.org/
>
>
> ___
> Mscore-developer mailing list
> Mscore-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
--
Marc Sabatella
m...@outsideshore.com
_
se suggestions will help you to keep Musescore such a brilliant
> software.
>
> Regards,
>
> R. C.
> ___
> Mscore-developer mailing list
> Mscore-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mscore-develope
__
> Mscore-developer mailing list
> Mscore-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
--
Marc Sabatella
m...@outsideshore.com
___
Mscore-developer mailing list
Mscore-developer@lists.
I am on Windows 10 and plan to continue using mingw & QtCreator until it no
longer seems viable. I can't imagine any possible benefit that would
justify the pain of installing and learning new tools. I assume there was
some reason for the change, but I don't recall it ever being explained.
Marc
Hello! Quite a bit of work was done to improve accessibility last summer,
but unfortunately much of that work has yet to be merged. Hopefully at
some point that work will be resumed, as this is important to many of us.
Marc
On Tue, Nov 20, 2018 at 5:19 AM Alexander Yevdokimov
wrote:
> Hi, fri
My understanding is that this is to be expected if you attempt to compile
older branches (eg, 2.x) using a too-recent version of Qt. In particular,
for building 2.3.2, 5.4 is the only supported version of of Qt as far as I
know.
Marc
On Sun, Sep 16, 2018 at 1:46 PM Joachim Schmitz
wrote:
> Whi
Hello, and thanks for your interest!
There is already a shortcut to move the note input cursor to the next
staff: Alt+Down. Actually, it will first move to the next-lower voice on
the same staff if there is one present, but then it moves on to the next
staff. Similarly, Alt+Up moves up through t
asics like noteheads? Anyhow, could also be interesting to
see if some other font designer has a decent set of basics but is missing
microtonal accidentals...
Marc
On Tue, Feb 13, 2018 at 8:51 AM 000masa000 wrote:
> Hello, posting here at suggestion of my close namesake Marc Sabatella ;)
Hello! If you are asking how to add these markings, best to use the
Support forum on musescore.org. If you are asking if you can help develop
code to improve this feature, then here on the developers mailing is a good
place, and feel free to describe your idea for implementing this in more
detail
Hi! What you are describing is really a pretty monumental task, and I
can't imagine that the plugin framework would be a viable for developing
this. I personally think what makes more sense is to develop a standalone
program that outputs MIDI. If you get this far, then the work of figuring
out h
I'm not quite sure what you are asking here. Notes do not belong to a
staff, they belong to a chord. A Chord object contains an array of Note
objects (Chord::_notes). As per the comment in chord.h, this array is
sorted according to staff line number. Changing this order breaks the
layout algori
Joachim Schmitz
wrote:
> Actulally MuseScore does provide nightyies for 2.2, as AppImages
>
>
>
> *From:* Joachim Schmitz [mailto:j...@schmitz-digital.de]
> *Sent:* Monday, August 21, 2017 1:56 PM
> *To:* mscore-developer@lists.sourceforge.net; Marc Sabatella <
>
1:48 PM Ralf Mattes wrote:
>
> Am Sonntag, 20. August 2017 21:21 CEST, Marc Sabatella <
> m...@outsideshore.com> schrieb:
>
> > Could be, or it might just be that while 5.4 is recommended and what
> > released builds use, 5.3 might technically be sufficient.
> >
only exists in that branch but has already been
fixed (or otherwise does not apply) in master.
Marc
On Sun, Aug 20, 2017 at 9:10 AM Ralf Mattes wrote:
>
> Am Sonntag, 20. August 2017 16:43 CEST, Marc Sabatella <
> m...@outsideshore.com> schrieb:
>
> > I might have mis
I might have missed this discussion, but there a reason you are building
2.2? New development should normally be on master.
Anyjow, my understanding is the spurious Loading dialog on Linux of using
the wrong Qt version. I believe 2.2 is supposed to use 5.4, some newer
versions aren't totally compa
Probably you have a corrupt workspace. Try Help / Revert to Factory
Settings.
On Fri, Jun 30, 2017 at 1:03 PM mxordn wrote:
> In the recent version of MuseScore 2.1. Build 871c8ce the application
> crashes
> when opening the palette (Gesamtpalette) window.
>
> By clicking on the menu-item the win
oing again, I guess this weekend I'll do that.
Marc
On Wed, May 24, 2017 at 3:48 PM Lasconic wrote:
> The majority of the issues you listed applies to master too. It would then
> make sense to fix them in master first. No?
>
> lasconic
>
> 2017-05-24 23:37 GMT+02:00 Marc S
in this branch. We just need to make sure we have nightlies and testers.
>
> lasconic
>
> 2017-05-24 22:45 GMT+02:00 Marc Sabatella :
>
>> I wonder if maybe there couldn't be a more streamlined process for purely
>> bug fix releases? Not every release necessar
I wonder if maybe there couldn't be a more streamlined process for purely
bug fix releases? Not every release necessarily requires a lengthy
announcement or a newsletter, maybe not all require updating apps, not all
have translation implications, etc.
Because absolutely I agree we shouldn't diver
keys, etc)
> - If not, what non-automatable parts can be distributed?
>- Is the issue the QA, as Sideways Skullfinger suggests?
> - Is there a pre-release user group that could be leveraged to
> report issues?
> - If so, how do we go about getting them new
Generally speaking, we don't release bug fix updates as often as some
projects do, and I get the sense that a big reason for this is how much work
is involved in actually producing packages for release. On the assumption
that this is in fact the case, I'm wondering, what can we do to lessen /
shar
I've definitely seen that error before, but it always turned out to be
something I had done wrong in my cmake configuration within QtCreator.
Like I left out the CMAKE_BUILD_TYPE=DEBUG, or the -G"Unix Makefiles", or I
didn't do a make clean after a previous build attempt with bad
configuration, etc
If you're asking for help on using MuseScore, the best place to do that is
the support forum on msuescore.org. When you ask there, please describe in
more detail what exactly you are trying to do. But first you might want to
read the Handbook, paying attention to the part on "Tempo" - it might
an
I've never used the Git/GitHub integration feature of QtCreator. I just
barely have a grasp on how those tools work but would not trust the GUI to
do exactly what I know needs to be done or how to undo the damage if it
does something I don't expect. That's me; others do use the integration I
hear
It's very common in publsihed music for all syllables in a measure to be
aligned togetyher. Often, for the entire *system*. So if we can be doing
that by default, great. for the special situatiosn where you want your
lyrics *not* aligned in this standard way, it seems manually adjusting
should b
No, that copy is not installed. The point of the install step is to copy it
to a folder it can be run from and can find its auxiliary files like
soundfont etc. Sounds like sourceDir is not set how it needs to be, or
maybe ".." isn't relative to what you think it is.
On Sat, Aug 13, 2016 at 7:51 AM
It should work anywhere as long asd you've fully installed into that
folder. So my original question remains - did you run make install? Did
you set CMAKE_INSTALL_PREFIX?
On Fri, Aug 12, 2016 at 9:37 AM garbo wrote:
> Happy to report a bit of success: I found a directory called
> "C:\win32inst
It seems the sysStaff is partially laid out in System::layoutSystem - we at
least calculate x offsets and heights for each staff. But the rest of the
layout doesn't happen until layout2() - in particular, the y offsets don't
get calculated until then. I can see why: the layout of spanners can
aff
Did you do a "make install" as your deploy step? That is what puts the exe
in that folder (and sets up other files necessary to run MuseScore
successfully).
On Fri, Aug 12, 2016 at 9:00 AM garbo wrote:
> I am trying to build MuseScore for the first time.Environment:- Windows 7-
> Qt
> Creator 4
As part of the GSoC, Ruchit (shredpub) is implementing support for score
annotations, with me as mentor. For annotations that attach to a single
element - like text or a shape - the implementation seems straightforward.
But one type of annotation probably deserves some discussion, and that is
the
There is already a baritone ukulele in the instrument list - just type
"ukulele" into the search bar to see all the different options. In the
future, the support forums on musescore.org are the better place to ask
support questions. That would also be the place to discuss what the
specific needs
I am sorry your project did not get selected. We had a limited number of
slots to fill so there were difficult choices to make. But this project is
very import to me personally, so I'm definitely still wanting to help with
this.
Probably what makes sense is to look at the individual problems to
vtests themselves are all created manually - the source files and the
reference graphics. The tests are run via the "gen" script in the vtest
folder - that's what actually generates the tests files and diffs them
against the reference. Go to vtest and type ./gen (you might need to
configure some t
other branch, please do so.
>> Less than 10 lines of code changed across the 3 combined PRs. That is the
>> positive side of the recent issues reported, and a positive reflection on
>> the health of the code (I'm feeling some small need to defend my work
>> here).
t might be worth it to hold
onto a 2.0.3 build environment for now in anticipation of further fixes
needing to be applied.
On Fri, Apr 22, 2016 at 11:17 AM Lasconic wrote:
> Which issues are you talking about in particular?
>
> lasconic
>
> 2016-04-22 19:09 GMT+02:00 Marc Sabatella :
As the author of the implode tool, I can address some of this:
Implode is internal for several reasons. It was originally a plugin (which
I also wrote), but a) the framework was too limited at the time (might be
better now?) to do a good job of it, and b) having it only as a plugin
means it is on
I seems like many of these issues are serious enough to want fixed on the
2.0.4 branch, so maybe focus first on building, developing, and testinh
there? Then worry about restructuring for master later? Unless werner or
lasconic advise otherwise...
On Fri, Apr 22, 2016 at 10:26 AM Sideways Skullfing
FWIW, I had the same problem - undefined reference
to QWindowSystemInterface::registerTouchDevice(QTouchDevice*) from
libQtWebKit, version 5.3. There is no libQtWebKit in version 5.6, so the
build shouldn't have been trying to use it. In my case, the problem was
that for some reason, I still had
>From within QtCreator, be sure to check the Compile Output tab, not just
the Issues tab at the bottom of the screen. The Issues shows only a
summary, which indeed sometimes is not helpful - it tends to be useful more
once you have a basically working build and you have only "regular" compile
error
pprot forum to figure out that specific problem would be a good idea.
On Tue, Apr 12, 2016 at 1:33 AM antonjazzsax wrote:
> Marc Sabatella wrote
> > I was uncomfortable with making the tie command a toggle, as that would
> > make it harder to correct the situations where this happens
ix to be
made harder. But making the tie command a toggle would have just that
effect, unless we were very careful in implementing it to only work as a
toggle if all selected notes have the same tie status. That's certainly a
possibility.
On Mon, Apr 11, 2016 at 2:58 PM antonjazzsax wrote:
ected.
>
> A simple toggle for tie
> Why not, it might be possible to change the + action so that we can add
> and delete a tie with it.
>
> lasconic
>
> 2016-04-11 1:50 GMT+02:00 Marc Sabatella :
>
>> I can totally agree with the idea of a command to automatically
>
Michael - obviously I don't know the specifics of what you have in mind,
but I *can* say that this is indeed the sort of thing I mean when I say if
there is to be a grand re-design, it should give thought to how it could
fit within the current model of an internal syntehsizer playng a soundfont
we
I can totally agree with the idea of a command to automatically recaculate
note lengths after a copy paste, to replace unnecessary ties with the
correct note value. But this has nothing to do with deleting a tie. I'd
want a single command the did this for the whole selection - I wouldn't
want to
Let me be more specific, then: I am primarily interested in improvements
that benefit people using the default syntheszier *with the default
soundfont* (which, of course, could potentially be something other than the
current default - if there exists a suitable candidate). The 99% of users
I am ta
I can only speak for myself here, as one of many contributors to MuseScore.
I personally find it hard to get excited about a change that will only
benefit users who are using JACK and external synthesizers. That's
probably less than 1% (most likely *much* less than 1%) of users. I'd be
far more
ct
things without the mouse is important, a special "delete tie" command would
be far less valueable..
Marc
On Sun, Apr 10, 2016 at 8:47 AM antonjazzsax wrote:
> Marc Sabatella wrote
> > From your description of the difficulty you are having with ties, it
> > sounds
> >
Also, deleting ties would normally be a pretty rare operation. Comapred to
other items that might be deleted, it's probably *less* common to delete
ties once entered than, say, articulations. I can't imagine reason why
there would need to be a special way to delete ties that is any different
from
Are there any freely available soundfonts (SF2 or SFZ) that actually do any
of this (provide multiple samples for all these different articulations)?
If so, can you point to some documentation on how they are set up? Or
maybe there are standards for this?
On Mon, Apr 4, 2016 at 11:37 AM Peter Eas
I had tried responding earlier but am not sure I succeeded. Anyhow, I
encourage to discuss your ideas here. if you check discussion over the
past couple of weeks, you'll see we've been touching on this topic a bit,
so if you have comments to add to any of those discussions, that could be a
place
ck. The status bar is extra.
> Once the QAccessibleWidget is implemented for a QWidget,
> QAccessibleInterface for QObject and registered you have screen-reader
> support. You might have to implement yourself a QAccessibleWidget depending
> on how you design your search feature for the pale
On Sat, Mar 19, 2016 at 1:51 AM Samadhi Poornima <
samadhipoornima...@cse.mrt.ac.lk> wrote:
> 2). Enable the use of keyboard to navigate to a text element or an
> articulation or a crescendo marking.
>
I think there is probably a pretty straightforward model for how this could
work, based on the
I will first try to address the technical aspects of your questions, from
my personal perspective as one of the developers:
I think you'll find this is a far more complex topic than you might
realize. Just doing the translation from audio to pitches is hard enough,
then on top of that you need to
Thanks for your interest in this project. Do you have ideas on how this
system you mention might work? The main thing thst is not currently
keybaord-acciessible now are the palettes. One idea lasconic had was to
make these searchable much liek the Symbols dialog (press "Z" to display)
or the Ins
FWIW, I think the algorithm to come up with a voicing is the least
important part of this project. Deciding on on overall idesign for how the
feature would work in general is much more important. So hopefully rhe
forum thread generates some good ideas there.
On Wed, Mar 16, 2016 at 7:50 AM Johan
;while note < highest_note-12
> note += 12;
>
> That's all you need to get surprisingly good results.
>
> -- David
>
>
> On Tue, Mar 15, 2016 at 3:55 PM, Tobia Tesan
> wrote:
>
>> On 15/03/2016 23:29, Marc Sabatella wrote:
>>
>> > Indeed
;>> * Include 9th and 13th whenever possible
>>>> * Avoid a minor second at the top of the chord, since it's a strong
>>>> dissonance.
>>>>
>>>> These rules ignore what's in the melody - things get more complex if
>>>>
.
>> 2. Where possible, resolve tensions (7ths or suspensions) of the prior
>> chord using downward, stepwise motion.
>> 3. Where possible, resolve the remaining notes using stepwise motion (up
>> or down).
>> 4. Keep the remaining notes in the middle register - roughly E3
I think from previous discussions there seems to be general agreement that
the way forward is for any chord playback syste, to simply generate actual
notes on an actual staff, the user could then edit or make that staff
invisible etc. So there would really be no special MIDI implications.
With thi
Thanks for taking my comment in the spirit in which it was meant!
If it were just about having an additional way of creating them, I wouldn't
be concerned. But right now, multimeasure rests are an all-or-nothing
thing internally, and this assumption is spread throughout the code. We
have had a n
d for
such a feature.
Marc
On Mon, Mar 14, 2016 at 8:00 PM Marc Sabatella
wrote:
> That sounds much *harder* to me, not easier at all. How is going to all
> that trouble easier than just pressing "M"? Or, better yet, having created
> automatically for you when you generat
That sounds much *harder* to me, not easier at all. How is going to all
that trouble easier than just pressing "M"? Or, better yet, having created
automatically for you when you generate parts from your scores? They break
autmatically at double bars and other significant events, so the "specific
One tip: be sure to start a new branch for the new issue, as described in
the Git Workflow document.
On Sun, Mar 13, 2016 at 6:42 AM Lasconic wrote:
> I can confirm what akhilesh just said.
> If there is anything wrong in the PR, we will comment on github or the
> issue tracker and you will be n
Hello! The place to report possible bugs is in the Support forum on
msuescore.org, or in the Issue Tracker if it's *definitely* a bug (and
crashes are definitely bugs). When posting a bug report, be sure to attach
the specific score you are having problems with and precise steps to
reproducve the
Yes that would be be best. The unforked repo on your system serves no
useful purpose.
On Thu, Mar 10, 2016 at 1:57 AM salil wrote:
> Yes i want to contribute , so should i recompile again using the cloned
> repository after forking and remove the repository I added yesterday
> without
> forking
Adding a break means break *after* that measure, just like it does in a
word processor. So add the break to the measure you want to *end* the
line, not the one you want to *start* the line.,
For further questions on how to use MsueScore, again, please ask in the
support forum.
On Tue, Feb 16, 20
Questions like this are better asked in the support forum on musescore.org
(see "Help / Ask for Help" from within MuseScore doesn't really have a a
way of setting a fixed measure width, so there would be no way I can think
of for any MusicXML tag that specifies this to be interpreted. As for
movin
We use mscVerssion in a score file to track the version it was saved with.
Prior to the release of 2.0, we added code to the end of doLayout() to set
this to the current version, so that the saved version info is used only
during the initial score read & first layout, and then the score is treated
Good points! I recall there are places where we do try to differentiate in
this way, checking to see if a linked element is in the same score as the
original before deciding what to do with it, but I am not sure it's really
the same type of case you are describing. One reason I haven't tried to
tac
There are two addPitch() functions. You want the one that, as I said,
takes a "step" and not a pitch - the one that is called when you enter a
note by typing its letter name.
On Sun, Aug 23, 2015 at 3:45 AM Jim Newton wrote:
> Hi Marc, I haven't dug deeply into the code yet, but it appears that
ses
some button, and the contents of some totally different staff affects what
happens next?
On Sat, Aug 22, 2015 at 11:09 AM Marc Sabatella
wrote:
> Again, you don't even have to know or care if there is an accidental
> applied already, nor do you have to think about transposition.
Again, you don't even have to know or care if there is an accidental
applied already, nor do you have to think about transposition. If you call
the addPitch() function I mentioned, it does all the work for you. Did you
try it? If you want to see how it is used, just find other places where it
is
I think that suggestion does not really make sense given what I thinkl you
are actually trying to do. Your problem is simply that you chose the wrong
function to use to add notes. if you care about line, you should use a
function that works with line, simple as that. You won't have to calculate
If I understand correctly, 1) and 2) would happen in rendermidi somewhere,
hence after layout, hence no issues, and it's only 3) where you are trying
to actually add notes as opposed to playback events?
The I guess the more basic question is, if you are starting from a point of
knowing what line y
I'd still like to understand the broader context - what in general are you
actualy trying to accomplish (a new feature? a bug fix? can you explain how
a user would take advantage of the code you are adding?)
Assuming you are talking about something having to do with playback, then
layout is comple
I'm finally getting around to looking at Andrei's accessible palettes
code. In some quick testing, it does seem to work as advertised. Palettes
have "state" only if focus is placed there using keyboard commands, so for
normal mouse-based use, I see no obvious changes. When I tab into the
palette
It would really help to understand the context - what you are trying to do,
how you are trying to do it. The easy answer is, if you want to do
something that depends on the note being laid out, don't do it until later
in the process.
On Mon, Aug 3, 2015 at 2:56 PM Jim Newton wrote:
> Great, so
Sorry, I guess I just don't have enough context to understand what you are
actually asking here then. It is true that line calculations happen at
specific points in the code - most importantly, if I remember/understand
correctly, during cmdUpdateNotes(), which is called during the layout
process.
I think the code in repeatlist.cpp deals with this. Note we already skip
the first ending on a DS; I guess maybe you mean an option to skip first
ending even when not on the DS? We already have an option to turn off
repeats, but this plays both first and second ending. Might be just as
well to h
Hard to say without understand the actual problem you are perceiving there
to be. Are you saying there is somew sort of bug that can be reproduced by
following some certain series of steps?
On Sun, Aug 2, 2015 at 8:45 AM Marc Sabatella wrote:
> I don't understand. Are you saying
I don't understand. Are you saying your own function is trying to use
"line" as the way of knowing which notes you yourself have not processed
yet? That sounds unlikely to work.
If you are syaing you think there is some sort of problem with now
addNote(0 works, can you give steps to reproduce th
Also, if you browse the source and look at other qDebug() calls, you'll see
we print qStrings all the time, normally using qPrintable().
On Sun, Aug 2, 2015 at 8:22 AM Jim Newton wrote:
> Thanks, i'll give it a try.
>
>
>
> --
> View this message in context:
> http://dev-list.musescore.org/help-
See Note::tpcUserName(), also see how it is used in, for instance,
Note::accessibleInfo().
On Sun, Jul 26, 2015 at 11:22 AM Jim Newton wrote:
> Can someone tell me the correct way to print the "name" of a note (Note
> *note) using qDebug() ?
> By name, I mean something like Ab3, but even somethi
For anyone who didn't see lasconic's post in the forum
(https://musescore.org/en/node/70006), I have been working on a roadmap
document for future development. It is based on the document that was
developed for a recent-ish Google Hangout, but is also augmented by things I
threw in there because I
See the (long) discussion here: https://musescore.org/en/node/32966. Seems
everyone else was pretty unanimous in wanting fingering on standard but
*not* tab, so that is how it was implemented. You might want to start a
discussion in the Technology Preview forum to discuss your reasons for
wanting
upport with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> ___
> Ms
I am not saying don't work on figured bass playback - i'm just saying that
whatever code is written to support it, should *also* be made to support
chord symbols. So if there is someone working on chord symbols, you should
coordinate your efforts. If the other person who was going to work on
chor
MuseScore 2.0.2
> release.
>
>
>
> lasconic
>
>
>
>
>
>
> --
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monito
290420510;117567292;y
> _______
> Mscore-developer mailing list
> Mscore-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
--
Marc Sabatella
m...@outsideshore.com
--
rts that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> ___
> Mscore-developer mailing list
> Mscore-developer@lists.sourceforge.net
> Mscore-developer mailing list
> Mscore-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
--
Marc Sabatella
m...@outsideshore.com
--
One dashboard for servers an
67292;y
> ___
> Mscore-developer mailing list
> Mscore-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
--
Marc Sabatella
m...@outsideshore.com
/clk/290420510;117567292;y
> ___
> Mscore-developer mailing list
> Mscore-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
--
Marc Sabatella
m...@outsideshore.com
---
It's a little confusing with the formatting messed up, but I think yes,
this is "funny". Should still work fine though.
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box mon
tion tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> ___
> Mscore-developer mailing list
> Mscore-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
--
Marc Sabatella
m...@ou
e visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> ___
> Mscore-developer mailing list
> Mscore-developer@lists.sourceforge.net
>
"Cannot read file … bad format"?
> That is what I was seeing. And yes, you are right. There was a “<"
> missing in the xml file.
> It is no doubt my fault. I undoubtedly deleted when I was looking at the
> file with my editor.
>
> You have a clever eye that
May 3, 2015 at 12:55 PM, Jim Newton wrote:
> 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,
To be clear, we normally use the word "corruption" to indicate a measure
woith the improper number of beats, particularly in voice 1. Something
that you can see when you load the score and count the beats. Not sure how
running "diff" would be involved; you seem to be referring to something
very d
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
1 - 100 of 235 matches
Mail list logo
