Closed xylucien closed 4 years ago
Maybe a path issue - ssh into the machine and see whether lilypond is installed?
i see the problem - lilypond is not installed! more specifically, apt-get is not available on eb server.
yum still works. the problem, however, is that lilypond cannot be found with yum
command
IT WORKS!!!
How come I still get the following?
Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
http://musicxml2abc.musicalkits.me/ ?
it even works on my phone.
http://musicxml2abc.musicalkits.me/get-image/
This is after getting "Get the Score Visualization"
Can you try with this file? I got the error on my Mac's chrome browser. Can you check server logs?
it seems that lilypond cannot process this file... I tried other several music XML files and it worked
i may try to change the image generator to musescore, which theoretically works much better
Ok, I see that for some musicxml files it works, but for the one I sent you, and quite a few others it doesn't and crashes the server. We need to investigate these issues.
But good job on getting the initial steps work.
We at least should catch error and report to user. The server cannot be crashed because of this.
will fix this first.
I am having trouble installing musescore - I can only get the AppImage. The install method on musescore.org
does not work (amazon Linux uses Fedora)
Let's leave the musicscore to a separate issue and deal with that later. Can we first fix the error handling of lilypond?
yes, with the current update the website will never crash.
it is really weird that some files work while others dont. When the error occurs it says must be str, not PosixPath
well, that speaks the complexity of expressing music with computer files, and there are always bugs in software.
I think we should add tests to prevent regression. Furthermore, can you review the previous batches of changes and clean up stuff that are not needed? Let's bring the current version to stable, and then I have some front-end changes to propose.
everything for now is clean. This should be a stable version (aka no website crashing)