gmane.music.mutopia.discuss

Re: Musical score transcription as a Wikimediaproject

BrumleyGap — 2013-04-25T21:00:10

I am excited about the <score> tag, and I'd find a Wikisource for music
transcriptions useful and interesting. I'd enjoy working on that project.


On Thu, Apr 25, 2013 at 4:05 PM, David Cuenca <dacuetu-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

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

Musical score transcription as a Wikimedia project

David Cuenca — 2013-04-25T20:05:01

Hi all,

At the Wikimedia community we are discussing about the possible creation of
a project for musical score transcription based on LilyPond:
https://meta.wikimedia.org/wiki/Requests_for_comment/Musical_score_transcription_project_proposal

Currently we have a project called Wikisource, where users can proofread
books (ocr text vs scanned image), and we were thinking of expanding this
concept to musical scores. Here a couple of examples:
https://en.wikisource.org/wiki/Page:A_Dictionary_of_Music_and_Musicians_vol_1.djvu/24
https://fr.wikisource.org/wiki/Page:Barzaz_Breiz,_huiti%C3%A8me_%C3%A9dition.djvu/642

This score rendering capability has been just released so it still needs
some polishing, but we are assessing the interest to develop it further.

What would be your opinion on such a project? Would the Mutopia community
be open for a potential collaboration?

Regards,
David ---User:Micru
_______________________________________________
Mutopia-discuss mailing list
Mutopia-discuss-KSwT1vaRc9aJnvDnx1gen

Help with Lilypond

Huw Richards — 2013-04-21T09:42:43

Dear All,

I have been using Lilypond to transcribe various pieces of music for  
Mutopia for 2 or 3 years now, but have not yet uploaded anything to  
Mutopia. I am very happy with typing in the notes, clefs, time  
signatures etc. but I struggle to know how to produce a complete  
assembled document with page numbers, cover, text etc.

As an example of what I mean, I have produced a set of six viola/ 
violin duets by Benjamin Blake. I have them as multiple files (- viola  
file, violin file, score file) for each duet.

I would like to be able to combine them elegantly into a book.  I  
think I may have started in the wrong way and perhaps should have  
understood more about possible file structures before I started.
I do not understand how, or if,  Lilypond can combine files together  
to produce a single output.

Is there any way / anywhere I can get face-to-face training or help  
with this in particular and with Lilypond in general?

I live in Cambridge, UK.


Huw Richards - ahr-NYm7L50haCA2EctHIo1CcQ< at >p

Re: Help in typesetting/decyphring a song into a musical notation

Glen Larsen — 2013-04-20T05:50:51

Mutopia's goal is to provide high quality typeset editions of legally
available sheet music.
Modern jazz and popular music are unavailable due to copyright
restrictions. Unless the music has been officially released to the public
domain, Mutopia would be unable to help.

'Creating one' translates to divining the notation of the composition by
ear. Just like a personal recording, it is fine for you to do that for
personal use but not for you to publish without permission. Given that your
article may have some benefit to the commercial popularity of the music
itself, you may be able to persuade the artist to allow portions of the
sheet music to be released to the public domain. Write and ask.

-glen


On Fri, Apr 19, 2013 at 9:39 PM, Ricardo Barros Duarte d'Oliveira <
richardtrle-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

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

Help in typesetting/decyphring a song into amusical notation

Ricardo Barros Duarte d'Oliveira — 2013-04-20T04:39:40

Hello there, I've been seeking/hunting for a musical sheet for a song,
which I'm delightfully writing about on Wikipedia, the song is written,
produced and composed by Boney James (which features his saxophone along
LeToya Luckett's vocal, former member of Destiny's Child) and the song is
titled When I Had The Chance, however I've had no success in my search.

Even though I hadn't luck in finding its musical composition, I could
create or ask for helping on *creating* one, this is important to the
song's article in Wikipedia because details such as composition key, time
and vocal range would enhance its encyclopedic value. So I came accross
Mutopia, and the intriguing detail is that I'm fancy of open
community/projects/source things.

So, can anyone aid me in this?

Your Participation Requested: New Tagline Design

Javier Ruiz-Alma — 2013-02-20T07:43:18

Hello friends and contributors,

Mutopia includes a distinctive tagline on the last page of its sheet 
music. We will be updating to a new design for future and updated 
publications.

We invite your contributions and ideas.

To minimize email traffic to the discussion list, please visit the 
following link to comment, contribute, and (gently) critique:

https://github.com/chrissawer/The-Mutopia-Project/issues/131

