gmane.music.mutopia.discuss

Re: re contribution

Chris Sawer — 2012-02-07T21:53:31

Unfortunately the github issue tracker is a bit too simplistic.

We really need some way of categorising issues, eg. to separate code 
changes to the website backend, corrections of errors in pieces, 
updates, etc. and the github tracker doesn't allow this, as far as I know.

However it sounds like Valentin is working on things (thanks Valentin!) 
and I look forward to seeing the system when it is up and running.

Chris

Re: re contribution

Robert Ames — 2012-02-07T04:07:53

If the project is already hosted with github is there an issue with using the github issue tracker?  Maybe it isn't the most welcoming for non-technical contributors but surely there would be a way to interface between something simple and the github issue APIs?

--Robert

On Feb 6, 2012, at 5:02 PM, Valentin Villenave <valentin-RoNcNBGe6/kqcZcGjlUOXw< at >public.gmane.org> wrote:

Re: re contribution

Valentin Villenave — 2012-02-06T23:02:55

Oh yeah, about that: as you may have noticed, I've been struggling for
a while to install Redmine, which seems better documented than
FusionForge (and it's less of a mess). I have made a SQL dump from the
FusionForge database (there were only 6 entries at this time). I
didn't want to tell you about it before I could reach some kind of a
result...

I miss FlySpray, it was the easiest bug-tracker I've ever installed!
But it's been left unmaintained for several years now. (Now, back to
Redmine and this pretty bizarre RoR thing...)

Cheers,
Valentin.

Re: re contribution

Chris Sawer — 2012-02-06T22:05:15

That sounds like a nice project to be working on.  :-)

Thanks for the offer of help last year. Quite a number of people 
responded, and our plan was to put in place a system to allow the work 
to be distributed and co-ordinated amongst volunteers.

Unfortunately there have been some problems with the system that was 
installed (FusionForge). It is not currently in a fully usable state 
which is preventing us from making real progress.

I don't have any time to work on it now. If anyone has experience of 
FusionForge, or fancies diving into a large PHP/MySql based project to 
figure out how to make it work, then let us know.

In the meantime I am dealing with new music contributions (not doing 
very well at staying up-to-date, sorry) and Javier is helping out with 
corrections and fixes.


Ultimately all files end up in Git, and are compiled using latest stable 
LilyPond on my Ubuntu box (currently Ubuntu 11.04 with LilyPond 2.14.2 
from the LilyPond website).

If you want to send me an example piece I woul

Re: Lilypond web-editor

Pavel Roskin — 2012-02-06T12:16:45

Quoting Calixte FAURE <calixte.faure-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>:


I'd rather see Lilypond support a command line option to transpose the score.

I posted so many feature requests to Lilypond lists lately, I'll  
appreciate if someone else posts this one.

Re: Lilypond web-editor

Valentin Villenave — 2012-02-06T10:39:39

Hi Calixte,
(for future conversations: feel free to send me whatever messages you
need to post (either on LilyPond or Mutopia mailing lists) and I'll
translate for you.)


Yes, Nicolas Sceaux had a similar idea a while back. It does require a
lot of work and resources, though: web development, debugging,
computing power, security risks etc.

This online editor certainly works well for simple scores but for
longer scores (with \includes etc.) it's not so simple.

Cheers,
Valentin

_______________________________________________
Mutopia-discuss mailing list
Mutopia-discuss< at >mutopiaproject.org
http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss

Lilypond web-editor

Calixte FAURE — 2012-02-06T09:24:22

[Thanks to Dean Herington for the translation]

Hi, I posted this message on the english-speaking list, it’s about Mutopia,
so i post it on this list too.
Please read on the english list at first:
http://old.nabble.com/Experimental-Web-based-Lilypond-Editor-td33242123.html#a33242123

Hello,

I've tried in vain to write my message in
English, but given the difficulty I've had, I'm
posting in French, hoping that someone will post
it to the English-speaking list...
We could discuss it here [on the French-speaking
list], but there's more response on the
English-speaking list!

It would be interesting to combine some of the
Mutopia files with this online editor, especially
melodies and songs, to make it easy to transpose
these scores automatically without having to
copy/paste the source code, add the \transpose
command, etc.  Maybe a simple interface could be
created for this specific purpose?

I use Mutopia mainly for this purpose, and with
this feature I would be able to share [the
transposed scores] with my

re contribution

