So, I guess be aware that if youâre working with complex material, you might end up doing a LOT of hand tweaking of the output. I showed them to a person that was working with us on the scoring part of this project (see above, I donât know music theory / notation well at allâ¦), and he said they were barely comprehensible and definitely wouldnât work for the production setup (really professional ensemble, only 1-2 rehearsals kinda thing) :). no tempo changes, everything rounded to a 1/4 note, etc. output using either SuperFOMUS or the LIlypond quark. I have a few local changes to the lilypond library, but these were bug fixes / score generation issues - Iâm happy to share them if you run into trouble. I donât remember significant problems with running them in current version of SC.IIRC Fomus isnât very stable with respect to itâs syntax, and I recall finding some things where SuperFOMUS output syntax that my build of FOMUS didnât understand.This also pushed me in the direction of the above quark. I ran into pretty serious bugs between SuperFomus and the FOMUS implenentations I was using - scores with certain kinds of elements in them caused FOMUS to crash.I donât know notation really at all, so take that with a grain of salt I was using this because there were a few notational things that SuperFOMUS wasnât doing very well, and this one seemed more powerful. I ended up settling on this Lilypond quark: for score generation.I recently went through a research spike on SuperCollider + FOMUS/Lily for a project. finally, superfomus still doesnât seem to handle some events well and if it fails itâs not clear whatâs wrong.I believe that the files you are working on canât have spaces in the whole path, so no spaces in folder names either (I worked around that by adding quotes in the class file, but I havenât made a pull request to the quark repo yet).Add its path (where you installed it) to the PATH env variable, in my case: "PATH".setenv("PATH".getenv ++ ":/usr/local/bin") and re-run "which fomus".unixCmd, which should now return a path to the fomus executable ![]() "which fomus".unixCmd if this returns non-0, that means that SC canât find fomus. You need to make sure that fomus executable is in the PATH You need to install fomus - the installer fails but I was able to install by hand, I believe Iâm on macOS and the issues I encountered were mostly with handling of paths (and installing fomus itself). For example, if chorus.ily is changed, then 失æéµçº¿èç.ly is made.I have just started using superfomus recently (with 3.10/3.11). The behavior I want is if any of the files in the source directories are changed, the corresponding PDF is updated. I may not have been clear enough with my first question. How can I write a pattern rule that makes each PDF depend on all the files in the appropriate corresponding source directory? EDIT I've looked at the GNU make manual online for help, but I didn't come up with anything that that I was able to apply to my particular situation. I tried doing several different things, like appending $( ![]() ly files in the corresponding directory in src. The PDFs in the out directory depend on the. ![]() I have a directory structure as follows: scores/ I'm using GNU Make on Arch Linux to generate PDFs from LilyPond source files.
0 Comments
Leave a Reply. |