I was looking for a good textual notation system to use and soon found
Lilypond.
I wonder, are there tools for converting Lilypond format to Csound scores?


Richard



--
View this message in context: http://csound.1045644.n5.nabble.com/Lilypond-ponderings-tp5734825.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thanks. I was thinking of using the format in my own Python based Csound
GUI's, so maybe I'll write something myself to do that.

BTW, as I understand it, 'c4' can be interpreted as a quarter c note, or the
fourth octave, depending on the context, am I correct? 

Richard



--
View this message in context: http://csound.1045644.n5.nabble.com/Lilypond-ponderings-tp5734825p5734828.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thanks Michael, I am looking at CsoundAC again.
Trying the csoundac-tutorial-1.py (after correcting the path to the csd
file), I get:

Generated 200 events.
addToScore.length(): 838
BEGAN CppSound::perform(18, 0x7fcdca931610)...
BEGAN CppSound::compile(18, 0x7fcdca931610)...
Parsing failed due to 0 semantic errors!
WARNING: Stopping on parser failure

Any clues? Or could it be caused by the soundfont files that are referenced
in the csd?

Richard




--
View this message in context: http://csound.1045644.n5.nabble.com/Lilypond-ponderings-tp5734825p5734833.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

This is Csound 6.02.0 on OS X 10.9.2



--
View this message in context: http://csound.1045644.n5.nabble.com/Lilypond-ponderings-tp5734825p5734842.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

el 2014-04-30 a las 03:13 zappfinger escribió:

> BTW, as I understand it, 'c4' can be interpreted as a quarter c note, or
> the fourth octave, depending on the context, am I correct? 

no, i'm afraid that's not correct. 

c4 means it's a c quarter note. that is, the numbers always mean the note
value or duration: 1 = whole note, 2 = half note, 4 = quarter note, 8 =
eight note, etc.

what depends on the context is the octave.

in absolute octave entry, c is the octave below middle C.
each single quote (') added to a note raises it an octave, and each added
comma (,) lowers it an octave. 

c' is therefore middle C, c'' the octave above middle C, etc. 
c, is two octaves below middle C, etc.

in relative mode, c without a comma or quote is the closest c to the
previous note (in interval type, not size).

but you can read the proper explanation here:

http://lilypond.org/doc/v2.18/Documentation/notation/writing-pitches

using absolute or relative octave entry is a matter of personal
preference, of course. 


Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thanks for the explanation, Luis.
I already found it a bit strange if c4 could mean two things...
BTW, I think it would be fairly easy to make a basic (Python) parser that
translates Lilypond style text to Csound score. After all, a lot of Lilypond
commands have to do with graphical representation.
I am thinking of adding also a rhythm & loudness tag, that could be applied
to chords or notes, like this:
\rhythtl{ ff4 f mf mp }, meaning the first note has a loudness of ff, the
second of f, etc.
'Multplying' this with a normal score, like {1} could give
interesting rhythmic patterns...

Richard 



--
View this message in context: http://csound.1045644.n5.nabble.com/Lilypond-ponderings-tp5734825p5734851.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

el 2014-05-01 a las 01:29 zappfinger escribió:

> BTW, I think it would be fairly easy to make a basic (Python) parser that
> translates Lilypond style text to Csound score.

there's a consensus that converting lilypond code (to csound or anything
else) is an intractable problem. maybe not in theory, but in practice it
certainly is (see michael's post on this). 

the only way i see is using the event-listener. this will save the list of
events in plain text format:

http://lilypond.org/doc/v2.18/Documentation/notation/saving-music-events-to-a-file

the output is fairly easy to parse. unfortunately, not all lilypond music
events are supported by event-listener.ly. two years ago i started a
thread in the lilypond mailing list about this subject:

http://web.archiveorange.com/archive/v/nRTVVayRlCUzdu7AJ39k

i think it would be great if someone with the necessary skills in scheme
(or ready, willing and able to learn) could expand event-listener.ly to
make it more comprehensive. writing a python script to convert its output
to csound score format would not only be easy, but also fun...


best,


lj


Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"