corallina — 2012-02-04T18:40:36

Greetings,

I posted mid last year that I would be willing to help with mutopia, mostly
on some administrative things like getting some of my submissions
in place.   Unfortunately I was delayed on a project (barn roof) until now.

So now I am back and would like to work on my queued project.
I have the links for the readme.html and have looked at the git url.

Please advise what I can do as my last submission has some files
with japanese hiragana text and I would like to see how they come
out mutopiaproject.org

thanks

Re: What is the accepted 'form' when convertingsomeone else's score to latest stable LilyPond

J Ruiz — 2012-01-19T08:31:02

Hi Pavel, Herbert,

For corrected scores, the "View Change History" link available in the "more details" page of the score can show names of other contributors that submitted corrections.  If the correction request was not a revised lilypond file, the implementer of the change may also be listed in change history.

Indeed, for older scores the maintainer info may be stale or the original typesetter may not reply to requests.

Mutopia gets a fair amount of corrections requests that just state the nature of the correction in text form.  In these cases, a Mutopia Project contributor will validate and implement these correction requests in Lilypond.

Check the change history for this piece as example:
http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=199 


Best Rgds, Javier

Javier Ruiz-Alma



________________________________
 From: Pavel Roskin <proski-mXXj517/zsQ< at >public.gmane.org>
To: hhebert-WV4amv3fr2bMB8ReZkJZ5g< at >public.gmane.org 
Cc: mutopia-discuss< at >mutopiaproject.org 
Sent: Tuesday, January 17, 2

Re: What is the accepted 'form' when converting someone else's score to latest stable LilyPond

Pavel Roskin — 2012-01-17T22:47:03

On Tue, 17 Jan 2012 08:05:26 -0200 (BRST)
"Hermogenes Hebert Pereira Oliveira" <hhebert-WV4amv3fr2bMB8ReZkJZ5g< at >public.gmane.org> wrote:


That sounds reasonable to me.  The contributors could be mentioned on
the page containing the links to the source, the PDF and the MIDI file.

Re: What is the accepted 'form' when converting someone else's score to latest stable LilyPond

Hermogenes Hebert Pereira Oliveira — 2012-01-17T10:05:26

Hi, James.


I think the best practice is to have no name at all in the score
itself.  Only the name of the project.  Individual contributors to a
given score should be credited in a commentary at the beginning of the
source .ly file or in a separate text file named something like
"contributors" or "typesetters".  A brief description of that person's
contributions should accompany each name.

That's my two cents.

Regards,

Re: What is the accepted 'form' when converting someone else's score to latest stable LilyPond

Pavel Roskin — 2012-01-16T15:07:12

On Mon, 16 Jan 2012 12:15:28 +0000
Ubw iobt <ubw106t-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:


Indeed, the tagline is misleading because it says "typeset by
\maintainer", but it's not always the maintainer who did most of the
typesetting work.

It should be possible to credit the original typesetter in the source,
but I think it's still wrong to mislead those who get the printed score.

To make the matter more complicated, the amount of effort may be very
different for different scores. In some cases, it's just running
convert-ly.  In other cases, a lot of work may be needed to display the
score correctly and to produce a nice sounding MIDI file.

And then there is proofreading, which changes very little but takes a
lot of time...

What is the accepted 'form' when converting someone else's score to latest stable LilyPond

Ubw iobt — 2012-01-16T12:15:28

Hello,

I have not posted anything to Mutopia before and I wasn't easily able to
find the answer in the email threads.

What is the accepted behaviour when taking someone else's .ly file and
converting it with regard to the tagline.

Not that I want my own name in there or am trying to take any 'glory' for
simply running convert.ly on an old score, but I am more thinking in cases
of old versions of LilyPond or pieces which have not been converted for
many years, is it really acceptable or fair to leave the original person's
name and/or email in the ly file?

Thanks for your time

James
_______________________________________________
Mutopia-discuss mailing list
Mutopia-discuss-KSwT1vaRc9aJnvDnx1genB2eb7JE58TQ< at >public.gmane.org
http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss

Re: Unclear sources

Javier Ruiz-Alma — 2011-09-19T18:30:08

Hello Glen,
...and welcome to the Mutopia discussion list,
If you attached a .ly file, it didn't come through.  You may opt to just copy/paste the text to the end of future messages.
 
I have some generic input, but please note my experience is primarily typesetting piano scores.
 
