"Janek Warchoł" schrieb:
>2014/1/12 Carl Peterson :
>> What I would *ultimately* like is the ability for someone to visually
>write
>> each part on separate staves (or using two staves with two voices
>each),
>> then those parts are translated into the template without any direct
>code
>> manipu
Janek Warchoł writes:
> 2014/1/12 Carl Peterson :
>> What I would *ultimately* like is the ability for someone to visually
>> write each part on separate staves (or using two staves with two
>> voices each), then those parts are translated into the template
>> without any direct code manipulation
2014/1/12 Carl Peterson :
> What I would *ultimately* like is the ability for someone to visually write
> each part on separate staves (or using two staves with two voices each),
> then those parts are translated into the template without any direct code
> manipulation. The visual interface would b
On Sat, Jan 11, 2014 at 11:50 PM, Paul Morris wrote:
> Carl Sorensen-3 wrote
> > I can't speak for Carl P's work. For me, effective LP input files
> require
> > structure (variables, contexts) that MusicXML knows nothing of. And it's
> > generally easier to create them than to fix them on import
Carl Sorensen-3 wrote
> I can't speak for Carl P's work. For me, effective LP input files require
> structure (variables, contexts) that MusicXML knows nothing of. And it's
> generally easier to create them than to fix them on import.
I see what you mean. Unfortunately it makes it harder to use
Am Donnerstag, den 09.01.2014, 10:13 -0500 schrieb Carl Peterson:
> On Thu, Jan 9, 2014 at 6:20 AM, David Kastrup wrote:
> > Another problem is that LilyPond has a usage philosophy and workflow
> > that strongly penalizes manual tweaks. Graphically/manually oriented
> > workflows detract from the
Janek Warchoł writes:
> 2014/1/11 David Kastrup :
>> One very nice integrated experience is offered by preview-latex
>> http://www.gnu.org/software/auctex/preview-latex>.
>
>
> Indeed, this is very nice. Although i haven't used it, i know i would
> enjoy it :)
Well, actually it's a lot better t
2014/1/11 David Kastrup :
> One very nice integrated experience is offered by preview-latex
> http://www.gnu.org/software/auctex/preview-latex>.
Indeed, this is very nice. Although i haven't used it, i know i would
enjoy it :)
j
___
lilypond-devel ma
On Jan 10, 2014, at 11:41 PM, "Paul Morris" wrote:
> Seems like getting just the notes (not layout) out of an
> imported musicXML file should be an easy and straightforward thing, but I
> guess not?
>
I can't speak for Carl P's work. For me, effective LP input files require
structure (vari
Janek Warchoł writes:
> 2014/1/10 Urs Liska :
>>
>> 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 in
>> Fresco
2014/1/10 Urs Liska :
>
> 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 in
> Frescobaldi.
I know that this is not
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
Am 10.01.2014 23:37, schrieb Carl Peterson:
> On Fri, Jan 10, 2014 at 4:25 PM, Urs Liska 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
On Fri, Jan 10, 2014 at 4:25 PM, Urs Liska 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 in
> Frescobal
On 1/9/14 9:43 PM, "SoundsFromSound" wrote:
>dak wrote
>> Joseph Rushton Wakeling >Word document features the
>> consistent use of document styles for arriving at typographically
>> superior results.
>>
>> --
>> David Kastrup
>>
>> __
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 sp
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 e
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
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 dur
On Fri, Jan 10, 2014 at 12:46 AM, Paul Morris 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 have instant a
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 have instant aural feedback on
> what I've written (particularly if I'm not at
dak wrote
> Joseph Rushton Wakeling <
> joseph.wakeling@
> > writes:
>
>> On 09/01/14 12:20, David Kastrup wrote:
>>> Another problem is that LilyPond has a usage philosophy and workflow
>>> that strongly penalizes manual tweaks. Graphically/manually oriented
>>> workflows detract from the impo
On 09/01/14 21:05, David Kastrup wrote:
That must be the reason why the typical Word document features the
consistent use of document styles for arriving at typographically
superior results.
I'm not sure that I feel happy about your benchmark for comparison. I think
Lilypond's user base is a
David Kastrup schrieb:
>Joseph Rushton Wakeling writes:
>
>> On 09/01/14 12:20, David Kastrup wrote:
>>> Another problem is that LilyPond has a usage philosophy and workflow
>>> that strongly penalizes manual tweaks. Graphically/manually
>oriented
>>> workflows detract from the importance of g
Joseph Rushton Wakeling writes:
> On 09/01/14 12:20, David Kastrup wrote:
>> Another problem is that LilyPond has a usage philosophy and workflow
>> that strongly penalizes manual tweaks. Graphically/manually oriented
>> workflows detract from the importance of getting good default
>> typesettin
On 09/01/14 12:20, David Kastrup wrote:
Another problem is that LilyPond has a usage philosophy and workflow
that strongly penalizes manual tweaks. Graphically/manually oriented
workflows detract from the importance of getting good default
typesetting.
I'm not sure that's necessarily the case.
Carl Peterson:
...
> Now, consider an IDE/GUI setup
> (perhaps an extension of Frescobaldi) that would allow me to define a
> variable for a voice, then pop up a musical staff to enter and play
> back the notes for that variable without dealing with the whole
> compilation process. No manual tweaki
On Thu, Jan 9, 2014 at 6:20 AM, David Kastrup wrote:
> Another problem is that LilyPond has a usage philosophy and workflow
> that strongly penalizes manual tweaks. Graphically/manually oriented
> workflows detract from the importance of getting good default
> typesetting.
I don't know that I ag
Urs Liska writes:
> Please don't beat me up, but that's something I wondered about for
> quite some time:
> Is there _any_ notion what a LilyPond 3.0 may be?
> I mean 2.0 followed on 1.8, and now we're already towards .20
>
> Is there any general idea about what would make the next major program
Urs Liska writes:
> Am 09.01.2014 12:03, schrieb Jan Nieuwenhuizen:
>> Urs Liska writes:
>>
>>> Is there _any_ notion what a LilyPond 3.0 may be?
>>
>> I could imagine that if LilyPond were made into an engraving library,
>> and/or heavy rewiring to make it deeply integrated with a gui,
>
> Hm, t
On Thu, Jan 09, 2014 at 12:07:07PM +0100, Urs Liska wrote:
> But it would probably make it more attractive for the consumer
> market if it had a nice default GUI. I personally would be pleased
> to see Frescobaldi become such a default GUI (of course not cutting
> out other options). Particularly g
On Jan 9, 2014, at 1:07 PM, Urs Liska wrote:
> Am 09.01.2014 12:03, schrieb Jan Nieuwenhuizen:
>> Urs Liska writes:
>>
>>> Is there _any_ notion what a LilyPond 3.0 may be?
>>
>> I could imagine that if LilyPond were made into an engraving library,
>> and/or heavy rewiring to make it deeply in
Am 09.01.2014 12:03, schrieb Jan Nieuwenhuizen:
Urs Liska writes:
Is there _any_ notion what a LilyPond 3.0 may be?
I could imagine that if LilyPond were made into an engraving library,
and/or heavy rewiring to make it deeply integrated with a gui,
Hm, this is something I was also thinking
- Original Message -
From: "Urs Liska"
To: "LilyPond Development Team"
Sent: Thursday, January 09, 2014 10:53 AM
Subject: 3.0?
Please don't beat me up, but that's something I wondered about for quite
some time:
Is there _any_ notion what a LilyPond 3.0 may be?
I mean 2.0 followed on
Urs Liska writes:
> Is there _any_ notion what a LilyPond 3.0 may be?
I could imagine that if LilyPond were made into an engraving library,
and/or heavy rewiring to make it deeply integrated with a gui, or accept
another native input language like the lilypond-driven fixed fresh
release of MusicX
Nicolas Sceaux <[EMAIL PROTECTED]> writes:
> My mistake.
> pango 1.4.1 was the debian's one. I have 1.5.0 from (old) CVS. This is the
> one that was used to compile LilyPond with --enable-gui.
> I am upgrading to pango 1.5.2.
>
> What does BLOEDIGE_RAND mean? bleeding edge?
> Should I use pango, g
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> Nicolas Sceaux writes:
>
>>> That's quite strange. I tested on a fresh machine. What versions of
>>> fontconfig/gnome/pango do you use?
>>
>> fontconfig is version 2.2.3
>> gnome is 2.6.1
>> pango is 1.4.1
>>
>> ohoh, maybe I should look at guile-
Nicolas Sceaux writes:
>> That's quite strange. I tested on a fresh machine. What versions of
>> fontconfig/gnome/pango do you use?
>
> fontconfig is version 2.2.3
> gnome is 2.6.1
> pango is 1.4.1
>
> ohoh, maybe I should look at guile-gnome.sh again, and get a more
> recent pango. I'm doing t
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> That's quite strange. I tested on a fresh machine. What versions of
> fontconfig/gnome/pango do you use?
fontconfig is version 2.2.3
gnome is 2.6.1
pango is 1.4.1
ohoh, maybe I should look at guile-gnome.sh again, and get a more
recent pango. I'
Nicolas Sceaux writes:
> (without the closing tag)
Of coures, sorry.
fc-list |grep -i lily
Fontconfig error: "~/.fonts.conf", line 3: mismatched tag
> LilyPond\-feta:style=Regular
Ok.
> but still no feta glyphs displayed when invoking lilypond -fgnome.
That's quite strange. I tested on a f
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> Han-Wen Nienhuys writes:
>
>> I recall that it wasn't so long ago that not all distributions shipped
>> with fontconfig, which is instrumental in getting fonts from
>> ~/.fonts/ configured correctly.
>
> That's it! xset/xlsfonts has nothing todo wi
Lilypond 2.3 is marked as broken on freebsd. Now that I'we moved to
freebsd, I notice a lot more when the luxury of an up to date lilypond
doesn't exist. I will try to do what I can to help straighten it out
before 3.0.
Has anyone heard form Patrick Atamaniuk (the freebsd packager)? I have
had
Han-Wen Nienhuys writes:
> I recall that it wasn't so long ago that not all distributions shipped
> with fontconfig, which is instrumental in getting fonts from
> ~/.fonts/ configured correctly.
That's it! xset/xlsfonts has nothing todo with gnome/pango fonts. It
seems gnome-font-install doesn
[EMAIL PROTECTED] writes:
> Han-Wen Nienhuys writes:
>
> >> > $ ln -s ~/cvs/lilypond/mf/out ~/.fonts
> >> > $ mkfontdir ~/.fonts
> >> > $ xset +fp ~/.fonts
> >>
> >> Something went wrong here. Does xlsfonts report the feta fonts?
> >
> > Could it be that this is system/distribution specifi
Han-Wen Nienhuys writes:
>> > $ ln -s ~/cvs/lilypond/mf/out ~/.fonts
>> > $ mkfontdir ~/.fonts
>> > $ xset +fp ~/.fonts
>>
>> Something went wrong here. Does xlsfonts report the feta fonts?
>
> Could it be that this is system/distribution specific?
Until we know what's wrong, it could be
[EMAIL PROTECTED] writes:
> Nicolas Sceaux writes:
>
> > I have some troubles with it: feta fonts seem not to be found when
> > the gnome output is displayed, although I have done:
> > $ ln -s ~/cvs/lilypond/mf/out ~/.fonts
> > $ mkfontdir ~/.fonts
> > $ xset +fp ~/.fonts
>
> Something went
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> Nicolas Sceaux writes:
>
>> I have some troubles with it: feta fonts seem not to be found when
>> the gnome output is displayed, although I have done:
>> $ ln -s ~/cvs/lilypond/mf/out ~/.fonts
>> $ mkfontdir ~/.fonts
>> $ xset +fp ~/.fonts
>
>
Nicolas Sceaux writes:
> I have some troubles with it: feta fonts seem not to be found when
> the gnome output is displayed, although I have done:
> $ ln -s ~/cvs/lilypond/mf/out ~/.fonts
> $ mkfontdir ~/.fonts
> $ xset +fp ~/.fonts
Something went wrong here. Does xlsfonts report the feta
On Saturday 18 September 2004 13.24, Han-Wen Nienhuys wrote:
> Hi guys,
>
> 3.0 is almost ready. For the 3.0 release
>
> 1. I've put back TeX as the default backend. I welcome patches that
> will Do The Right thing for encodings and landscape options of
> \bookpaper.
>
> 2. I will have a anoth
> Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>> There is also some other good news: some of the dependencies for the
>> LilyPond GNOME backend have been released or are almost ready to be
>> released. This means that in a short while we will have "native"
>> point-and-click, without requiring
[EMAIL PROTECTED] writes:
> > 1. I've put back TeX as the default backend. I welcome patches that
> > will Do The Right thing for encodings and landscape options of
> > \bookpaper.
>
> may I ask why have you put the TeX back-end back as the default?
> although not yet perfect the ps back-end
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> 3.0 is almost ready. For the 3.0 release
that's great!
> 1. I've put back TeX as the default backend. I welcome patches that
> will Do The Right thing for encodings and landscape options of
> \bookpaper.
may I ask why have you put the TeX bac
52 matches
Mail list logo
