Error: Failed to parse ly2video line about ly2video HOT 6 OPEN

I suspect this is probably because ly2video doesn't expect the path to the .ly file to contain any : characters, but since you're on Windows, it begins with C:. This should be a simple fix - can you try changing the second line of these two in cli.py:

                     # file:line:char
                     '([^:]+): *(\d+):(\d+)'

to

                     # file:line:char
                     '(.+): *(\d+):(\d+)'

and then try again?

from ly2video.

I tried it but it still gives me the same error with the same values

Edit:

The problem occurs on the line i marked with * so I think the problem is with the file regex:

\include "dump-spacetime-info.ly"
\include "dump-spacetime-info.ly"
\version "2.16.0"
\paper {
   page-breaking = #ly:one-line-breaking
   top-margin    = 83\mm
   bottom-margin = 83\mm
   left-margin   = 46\mm
   right-margin  = 46\mm
}
#(set-global-staff-size 20)

\header {
   tagline = ##f composer = ##f
}

music = \new Voice {
  \relative c' {
    <a c e>1 q <f a c>2 q            ************************************************************************
  }
}

\score {
 \unfoldRepeats
  \music
  \layout { }
  \midi { }
}

from ly2video.

Did you reinstall the updated code with pip install after editing it?

from ly2video.

Yes, I tried that it didn't work but then I removed '$' in

# file:line:char
'(.+): *(\d+):(\d+)'
'$', line)

so the final version would be:

# file:line:char
'(.+): *(\d+):(\d+)'
,line)

after that, Timidity++ gave errors so I had to port it to fluidsynth instead, now it can generate sound and video for normal notation but i am getting errors when i try to use guitar tableture instead. I can close this issue and create a seperate issue for that if you prefer keeping things clean.

ERROR: Didn't find any notes; something must have gone wrong with the use of dump-spacetime-info.

from ly2video.

If the final $ was causing problems then I suspect it could be a Windows CR/LF line-ending issue. Perhaps changing to \r?$ would work?

Let's keep this open until we figure out exactly what the parsing issue was. And yes please, let's have separate issues filed for each issue found - thanks!

from ly2video.

@miifanboy This may be fixed in master now; please can you test?

from ly2video.