I think this is important also for us:
http://www.sibeliusblog.com/news/mei-plug-in-released-for-sibelius/
MEI is an important initiative for standardizing the encoding of music,
with particular interest in encoding every aspect of a composition and
its sources. I think this will be an
LGTM, although I'm not sure I could identify weakness in such a patch.
The idea is good. I like the structure and the comments.
https://codereview.appspot.com/50130044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
On Fri, Jan 10, 2014 at 12:46 AM, Paul Morris p...@paulwmorris.com wrote:
Carl Peterson wrote
I use MuseScore,
Scorio, and Finale Notepad (depending on where I am and how I feel)
for compositional work because they provide ease of note entry in the
composing process and the ability to
https://codereview.appspot.com/49470049/diff/1/Documentation/learning/fundamental.itely
File Documentation/learning/fundamental.itely (right):
https://codereview.appspot.com/49470049/diff/1/Documentation/learning/fundamental.itely#newcode1054
Documentation/learning/fundamental.itely:1054: r8 e4
Reviewers: Trevor Daniels,
https://codereview.appspot.com/49470049/diff/1/Documentation/learning/fundamental.itely
File Documentation/learning/fundamental.itely (right):
https://codereview.appspot.com/49470049/diff/1/Documentation/learning/fundamental.itely#newcode1054
On 2014/01/10 17:53:46, dak wrote:
Now the thing is that if you attach ties to
notes without an intervening space (or at least let them stand if they
were so
before), we have possibilities
r8 e4 d c8~ | c8 b16 a b8 g~ g2 |
r8 e4 d c8~ | 8 b16 a b8 g~2 |
r8 e4 d c8~ | 8 b16 a b8 g~ 2 |
tdaniels wrote Friday, January 10, 2014 8:39 PM
It would seem that when you added the respective template lines, you
should have
updated the version number of the file as well.
With hindsight. But we never do that when editing
doc files as a rule.
Now of course, in analogy to the last
On 2014/01/10 20:56:26, t.daniels_treda.co.uk wrote:
Actually this seems to be a consequence of not bumping _all_
version numbers to the current release.
No, it is a consequence of not bumping the version number to the syntax
used for adding material.
A \version header of xx.yy.zz means this
Carl Peterson:
...
I know someone suggested just turning off the PDF conversion to speed
things up, but it's not just a matter of instantaneous aural feedback.
Ok.
There's a visual component and a matter of input error reduction, because I
have been known to enter incorrect octaves or
Am 10.01.2014 22:23, schrieb k...@aspodata.se:
Carl Peterson:
...
I know someone suggested just turning off the PDF conversion to speed
things up, but it's not just a matter of instantaneous aural feedback.
Ok.
There's a visual component and a matter of input error reduction, because I
have
On 2014/01/10 20:39:03, Trevor Daniels wrote:
My preference would be no space before ties, one space after.
That leaves ties properly associated with the note to which
they are a post event, but with a clear separation from the
following note.
So: c'4~ 2~ 2 rather than c'4~2~2 or c'4 ~ 2 ~ 2
Carl Peterson:
...
Retyping by far. I pretty much write exclusively a cappella SATB, and I
have developed a very specific template/workflow for the part combining and
layout. I've tried a few different ways of getting the music from these
formats into LP, and in each case, I found myself
Urs Liska:
Am 10.01.2014 22:23, schrieb k...@aspodata.se:
Carl Peterson:
...
There's a visual component and a matter of input error reduction, because I
have been known to enter incorrect octaves or durations and not realize it
until I've finished typing and have compiled the entire
On 1/9/14 9:43 PM, SoundsFromSound soundsfromso...@gmail.com wrote:
dak wrote
Joseph Rushton Wakeling lt;That must be the reason why the typical
Word document features the
consistent use of document styles for arriving at typographically
superior results.
--
David Kastrup
On Fri, Jan 10, 2014 at 4:25 PM, Urs Liska u...@openlilylib.org wrote:
Well,
compiling a few measures of a single staff feels nearly instantaneous, and
when you're editing an orchestral score this makes a huge difference.
Generally I'd think it would be a good idea to have such an interface
Am 10.01.2014 23:37, schrieb Carl Peterson:
On Fri, Jan 10, 2014 at 4:25 PM, Urs Liska u...@openlilylib.org wrote:
Well,
compiling a few measures of a single staff feels nearly instantaneous, and
when you're editing an orchestral score this makes a huge difference.
Generally I'd think it
Hi Urs,
On 09/01/14 11:01, Urs Liska wrote:
Is there already a clean way to let LilyPond/Scheme code be executed
depending on the version number of the currently executed LilyPond?
If not, would it be useful/acceptable to include something like
Carl Peterson wrote
Retyping by far. I pretty much write exclusively a cappella SATB, and I
have developed a very specific template/workflow for the part combining
and
layout. I've tried a few different ways of getting the music from these
formats into LP, and in each case, I found myself
From a Fringe Coder,
I like Vim (text editor). I like to code with minimal but descriptive
syntax(ie. Visual Basic). XML code for web-applications I find bloated
and working with it is ugly. If MusicXML is guided by the right people
and does become/is a definitive standard that can support the
19 matches
Mail list logo