There, you'll find all the details behind this request, as well as 
sample submissions.

If you have a tagline-specific question, contact me directly:
javier (at) ruiz-alma.com

We plan on selecting the new tagline in the coming weeks.

Thanks in advance for your support,

Javier

Re: On the header parsing

Felix Janda — 2013-01-09T18:40:57

Ah, the tagline depends on the license. So one should maybe put it into a
different file for later processing? I mean the parsing with lilypond still
takes much longer than the scripts currently used at Mutopia, especially for
big orchestral project. Therefore it would be good to ask lily only once for
the header fields.

I'm not sure what you mean by the "date-id field".


You can also have commands broken in several lines on the command line if you
have them in single quotation marks ("'").

Felix

Re: On the header parsing

David Kastrup — 2013-01-09T18:34:55

Felix Janda <felix.janda-1KBjaw7Xf1+zQB+pC5nmwQ< at >public.gmane.org> writes:


[...]


ly:book-header would appear to be essential for reading this kind of
info out again from Scheme, and it has only been available since this
same commit.  So it is not just markup->string that is relevant for this
technique.

Re: On the header parsing

Felix Janda — 2013-01-09T18:23:50

Thanks, markup->string is quite useful.

Felix

Re: On the header parsing

David Kastrup — 2013-01-09T09:54:09

Felix Janda <felix.janda-1KBjaw7Xf1+zQB+pC5nmwQ< at >public.gmane.org>
writes:


Huh.  Several functions are only available with

commit eab591fe423ef0eeb03d8bbedf7d43185d2fbc74
Author: Reinhold Kainhofer <reinhold-b4yQ/SkZ5D954TAoqtyWWQ< at >public.gmane.org>
Date:   Mon Dec 27 15:49:30 2010 +0100

    Print out header fields as PDF metadata; Add simple markup->string function
    
    -) Create DOCINFO pdfmark, with the metadata fields extracted
       from the \header block
    
    -) Add scheme function markup->string that extracts and returns only the
       string part of a markup. As all header fields are possibly markups,
       we need to call this function on the header fields and use only
       the string representation (formatting and possibly some information
       lost!) as metadata.
       This function is very simply (for all known text markup functions,
       it extracts the text and ignores the formatting, all other markup
       functions are entirely ignored), so it might not work perfectly

Re: On the header parsing

Glen Larsen — 2013-01-08T22:51:47


It is likely this code will supplant the pure-python version that applies
Mutopia's header rules to the key/value pairs. These are required to build
the Mutopia tagline, fix up the date-id field, as well as the RDF files.



Thanks. The motivation for it was to make this sort of experimentation with
lilypond a little easier. For me it is much easier to read scheme code when
it is formatted; put it in one-long-string and I get lost.

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

Re: On the header parsing

Felix Janda — 2013-01-08T19:25:11

