Re: [Mutopia-discuss] Mutopia restoration at https://mutopia.omet.ca
I ran across this post today and I'm wondering if the ability to contribute has been restored. -- Knute Snortum On Mon, Mar 28, 2022 at 5:55 PM Paul Morris wrote: > > Oh wow, this is wonderful, thanks! > > Paul > > On Sat, Mar 26, 2022, at 6:17 AM, mike wrote: > > https://mutopia.omet.ca > All pieces should be restored by next week. > 'How to contribute' options will be posted after that. > > -Mike > > ___ > 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
Re: [Mutopia-discuss] Mutopia restoration at https://mutopia.omet.ca
Wow, nice. Looking forward to submitting. -- Knute Snortum On Sat, Mar 26, 2022 at 3:19 AM mike wrote: > > https://mutopia.omet.ca > All pieces should be restored by next week. > 'How to contribute' options will be posted after that. > > -Mike > > ___ > 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] Site outage
I think the Mutopia Project has been abandoned, which is really too bad. There is the OMET Library (https://scores.omet.ca/) that has picked up the baton. And you can try the IMSLP site (https://imslp.org/wiki/Main_Page) but it's mostly scans of sheet music. Finding LilyPond source files is hard. If anyone knows anything else, I would love to hear it. -- Knute Snortum On Tue, Mar 1, 2022 at 12:57 PM Ryan Prince wrote: > > Hi Mutopia Project, > > I went to visit http://www.mutopiaproject.org, and saw that the server is > unavailable. Just wanted to let you know. > > Best, > > Ryan > ___ > 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] Beginner (nine months) at Lilypond, interested in helping converting/updating Mutopia works
I wanted to add that there is a wonderful site -- https://blackstock.media/ -- that incorporates The Mutopia Project (and more) with some nice interactive widgets. Check it out. -- Knute Snortum On Mon, Feb 22, 2021 at 7:17 AM Knute Snortum wrote: > > On Sun, Feb 21, 2021 at 12:26 PM Kenneth Wolcott > wrote: > > > > Hello, > > > > Beginner (nine months) at Lilypond, interested in helping > > converting/updating Mutopia works... > > Hello and welcome! I didn't want this email to go unanswered. The > Mutopia Project is in transition, to put it mildly. New submissions > have been backlogged for a year or so. However, there has been some > interest in starting them up again, or moving to a similar site. I > think you should definitely get music ready to submit to Mutopia, but > I don't want you to be surprised if your submissions don't show up on > the site for a while. > > >I've been experimenting with Lilypond for less than a year, > > downloading some works already engraved and trying to engrave them > > with Lilypond. I have learned most of the elementary aspects of > > Lilypond now. I'm still working on many aspects of Lilypond that I do > > not yet understand. > > Lilypond has a mailing list you can join: > https://lilypond.org/contact.html. It's fairly high in the amount of > email you get, so I would recommend using an email filter. The people > there are often experts at what they do, but simple questions are > welcomed if they are well thought out. (Don't, for instance, post: > "It doesn't work.") > > > I recently started downloading both Lilypond source and pdf (Letter) > > engraved music from Mutopia (mostly Bach and Mozart). I have tried > > using convert-ly (both version 2.20.0 and 2.22.0 of Lilypond), > > capturing/saving the output and trying to understand the warnings that > > sometimes occur. I subsequently try to engrave the converted Lilypond > > source. Most often there is success, sometimes there is something > > that goes a bit awry. I am learning, slowly, how to manually perform > > conversions that convert-ly was not able to do (which the convert-ly > > did report). > > The Mutopia Project has some very old versions of Lilypond that are > difficult to convert to a modern version, as you've seen. Submitting > updated versions of old submissions is a valid and welcomed activity. > > > As I get a bit better at doing this, I'd like to contribute to > > Mutopia by performing some of these conversion updates and providing > > the updated Lilypond source, trying to make the pdf output look as > > close to as accurate to the Mutopia Lilypond engraver's pdf. I do not > > think I am ready to perform this action just yet, but I'd like to be > > able to do so soon. > > > > I really appreciate the works that already exist on Mutopia. I > > think that this is not only a great resource for high quality engraved > > music, but a great educational resource for the engraving process > > itself. > > I agree, and hopefully there will be some movement in getting The > Mutopia Project back up and running -- or a similar site. > > > Ken Wolcott > > > > ___ > > Mutopia-discuss mailing list > > Mutopia-discuss@mutopiaproject.org > > http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss > > > -- > Knute Snortum ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Beginner (nine months) at Lilypond, interested in helping converting/updating Mutopia works
On Sun, Feb 21, 2021 at 12:26 PM Kenneth Wolcott wrote: > > Hello, > > Beginner (nine months) at Lilypond, interested in helping > converting/updating Mutopia works... Hello and welcome! I didn't want this email to go unanswered. The Mutopia Project is in transition, to put it mildly. New submissions have been backlogged for a year or so. However, there has been some interest in starting them up again, or moving to a similar site. I think you should definitely get music ready to submit to Mutopia, but I don't want you to be surprised if your submissions don't show up on the site for a while. >I've been experimenting with Lilypond for less than a year, > downloading some works already engraved and trying to engrave them > with Lilypond. I have learned most of the elementary aspects of > Lilypond now. I'm still working on many aspects of Lilypond that I do > not yet understand. Lilypond has a mailing list you can join: https://lilypond.org/contact.html. It's fairly high in the amount of email you get, so I would recommend using an email filter. The people there are often experts at what they do, but simple questions are welcomed if they are well thought out. (Don't, for instance, post: "It doesn't work.") > I recently started downloading both Lilypond source and pdf (Letter) > engraved music from Mutopia (mostly Bach and Mozart). I have tried > using convert-ly (both version 2.20.0 and 2.22.0 of Lilypond), > capturing/saving the output and trying to understand the warnings that > sometimes occur. I subsequently try to engrave the converted Lilypond > source. Most often there is success, sometimes there is something > that goes a bit awry. I am learning, slowly, how to manually perform > conversions that convert-ly was not able to do (which the convert-ly > did report). The Mutopia Project has some very old versions of Lilypond that are difficult to convert to a modern version, as you've seen. Submitting updated versions of old submissions is a valid and welcomed activity. > As I get a bit better at doing this, I'd like to contribute to > Mutopia by performing some of these conversion updates and providing > the updated Lilypond source, trying to make the pdf output look as > close to as accurate to the Mutopia Lilypond engraver's pdf. I do not > think I am ready to perform this action just yet, but I'd like to be > able to do so soon. > > I really appreciate the works that already exist on Mutopia. I > think that this is not only a great resource for high quality engraved > music, but a great educational resource for the engraving process > itself. I agree, and hopefully there will be some movement in getting The Mutopia Project back up and running -- or a similar site. > Ken Wolcott > > ___ > Mutopia-discuss mailing list > Mutopia-discuss@mutopiaproject.org > http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss -- Knute Snortum ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Is The Mutopia Project done for?
I was wondering recently what the status of Mutopia was, and finding the last thread I saw this post again. Going to https://blackstock.media was a pleasant surprise! That is a really nice website that has all of Mutopia, as well as other sources, "plugged in". Now my question is, do I start contributing to blackstock.media, and if so how? -- Knute Snortum On Tue, Oct 27, 2020 at 5:15 PM Mike Blackstock wrote: > I've been working on a Mutopia fork/clone that will allow > users to work in realtime on scores: > > https://blackstock.media > > The Mutopia folder has the complete Mutopia repository, which > will be keyword-searchable just as soon as I upload the search > module. > > It'll be very easy for users to contribute new functionality via > user-contributed apps, which can be written in hyperapp, or Vue, > or React, or just a plain-old iframe app. > > I have a login and signup system ready to deploy; here's a quick > demo of it: https://omet.ca > > Roadmap for this week: > > -- install search/index system on the demo site at ' > https://blackstock.media' > -- install File 'Tree' view with expandable folder views; > -- move 'Chamber Guitar' stuff to a separate site, make the demo > Mutopia-only > > It'll be nice to get a few volunteers to help out. > More to come... > > -Mike > > > Quoting Josiah Boothby : > > > It sure looks dormant (to say the least) and all of the discussion in the > > mailing list in the past few months has been to this effect. Someone with > > the right know-how could probably fork the project, but that's beyond my > > skills. I have web hosting that I'd be happy to devote to it but I don't > > have the skills to be a site maintainer. > > > > On Tue, Oct 27, 2020 at 7:58 AM Knute Snortum > wrote: > > > >> No music has been processed since 2019/07/24. I'm willing to help > anyway > >> I can, or is the Mutopia Project dead. I'd be really sad if that is so. > >> > >> --- > >> Knute Snortum > >> (via Gmail) > >> ___ > >> Mutopia-discuss mailing list > >> Mutopia-discuss@mutopiaproject.org > >> http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss > > > -- > Mike Blackstock > https://blackstock.media > > > ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] Is The Mutopia Project done for?
No music has been processed since 2019/07/24. I'm willing to help anyway I can, or is the Mutopia Project dead. I'd be really sad if that is so. --- Knute Snortum (via Gmail) ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Is the Mutopia Project still going?
I certainly could be one of the maintainers/reviewers of the project. --- Knute Snortum (via Gmail) On Wed, Sep 23, 2020 at 2:53 PM Joel Swanson wrote: > Hello, > > I'm definitely interested in the project. Currently I don't time available > to contribute, but I've forked the repository [1] and I'm hoping to > contribute in the future. > > I'm particularly interested in public domain English and French hymnody, > including the Genevan psalter. > > Cheers, > > Joel Swanson > > > [1] https://github.com/MutopiaProject/MutopiaProject > > On Wed, Sep 23, 2020 at 11:37:20AM -0700, Knute Snortum wrote: > > It looks like no one has responded to this thread since February. (I > know, > > a little thing like COVED-19 happened.) Is there a chance of getting The > > Mutopia Project going again? > > > > --- > > Knute Snortum > > (via Gmail) > > > > > > On Wed, Feb 19, 2020 at 4:08 AM Federico Bruni > wrote: > > > > > +1 > > > > > > I'm currently involved in other lilypond stuff and can't contribute to > > > Mutopia right now, but I will in the future. > > > > > > I think we need more reviewers of pull requests. > > > It's not a fun task, but it's important and can't be left to only > > > one/two persons. > > > I guess that after some time an active and experienced reviewer may > > > gain write access and help also with merging PRs. > > > > > > I think a checklist for PR's review would be very useful. > > > > > > Let's wait for ideas from Chris and Glen. > > > > > > > > > Il giorno mer 19 feb 2020 alle 10:43, j.scholb...@posteo.de ha > scritto: > > > > I am by far not one of the strongest contributors to Mutopia. But I > > > > would like to express that I value the project very much and that I > > > > will definitely contribute in the future. I would be very sad if > > > > Mutopia stalled or went down. And I am sure, many people feel alike. > > > > > > > > Chris, could you explain how the community could help to make run > > > > Mutopia smoothely again? > > > > > > > > Jonathan Scholbach > > > > > > > > Am 18.02.2020 16:15 schrieb Knute Snortum: > > > >> That's great! > > > >> > > > >> I believe the main gatekeeper is Chris Sawer, and if I remember > > > >> correctly the finalizing process is moderately complex. It would > > > >> make > > > >> sense to have another gatekeeper if Chris is too busy. > > > >> > > > >> --- > > > >> Knute Snortum > > > >> (via Gmail) > > > >> > > > >> On Mon, Feb 17, 2020 at 9:20 PM Mike Blackstock > wrote: > > > >> > > > >>> I'm interested. I have some stuff to contribute in the next little > > > >>> while and, additionally, I'd be willing to help out in other ways > > > >>> to keep the project going if it's in jeopardy. > > > >>> > > > >>> Quoting Knute Snortum : > > > >>> > > > >>>> It looks like pull requests are starting to back up and nothing > > > >>> has been > > > >>>> committed for months. I'm trying to decide if trying to > > > >>> contribute is > > > >>>> worth it anymore. Is there still interest in this project? > > > >>>> > > > >>>> --- > > > >>>> Knute Snortum > > > >>>> (via Gmail) > > > >>> > > > >>> -- > > > >>> "Large streams from little fountains flow, > > > >>> Tall oaks from little acorns grow" > > > >>> - D. Everett > > > >>> Website: https://blackstock.media [1] > > > >>> > > > >>> ___ > > > >>> Mutopia-discuss mailing list > > > >>> Mutopia-discuss@mutopiaproject.org > > > >>> > http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss > > > >>> [2] > > > >> > > > >> > > > >> Links: > > > >> -- > > > >> [1] https://blackstock.media > > > >> [2] > > > >> 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 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
Re: [Mutopia-discuss] Is the Mutopia Project still going?
It looks like no one has responded to this thread since February. (I know, a little thing like COVED-19 happened.) Is there a chance of getting The Mutopia Project going again? --- Knute Snortum (via Gmail) On Wed, Feb 19, 2020 at 4:08 AM Federico Bruni wrote: > +1 > > I'm currently involved in other lilypond stuff and can't contribute to > Mutopia right now, but I will in the future. > > I think we need more reviewers of pull requests. > It's not a fun task, but it's important and can't be left to only > one/two persons. > I guess that after some time an active and experienced reviewer may > gain write access and help also with merging PRs. > > I think a checklist for PR's review would be very useful. > > Let's wait for ideas from Chris and Glen. > > > Il giorno mer 19 feb 2020 alle 10:43, j.scholb...@posteo.de ha scritto: > > I am by far not one of the strongest contributors to Mutopia. But I > > would like to express that I value the project very much and that I > > will definitely contribute in the future. I would be very sad if > > Mutopia stalled or went down. And I am sure, many people feel alike. > > > > Chris, could you explain how the community could help to make run > > Mutopia smoothely again? > > > > Jonathan Scholbach > > > > Am 18.02.2020 16:15 schrieb Knute Snortum: > >> That's great! > >> > >> I believe the main gatekeeper is Chris Sawer, and if I remember > >> correctly the finalizing process is moderately complex. It would > >> make > >> sense to have another gatekeeper if Chris is too busy. > >> > >> --- > >> Knute Snortum > >> (via Gmail) > >> > >> On Mon, Feb 17, 2020 at 9:20 PM Mike Blackstock wrote: > >> > >>> I'm interested. I have some stuff to contribute in the next little > >>> while and, additionally, I'd be willing to help out in other ways > >>> to keep the project going if it's in jeopardy. > >>> > >>> Quoting Knute Snortum : > >>> > >>>> It looks like pull requests are starting to back up and nothing > >>> has been > >>>> committed for months. I'm trying to decide if trying to > >>> contribute is > >>>> worth it anymore. Is there still interest in this project? > >>>> > >>>> --- > >>>> Knute Snortum > >>>> (via Gmail) > >>> > >>> -- > >>> "Large streams from little fountains flow, > >>> Tall oaks from little acorns grow" > >>> - D. Everett > >>> Website: https://blackstock.media [1] > >>> > >>> ___ > >>> Mutopia-discuss mailing list > >>> Mutopia-discuss@mutopiaproject.org > >>> http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss > >>> [2] > >> > >> > >> Links: > >> -- > >> [1] https://blackstock.media > >> [2] > >> 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 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] Is the Mutopia Project still going?
That's great! I believe the main gatekeeper is Chris Sawer, and if I remember correctly the finalizing process is moderately complex. It would make sense to have another gatekeeper if Chris is too busy. --- Knute Snortum (via Gmail) On Mon, Feb 17, 2020 at 9:20 PM Mike Blackstock wrote: > I'm interested. I have some stuff to contribute in the next little > while and, additionally, I'd be willing to help out in other ways > to keep the project going if it's in jeopardy. > > Quoting Knute Snortum : > > > It looks like pull requests are starting to back up and nothing has been > > committed for months. I'm trying to decide if trying to contribute is > > worth it anymore. Is there still interest in this project? > > > > --- > > Knute Snortum > > (via Gmail) > > > -- > "Large streams from little fountains flow, > Tall oaks from little acorns grow" > - D. Everett > Website: https://blackstock.media > > > ___ > 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] Is the Mutopia Project still going?
It looks like pull requests are starting to back up and nothing has been committed for months. I'm trying to decide if trying to contribute is worth it anymore. Is there still interest in this project? --- Knute Snortum (via Gmail) ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] 403 Forbidden for any file on Mutopia website
I can confirm this. The same thing happens to me. --- Knute Snortum (via Gmail) On Sun, Oct 21, 2018 at 8:10 AM Federico Bruni wrote: > Hi all > > Yesterday I noted that I cannot get access to any file on Mutopia > website. > Main pages in the web root as well as cgibin/ pages are accessible, but > it seems that any other page within ftp/ is not. > > Example: > > Forbidden > > You don't have permission to access > /ftp/AlkanCV/O31/alkan-op31-8/alkan-op31-8.mid on this server. > > > > > > ___ > 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] typo in webpage title
Ah yes, now I see it. -- Knute Snortum On Sun, Oct 7, 2018, 4:36 PM Bob Bib wrote: > On 2018-10-08, Knute Snortum wrote: > > Hmm, looks okay now. Maybe someone fixed it. > > Hmm, not for me. > Excuse me, maybe you've looked at the page body (it was OK and still > is), instead of the title bar of your browser? > > The title tag in page source still has the typo: > Mutopia: List of all usic > > -- > Best wishes, > Bob > ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] potential new contributor
On Mon, Jun 18, 2018 at 10:14 AM Nah wrote: > Okay, I forked Mutopia. The instructions suggest creating a separate > branch for multiple submissions. Does that mean multiple submissions at > once or for the foreseeable future? I intend to start with Kohler's op > 151, since it's pretty straightforward. > You should have separate branches for each piece. A piece may have multiple files and sometimes multiple movements. Other times, like the Chopin Preludes, each piece has its own branch. I'm not that familiar with Kohler opus 151, but I believe it has twelve sections. Each section such have a branch and be submitted separately. At least that is my understanding. > > When run with ly:page-turn-breaking, Lilypond is giving me a > "programming error", something about page breaking, and then says > "crossing fingers". It's not highlighted as a normal error or warning, > and everything works out fine. What does it mean? > This kind of question is better submitted to the LilyPond users' mailing list (http://lilypond.org/contact.html). You should state the version of LilyPond you use, the full error message, and if possible, a tiny example. > > Also, I created a cover.ily, which just contains some markup to create a > cover page. But when I include it in the main .ly, it pushes the TOC to > an even page, which results in 3 blank pages. When I comment it out, the > TOC is on page 1, the scores begins on page 2, and everything is fine. I > haven't found any combination commands that will give me a cover, blank > reverse side, then TOC on the next page (physical page 3). > This would be a separate submission to the LilyPond users' mail list too. --- Knute Snortum (via Gmail) ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] I've re-created a ly file for Scott Joplin's The Easy Winners
On Fri, Jun 15, 2018 at 10:34 AM Shachar Shemesh wrote: > You forgot to answer about the lack of "Ragtime" category :-) > I don't know what it would take to create a new category. I'd be all for it but I don't have that authority. > On 15/06/2018 16:08, Knute Snortum wrote: > > I would frown upon changing the pitch of a note that "sounds wrong" to you > unless you have some evidence to back it up. I would want the piece > exactly how Joplin wrote it. A footnote would be acceptable, I think. > > > You do realize that there is a difference between "How Joplin wrote it" > and "How it was first published", right? > > The case is not so obvious in The Easy Winners, but in Maple Leaf Rag > there is a place where there is obviously a note they forgot to print while > type-setting it. It is missing from the first seuence, but present in the > second time the sequence is given one octave down. It is also present in > the first sequence the second time the notes are given (the second time > part A is played). > > As such, it is fairly obvious that the piece as published does not reflect > how Joplin wrote it. > > Having said that, and assuming you're using the same source as me for the > notes (the yellow book bundling all of Joplin's works), the editorial at > the beginning claims they have already incorporated all erratas they could > find. > As I said, if you have evidence to backup the change, them make it. ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] potential new contributor
I'll answer you as best I can. No, you don't need separate files to post to Mutopia. I know that with some big pieces they release both the complete work and separate parts, but using separate files to create a complex piece is a good thing. I think that the exact way to setup a complex piece to be usable as both separate parts and a complete piece is not yet agreed upon -- I could be wrong. If you're creating multipart sheet music with LilyPond, I think you're a step above novice. But if you'd like I'd be happy to look at your ly and ily files and give you my comments. But this is absolutely not required to submit to Mutopia. The two things I know are requirements are that your submission be able to compile in both letter and a4 paper sizes without warnings or errors, and that you're able to provide a source that is not under copyright. The first one may be difficult in your situation, but honestly, I usually write my pieces to look good in letter and just work in a4. That's because I live in the US I guess. Honestly, I don't know how a well-typeset piece is expected to look good in two different paper sizes. But that's a discussion for another day. I hope to see your submission to Mutopia soon! --- Knute Snortum (via Gmail) On Thu, Jun 14, 2018 at 5:36 AM Nah wrote: > A little while ago, I started typesetting some pdf's I found on IMSLP. > I've been doing it for my own personal use, primarily to make the music > more readable for me on letter size paper. So I have some less than > elegant lilypond files. To make them suitable for Mutopia, doe each > piece need to be separated into its own file? For example, I typeset > Louis Kohler's op 151, which consists of 12 lessons. I put each one in a > .ily and the whole book as a master .ly file that includes all the > lesson .ily files. I set it up this way so I could put an \allowPageTurn > after each lesson and get the whole thing as a nice little book that I > can comb bind. If the lessons need to be separated for Mutopia, are > there some examples of how to set it up to make individual files with > their midi files, and also make a complete book. And does Mutopia want > the complete book? > > I'm still a relative novice with lilypond, and pretty inept with scheme. > I have some competence with python, if that's relevant. > > Ultimately, I want to create some collections of graded works, 50 or so > pages of grade 2, for example. A collection that might be useful for > someone at grade 2 to use as practice material, or that someone at grade > 3 can use for sight-reading. > > > ___ > 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] Mendelssohn String Octet MIDI
I converted the LilyPond source to version 2.18 and the MIDI now seems "good", at least it plays violin sounds. Are you interested in the .ly files or just the MIDI files? I will submit the .ly files to Mutopia, but it can take a while for them to show up on the site, so contact me directly if you want the files now. --- Knute Snortum (via Gmail) On Mon, Feb 19, 2018 at 3:54 PM, Knute Snortum <ksnor...@gmail.com> wrote: > I'm taking a look at it too. > > -- > Knute Snortum > > On Feb 19, 2018 1:10 PM, "Francisco Vila" <paconet@gmail.com> wrote: > >> On 18/02/18 07:00, Ella Yu wrote: >> > Hello, Can I just point out that the MIDI for the Mendelssohn >> > String Octet is terrible? It is written in percussion notation, >> > which is totally not right. Can this be fixed? Thank you in >> > advance. >> > >> > ___ >> > Mutopia-discuss mailing list >> > Mutopia-discuss@mutopiaproject.org >> > http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss >> > >> >> It looks that for some reason, all music goes to channel 10 in the MIDI, >> and the instrument name metadata is always "drums". >> >> -- >> Francisco Vila. Badajoz (Spain) >> paconet.org , csmbadajoz.com >> >> ___ >> 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] Mendelssohn String Octet MIDI
I'm taking a look at it too. -- Knute Snortum On Feb 19, 2018 1:10 PM, "Francisco Vila" <paconet@gmail.com> wrote: > On 18/02/18 07:00, Ella Yu wrote: > > Hello, Can I just point out that the MIDI for the Mendelssohn > > String Octet is terrible? It is written in percussion notation, > > which is totally not right. Can this be fixed? Thank you in > > advance. > > > > ___ > > Mutopia-discuss mailing list > > Mutopia-discuss@mutopiaproject.org > > http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss > > > > It looks that for some reason, all music goes to channel 10 in the MIDI, > and the instrument name metadata is always "drums". > > -- > Francisco Vila. Badajoz (Spain) > paconet.org , csmbadajoz.com > > ___ > 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] New contributor
The output looks great! Did you want someone to review your input file or proofread the output against the source or something else? --- Knute Snortum (via Gmail) On Wed, Jul 26, 2017 at 5:12 PM, Alexander Brock <alexan...@lunar-orbit.de> wrote: > Hi, > > I'm new to contributing to the Mutopia project. I play the organ and > sometimes the piano and I regularely come across nice pieces where only > terrible scans are available so I often end up typesetting them. > > I typeset two pieces for organ and created pull requests: > > https://github.com/MutopiaProject/MutopiaProject/pull/904 > https://github.com/MutopiaProject/MutopiaProject/pull/905 > > I proofread my results and made some minor fixes to layout and now I'm > happy with the results, can someone review them? > > Best regards, > Alexander > > ___ > 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] Different page numbers and formatting between A4 and Letter sizes
Thanks for your post, Javier This LilyPond file has so many manual adjustments that I have to pick a page size and make that one look good. As I'm in the US, I'm going to make letter size look good. People who need A4 have the source -- although I feel for that person. These changes aren't trivial. --- Knute Snortum (via Gmail) On Tue, Apr 11, 2017 at 3:16 PM, Javier Ruiz-Alma <jav...@ruiz-alma.com> wrote: > There's an accepted enhancement to add command-line support for > global-staff-size to LilyPond: > > https://sourceforge.net/p/testlilyissues/issues/2095/ > > The enhancement would open the door to specify override values for > global-staff-sizes for letter/A4 in the source code. Mutopia scripts could > then implement the distinct values for Letter vs. A4 PDF generation...I'm > thinking headers \mutopiaLetterStaffSize = X, \mutopiaAFourStaffSize = Y, > or some other more elegant solution. > > I often spend time adjusting spacing to make both letter & A4 acceptable, > while avoiding orphan systems, page breaks in less-than-ideal measures, > too-airy pages, etc. > > Adjustments (in order of preference and their impact on maintainability & > readability): > * adjust vertical margins/distances/padding for titles & footers > * adjust left/right margins > * fixed line-width > * adjusting staff-staff-spacing min distance > * add breaks and/or noBreaks here an there > * adjust staff-size (within range 18-21) > > It's surely a matter of personal preference, but in general, I prioritize > font-size over other formatting adjustments. That is to say, I spend time > trying out other formatting fixes, including ragged pages, before I decide > to go with global-staff-size smaller than ~18. > > > Javier > > > From: Knute Snortum <ksnor...@gmail.com> > To: "mutopia-discuss@mutopiaproject.org" <mutopia-discuss@ > mutopiaproject.org> > Sent: Tuesday, April 11, 2017 11:45 AM > Subject: [Mutopia-discuss] Different page numbers and formatting between > A4 and Letter sizes > > > > I try to make my contributions fit in a whole number of pages, that is, > not with a ragged last page. To do this, I often change the global staff > size. The problem arises when I have to change from A4 to Letter paper > size. Often the number of pages changes, making one look too spaced out. > > What would be nice is if I could specify a different staff size for > different paper sizes. If not, I have to decide between a ragged last > page, or worse, making one size look bad for the sake of the other. Since > I'm from the US, I would favor Letter. The A4 people would need to change > some settings and recompile. How can we avoid 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] R.B.Hall Tenth Regiment march - sanity check
Just a quick look at the pull request; seems to be fine. Git can be confusing. I got things very messed up a couple of times, and I know git! --- Knute Snortum (via Gmail) On Thu, Dec 15, 2016 at 7:16 PM, Garrett Fitzgerald <sarekofvul...@gmail.com > wrote: > Good evening, all. I recently typeset R. B. Hall's Tenth Regiment March > for the Bangor Band, and since it passed through a performance with no > major disasters, I figured I'd submit it here. > > However, I didn't realize how little I know about using git. > > I think I successfully submitted it to its own branch of the repository > and created a pull request, but I'm not sure. If someone has a moment, > could you check that? Also, if I should have done something more elaborate > than separate files for each part and the score, please let me know. Thanks. > > ___ > 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] Peter Pan incidental music
Sound like you could be posting those kind of questions to the LilyPond users mailing list: https://lists.gnu.org/mailman/listinfo/lilypond-user --- Knute Snortum (via Gmail) On Fri, Aug 19, 2016 at 11:53 AM, Joel C. Salomon <joelcsalo...@gmail.com> wrote: > A year and a half ago, on 2014-12-23 7:10 PM, 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. > > > At any rate, I've begun to re-typeset some of this in Lilypond with the > > intention of submitting this to Mutopia. I've forked the project at > > GitHub; see https://github.com/jcsalomon/MutopiaProject/commit/14e70804 > > Returning to this at long last… > > While I do still intend to contribute a version of this effort to > Mutopia, I’m finding it easier to work on it as an independent project; > see <https://github.com/jcsalomon/CrookJ-PeterPan>. > > In the Releases page for that project, I have my current drafts of the > first 13 scores in this collection: LilyPond source, PDF score, and MIDI > rendering. > > I can use some help with this from folks who are more familiar with > LilyPond or musical notation than I. There are minor details (which > relative key is correct for any given score, whether any particular slur > should be a phrasing slur instead), more noticeable formatting issues > (how to program the accelerando/ritardando in PP04 “The Shadow Dance”, > or the change of singer in PP13 “The Building of the House”), and > LilyPond issues (are my score blocks overly complicated, or am I perhaps > missing some things that should be there? can I combine articulate.ly > with \acciaccatura? how do I make fermata sound better?). > > —Joel C. Salomon > > ___ > 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] Dvorak symphony 9
My binaries are for Windows, FYI. Knute Snortum (via Gmail) On Sun, Mar 20, 2016 at 8:51 AM, Chris Sawer <ch...@mutopiaproject.org> wrote: > We keep a stack of old LilyPond binaries around for corrections to older > pieces. They are available from the LilyPond website, eg: > > http://download.linuxaudio.org/lilypond/binaries/linux-64/ > > Version 2.14 runs fine on our CentOS 7 build server so I think you'll > probably be ok on Fedora 22. If you get stuck let me know and I can rebuild > the piece with tenor clef for you. > > If anyone has time to update the LilyPond source to output both alto and > tenor clef for this part, that would be great. I don't think many trombone > players are comfortable in alto clef these days, according to wikipedia it > used to be standard for the 1st trombone part though. > > Chris > > > > > On 19/03/2016 14:32, Knute Snortum wrote: > >> I can send you Lilypond 2.14 if you want to go that way. I engraved >> brass.ly <http://brass.ly> with it with only warnings. >> >> If I had to guess, Frescobaldi converted just brass.ly <http://brass.ly> >> and not the other files it relies on. I will look into that further. >> >> >> Knute Snortum >> (via Gmail) >> >> On Fri, Mar 18, 2016 at 2:15 PM, Steve Taylor <steve.taylor...@gmail.com >> <mailto:steve.taylor...@gmail.com>> wrote: >> >> Hi there, >> >> I wonder of anyone can quickly solve this? I'd like to print out >> the 1st trombone part in tenor clef (rather than alto clef) as I'll >> be playing it next month. >> >> I downloaded all the files and converted them from 2.14.2 to my >> latest version (2.18.0) without any apparent errors. But running >> lilypond on brass.ly <http://brass.ly> caused lots of errors >> (particularly many saying "wrong type of argument") - culminating in >> a segmentation fault and core dump (on Fedora 22). >> >> http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=1793 >> >> cheers, >> Steve >> >> >> ___ >> Mutopia-discuss mailing list >> Mutopia-discuss@mutopiaproject.org >> <mailto: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 mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Dvorak symphony 9
I can send you Lilypond 2.14 if you want to go that way. I engraved brass.ly with it with only warnings. If I had to guess, Frescobaldi converted just brass.ly and not the other files it relies on. I will look into that further. Knute Snortum (via Gmail) On Fri, Mar 18, 2016 at 2:15 PM, Steve Taylor <steve.taylor...@gmail.com> wrote: > Hi there, > > I wonder of anyone can quickly solve this? I'd like to print out the 1st > trombone part in tenor clef (rather than alto clef) as I'll be playing it > next month. > > I downloaded all the files and converted them from 2.14.2 to my latest > version (2.18.0) without any apparent errors. But running lilypond on > brass.ly caused lots of errors (particularly many saying "wrong type of > argument") - culminating in a segmentation fault and core dump (on Fedora > 22). > > http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=1793 > > cheers, >Steve > > > ___ > 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] Mutopia-discuss Digest, Vol 65, Issue 1
Can Finale export to XML? I believe LilyPond can read that format and import it. Knute Snortum (via Gmail) On Sun, Jul 12, 2015 at 6:43 AM, FgCogent f...@cogentwm.com wrote: I would like to submit a Bach transcript. I use finale. Is that acceptable or do your other formats? Thank you! Frank Grasso, CFP Managing Director Cogent Wealth Management, Inc. We Protect Your Bottom Line! (631) 838-8028 Mobile 1895 Walt Whitman Road; Suite 6, Melville, NY 11747 (631) 420-4242 x 223 (631)%20420-4242;223 Melville (631) 420-4243 Fax Melville 22 Railroad Avenue; Suite 2, Sayville, NY 11782 (631) 699-2046 Sayville (631) 456-4915 Fax Sayville God Bless America! On Jul 12, 2015, at 7:00 AM, mutopia-discuss-requ...@mutopiaproject.org wrote: Send Mutopia-discuss mailing list submissions to mutopia-discuss@mutopiaproject.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss or, via email, send a message with subject or body 'help' to mutopia-discuss-requ...@mutopiaproject.org You can reach the person managing the list at mutopia-discuss-ow...@mutopiaproject.org When replying, please edit your Subject line so it is more specific than Re: Contents of Mutopia-discuss digest... Today's Topics: 1. frescobaldi manuscript viewer (still indevelopment) (Federico Bruni) -- Message: 1 Date: Sun, 12 Jul 2015 11:37:36 +0200 From: Federico Bruni f...@inventati.org To: Mutopia discuss mutopia-discuss@mutopiaproject.org Subject: [Mutopia-discuss] frescobaldi manuscript viewer (still in development) Message-ID: 1436693856.1903...@smtp.autistici.org Content-Type: text/plain; charset=utf-8; Format=flowed Hi all I think that you might be interested to checkout the manuscript-viewer branch of Frescobaldi. It's still in early stages of development but already working. See this screenshot: http://postimg.org/image/gs4lgw80v/ More information: https://github.com/wbsoft/frescobaldi/issues/112 https://github.com/wbsoft/frescobaldi/issues/704 Cheers Federico -- next part -- An HTML attachment was scrubbed... URL: http://lists.bcn.mythic-beasts.com/mailman/private/mutopia-discuss/attachments/20150712/f98066ad/attachment.htm -- Subject: Digest Footer ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss -- End of Mutopia-discuss Digest, Vol 65, Issue 1 ** ___ 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] Changing several files all the same way
I should have used \bookpart from the beginning. I was either unaware of
this option or forgot for the first several movements. Once I remembered,
I decided to do them all at once after I finished. Maybe this was a bad
decision.
Knute Snortum
(via Gmail)
On Mon, Jun 30, 2014 at 10:24 PM, Federico Bruni f...@inventati.org wrote:
Il giorno lun 30 giu 2014 alle 20:40, Knute Snortum ksnor...@gmail.com
ha scritto:
I have finished transcribing the individual movements of Pictures in an
Exhibition. Now i want to create the file that will contain all of them in
order. I'm doing this with one file like this:
%%%
\header {
...
}
\include movement-1.ly
\include movement-2.ly
...
%%
...with the movement files like this:
upper = { ... }
lower = { ... }
\bookpart {
\header {
...
}
\score {
...
\upper
...
\lower
}
}
%%%
I have to add the \bookpart {} to all the movement files. I feel that
this should be all one branch, but should it be separate branches?
I think that it should be one branch.
But.. why didn't you use \bookpart from the beginning? Now you'll have to
move the \header blocks of movements inside \bookpart.
I attach a patch of my test, just to illustrate what I've tried.
As you can see, there's a second \score in ballet.ly which disturbs this
setup.
BTW, some changes are due to the fact that I set the automatic removal of
trailing spaces on save in Frescobaldi preferences.
___
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] Changing several files all the same way
I have finished transcribing the individual movements of Pictures in an
Exhibition. Now i want to create the file that will contain all of them in
order. I'm doing this with one file like this:
%%%
\header {
...
}
\include movement-1.ly
\include movement-2.ly
...
%%
...with the movement files like this:
upper = { ... }
lower = { ... }
\bookpart {
\header {
...
}
\score {
...
\upper
...
\lower
}
}
%%%
I have to add the \bookpart {} to all the movement files. I feel that this
should be all one branch, but should it be separate branches?
Knute Snortum
(via Gmail)
___
Mutopia-discuss mailing list
Mutopia-discuss@mutopiaproject.org
http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] Update the contribute part of website
The contribution page on the Mutopia website [1] doesn't reference the Wiki contribution page [2]. New contributors may not know the specific way that we submit new files. [1] http://www.mutopiaproject.org/contribute.html [2] https://github.com/chrissawer/The-Mutopia-Project/wiki/Setting-up-for-Contributions-via-GITHUB Knute Snortum (via Gmail) ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] clean pull requests?
Regarding merge commits: I will (and have) stopped merging the topic branches into main. But there are merges I'm supposed to make: Synchronize with your local repository Make sure you are in your master branch (not one of your topic branches), and fetch any upstream changes: $ git checkout master $ git fetch upstream $ git merge upstream/master From what I can see, this will cause merge commits when I create a pull request. Am I doing something wrong? Not understanding? Knute Snortum (via Gmail) On Tue, May 13, 2014 at 11:11 PM, Glen Larsen glenl@gmail.com wrote: On Tue, May 13, 2014 at 5:41 PM, Knute Snortum ksnor...@gmail.com wrote: Frederico, I am confused by what you mean by a merge commit. Since it is something I should try to avoid, I should understand what it is. Is it merging a branch into master and committing it? Any merge from another branch will cause GIT to insert a merge commit message into the log file. Glen, I know I'm new to Mutopia. Help me understand why you are using git. It seems you do not want any of the things (at least I) use git for. One file on one branch with no commit history. Why not just send the files in via email? We want the history of changes made to the source files. By squashing commits I mean the process of compressing the series of commits you have used during development into a single commit using git rebase -i or something similar. I may be an edge case, but let me show you why the git model as I understand it adds complexity without any advantage (in fact, there is a major disadvantage.) So, to add a movement to a suite, I - checkout master - fetch upstream - merge with master - create a branch - checkout the branch - create the ly file - add the ly file - commit the ly file - push the branch to my forked github account - get on github - select the new branch - create a pull request - delete the branch on github - delete the branch on my local repository Instead of - create the ly file - send in the ly file via email Source code management systems are necessarily complex, but all we really want from them is to track history. The reason merging and rebasing are powerful is because they need to be for group collaboration. In the Mutopia environment collaboration happens differently than software projects. Does submitting the file via github make it easier for you? Absolutely. If you email it, Chris will be doing half of the steps you outline above. Because it makes it harder for me. I'm not working at the moment to I have a lot of time and I like to spend a good chunk of it transcribing music. This means I can sometimes do a movement in a day or two. I currently have about seven files (and seven branches) that are not on the master. I am still learning how to best create ly files. I may have a trick or a section of code I want to reused from an older branch but because I can't merge back to master, I have to checkout the old branch, stow the file somewhere, checkout the new branch and pull in the file. If I want something from several branches, this can be a real mess. I have run into this as well and I agree it gets more difficult with multiple branches under development. So why are we doing fourteen steps to get one file into git without version or commit history that no one is going to merge with anyway? I think you may have misunderstood me. My opinion is that the log file should contain log messages more relevant to its history than its development. For example, in a long piano piece I may choose to transcribe the treble staff, commit, then the bass, commit, dynamics, commit, then commit aesthetic and midi tweaks. But before I check it in, I may choose to squash those into initial content for ... because, IMO, the user doesn't need or care to know how I chose to work on the piece. I don't think you are an edge case, in fact your workflow is similar to mine. I just choose to minimize log messages. ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] clean pull requests?
Regarding pull requests: I would like to be able to see what is going to be on a pull request before I create it -- or be able to delete a pull request if it has commit on it I don't want. From what I can see in GitHub, once you create a pull request, it's too late to modify it. Is there some solution to this? Knute Snortum (via Gmail) On Wed, May 14, 2014 at 4:58 AM, Knute Snortum ksnor...@gmail.com wrote: Regarding merge commits: I will (and have) stopped merging the topic branches into main. But there are merges I'm supposed to make: Synchronize with your local repository Make sure you are in your master branch (not one of your topic branches), and fetch any upstream changes: $ git checkout master $ git fetch upstream $ git merge upstream/master From what I can see, this will cause merge commits when I create a pull request. Am I doing something wrong? Not understanding? Knute Snortum (via Gmail) On Tue, May 13, 2014 at 11:11 PM, Glen Larsen glenl@gmail.com wrote: On Tue, May 13, 2014 at 5:41 PM, Knute Snortum ksnor...@gmail.com wrote: Frederico, I am confused by what you mean by a merge commit. Since it is something I should try to avoid, I should understand what it is. Is it merging a branch into master and committing it? Any merge from another branch will cause GIT to insert a merge commit message into the log file. Glen, I know I'm new to Mutopia. Help me understand why you are using git. It seems you do not want any of the things (at least I) use git for. One file on one branch with no commit history. Why not just send the files in via email? We want the history of changes made to the source files. By squashing commits I mean the process of compressing the series of commits you have used during development into a single commit using git rebase -i or something similar. I may be an edge case, but let me show you why the git model as I understand it adds complexity without any advantage (in fact, there is a major disadvantage.) So, to add a movement to a suite, I - checkout master - fetch upstream - merge with master - create a branch - checkout the branch - create the ly file - add the ly file - commit the ly file - push the branch to my forked github account - get on github - select the new branch - create a pull request - delete the branch on github - delete the branch on my local repository Instead of - create the ly file - send in the ly file via email Source code management systems are necessarily complex, but all we really want from them is to track history. The reason merging and rebasing are powerful is because they need to be for group collaboration. In the Mutopia environment collaboration happens differently than software projects. Does submitting the file via github make it easier for you? Absolutely. If you email it, Chris will be doing half of the steps you outline above. Because it makes it harder for me. I'm not working at the moment to I have a lot of time and I like to spend a good chunk of it transcribing music. This means I can sometimes do a movement in a day or two. I currently have about seven files (and seven branches) that are not on the master. I am still learning how to best create ly files. I may have a trick or a section of code I want to reused from an older branch but because I can't merge back to master, I have to checkout the old branch, stow the file somewhere, checkout the new branch and pull in the file. If I want something from several branches, this can be a real mess. I have run into this as well and I agree it gets more difficult with multiple branches under development. So why are we doing fourteen steps to get one file into git without version or commit history that no one is going to merge with anyway? I think you may have misunderstood me. My opinion is that the log file should contain log messages more relevant to its history than its development. For example, in a long piano piece I may choose to transcribe the treble staff, commit, then the bass, commit, dynamics, commit, then commit aesthetic and midi tweaks. But before I check it in, I may choose to squash those into initial content for ... because, IMO, the user doesn't need or care to know how I chose to work on the piece. I don't think you are an edge case, in fact your workflow is similar to mine. I just choose to minimize log messages. ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Renaming file names of movements
This is how I propose to have the movements and the suite: https://drive.google.com/folderview?id=0B_aEseOV9KTXamtCeUhXenF2eWcusp=sharing Knute Snortum (via Gmail) On Wed, May 14, 2014 at 4:44 AM, Knute Snortum ksnor...@gmail.com wrote: I agree. My original idea was to do this: put the music into includable files, e.g. allegro.ily, andante.ily, presto.ily. Then use the ily files to create individual movements and the suite or sonate: allegro.ly, andante.ly, presto.ly, sonate.ly. That way if the music has to be changed, it will change in the individual file and the aggregate file. What I'm trying to avoid is a sonate.ly which is just a cut and paste of the movements. Knute Snortum (via Gmail) On Wed, May 14, 2014 at 1:07 AM, Federico Bruni f...@inventati.orgwrote: I would not hard-code the numbers in the names. If you have a file for the whole suite, which includes all the movements in the right order, you have already defined the order. Cleaner and more flexible, in my opinion. On 14 maggio 2014 04:46:22 CEST, Knute Snortum ksnor...@gmail.com wrote: I brought up the problem here of how to present a set of movements that can be individually downloaded and yet allow the user to play the suite as a whole in the correct order. The easiest solution was deemed the best, that is, rename the movements with numbers as the beginning of their name so that the order is evident. To that effect, I'd like to propose the renaming of these files. First, from The-Mutopia-Project\ftp\BachJS\BWV814\french-suite-3\french-suite-3-lys 01-bach-french-suite-3-allemande.ly 02-bach-french-suite-3-courante.ly 03-bach-french-suite-3-sarabande.ly 04-bach-french-suite-3-menuet.ly 05-bach-french-suite-3-trio.ly 06-bach-french-suite-3-gavotte.ly 07-bach-french-suite-3-gigue.ly Second, from The-Mutopia-Project\ftp\BachJS\BWV817\french-suite-6\french-suite-6-lys 01-bach-french-suite-6-allemande.ly 02-bach-french-suite-6-courante.ly 03-bach-french-suite-6-sarabande.ly 04-bach-french-suite-6-gavotte.ly 05-bach-french-suite-6-polonaise.ly 06-bach-french-suite-6-bourree.ly 07-bach-french-suite-6-menuet.ly 08-bach-french-suite-6-gigue.ly Knute Snortum (via Gmail) -- Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss -- Federico ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Renaming file names of movements
I love it. A while ago I asked how to create a single all-movements suite file and this is exactly what I needed to see. Now I need to know how to submit this. One branch and pull request for each movement separately and one for the suite? Knute Snortum (via Gmail) On Wed, May 14, 2014 at 6:37 AM, Federico Bruni f...@inventati.org wrote: Il 14.05.2014 14:43 Knute Snortum ha scritto: This is how I propose to have the movements and the suite: https://drive.google.com/folderview?id=0B_aEseOV9KTXamtCeUhXenF2eWcusp= sharing [21] A couple of comments: - your -all.ly file, which includes all the movements, doesn't print the titles of each movement. You may use print-all-headers, but I think that it's better using \bookpart - personally I don't like splitting each piece in two files (one for the music definitions and one for the \score block), unless it's really necessary I've changed the suite file and the first two pieces. This is how I would do it, but of course others may have different opinions. ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] git advice: remove a merge
Do we have any git experts here? I merged a topic branch to master, which I now know not to do. But this merge shows up on all of my pull requests. How do I back out the merge and make the pull requests clean? git revert doesn't seem like the right thing, because it creates commits rather than removing them. git rebase doesn't seem right either because again, it resets the head, but then replays all the commits after that. Any ideas? Knute Snortum (via Gmail) ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Renaming file names of movements
I would put all the changes into one pull request (I wouldn't even use a branch) but Glen has said (and this document [1] implies) that there should be one file per branch per pull request. I admit that this seems strange but I'm trying to do things the Mutopia way. [1] https://github.com/chrissawer/The-Mutopia-Project/wiki/Setting-up-for-Contributions-via-GITHUB Knute Snortum (via Gmail) On Wed, May 14, 2014 at 7:55 AM, Federico Bruni f...@inventati.org wrote: Il 14.05.2014 16:20 Knute Snortum ha scritto: I love it. A while ago I asked how to create a single all-movements suite file and this is exactly what I needed to see. Great! Now I need to know how to submit this. One branch and pull request for each movement separately and one for the suite? Why splitting in two pull requests? The suite file is quite trivial (there's only the header to check). I would use one branch for everything, hence one pull request. ___ 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
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. Knute Snortum (via Gmail) On Wed, May 14, 2014 at 11:00 AM, Felix Janda felix.ja...@posteo.de wrote: git reset --hard should be able to fix up your master. Then make new topic branches and git-cherry-pick your work into them. Then make new pull-requests and close the old ones. (Can you really not do this yourself? If not you could still add a comment to the pull-request.) Felix ___ 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
I have pulled out all the ly files I have been working on and stowed them. I'll put them back one by one when my repository is clean. Then hopefully I will be able to create clean pull requests. BTW, I found out how to delete a pull request: close it first. I had assumed Close meant the comments. Knute Snortum (via Gmail) On Wed, May 14, 2014 at 11:30 AM, Glen Larsen glenl@gmail.com wrote: On Wed, May 14, 2014 at 11:23 AM, Knute Snortum ksnor...@gmail.comwrote: 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?
Frederico, I am confused by what you mean by a merge commit. Since it is something I should try to avoid, I should understand what it is. Is it merging a branch into master and committing it? Glen, I know I'm new to Mutopia. Help me understand why you are using git. It seems you do not want any of the things (at least I) use git for. One file on one branch with no commit history. Why not just send the files in via email? I may be an edge case, but let me show you why the git model as I understand it adds complexity without any advantage (in fact, there is a major disadvantage.) So, to add a movement to a suite, I - checkout master - fetch upstream - merge with master - create a branch - checkout the branch - create the ly file - add the ly file - commit the ly file - push the branch to my forked github account - get on github - select the new branch - create a pull request - delete the branch on github - delete the branch on my local repository Instead of - create the ly file - send in the ly file via email Does submitting the file via github make it easier for you? Because it makes it harder for me. I'm not working at the moment to I have a lot of time and I like to spend a good chunk of it transcribing music. This means I can sometimes do a movement in a day or two. I currently have about seven files (and seven branches) that are not on the master. I am still learning how to best create ly files. I may have a trick or a section of code I want to reused from an older branch but because I can't merge back to master, I have to checkout the old branch, stow the file somewhere, checkout the new branch and pull in the file. If I want something from several branches, this can be a real mess. So why are we doing fourteen steps to get one file into git without version or commit history that no one is going to merge with anyway? Knute Snortum (via Gmail) On Tue, May 13, 2014 at 3:27 PM, Glen Larsen glenl@gmail.com wrote: 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.orgwrote: 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
[Mutopia-discuss] Remove the following pull requests
Please remove, close, ignore, or whatever you do to get rid of pull requests for the following: #382 - promenade 5 #381 - two-jews #380 - ballet #379 - Promenade 4 #378 - Bydlo #377 - Tuileries #376 - Promenade 3 #375 - Il vecchio castello #374 - Promenade 2 #373 - Gnomus #370 - put back nobm I will either cleanup my git repository and resubmit them cleanly, or send them in via email. Knute Snortum (via Gmail) ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] Suggested file directory changes
I'd like to suggest the following changes to *The-Mupodia-Project/ftp/MussorgskyM* 1. create a directory called *pictures-at-an-exhibition* 2. Under that, create a directory named *pictures-at-an-exhibition-lys* 3. rename *promenade/promenade.ly http://promenade.ly* to *promenade-1.ly http://promenade-1.ly* 4. Move *promenade-1.ly http://promenade-1.ly *to *pictures-at-an-exhibition-lys* 5. remove the directory *promenade* Knute Snortum (via Gmail) ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] Renaming file names of movements
I brought up the problem here of how to present a set of movements that can be individually downloaded and yet allow the user to play the suite as a whole in the correct order. The easiest solution was deemed the best, that is, rename the movements with numbers as the beginning of their name so that the order is evident. To that effect, I'd like to propose the renaming of these files. First, from The-Mutopia-Project\ftp\BachJS\BWV814\french-suite-3\french-suite-3-lys 01-bach-french-suite-3-allemande.ly 02-bach-french-suite-3-courante.ly 03-bach-french-suite-3-sarabande.ly 04-bach-french-suite-3-menuet.ly 05-bach-french-suite-3-trio.ly 06-bach-french-suite-3-gavotte.ly 07-bach-french-suite-3-gigue.ly Second, from The-Mutopia-Project\ftp\BachJS\BWV817\french-suite-6\french-suite-6-lys 01-bach-french-suite-6-allemande.ly 02-bach-french-suite-6-courante.ly 03-bach-french-suite-6-sarabande.ly 04-bach-french-suite-6-gavotte.ly 05-bach-french-suite-6-polonaise.ly 06-bach-french-suite-6-bourree.ly 07-bach-french-suite-6-menuet.ly 08-bach-french-suite-6-gigue.ly Knute Snortum (via Gmail) ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] Fwd: Add LilyPond incipit on an IMSLP page.
(Forwarding to the Mutopia mailing list) Knute Snortum (via Gmail) -- Forwarded message -- From: Knute Snortum ksnor...@gmail.com Date: Thu, May 8, 2014 at 10:27 AM Subject: Re: Add LilyPond incipit on an IMSLP page. To: Pierre Perol-Schneider pierre.schneider.pa...@gmail.com Cc: Federico Bruni fedel...@gmail.com, lilypond-user lilypond-u...@gnu.org Pierre: (Why I'm not a Mutopia user.) I think many of your criticisms are legitimate. I'd like to be part of making Mutopia a better site. Right now I am just a contributor but at some point maybe I can help with making the site better. I don't think there is competition between IMSLP and Mutopia. There is some overlap, of course. I could be wrong but what I see mostly at IMSLP are photocopies of scores. If that's right, I think there's a place for newly created PDFs that are clear. Also, many times I click on a PDF and it's so old a version that it doesn't render. At least with a LilyPond file you can (usually) update it and get a decent PDF out of it. I'd like to see more cooperation between Mutopia and IMSLP. Is there anything you could suggest? Perhaps cross links? Knute Snortum (via Gmail) On Thu, May 8, 2014 at 7:49 AM, Pierre Perol-Schneider pierre.schneider.pa...@gmail.com wrote: 2014-05-08 8:58 GMT+02:00 Federico Bruni fedel...@gmail.com: It's the LilyPond plugin for MediaWiki? Yep, see : http://www.imslpforums.org/viewtopic.php?f=3t=7034hilit=incipit BTW, in January I launched a survey about contributions to Mutopia: http://lists.gnu.org/archive/html/lilypond-user/2014-01/msg9.html Hum, I've missed this one. As far as I know, you never contributed to it (just had a look on Mutopia git repository). No I didn't. Can I ask you why? It's because of the license restrictions (NonCommercial clause is not accepted by Mutopia)? Because I'm no Mutopia user. Now the right question would be why am I not a user ? Well, few years ago I've downloaded one or two files and, as far as I remember : a) None of'em were compilable. b) Copy/paste-ing the notes took me much more time than rewriting the whole score after a facsimile. c) Pdfs look bad (what's the purpose of such footers ??). I've just take a quick look at the Mutopia site. I'd like to add : a) it is written The Mutopia Project offers sheet music editions of classical music for free download ; which means that it is in direct competition with IMSLP. Does it make sense ? b) the composer's pages are not user-friendly ; why not using a wiki system ? c) a majority of (all ?) scores are coded relatively ; exept when coding for organ, piano, harp, etc. I never use \relative d) there is no coding convention; many Mutopia codes (e.g. http://www.mutopiaproject.org/ftp/BrownCJ/lullaby/lullaby.ly) give me headhaches. e) there are numbers of pretty old version (v2.4 for this one : http://www.mutopiaproject.org/ftp/CarcassiM/O60/carcassi-op60-01/carcassi-op60-01.ly ) f)...etc. (too long) I'd like to conclude that Mutopia site remains the same for years, no improvement, no discussion (except you, Federico). So, if nothing changes, I don't see any future for this site. Cheers, ~Pierre ___ lilypond-user mailing list lilypond-u...@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] Helping
I can see that Mutopia is starting get moving again. I want to help. That may mean just typesetting as many pieces as I can. I am on disability so I have a lot of time on my hands. Can I help with cleaning up the old source files? Merging pull request? Improving the web site? Improving automation of the merge procedure? I have a programmer background. Tell me how I can help. Knute Snortum (via Gmail) ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] Presenting multi-movement music as one piece
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
