Re: Lilypond to XML Conversion Help
Link to source is here: https://le-concert.pagesperso-orange.fr/boieldieu/19-Boieldieu-CalifeBagdad-LYS.zip Just need violin and viola parts. Thanks everyone for helping! On Tue, Oct 4, 2022 at 2:56 PM Jacques Menu wrote: > Hello Ella, > > I have some experience with MusicXML and I’m interested too in trying to > export your .ly file to MusicXML using Fresco. > > Thanks if you can send me this file. > > JM > > Le 4 oct. 2022 à 22:16, Stephan Schöll a écrit : > > Tried to follow the thread and > > <89v5MD16SNxJTYXF.png> > > - exported an arbitrary ly file using Frescobaldi experimental feature as > Jean described -> *.xml > > - open *.xml file in MuseScore 3.0 > > <2MHR5bs5tHo0qkAF.png> > > (Translation: File xyz is no valid MusicXML file. Should I try to open > anyway?) > > Error message: > > Fatal error: Line 11 Column 29 element 'creator' is not defined in this > area/context (namespace?) > > If I decide for "load anyway" I get a reasonable result in MuseScore (I > have to admit that I never used MuseScore before ;-) ) with only a few > header elements missing. > > > Am 04.10.2022 um 21:38 schrieb Jean Abou Samra: > > Le 04/10/2022 à 21:15, Ella Yu a écrit : > > Thanks Jean. So basically the resulting exported XML literally won't open > in MuseScore because it says it's not a valid XML file, so I went and > opened it in Finale Notepad and then re-exported it and the notes were all > wrong. [...] > > > Interesting. Would you mind sending the .ly file to me? I would like to > understand what is invalid about the generated MusicXML. > > Thanks, > Jean > > > > > > > > >
Re: Lilypond to XML Conversion Help
Hello Ella, I have some experience with MusicXML and I’m interested too in trying to export your .ly file to MusicXML using Fresco. Thanks if you can send me this file. JM > Le 4 oct. 2022 à 22:16, Stephan Schöll a écrit : > > Tried to follow the thread and > > <89v5MD16SNxJTYXF.png> > > - exported an arbitrary ly file using Frescobaldi experimental feature as > Jean described -> *.xml > > - open *.xml file in MuseScore 3.0 > > <2MHR5bs5tHo0qkAF.png> > > (Translation: File xyz is no valid MusicXML file. Should I try to open > anyway?) > > Error message: > > Fatal error: Line 11 Column 29 element 'creator' is not defined in this > area/context (namespace?) > > If I decide for "load anyway" I get a reasonable result in MuseScore (I have > to admit that I never used MuseScore before ;-) ) with only a few header > elements missing. > > > > Am 04.10.2022 um 21:38 schrieb Jean Abou Samra: >> Le 04/10/2022 à 21:15, Ella Yu a écrit : >>> Thanks Jean. So basically the resulting exported XML literally won't open >>> in MuseScore because it says it's not a valid XML file, so I went and >>> opened it in Finale Notepad and then re-exported it and the notes were all >>> wrong. [...] >> >> Interesting. Would you mind sending the .ly file to me? I would like to >> understand what is invalid about the generated MusicXML. >> >> Thanks, >> Jean >> >> >> >> >> >
Re: Lilypond to XML Conversion Help
Tried to follow the thread and - exported an arbitrary ly file using Frescobaldi experimental feature as Jean described -> *.xml - open *.xml file in MuseScore 3.0 (Translation: File xyz is no valid MusicXML file. Should I try to open anyway?) Error message: Fatal error: Line 11 Column 29 element 'creator' is not defined in this area/context (namespace?) If I decide for "load anyway" I get a reasonable result in MuseScore (I have to admit that I never used MuseScore before ;-) ) with only a few header elements missing. Am 04.10.2022 um 21:38 schrieb Jean Abou Samra: Le 04/10/2022 à 21:15, Ella Yu a écrit : Thanks Jean. So basically the resulting exported XML literally won't open in MuseScore because it says it's not a valid XML file, so I went and opened it in Finale Notepad and then re-exported it and the notes were all wrong. [...] Interesting. Would you mind sending the .ly file to me? I would like to understand what is invalid about the generated MusicXML. Thanks, Jean http://www.musicxml.org/dtds/partwise.dtd";> Pomp and Circumstance March No. 1 Frescobaldi 3.1.3 2022-10-04 Edward Elgar 1901 Op. 39, 1 Land of Hope and Glory https://lilypond.org/ Notensatz mit Lilypond - www.lilypond.org Bass electric piano 1 1 electric piano 1 2 1 major 2 4 G 2 Largamente, cantabile G 4 2 1 quarter single Land G 4 2 1 quarter single of F 1 4 1 1 eighth sharp single hope G 4 1 1 eighth single and A 4 2 1 quarter begin glo E 4 4 1 half end ry, D 4 4 1 half begin moth C 4 2 1 quarter end er C 4 2 1 quarter single of B 3 1 1 eighth single the C 4 1 1 eighth single free, D 4 2 1 quarter single how A 3 4 1 half single shall A 3 2 1 quarter single we 2 1 quarter \version "2.22.2" date = #(strftime "%d.%m.%Y" (localtime (current-time))) \header { title = "Pomp and Circumstance March No. 1" opus = "Op. 39, 1" subtitle = "Land of Hope and Glory" composer = "Edward Elgar 1901" copyright = \markup { \tiny \date } tagline = \markup {\with-url #"https://lilypond.org/"; { \small {"Notensatz mit Lilypond - www.lilypond.org" } }} } global = { %\clef soprano \set Score.markFormatter = #format-mark-box-alphabet \compressEmptyMeasures } bassNotes = \relative c'' { \global \dynamicUp % Die Noten folgen hier. \time 2/4 \set Score.currentBarNumber = #115 \set Timing.beamExceptions = #'() \set Timing.baseMoment = #(ly:make-moment 1/4) \set Timing.beatStructure = 1,1 \key g \major \tempo "Largamente, cantabile" \set Score.currentBarNumber = #115 \mark \markup { \box {\bold "I/K"} } g4 g fis8( g) a4 e2 d c4 c b8( c) d4 a2~4 r %{ b2 cis8 d4 e8 a2 d,2 g4 4 g8( fis4) e8 d2~4 r4 \mark \markup { \box {\bold "J/L"} } g4 g fis8( g) a4 e2 d c4 c b8( c) d4 a2~4 r b4. 8 cis8( d4) e8 a2 d,2 \breathe c'4 c c8( b4) a8 b2~4 r
Re: Lilypond to XML Conversion Help
Le 04/10/2022 à 21:15, Ella Yu a écrit : Thanks Jean. So basically the resulting exported XML literally won't open in MuseScore because it says it's not a valid XML file, so I went and opened it in Finale Notepad and then re-exported it and the notes were all wrong. [...] Interesting. Would you mind sending the .ly file to me? I would like to understand what is invalid about the generated MusicXML. Thanks, Jean
Re: Lilypond to XML Conversion Help
Thanks Jean. So basically the resulting exported XML literally won't open in MuseScore because it says it's not a valid XML file, so I went and opened it in Finale Notepad and then re-exported it and the notes were all wrong. I'll have to look at how to export the MIDI fles as it requires some LilyPond code know-how and I don't really know anything about the LilyPond code. I'll think about it, since I don't need those fles ready urgently but I do need them later this month. On Tue, Oct 4, 2022 at 12:04 PM Jean Abou Samra wrote: > Le 04/10/2022 à 21:00, Ella Yu a écrit : > > Hi everyone, Thanks for telling me about the enable experimental > > features thing. I did finally see the export XML function but the > > results are terrible. Unfortunately I can't find the export MIDI > > option. Can someone please explain how to access it? Thanks. > > > > I am curious to know about the shortcomings of this Frescobaldi > feature. Could you tell more about it? > > MIDI export is a feature of LilyPond itself, not Frescobaldi. It's > documented here: > > https://lilypond.org/doc/v2.23/Documentation/notation/the-midi-block > > In short, you have to wrap the music of each piece in a \score > block if it's not already the case, and add a \midi { } block > inside \score. > > Best, > Jean > > >
Re: Lilypond to XML Conversion Help
Le 04/10/2022 à 21:00, Ella Yu a écrit : Hi everyone, Thanks for telling me about the enable experimental features thing. I did finally see the export XML function but the results are terrible. Unfortunately I can't find the export MIDI option. Can someone please explain how to access it? Thanks. I am curious to know about the shortcomings of this Frescobaldi feature. Could you tell more about it? MIDI export is a feature of LilyPond itself, not Frescobaldi. It's documented here: https://lilypond.org/doc/v2.23/Documentation/notation/the-midi-block In short, you have to wrap the music of each piece in a \score block if it's not already the case, and add a \midi { } block inside \score. Best, Jean
Re: Lilypond to XML Conversion Help
Hi everyone, Thanks for telling me about the enable experimental features thing. I did finally see the export XML function but the results are terrible. Unfortunately I can't find the export MIDI option. Can someone please explain how to access it? Thanks. On Tue, Oct 4, 2022 at 11:50 AM Jean Abou Samra wrote: > Le 04/10/2022 à 18:51, Ella Yu a écrit : > > Hi everyone, I know the subject of xml export has been discussed a > > lot, but I do need help. I found some LilyPond files online for a > > particular piece that I need to convert to xml so I can then turn it > > into braille music. I know nothing about LilyPond code but am willing > > to give command line options a shot if it doesn't involve a lot of > > coding. I am using Windows. I am aware that experimental xml export is > > available but I want something reliable. And yes, I do have > > Frescobaldi and am willing to try MIDI export but I can't get that to > > work either. Any and all help is hugely appreciated. If anyone wants > > to help do the conversion for me, I am more than happy to send the > > files over privately. The files are some orchestral parts for a piece > > that's not too long. > > > > I will save you time searching: at this time, no completely > reliable option for converting LilyPond to MusicXML exists. > > The best option available is Frescobaldi's function, which > you can try out by activating experimental features in > Edit > Preferences, then restarting Frescobaldi, opening the > file, and using Import/Export > Export MusicXML. > > Best, > Jean > >
Re: Lilypond to XML Conversion Help
Le 04/10/2022 à 18:51, Ella Yu a écrit : Hi everyone, I know the subject of xml export has been discussed a lot, but I do need help. I found some LilyPond files online for a particular piece that I need to convert to xml so I can then turn it into braille music. I know nothing about LilyPond code but am willing to give command line options a shot if it doesn't involve a lot of coding. I am using Windows. I am aware that experimental xml export is available but I want something reliable. And yes, I do have Frescobaldi and am willing to try MIDI export but I can't get that to work either. Any and all help is hugely appreciated. If anyone wants to help do the conversion for me, I am more than happy to send the files over privately. The files are some orchestral parts for a piece that's not too long. I will save you time searching: at this time, no completely reliable option for converting LilyPond to MusicXML exists. The best option available is Frescobaldi's function, which you can try out by activating experimental features in Edit > Preferences, then restarting Frescobaldi, opening the file, and using Import/Export > Export MusicXML. Best, Jean
Re: Placement of Coda
Le 03/10/2022 à 14:44, Greg Lindstrom a écrit : Hello All, I keep learning and my score is looking even better! With help from this list, I separated the Coda from the main body of the score and even figured out how to suppress a time signature which was appearing at the end of the "blank" line between the main part and coda. The even better part is that I place all my "transition" code (the tempo, time signature and any other "common" code going into every part) in variables so all I had to do was modify this "transition" variable and every part was updated! I'm getting some (apparent) inconsistencies with where the Coda sign is being placed: Solo Euphonium (placement is great, maybe a bit high): [image] Here's the Bass Trombone part. Notice the Coda sign is much lower (actually touching the staff). This appears to be due to the Solo Euphonium having the 3 measures rest which must fint "under" the Tempo marking. [image] And the Eb Bass part is colliding with the clef sign. Is this due to a lack of key signature? [image] Here's the transition definition: [...] \once \override Staff.KeySignature.break-visibility = #end-of-line-invisible \once \override Staff.TimeSignature.break-visibility = #end-of-line-invisible \once \override Staff.Clef.break-visibility = #end-of-line-invisible \once \override Score.RehearsalMark.extra-offset = #'( -5 . -3 ) Here you are using extra-offset on the RehearsalMark. extra-offset is for last resorts, and the reason is exactly what you are experiencing: it acts after LilyPond has done all its spacing, just before outputting the object, so it completely bypasses the formatting engine. Because of the multi-measure rest number "3", the mark is placed higher by default in the first case (solo euphonium) than in the others. Then you ask LilyPond to put this mark lower, which causes the collisions. Instead, use something like \once \override Score.RehearsalMark.padding = 0 \once \override Score.RehearsalMark.outside-staff-padding = 0 padding is the minimum distance from the staff, while outside-staff-padding is the minimum distance from any object, including the staff. Best, Jean
Lilypond to XML Conversion Help
Hi everyone, I know the subject of xml export has been discussed a lot, but I do need help. I found some LilyPond files online for a particular piece that I need to convert to xml so I can then turn it into braille music. I know nothing about LilyPond code but am willing to give command line options a shot if it doesn't involve a lot of coding. I am using Windows. I am aware that experimental xml export is available but I want something reliable. And yes, I do have Frescobaldi and am willing to try MIDI export but I can't get that to work either. Any and all help is hugely appreciated. If anyone wants to help do the conversion for me, I am more than happy to send the files over privately. The files are some orchestral parts for a piece that's not too long. Thanks so much, Ella
Re: edition-engraver engine.scm with 2.23.6
Hi, Le 28/09/2022 à 12:13, Jean Abou Samra a écrit : It seems that LilyPond does an inappropriate type check on the second argument of ly:make-stream-event (pair? instead of cheap-list?), but it also looks like edition-engraver is missing some bits. The basic failure in LilyPond is fixed now (https://gitlab.com/lilypond/lilypond/-/merge_requests/1644), although the deeper problems of the edition engraver remain. Best, Jean