Deutsch  English  Français  中文 

Logging in is required for posting.

Special forum features: inserting music notation, posting audio recordings.

All Categories > Musipedia > Musipedia General > lilypond code errors
Total Posts: 1 - Pages (1): [1]
follow Author: a1s2d3f4
Posted: May 31 2013 - 05:44 PM
Subject: lilypond code errors
Hi, I used a notation program to enter the piece I wanted to add to the database, then had it exported as a MIDI file, then I used on my Windows machine to convert it to .ly. Then I rendered .ly to make sure I got a working PDF out of it, then I tried to paste it into the page on this site where I can add new music by pasting in lilypond code. I got a whole bunch of errors, which I can paste here, if it helps.

Code I pasted in

% Lily was here -- automatically converted by C:\Program Files\LilyPond\usr\bin\ from C:\temp\TheShowMustGoOn.mid
\version "2.7.18"

trackAchannelA =  {
  % [COPYRIGHT_NOTICE] Copyright ©
  \time 4/4

  \key b \minor
  \skip 2.
  \tempo 4 = 100

trackA = <<
  \context Voice = channelA \trackAchannelA

trackBchannelA = \relative c {
  d'8 d8 |
  % 2
  cis8 d2 d8 d8 cis8 |
  % 3
  cis4 b8 b4 r16 d16 d8 d8 |
  % 4
  cis8 d2 r8 d8 e8 |
  % 5
  fis4 g8 e2 r8 |
  % 6
  fis4 g8 e2 r16 e16 |
  % 7
  fis16 g16 fis16 g16 fis4. e8 d8 cis8 |
  % 8
  cis16 b8 b2 d16 d8 d8 |
  % 9
  cis8 d4. r8 d8 d8 cis8 |
  % 10
  cis4 b8 b4 r8 d16 d8 d16 |
  % 11
  cis8 d2 r8 d8 e8 |
  % 12
  fis4 g8 e4. r4 |
  % 13
  a4. g8 fis8 e4 r16 e16 |
  % 14
  fis16 g16 fis16 g16 fis4 r8 e8 d8 cis8 |
  % 15
  cis16 b8 b4. r16 b'8 b8 b8 |
  % 16
  b8. a16 fis4

trackB = <<
  \context Voice = channelA \trackBchannelA

\score {
    \context Staff=trackBChannelA \trackB

Output from the website:


Something went wrong...
Lilypond's output:

Processing `'
error: Incorrect lilypond version: 2.7.18 (2.7.38, 2.10.33)
error: Consider updating the input with the convert-ly script error: syntax error, unexpected \invalid
         "2.7.18" error: syntax error, unexpected STRING

trackA = << error: unknown escaped string: `\trackAchannelA'
  \context Voice = channelA
                            \trackAchannelA error: syntax error, unexpected STRING
  \context Voice = channelA
                            \trackAchannelA error: syntax error, unexpected STRING

trackB = << error: unknown escaped string: `\trackBchannelA'
  \context Voice = channelA
                            \trackBchannelA error: syntax error, unexpected STRING
  \context Voice = channelA
                            \trackBchannelA error: unknown escaped string: `\trackB'
    \context Staff=trackBChannelA
                                  \trackB error: syntax error, unexpected STRING
    \context Staff=trackBChannelA
                                  \trackB error: errors found, ignoring music expression
\score {

Could someone tell me what's wrong with this code, please?
Total Posts: 1 - Pages (1): [1]
You must login to post a message to this conference.

How to insert music:

Add a bit of sheet music, along with a MIDI file, simply by entering note names in Lilypond syntax between the [L] and [/L] tags.
For example, you can try what happens if you enter: [l]g'4 g'4 d''4 d''4 e''4 e''4 d''2[/l] (use the Preview function if you don't actually want to post this).
You can create these lists of note names by clicking on piano keys here.

How to post an audio recording:

If you just want to sing, whistle, or play a melody so that other forum visitors can hear it, follow these steps:

  1. Record your audio here.
  2. You should notice a 32-character hash code, something like: 2a40281c5001c5a7d8c9f57fcdeccfaf
  3. copy this hash code and paste it into a forum post, enclosed in the audio tags, for example: [audio]2a40281c5001c5a7d8c9f57fcdeccfaf[/audio]

How to mark a thread as solved:

If the original question in a thread is solved, please mark it as solved using the "solved" icon (or by just typing [solved] into your post). This makes life easier for people who are willing to identify melodies, since unsolved problems are easier to spot that way. If a problem turns out to not be solved after all, just write [/solved] in a new post, and the thread will be labeled accordingly.