Yeah, I think it still needs some processing. IMO, The header fields should be
checked for their validity and the remaining fields written to a preliminary
(incomplete) .rdf-file. (They are only required for the .rdf aren't they?)

Your wrapper looks like a good start.

which could mess up parsing. I'd replace those with nulls in the scheme and change
them back with the python. (If there are nulls in header fields this will go wrong,
but I don't really see an application for having nulls in header fields.) So
varying David's command line a bit

lilypond -e '(set! print-book-with-defaults (lambda (parser book)
             (module-for-each (lambda (sym var) (if (markup? (variable-ref var))
             (format #t "~a=~a~%" sym
             (string-map (lambda (c) (if (eq? c #\newline) #\nul c))
             (markup->string (variable-ref var)))))) (ly:book-header book))))' file.ly

replaces newlines by nulls and prints header fields literally without escaping
characters. (Otherwise the nulls would be displaye

Re: On the header parsing

Felix Janda — 2013-01-08T18:50:17

Thanks, that's really elegant.

So the expressions in lilypond's -e option are interpreted after the input
file so that something like print-book-with-defaults, which is usually
defined in lily-library.scm, can be overidden?

Do you have a (rough) estimate for what's the earliest lilypond version which
works with this command line?

Felix

Re: On the header parsing

Glen Larsen — 2013-01-08T01:24:40

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 <dak-mXXj517/zsQ< at >public.gmane.org> wrote:

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

Re: On the header parsing

David Kastrup — 2013-01-07T15:59:36

Felix Janda <felix.janda-1KBjaw7Xf1+zQB+pC5nmwQ< at >public.gmane.org>
writes:


dak< at >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="hanwen-qWit8jRvyhVmR6Xm/wNWPw< at >public.gmane.org"
instrument="Horn in F"
editor="Henri Kling"
maintainer="hanwen-qWit8jRvyhVmR6Xm/wNWPw< at >public.gmane.org"
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

Re: On the header parsing

2013-01-06T10:36:42

This version logged as discussion on Mutopia github tracker:<br/>https://github.com/chrissawer/The-Mutopia-Project/issues/66<br/><br/>Rgds Javier<br/><br/><br/>Javier Ruiz<br/>javier-Fg0WtujUEU+B+jHODAdFcQ< at >public.gmane.org<br/>_______________________________________________
Mutopia-discuss mailing list
Mutopia-discuss-KSwT1vaRc9aJnvDnx1genB2eb7JE58TQ< at >public.gmane.org
http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss

Re: On the header parsing

Felix Janda — 2013-01-01T14:46:45

The shell script errors if header fields are not defined or markups.

Attached is an extended version which reads all headers mentioned in [1],
tries to validate them and print as much useful info as possible.

It's called like "sh mutopia-check.sh file.ly". Before using it you should
setup the environment variable MUTOPIA_BASE (see UsefulScripts/readme.html)
so that it can find the datafiles. (and you should have read the script. I
could have put some evil stuff into it...)

This is my first exprience with scheme.

I have no idea what lilypond versions the script works with.

Felix

[1]: http://www.mutopiaproject.org/contribute.html
_______________________________________________
Mutopia-discuss mailing list
Mutopia-discuss-KSwT1vaRc9aJnvDnx1genB2eb7JE58TQ< at >public.gmane.org
http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss

Re: On the header parsing

Felix Janda — 2012-12-29T21:15:22

snip

I just played a bit more around and found a way to get lilypond to output
header fields just after parsing by inserting some scheme code at the end of
the file. Attached is a proof-of-concept script for retrieving the composer
name (use it like "sh composer.sh file.ly").

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

Re: On the header parsing

Glen Larsen — 2012-12-17T07:40:28

Felix,
Thanks for clarifying. The evolution of mutopia moving to a git archive and
allowing submissions via an SCM has created a motivation for separating
music content form archive management content. It's a good idea: make
processing at the "pull acceptance" side of things easier. The person
accepting the pull is going to want to visually review the change. That's
time-consuming. If after review you can simply run a move-to-server script
without making further edits, that would be an advantage.

-glen


On Sun, Dec 16, 2012 at 1:58 PM, Felix Janda <felix.janda-1KBjaw7Xf1+zQB+pC5nmwQ< at >public.gmane.org> wrote:

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

Re: On the header parsing

Felix Janda — 2012-12-16T21:58:03

Thanks for your comments!


lilypond has an -dbackend=null option which at least omits the pdf file.
However when using this the -H option seems to be ignored...
Maybe this will get more useful in a future lilypond version.

I agree that in the usual case parsing is not difficult.



No, I meant something different. To summarise:
The goal is to keep the least possible amount of information in the git
repository. So all fields which are regenerated with each update should not
be kept in the repository. Therefore the fields "lastupdated", "footer" and
(standard mutopia) "tagline" should be removed. But the ID of the piece has to
be kept, so add a new header field for that. When preparing the piece for
publishing, add "lastupdated", "footer" (as mentioned above) and "tagline"
according to the license and footer. The only thing which changes is the content
of the files in the git repository.

The preprint archive arxiv.org does something similar: They add a watermark to
each preprint, but also offer the unmodif

Re: On the header parsing

Glen Larsen — 2012-12-16T20:04:42

Felix, some comments below. -gl

On Sun, Dec 16, 2012 at 3:29 AM, Felix Janda <felix.janda-1KBjaw7Xf1+zQB+pC5nmwQ< at >public.gmane.org> wrote:


I will agree that the lilypond grammar is complex but argue that elements
like the header are regular enough that they can be parsed easily. If only
lilypond had, in addition to the --header switch, a switch that would exit
after the parse phase; as you mentioned, it simply takes too long to get a
single header value. Except in pathological cases, the parsing can be
scripted in python easily enough.



I like the idea of a separate chunk of Mutopia header. The script would
have to continue scanning an entire file in the event an additional header
is at the bottom but it should do that anyway. Header keywords can also be
found within scores but typically that is just to specify the 'piece'
keyword.



I read this as a desire to have the above markup as both the footer and
tagline. If you are suggesting that the copyright statement be removed from
the PDF, then I don't ag