I reloaded LilyPond and mapped the denemo externales field to the Lilypond application and denemo is happy now.
I had installed LilyPond in my initial troubleshooting before contacting you and was able to paste from the denemo Lilypond window to a text file, change the extension to ly, and have LilyPond compile the file to a pdf. But I could not get it to work through denemo so I uninstalled Lilypond and reached out for your help. Thank you and Joseph for all your help. Stephen On Fri, Mar 12, 2021 at 6:52 AM Richard Shann <[email protected]> wrote: > On Thu, 2021-03-11 at 19:25 -0500, Stephen Crowley wrote: > > Richard I removed denemo from my system and scrubbed every > remnant > > of denemo from the system files on my machine. I downloaded 2.51, > > scanned it with Windows defender and Malwarebytes and unzipped it > and > > installed it on my machine. The same error has recurred. > > Thank you very much for looking into this so thoroughly. > > > > > I checked for the version of lilypond-windows.exe and there was no > > response. I also checked the version of lilypond.exe and it > returned > > the value 2.22.0. > > > > I created a test.ly file and tried running it with both executables > > and the results are below. > > The best thing to do is to go to http://lilypond.org/ and download > the > current stable version of LilyPond. If you can test that via the > Command Prompt window and if it works then you will be able to set > the > File->Edit->Change Preferences->Externals->lilypond field to the full > pathname of the lilypond-windows.exe executable and Denemo should > work. > > If, on the other hand, a pristine download from lilypond.org fails to > execute properly on your machine we could approach the much larger > LilyPond community for a fix. > > From the error message you got running lilypond.exe I would have > guessed that there is more than one Pango library on your system and > for some reason a process is looking outside of the Denemo zip file > for > it - the obvious reason would be that some previously installed > software has set a global environment variable to point to its > preferred version of Pango. This could be fixed by un-setting the > offending variable on startup if you are able to look at the > environment variables on your system (they are rather hidden away on > Windows systems :( ). > > Lastly, our libraries are closed at present but when they were open I > took a USB stick with the denemo zip file on it and ran Denemo on it > successfully - if you have access to any other Windows 10 machine you > may be able to narrow down the problem that way. > > Thanks again for looking into this. > > Richard > p.s. Joe - if you have the time to repeat Stephen's test of the > bundled > version of Denemo from the Command Prompt on your Windows 10 machine > that would be comforting ... >
