Re: [Mutopia-discuss] Mutopia Project update #5
Thanks for the specific target. I have wondered about this tolerance. A quick histogram of our current state gives this (pared down to the major revision numbers): versioncount - -- 2.11 2.25 2.441 2.697 2.72 2.8146 2.916 2.10 454 2.11 308 2.12 186 2.13 27 2.14 75 2.16 314 2.17 1 2.18 209 2.19 59 Lots of work to do to get to the 2.8 area but nothing like the 2.10 - 2.12 hurdle. On Thu, Aug 27, 2015 at 10:20 PM, David Kastrup d...@gnu.org wrote: Glen Larsen glenl@gmail.com writes: This update will clear 2 LilyPond revisions from the Mutopia Project catalog. At the start of these update projects the total count of LilyPond versions in use was 127 and we are currently at 97. Now that all pieces are now in the 2.* range so, hopefully, the update tasks should be easier. Obviously, careful review must be done as they are converted to newer revisions. Current LilyPond executables refuse even trying to compile a file when the version is older than 2.7.38. While the probability of compiling without running convert-ly is likely not fabulous and the number seems somewhat arbitrary, it would appear to make for a nice milestone. -- David Kastrup ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] Opus transcriptions: one at a time or all at once?
I'm starting a new set of transcriptions, Aguado's Op. 3, and since this is only 8 small pieces, is there a preference for the work to be presented as one document of the entire opus, or 8 individual documents? (I prefer single pieces since I rarely print an entire opus at home.) Also, I am considering developing the tab notation for these. Previously, I have concentrated on making the score look as much like the original as possible but when I want to learn a piece I print it with tab notation because I can learn it quicker and this extra effort is easy with LilyPond. Also, I find that string and finger notation near the notes is distracting. WARNING: I'll be starting another update task next week. -glen ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Peter Pan incidental music
Taking a look at the title page on google books I would say that the source field in the header should read: source = Price Reynolds, 41, Berners Street W, London This, along with the publication date, provide a clear statement of what you used as a base for this transcription. You may want to use the phrase, The Music to J. M. Barrie’s Successful ... as a subtitle, depending on how busy you want the top of the page to look. Regarding a new style called incidental: as you observed it is not a style so much as it is an explanation for its purpose or, possibly, its brevity. I think study or overture would fall into the same category. In this collection, there is a music for The Pirates Depart which would be a fair result when searching for a march so I'm leaning towards selecting from existing styles. This is a good place for that discussion but you could also add it as an issue in github if you feel strongly about it. -glen On Tue, Dec 23, 2014 at 9:13 PM, Joel C. Salomon joelcsalo...@gmail.com wrote: On 12/23/2014 11:31 PM, Edward Cannon wrote: On Dec 23, 2014, at 7:53 PM, Joel C. Salomon joelcsalo...@gmail.com wrote: Earlier this evening, I wrote: I've just come across the incidental music to the original stage production of Peter Pan; or, The Boy who wouldn't Grow Up. Both Google Books (http://books.google.com/books?id=J-wQYAAJ) and the Internet Archive (https://archive.org/details/musictojmbarrie00barrgoog) seem to think this music, published in 1905, is in the public domain. snip According to http://worldcat.org/identities/lccn-no2002041637/, Crook lived from 1852--1922; his music is safely in the public domain. Does anyone know if there are specific legal restrictions on this music in the UK? As I recall Peter Pan is under perpetual copyright there-I wonder if that extends to this music as well, or just the text of the play. The text of the law, quoted at http://en.wikipedia.org/wiki/Peter_and_Wendy#United_Kingdom, implies it would not apply to the music detached from a performance of the story. But there's no need to play lawyer about this: J. M. Barrie gifted the copyright to Peter Pan to the GOSH, but the copyright to the music was never his to give away. The copyright page on the PDF reads, COPYRIGHT, MCMV FOR ALL COUNTRIES BY PRICE REYNOLDS., Price Reynolds being the publishers of the song book; and what rights the publishers didn't own would have been Crook's -- or possibly the Duke of York's Theatre's. In any case, this would never have been included in Barrie's gift. (But just in case, I wrote to the copyright folks at the GOSH to confirm this.) --Joel ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] reviewing pull requests in github
Ah, so right. My apologies for not doing deeper research. I'll take a more complete look later today. On Thu, Dec 4, 2014 at 3:12 AM, Federico Bruni f...@inventati.org wrote: Il giorno gio 4 dic 2014 alle 8:00, Glen Larsen glenl@gmail.com ha scritto: These instructions are modifying an inactive pull request. Looking at the first section about modifying an *active* pull request locally it mentions following commands given at the bottom of a pull request. Right, but only collaborators can merge a pull request through github. On the bottom of any pull request I can see only: This pull request can be automatically merged by project collaborators. Only those with write access to this repository can merge pull requests. ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] Latest update milestone
At this time there are only 5 pieces available for assignment in the phase 3 update task. It has been 2 days since the task was announced and the team has generated 14 pull requests. At the completion of this task the Mutopia Project archive will have no pieces built with LilyPond older than version 2.2. Thanks so far to the volunteers: Federico Bruni Abel Cheung Felix Janda Paul Morris Javier Ruiz-Alma Knute Snortum Francisco Vila The list and unassigned pieces can be viewed at the milestone tracker https://github.com/chrissawer/The-Mutopia-Project/issues/435 for this series of updates. -glen ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] Phase 3 updates
This is a request for volunteers to participate in another series of updates for the Mutopia Project archive. The 27 pieces in this set are all built with LilyPond version 2.1.*. Each target piece is entered as a GITHUB issue. This GITHUB milestone tracker https://github.com/chrissawer/The-Mutopia-Project/issues/435 will be used to track assignments. To participate: 1. Select an unassigned piece (not checked off in the tracker) 2. Send me an email informing me that you would like that piece assigned to you 3. Wait for my confirmation before starting to reduce the risk of duplicating effort 4. You may submit your update by email to me or through a pull request in GITHUB I'll process all assignment requests quickly as possible from the west coast of California, Pacific Daylight Time (-7 UTC.) Happy updating! -glen Mutopia Project WIKI https://github.com/chrissawer/The-Mutopia-Project/wiki Mutopia Project Contributing page http://www.mutopiaproject.org/contribute.html ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Contribute document clarification
On Wed, May 14, 2014 at 8:17 AM, Knute Snortum ksnor...@gmail.com wrote: In https://github.com/chrissawer/The-Mutopia-Project/wiki/Setting-up-for-Contributions-via-GITHUB Under Synchronize with your local repository, Couldn't $ git fetch upstream$ git merge upstream/master be simplified to $ git pull upstream master Yes. There is little or no difference. I've always done it in two steps out of habit. ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] clean pull requests?
Of course this will work --- master is a branch like any other branch and you could specify master in your pull request. It is not recommended practice because: - You now have to wait until that pull request is processed to submit other work - If you now create a branch that change is part of the new branch - You are presuming that your pull will be accepted - Ideally, you want the master in your fork repository to always match the fork in the upstream master. Creating a branch is cheap and mostly convenient. And yes, I understand the difficulty of multiple development branches where you want some bit of code from a sibling branch. Even in my own personal projects I don't ever edit in the master branch. [ ... snipped ... ] ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] git advice: remove a merge
On Wed, May 14, 2014 at 11:23 AM, Knute Snortum ksnor...@gmail.com wrote: Thanks Felix, I'll try that. If I can close a pull request, I don't see how to on GitHub. I may just be missing it, though. If anyone knows how to do it, please tell me. Closing is a product of merging the pull request. I believe if you delete the branch of the pull request in your remote fork it will effectively cancel/remove the pull request. I am assuming you still have the topic branch in your local repository! ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] clean pull requests?
In Mutopia there is typically no real need to merge other updates into a development branch because [1] it doesn't have dependencies to other parts of the Mutopia archive and [2] changes to a single piece within the archive are done by a single individual. I would prefer a minimal number of commit messages so I may add some pointers to resources explaining how to squash commits in GIT. [Thanks for the wiki edits, Federico!] On Tue, May 13, 2014 at 3:14 PM, Federico Bruni f...@inventati.org wrote: Il giorno mar 13 mag 2014 alle 23:09, Javier Ruiz-Alma jav...@ruiz-alma.com ha scritto: Hi Federico, Glen graciously added instructions on how to setup your github fork, and basic workflowhttps://github.com/chrissawer/The-Mutopia-Project/wiki/Setting-up-for-Contributions-via-GITHUB involved in maintaining existing pieces in Mutopia using github. He also a started a document to highlight LilyPond coding practiceshttps://github.com/chrissawer/The-Mutopia-Project/wiki/Best-practices-for-new-submissions for new submissions to Mutopia, which enhance the maintainability moving forward. Today, I drafted a new doc covering new submissions: https://github.com/chrissawer/The-Mutopia-Project/wiki/Guidelines-for-new-score-submissions-using-github Github has proven to be a great environment for code collaboration, and we welcome contributors using pull-requests. Javier Ruiz-Alma On Tuesday, May 13, 2014 8:29 AM, Federico Bruni f...@inventati.org wrote: I've just given a quick glance to the pull requests sent today by ksnortum. I see a lot of merge commits which are unnecessary. I don't know how this is sorted out when merging.. I'm writing here to get some feedback on how to improve our wiki: https://github.com/chrissawer/The-Mutopia-Project/wiki/Setting-up-for-Contributions-via-GITHUB I usually try to avoid any merge commit in my pull requests. I think that it's all about rebasing instead of merging, right? It should be quite easy for us, I think, since we usually organize and book the files to be added/updated. Suggestions are welcomed. Thanks Federico ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss Thanks Javier, this new page was the missing bit! I've updated the main page of the wiki and added an index of the articles (even if there's an automatic list under Pages on the right). It seems that wiki links are better: - [[|]] https://help.github.com/articles/adding-links-to-wikis https://github.com/chrissawer/The-Mutopia-Project/wiki ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Update to 2.16/2.18: next step?
I have enjoyed these update projects and plan more of them in the future. Right now I am absorbed in a transcription of Chopin's Nocturne, op 9, no 3 and I hope to get that done before moving house in about a month. When all that dust clears I hope to get another update chunk started. Until then, there is always this typesetting projecthttps://github.com/chrissawer/The-Mutopia-Project/issues/355 ... -glen On Thu, May 8, 2014 at 11:11 AM, Federico Bruni f...@inventati.org wrote: Glen, I see that most of pull requests are cleared. Let's start a new session of updates? -- Federico ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Presenting multi-movement music as one piece
It was interesting to review how differently Bach's French Suiteshttp://www.mutopiaproject.org/cgibin/make-table.cgi?collection=bachfrpreview=1and English Suiteshttp://www.mutopiaproject.org/cgibin/make-table.cgi?collection=bachengpreview=1are presented in Mutopia collections. The French Suites are presented with all parts of the suites available in a zipped PDF and the English Suites are presented with each piece as a separate Mutopia piece. I prefer the way the English Suites are presented --- I can simply download a single part of the suite --- but it seems that you would want to follow the layout as it is currently described for the collection you are working on so all parts stay somewhat consistent. Collections give you can give you flexibility with regards to final presentation. In addition to the individual pieces, an edition can be created with all pieces in a single PDF and put in the collections area. This is done with Sor's Opus 2http://www.mutopiaproject.org/cgibin/make-table.cgi?collection=sorop2preview=1and Blake's Opus 2http://www.mutopiaproject.org/cgibin/make-table.cgi?collection=blakeop2preview=1 . -glen On Sun, Apr 27, 2014 at 1:47 PM, Knute Snortum ksnor...@gmail.com wrote: I am working on two projects where there are several movements in the piece and no way to get the piece as one PDF/PS file. The way it is done now it seems is a zip file is created and all the movements are put in there. This is fine when the files are named something like Movement 1, Movement 2, etc. But with Bach's French Suites the movements are named things like Allemande, Menuet, Gigue, etc. There is no indication of which movement is played first, second, and so on. There are several possible solutions to this. The easiest would be to rename the files something like 01-allemande.ly, 02-gigue.ly, etc. Then we can still use the zip file structure. Another way is to include a README file that says, First movement: Allemande, Second: Gigue, etc. The third way is the hardest, but it would mean a person could download the entire multi-movement piece as one unit, and that the typesetter could make adjustments to the full score. What we could do it create ily (LilyPond include) files that have all the raw music info. Then there would be a shell ly file that includes one ily file for a single movement download. The last ly file would pull all the movements into one score for the entire suite. So for a five movement piece there would be five include files, five shell ly files for individual movements and one shell file for the whole thing. These would be compiled into PS and PDF files. Any thoughts on this? Knute Snortum (via Gmail) ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Call for volunteers: phase II updates
Javier has pointed out that each issue in this milestone requests that the piece be updated to 2.18 and that this might discourage some volunteers. Please note that you are free to use any relatively current stable version for these updates. Believe me, we would be ecstatic to get a piece converted from 2.0 to 2.14! Thanks, -glen On Mon, Feb 17, 2014 at 11:16 PM, Glen Larsen glenl@gmail.com wrote: I have begun another set of updates --- 15 files --- for the Mutopia Project and volunteers are welcome. When complete, we will have cleared the archive of all pieces built with LilyPond versions 2.0.1, 2.0.2, and 2.0.3. The target pieces and assignments are listed and will be tracked in this GITHUB milestone trackerhttps://github.com/chrissawer/The-Mutopia-Project/issues/283. There are 15 pieces and I have assigned myself to the first one. I will keep this tracker updated as pieces are assigned and completed. To volunteer, select a piece from the list that interests you and send me an email with the details. To prevent duplication of work, do not start on updates until I respond to you with a confirmation. You can submit the finished update to me by mail or with a GITHUB pull request. -glen [ Thanks, Javier, for the idea on this style of milestone tracking. ] ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Call for volunteers: phase II updates
There is a wiki article, Updating LilyPond files for Mutopiahttps://github.com/chrissawer/The-Mutopia-Project/wiki/Updating-Lilypond-files-for-the-Mutopia-Project. This is an evolving document and experienced contributors are invited to make edits, especially to the last section, 'Random Hints and Tips'. These phased updates are targeting the very oldest and, consequently, the more difficult pieces to convert. You might want to start with a piece written for your instrument that is not quite so old before jumping in. Obviously, you don't have to wait for these phased updates. I welcome you to accept the challenge and engage users on mutopia-discuss if you get stuck. -glen On Tue, Feb 18, 2014 at 3:07 AM, Philip Rhoades p...@pricom.com.au wrote: Glen, On 2014-02-18 18:16, Glen Larsen wrote: I have begun another set of updates --- 15 files --- for the Mutopia Project and volunteers are welcome. When complete, we will have cleared the archive of all pieces built with LilyPond versions 2.0.1, 2.0.2, and 2.0.3. The target pieces and assignments are listed and will be tracked in this GITHUB milestone tracker [1]. There are 15 pieces and I have assigned myself to the first one. I will keep this tracker updated as pieces are assigned and completed. To volunteer, select a piece from the list that interests you and send me an email with the details. To prevent duplication of work, do not start on updates until I respond to you with a confirmation. You can submit the finished update to me by mail or with a GITHUB pull request. -glen [ Thanks, Javier, for the idea on this style of milestone tracking. ] As a complete newbie and someone who has no clue whatsoever about what is involved with updating files, could you give me a quick overview or point me to where it is summarised? I am guessing it involves running convert-ly on older version Lilypond files and then fixing the issues that arise? I am probably not competent to be of much use (since I have only used Lilypond to the extent that it has allowed me to get to a level to do what I want now and further experience will probably be very slow) but it is worth knowing more . . Regards, Phil. -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: p...@pricom.com.au ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Status of latest update task
There is still one volunteer at work on a piece in the first update block. As always there is no serious deadline or rush but I will probably post the next block sometime later today. -glen On Sat, Feb 15, 2014 at 6:40 AM, Federico Bruni f...@inventati.org wrote: Hey Glen when will you post the second block of update targets? Il dom, gen 26, 2014 at 10:01 , Chris Sawer ch...@mutopiaproject.org ha scritto: Thanks indeed. A quick update from my side - my current priorities are as follows: (1) Add new contributions - I believe I am currently up-to-date with recent contributions. If you have sent one and not received a reply then please re-send it. (2) New tagline work including latest CC licenses (3) Update website text following suggestions from Federico Bruni (4) Improve compilation scripts/procedure so that I can process 2.18 updates more easily and quickly (5) Action 2.18 update pull requests I intend to have these finished by the end of February. Sorry that it means waiting a bit longer for the 2.18 updates but once the updating is more automated I should be able to process them more quickly in the future. Regards, Chris On 25/01/14 17:26, Glen Larsen wrote: It has been a little over 2 weeks since this task was started and I am happy to say that 14 of the 15 tasks have pull requests submitted. A big Thank You! to the volunteers who helped get Mutopia clear of LilyPond 1.x: Karsten Richter Valentin Villenave Javier Ruiz-Alma Francisco Vila Federico Bruni Calixte Faure I plan to post another block of update targets to clear the lowest 2.x versions. -glen ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] Status of latest update task
It has been a little over 2 weeks since this task was started and I am happy to say that 14 of the 15 tasks have pull requests submitted. A big Thank You! to the volunteers who helped get Mutopia clear of LilyPond 1.x: Karsten Richter Valentin Villenave Javier Ruiz-Alma Francisco Vila Federico Bruni Calixte Faure I plan to post another block of update targets to clear the lowest 2.x versions. -glen ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] What makes old LilyPond code challenging
Valentin, Thanks for this. It is always interesting to see how others get along with this task. On Mon, Jan 20, 2014 at 1:36 AM, Valentin Villenave valen...@villenave.netwrote: [ snip ] - Similarly, one has to remind that basic markups were used for practically everything, so you might want to double-check for dynamics, \tempo indications, etc. Sometimes I find the gyrations I have to go through with converting markup dynamics to be really daunting. It depends on time invested so far and the size and complexity of the piece. - Back then, LilyPond did a very bad job at avoiding collisions and there often was a need for since-then-long-forgotten hackish workarounds; therefore quite a lot of the oddities one may encounter in ancient code may now be safely removed altogether. (Even when it comes to manual \break points.) To be honest, there will be a few cases where you’ll just want to give up and leave these alone (for example ugly multiple voices that issue collision warnings when compiling). As long as it’s harmless enough, doesn’t cause weird output and won’t prevent future syntax updates, I think it’s fair game. Agreed on the fair game. I make use of GIT by doing a fairly minimalist, make-it-work-and-review, pass and commit that in a local branch. Then I can feel free to do more in-depth conversions that involve wholesale removal of old position tweaks, manual breaks, etc. - I took the liberty of concating the whole thing a single, 3000+ LOC file, rather than the original structure with no less than fifteen files. Working with a single file is much, much easier in my opinion (particularly when it’s a single-instrument piece). I haven't done anything quite that radical. I agree with your particular instance, however, where there are not many voices. I have recently committed a Mozart update (KV315) from LilyPond 1.5.x where several files were deprecated simply because they were cut paste of other files to get, for example, 2 horns into a part score. With very few edits the partcombine tool worked perfectly and I even uncovered an error during review. (For the age of the LilyPond version it went extremely well; way faster than the time I took reviewing.) - Handling such files is when you realize how much coding style quality does matter. Apart from the prehistoric weirdness of ancient people (I can’t bear to look at the way I wrote code in 2006), do keep in mind that there were less user-friendly editors back then. It may not matter for small scores, but for large scores where you can’t reasonably expect to come up with a proper diff showing just a dozen differences, you may want to reindent the whole text input, remove unnecessay newlines and reinsert your own newlines after every brace, every barcheck etc. Frescobaldi’s or LilyPondTool’s regexp search-and-replace, and auto-indenting functions, will be of great help in this regard. I know everybody has their editor preference but I wouldn't be nearly as efficient in updating without emacs, especially with point-and-click from the PDF viewer. I have a habit of removing trailing whitespace and that typically creates many additional diffs. And if my problem is reading LilyPond I'll just give up and re-indent the entire thing, understanding that it is tough on volunteer reviewers. [ Thanks, DK, for the mention of recode as a tool for UTF-8 updates. I've now got the tool but haven't taken it for a spin yet. ] ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Request for assistance: Updating Mutopia pieces from the oldest LilyPond versions
There was one final piece in the group and I have assigned it to myself. The public pad https://public.pad.fsfe.org/p/mutopiaUpdateStatus that Valentin Villenave provided is a good way to view the status. The GITHUB assignment process didn't work out exactly as I had hoped, but the experience helps to find better ways to do this in the future. If there are any difficulties with GITHUB submissions, feel free to email your update work to me and I will be happy to submit the pull request. Thanks for the resounding support. Don't worry, there are more update efforts in the pipeline. -glen On Thu, Jan 9, 2014 at 11:11 PM, Glen Larsen glenl@gmail.com wrote: I have started an update project in the Mutopia GIT repository and this is a request for assistance. There are 15 files in the archive that are written for LilyPond versions less than 2.0 and I have entered each one of them as an open issue in GIT. A milestonehttps://github.com/chrissawer/The-Mutopia-Project/issues/milestoneshas also been created to track the progress of the effort, [snipped] ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] On the header parsing
Very cool, David. Felix, I knew you'd want something like this made out of that: Simple python wrapper for this scheme code https://gist.github.com/4480245 On Mon, Jan 7, 2013 at 7:59 AM, David Kastrup d...@gnu.org wrote: Felix Janda felix.ja...@posteo.de writes: Hi, just some thoughts on the current header parsing of Mutopia's software motivated by (not wanting to install java and) the thought that lilypond's language is so complex that parsing it should be left to lilypond itself. dak@lola:/usr/local/tmp/lilypond$ time lilypond -e (set! print-book-with-defaults (lambda (parser book) (module-for-each (lambda (sym var) (if (markup? (variable-ref var)) (format #t \~a=~S\\n\ sym (markup-string (variable-ref var) (ly:book-header book input/regression/mozart-hrn-3.ly GNU LilyPond 2.17.7 Processing `input/regression/mozart-hrn-3.ly' Parsing...copyright=public domain opus=KV 447 maintainerEmail=han...@xs4all.nl instrument=Horn in F editor=Henri Kling maintainer=han...@xs4all.nl composer=Wolfgang Amadeus Mozart (1756-1791) maintainerWeb=http://www.xs4all.nl/~hanwen/; subtitle=für Horn und Orchester mutopiatitle=Horn Concerto 3 style=classical lastupdated=2002/May/21 source=Edition Breitkopf 2563 texidoc= This is the Mozart 3 for horn. It's from an Edition Breitkopf EB 2563, edited by Henri Kling. Henri Kling (1842-1918) was a horn virtuoso that taught in Geneva. footer=Mutopia-2002/05/21-25 mutopiaopus=KV447 title=Konzert Nr. 3 Es dur tagline=Mutopia-2002/05/21-25 This music is part of the Mutopia project, http://mutopiaproject.org/ It has been typeset and placed in the public domain by han...@xs4all.nl. Unrestricted modification and redistribution is permitted and encouraged - copy this music and share it! enteredby=HWN mutopiacomposer=W.A.Mozart Success: compilation successfully completed real0m0.992s user0m0.872s sys 0m0.104s dak@lola:/usr/local/tmp/lilypond$ -- David Kastrup ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] update of Sicilienne (Op 78) by Gabriel Fauré
My last push did the same thing --- merged my push into my most recent pull request. I'm familiar enough with git but need to figure out how to control the github behavior. -glen On Sun, Dec 9, 2012 at 12:49 PM, Chris Sawer ch...@mutopiaproject.orgwrote: On 04/12/12 08:07, Federico Bruni wrote: I've just committed it to my repo and sent the pull request. Apparently, it has been added to the first pull request (still to be merged, AFAICS) as a comment and a link to the commit: https://github.com/chrissawer/**The-Mutopia-Project/pull/1https://github.com/chrissawer/The-Mutopia-Project/pull/1 https://github.com/fedelibre/**The-Mutopia-Project/commit/** 19054a818345793a744295c2d9886e**08bfbfa2c8https://github.com/fedelibre/The-Mutopia-Project/commit/19054a818345793a744295c2d9886e08bfbfa2c8 Thanks, I have merged your pull request today and pushed the update to the Mutopia website. Not quite sure why the Sicilienne was added to the same pull request as Red Apple Rag. In the future separate pull requests for separate pieces (or at least separate composers) would make it easier for me to do updates in bitesize chunks. Regards, Chris ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] update of Sicilienne (Op 78) by Gabriel Fauré
Ah, thanks for the hint, Felix. if you have a pull request from your fork's master any subsequent commit before that pull request is handled is considered part of that pull request. I was creating branches on my local repository, then merging them locally. I need to adjust my workflow. On Sun, Dec 9, 2012 at 1:35 PM, Chris Sawer ch...@mutopiaproject.orgwrote: On 09/12/12 21:24, Felix Janda wrote: Would it be possible to send new/updated pieces as patches (git format-email) to the mailing list (to be imported with git am)? Then you can take one patch at the time. Yes, although pull requests are more convenient and they also integrate nicely into the GitHub issue tracker. If I keep up-to-date with pull requests then it won't be much of an issue. :-) Chris ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] Unclear sources
This is my first post to the discussion list and it is more of a
question about the clarity of a scanned source I am working on.
Please let me know if these questions are not appropriate to the
mailing list.
I am working from Boije 4, D. Aguado's Op4 Six Petites Pieces for
Guitar, and No4 illustrates 2 issues:
1. The piece starts with a markup, "6e en Pu." or "6e
en Puí." or, possibly, "6e en Pué.". I am guessing this
has something to do with detuning the 6th (E) string ('Sixth is
something') to a 'drop-D' tuning on the guitar. If someone
can give me the correct phrase and translation it would be
appreciated.
2. I have encountered several confusing parts where time signatures
do not add. The fix seems to be either making a beamed set of notes
a \grace{...} or one or more tuples. In one case, only a grace
managed to fix the required number of beats in the first case but in
the second case it was ambiguous.
That is one question and one issue on clarity. In the case of #2 I
made my best guess --- coding both and listening to the midi output,
playing the sequence, etc. I have annotated the problems in the
submitted lilypond file in case anybody has input.
-glen
___
Mutopia-discuss mailing list
Mutopia-discuss@mutopiaproject.org
http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