On your item#2, I think you have the right general approach in dealing with these issues:
-make a decision and typeset the approach that incorporates the notes as seen in the original that meet the timing and make best sense in midi.
-annotate the .ly with comments explaining your rationale and any sources you used to support your approach.
 
These issues are not terribly uncommon when typesetting older scores, but I can't recall an instance where I've used grace notes as a fix.
 
Typically, I've found these are due to:
-missing tuplet marking
-missing dot on a dotted note, or conversely misinterpreted a scanning blemish as note duration modifier.
-multiple voices typeset as single voice, or not correctly typesetting

Unclear sources

Glen Larsen — 2011-09-19T01:15:20

_______________________________________________
Mutopia-discuss mailing list
Mutopia-discuss-KSwT1vaRc9aJnvDnx1genB2eb7JE58TQ< at >public.gmane.org
http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss

Re: Mutopia - going forward

Chris Sawer — 2011-08-14T13:23:47

A further update :-

Getting GIT and the bug tracking system running has taken longer than 
expected, however we are aiming to have it in place for the beginning of 
September.

Once this is running I will start putting issues into it and those who 
have volunteered to help in various ways will be able to do so.

I should be able to spend a reasonable amount of time working on Mutopia 
from September until the end of the year. In January I move back to the 
UK and will have less time available. I hope by that point the new team 
will be running smoothly.

Thanks for your patience.

Regards,

Chris



On 03/07/11 23:18, Chris Sawer wrote:

java/python conversion

Christian Boyd — 2011-07-20T02:02:21

I'm interested in contributing to the java - python conversion.  I've looked
through a majority of the .java files to get the idea, would love to
communicate with whoever contributed to the java files in the past if
possible, I know Chris did, maybe others too?  Maybe this was covered, but
I'll risk asking an obvious question, which version of python are we
interested in using? More 2 or more 3 like?

Christian Boyd
_______________________________________________
Mutopia-discuss mailing list
Mutopia-discuss-KSwT1vaRc9aJnvDnx1genB2eb7JE58TQ< at >public.gmane.org
http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss

Mutopia - going forward

Udo Weigelt — 2011-07-18T14:17:32

_______________________________________________
Mutopia-discuss mailing list
Mutopia-discuss-KSwT1vaRc9aJnvDnx1genB2eb7JE58TQ< at >public.gmane.org
http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss

Re: Mutopia - going forward

Chris Sawer — 2011-07-04T16:11:33

Thanks for the offer Edward.

I will try and get together a list of requirements for what the python 
module should ultimately be able to do.

You are welcome to bug me re: expected results.  :-)

I think it would be useful to port some of the bash stuff to python, 
particularly mutopia-compile.sh which is a bit of a hacky mess at the 
moment.

Chris



On 04/07/11 00:39, Edward Cannon wrote:

Re: Mutopia - going forward

Edward Cannon — 2011-07-03T22:39:54

I've done a fair bit of Python in my time, and would be happy to
implement some more of the Mutopia.py process as long as there was
someone I could bug occasionally re: expected results. Also I don't
know if anyone is interested, but i could also port some of the bash
files to python if that is wanted (would work on windows as well, bash
on windows is not pretty)
Edward Cannon
Unicorn School

On Sun, Jul 3, 2011 at 2:18 PM, Chris Sawer <chris-KSwT1vaRc9aJnvDnx1genB2eb7JE58TQ< at >public.gmane.org> wrote:

Re: Mutopia - going forward

Chris Sawer — 2011-07-03T21:18:06

Dear all,

Thanks for all the responses and offers of help received in response to 
my e-mail below, both on and off-list. Those who responded off-list have 
been asked to join the mailing list so hopefully everyone will see this.

Valentin is in the process of setting up GIT and the bug tracking 
system. Once this is available I will start putting contributions and 
corrections into it.

However that's no good if people don't know what to do with them, so I 
have compiled a list of instructions of how I update pieces in Mutopia, 
along with the scripts for doing so. They will work on Linux or Mac OS, 
java and bash are required. See:

http://www.mutopiaproject.org/UsefulScripts/
http://www.mutopiaproject.org/UsefulScripts/readme.html

If you have volunteered to work on updating and/or adding new pieces to 
Mutopia please take a look at the scripts and see how they work.

The scripts are a bit clunky but generally get the job done. I am 
planning to move all the java stuff to python, along with the website