Hi,
2014-09-08 12:51 GMT+00:00 Johan Vromans :
> Hi,
>
> Often when processing music imported from Sibelius I have the problem
> that Sibelius doesn't seem to care whether a tie connects notes of the
> same pitch. As a consequence, some Sibelius users have become lazy and
> always use a tie even w
Maybe you could ask the people at NeoScores.
They are working on (or have aleady released?) a MusiXML cleaning tool. IIUC
this is one type of issues they might addtess.
Urs
On 8. September 2014 14:51:18 MESZ, Johan Vromans wrote:
>Hi,
>
>Often when processing music imported from Sibelius I hav
Hi,
Often when processing music imported from Sibelius I have the problem
that Sibelius doesn't seem to care whether a tie connects notes of the
same pitch. As a consequence, some Sibelius users have become lazy and
always use a tie even when the pitches differ.
LiliPond emits an error message wh
On Sun, Nov 14, 2010 at 2:02 PM, Trevor Daniels wrote:
>>> a~ b
>> should not be silently ignored, but issue a warning or error.
Ok, I've opened two tracker pages: one about the warning message, and
another one about the tie-turned-slur feature request:
http://code.google.com/p/lilypond/issues/de
Johan Vromans wrote Sunday, November 14, 2010 12:36 PM
Valentin Villenave writes:
On Sat, Nov 13, 2010 at 9:45 AM, David Kastrup
wrote:
Lilypond would see if that were the case.
What, are you implying that LilyPond should decide that
...
This seems haphazard to me. Perhaps I misundersto
2010/11/14 David Kastrup
> Valentin Villenave writes:
>
> > On Sun, Nov 14, 2010 at 12:38 PM, David Kastrup wrote:
> >> Means a tie, as indicated by the user.
> >
> > Oh. So, setting tieWaitForNote would disable the "automatic-slurs"
> > feature?
>
> They would be mutually exclusive, and both o
Valentin Villenave writes:
> On Sat, Nov 13, 2010 at 9:45 AM, David Kastrup wrote:
>> Lilypond would see if that were the case.
>
> What, are you implying that LilyPond should decide that
> ...
> This seems haphazard to me. Perhaps I misunderstood your comment?
I don't know what exactly tieWait
Valentin Villenave writes:
> On Sun, Nov 14, 2010 at 12:38 PM, David Kastrup wrote:
>> Means a tie, as indicated by the user.
>
> Oh. So, setting tieWaitForNote would disable the "automatic-slurs"
> feature?
They would be mutually exclusive, and both off by default, resulting in
a warning inste
On Sun, Nov 14, 2010 at 12:38 PM, David Kastrup wrote:
> Means a tie, as indicated by the user.
Oh. So, setting tieWaitForNote would disable the "automatic-slurs" feature?
> Means bad input. Configurable to be treated as a slur to b.
Then it would no longer be "bad input", would it?
I was abo
Valentin Villenave writes:
> On Sat, Nov 13, 2010 at 9:45 AM, David Kastrup wrote:
>> Lilypond would see if that were the case.
>
> What, are you implying that LilyPond should decide that
>
> #1:
> a~ b
>
> ...means a slur
Means bad input. Configurable to be treated as a slur to b.
> BUT
>
>
On Sat, Nov 13, 2010 at 9:45 AM, David Kastrup wrote:
> Lilypond would see if that were the case.
What, are you implying that LilyPond should decide that
#1:
a~ b
...means a slur
BUT
#2:
\set tieWaitForNote = ##t
a~ b c d | e1 | a,
...means a tie
BUT
#3:
a~ b c d
[insert 42 measures here w
Il 13/11/2010 09:45, David Kastrup ha scritto:
Valentin Villenave writes:
On Fri, Nov 12, 2010 at 9:52 PM, Johan Vromans wrote:
Is there a reason why LP doesn't flag this as an error?
Yes, because users might want to set tieWaitForNote = ##t in which
case "a ~ b" will wait
Valentin Villenave writes:
> On Fri, Nov 12, 2010 at 9:52 PM, Johan Vromans wrote:
>> Is there a reason why LP doesn't flag this as an error?
>
> Yes, because users might want to set tieWaitForNote = ##t in which
> case "a ~ b" will wait for another "a" in order to close the tie.
Lilypond would
On Fri, Nov 12, 2010 at 9:52 PM, Johan Vromans wrote:
> Is there a reason why LP doesn't flag this as an error?
Yes, because users might want to set tieWaitForNote = ##t in which
case "a ~ b" will wait for another "a" in order to close the tie.
Cheers,
Valentin.
Johan Vromans writes:
> We all know the difference between a tie and a slur, but some people are
> lax and some composer software packages don't really care...
>
> After automatic conversion of sibelius scores to lilypond I often have
> ties where a slur is needed, i.e., between notes of differen
Am 11.11.2010 17:20, schrieb Johan Vromans:
Valentin Villenave writes:
Are you referring to something like
http://code.google.com/p/lilypond/issues/detail?id=461 ?
Not quite. I was referring to two really different notes (e.g. a and b).
These should not be tied but it would be nice
Valentin Villenave writes:
> Are you referring to something like
> http://code.google.com/p/lilypond/issues/detail?id=461 ?
Not quite. I was referring to two really different notes (e.g. a and b).
These should not be tied but it would be nice if a ~ b was treated as
a ( b ) .
It's not a big is
On Thu, Nov 11, 2010 at 12:05 PM, Johan Vromans wrote:
> We all know the difference between a tie and a slur, but some people are
> lax and some composer software packages don't really care...
>
> After automatic conversion of sibelius scores to lilypond I often have
> ties where a slur is needed,
We all know the difference between a tie and a slur, but some people are
lax and some composer software packages don't really care...
After automatic conversion of sibelius scores to lilypond I often have
ties where a slur is needed, i.e., between notes of different pitch.
LilyPond ignores such a
19 matches
Mail list logo
