2007/7/24, Peter Terpstra <[EMAIL PROTECTED]>:
> http://lists.gnu.org/archive/html/lilypond-user/2007-01/msg00284.html
I absoluteley agree with graham, most people never need the .ps files.
The .ps file is just a temporary file.
I wouldn't put it that way (to me it is an essential fact that
l
Valentin Villenave in
<[EMAIL PROTECTED]> :
> There was a discussion about that a few months ago; maybe we should
> talk about it again...
Thanks to an emailed answer i have the `-ddelete-intermediate-files' option.
This option is now used by default.
> http://lists.gnu.org/archive/html/lilypond
2007/7/24, Peter Terpstra <[EMAIL PROTECTED]>:
PS: does anyone know how to prevent lilypond from making a .ps file?, i only
want the midi and the pdf.
There was a discussion about that a few months ago; maybe we should
talk about it again...
http://lists.gnu.org/archive/html/lilypond-user/200
Peter Terpstra in <[EMAIL PROTECTED]> :
> [ cut : errors ]
*All* the errors are solved by copying the notes in a modern setup!!
That was easy :-P
Peter
PS: does anyone know how to prevent lilypond from making a .ps file?, i only
want the midi and the pdf.
Kind Regards,
Peter
--
mailto:[
Mats Bengtsson in <[EMAIL PROTECTED]> :
> These indicate that you didn't update your file, i.e. that you
> forgot about the -e flag.
I'm Sorry.
This is with the -e flag:
GNU LilyPond 2.10.25
Processing `test.ly'
Parsing...
test.ly: 0: warning: old relative compatibility not used
Interpreting m
Peter Terpstra wrote:
Mats Bengtsson in <[EMAIL PROTECTED]> :
\set Voice.noAutoBeaming = ##t
into
\set autoBeaming = ##f
and
\set Staff.instrument = #"Guitar 1"
into
\set Staff.instrumentName = #"Guitar 1"
But that was not the mainproblem, the mainproblems where the notecollisions.
Mats Bengtsson in <[EMAIL PROTECTED]> :
> \set Voice.noAutoBeaming = ##t
> into
> \set autoBeaming = ##f
> and
> \set Staff.instrument = #"Guitar 1"
> into
> \set Staff.instrumentName = #"Guitar 1"
But that was not the mainproblem, the mainproblems where the notecollisions.
This is what happens
Peter Terpstra wrote:
Mats Bengtsson in <[EMAIL PROTECTED]> :
Since NoteEdit generates LilyPond code corresponding to
an old version of LilyPond, you have to upgrade the syntax
using convert-ly (see the manual for details about using
convert-ly).
That does not help, but thanks for y
Valentin Villenave in
<[EMAIL PROTECTED]> :
> https://canorus.berlios.de/
>
> It's in active development and one of its goals is to be fully
> compatible with LilyPond.
Interesting ...
P.
--
mailto:[EMAIL PROTECTED]
___
lilypond-user mailing lis
Mats Bengtsson in <[EMAIL PROTECTED]> :
> Since NoteEdit generates LilyPond code corresponding to
> an old version of LilyPond, you have to upgrade the syntax
> using convert-ly (see the manual for details about using
> convert-ly).
That does not help, but thanks for your answer.
P.
--
mailto
Since NoteEdit generates LilyPond code corresponding to
an old version of LilyPond, you have to upgrade the syntax
using convert-ly (see the manual for details about using
convert-ly).
/Mats
Peter Terpstra wrote:
Peter Terpstra in <[EMAIL PROTECTED]> :
warning: can't find property type-
2007/7/19, Peter Terpstra <[EMAIL PROTECTED]>:
Hoping that noteedit wil come with a upgrade to better compatibillity with
lilypond.
NoteEdit is no longer developed! Its developers are now working on a
rather exciting project: Canorus score editor
https://canorus.berlios.de/
It's in active de
Peter Terpstra in <[EMAIL PROTECTED]> :
> warning: can't find property type-check for `noAutoBeaming'
> (translation-type?). perhaps a typing error?
"\set Voice.noAutoBeaming = ##t" should be "\set Voice.noAutoBeaming = ##f"
"\set Staff.instrument = #"Guitar 1" should be "\set Staff.instrumentNa
Dear readers,
I liked to work with noteedit, but noteedit does not print any sheet (pdf).
( ... and noteedit does not have all the features i want/need.)
If I leave "keep beams" and "keep stem directions" *unchecked* in noteedit.
I get no errors when converting to pdf and midi.
But ties are crossi
14 matches
Mail list logo
