Hi,
just as an idea, it could be nice to have an option like :delete- intermediate-files in the ly backend. I am not sure, whether lilypond allows for doing this directly, but it could be most simple anyway to do something like the appended diff.
Cheers and have a wonderful day,
Kilian Sprotte
PS: Are you using emacs to edit the code? I sometimes wonder, what a big screen you must have.... ;-)
--- orig/backend_ly.lisp +++ mod/backend_ly.lisp @@ -51,6 +51,10 @@ (append (or exe-opts +lilypond-opts+) (list filename)) :wait t #|:output *standard-output*|#) (progn (unless (probe-file (change-filename filename :ext (or out-ext +lilypond-out-ext+))) (er "compiling")) + (ignore-errors (delete-file (change-filename filename :ext "dvi")) + (delete-file (change-filename filename :ext "log")) + (delete-file (change-filename filename :ext "ps")) + (delete-file (change-filename filename :ext "tex"))) (when view (unless (#+cmu extensions:run-program #+sbcl sb-ext:run-program # +openmcl ccl:run-program (or view-exe +lilypond-view-exe+) (append (or view-exe-opts +lilypond-view-opts+) (list (change-filename filename :ext (or out-ext +lilypond-out-ext+))))
This update should fix a few things--the delete-temp-files is a nice idea--I changed the code a bit so it works with the user setting for target output file (actually, the default output is ps--pdf never seems to work well and Apple's previewer does much better at converting the ps to pdf).
Kilian Sprotte wrote:
Hi,
just as an idea, it could be nice to have an option like :delete- intermediate-files in the ly backend. I am not sure, whether lilypond allows for doing this directly, but it could be most simple anyway to do something like the appended diff.
Cheers and have a wonderful day,
Kilian SprottePS: Are you using emacs to edit the code? I sometimes wonder, what a big screen you must have.... ;-)
And tiny little fonts...
--- orig/backend_ly.lisp +++ mod/backend_ly.lisp @@ -51,6 +51,10 @@ (append (or exe-opts +lilypond-opts+) (list filename)) :wait t #|:output *standard-output*|#) (progn (unless (probe-file (change-filename filename :ext (or out-ext +lilypond-out-ext+))) (er "compiling"))
(ignore-errors (delete-file (change-filename filename :ext"dvi"))
(delete-file (change-filename filename :ext "log"))(delete-file (change-filename filename :ext "ps"))(delete-file (change-filename filename :ext "tex"))) (when view (unless (#+cmu extensions:run-program #+sbclsb-ext:run-program # +openmcl ccl:run-program (or view-exe +lilypond-view-exe+) (append (or view-exe-opts +lilypond-view-opts+) (list (change-filename filename :ext (or out-ext +lilypond-out-ext+))))
fomus-devel mailing list fomus-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/fomus-devel
Hi,
thanks for the new update!!
Am 19.01.2006 um 02:35 schrieb David Psenicka:
This update should fix a few things--the delete-temp-files is a nice idea--I changed the code a bit so it works with the user setting for target output file (actually, the default output is ps-- pdf never seems to work well and Apple's previewer does much better at converting the ps to pdf).
I actually made the opposite experience... If I use tempo markup, the Apple previewer refuses to do the conversion and also this conversion progress bar annoys me....
But thank you for those general settings anyway (I overlooked that...)!
One issue that seems to remain (inside the lilypond backend, I suppose), is the immediate start of a new wedge, after one has finished as in the following:
(fomus:fomus-init :backend '(:lilypond :view t) :filename "/tmp/ fomus" :auto-accidentals nil) (fomus:fomus-newpart 2 :instr :violin) (fomus:fomus-newnote 2 :off 0 :dur 1 :note '(77 0) :marks '(:startwedge< :pp)) (fomus:fomus-newnote 2 :off 1 :dur 1 :note '(77 0) :marks '(:wedge<)) (fomus:fomus-newnote 2 :off 2 :dur 1 :note '(77 0) :marks '(:endwedge< :startwedge> :f)) (fomus:fomus-newnote 2 :off 3 :dur 1 :note '(77 0) :marks '(:endwedge> :mf)) (fomus:fomus-exec)
Sorry for never sending that official debug file - just tell me if thats needed.
Cheers,
-Kilian
Some more bug fixes... The program runs in Allegro 7 (and probably 5, 6) now, and I'll test it in Windows shortly...
Maybe I should set the OS X default to pdf then. The problems I had going straight to pdf (with Lilypond or Ghostscript) had to do with some missing slurs and problems with text, but this was a while ago when I was fiddling around with this...
-David
Kilian Sprotte wrote:
Hi,
thanks for the new update!!
Am 19.01.2006 um 02:35 schrieb David Psenicka:
This update should fix a few things--the delete-temp-files is a nice idea--I changed the code a bit so it works with the user setting for target output file (actually, the default output is ps-- pdf never seems to work well and Apple's previewer does much better at converting the ps to pdf).
I actually made the opposite experience... If I use tempo markup, the Apple previewer refuses to do the conversion and also this conversion progress bar annoys me....
But thank you for those general settings anyway (I overlooked that...)!
One issue that seems to remain (inside the lilypond backend, I suppose), is the immediate start of a new wedge, after one has finished as in the following:
(fomus:fomus-init :backend '(:lilypond :view t) :filename "/tmp/ fomus" :auto-accidentals nil) (fomus:fomus-newpart 2 :instr :violin) (fomus:fomus-newnote 2 :off 0 :dur 1 :note '(77 0) :marks '(:startwedge< :pp)) (fomus:fomus-newnote 2 :off 1 :dur 1 :note '(77 0) :marks '(:wedge<)) (fomus:fomus-newnote 2 :off 2 :dur 1 :note '(77 0) :marks '(:endwedge< :startwedge> :f)) (fomus:fomus-newnote 2 :off 3 :dur 1 :note '(77 0) :marks '(:endwedge> :mf)) (fomus:fomus-exec)
Sorry for never sending that official debug file - just tell me if thats needed.
Cheers,
-Kilian
fomus-devel mailing list fomus-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/fomus-devel
Hi David,
thanks for your fixes, its very nice to see those wedges correct :) Am 26.01.2006 um 07:59 schrieb David Psenicka:
Some more bug fixes... The program runs in Allegro 7 (and probably 5, 6) now, and I'll test it in Windows shortly...
That sounds good (although I wont have the possibility to test Allegro...).
Sorry to come back to the wedges once more. First a general question: In the example
q q q q |
p<-<-<-<-<-<-f>->->-mf
which was created by
:startwedge< :wedge< :endwedge< :startwedge> :endwedge>
would it also be okay to write
:startwedge< :wedge< :wedge< :startwedge> :wedge>
or in other words, are there two possibilities to specify a wedge?
One, with startwedge wedge* endwedge and the other with startwedge wedge*, where the last wedge "means" endwedge? (I suppose the latter could be generated more easily in a CM process, was that your reason to do it like that?)
Now I have a problem once again, sorry, if I turn things around a bit:
q q q q |
p<-<-<-<-<-<-f<-<-<-ff
(Why not a split crescendo.... ;-) )
(fomus:fomus-init :backend '(:lilypond :view t) :filename "/tmp/ fomus" :auto-accidentals nil) (fomus:fomus-newpart 2 :instr :violin) (fomus:fomus-newnote 2 :off 0 :dur 1 :note '(77 0) :marks '(:startwedge< :pp)) (fomus:fomus-newnote 2 :off 1 :dur 1 :note '(77 0) :marks '(:wedge<)) (fomus:fomus-newnote 2 :off 2 :dur 1 :note '(77 0) :marks '(:endwedge< :startwedge< :f)) (fomus:fomus-newnote 2 :off 3 :dur 1 :note '(77 0) :marks '(:endwedge< :FF)) (fomus:fomus-exec)
In my printout, the first wedge does not continue to the third note anymore, but stops on the second. -Kilian
Kilian Sprotte wrote:
Hi,
thanks for the new update!!
Am 19.01.2006 um 02:35 schrieb David Psenicka:
This update should fix a few things--the delete-temp-files is a nice idea--I changed the code a bit so it works with the user setting for target output file (actually, the default output is ps-- pdf never seems to work well and Apple's previewer does much better at converting the ps to pdf).
I actually made the opposite experience... If I use tempo markup, the Apple previewer refuses to do the conversion and also this conversion progress bar annoys me....
But thank you for those general settings anyway (I overlooked that...)!
One issue that seems to remain (inside the lilypond backend, I suppose), is the immediate start of a new wedge, after one has finished as in the following:
(fomus:fomus-init :backend '(:lilypond :view t) :filename "/tmp/ fomus" :auto-accidentals nil) (fomus:fomus-newpart 2 :instr :violin) (fomus:fomus-newnote 2 :off 0 :dur 1 :note '(77 0) :marks '(:startwedge< :pp)) (fomus:fomus-newnote 2 :off 1 :dur 1 :note '(77 0) :marks '(:wedge<)) (fomus:fomus-newnote 2 :off 2 :dur 1 :note '(77 0) :marks '(:endwedge< :startwedge> :f)) (fomus:fomus-newnote 2 :off 3 :dur 1 :note '(77 0) :marks '(:endwedge> :mf)) (fomus:fomus-exec)
Sorry for never sending that official debug file - just tell me if thats needed.
Cheers,
-Kilian
fomus-devel mailing list fomus-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/fomus-devel
fomus-devel mailing list fomus-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/fomus-devel
Finished the MusicXML output and it should also run in Windows now.
Unfortunately, there are some issues importing tremolos, harmonics and a few other things into Siblius and Finale...
Am 03.02.2006 um 09:16 schrieb David Psenicka:
Finished the MusicXML output and it should also run in Windows now.
Unfortunately, there are some issues importing tremolos, harmonics and a few other things into Siblius and Finale...
Cool, that sounds very good, I haven't really tried out the MusicXML using fomus, yet. But from other experiences I made, I believe that neither the import into Finale nor Sibelius (seems to be worse) works without issues that one would categorize as being solely cosmetic. : ( 5-Tuplets seem to be too hard for Sibelius and with Finale I don't remember what (nested tuplets?), but there has been something else as well concerning the rhythmical structure (I only used the demo version, so maybe...).
If one concentrates only on the rhythmical framework, time signatures, durations, tuplets, beaming and pitches, are your experiences with Finale or Sibelius pretty okay?
I have big problems importing rhythms into Sibelius when they involve any kind of tuplet, even triplets (by now I'm sure that this isn't a problem in the XML file but in Sibelius's importing)--the other obvious problem with Sibelius is that the parts don't get grouped correctly, (though this isn't as serious, I put in a way of getting around this--I'm putting in a growing list of "kludge" variables to get around these problems).
I'll put a list of these in the documentation as I find them--I wouldn't trust Sibelius at all at the moment. So far it seems that Finale (with Dolet) imports all of the basic things without mangling them...
Kilian Sprotte wrote:
Am 03.02.2006 um 09:16 schrieb David Psenicka:
Finished the MusicXML output and it should also run in Windows now.
Unfortunately, there are some issues importing tremolos, harmonics and a few other things into Siblius and Finale...
Cool, that sounds very good, I haven't really tried out the MusicXML using fomus, yet. But from other experiences I made, I believe that neither the import into Finale nor Sibelius (seems to be worse) works without issues that one would categorize as being solely cosmetic. : ( 5-Tuplets seem to be too hard for Sibelius and with Finale I don't remember what (nested tuplets?), but there has been something else as well concerning the rhythmical structure (I only used the demo version, so maybe...).
If one concentrates only on the rhythmical framework, time signatures, durations, tuplets, beaming and pitches, are your experiences with Finale or Sibelius pretty okay? _______________________________________________ fomus-devel mailing list fomus-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/fomus-devel
-
David Psenicka -
Kilian Sprotte