Step one complete but JEdit hangs on open at run startup
scripts, [V. 4.3pre17].
The same thing happened to me on Vista64, Java 1.6. The solution: when
you run the installer you are presented 4 options. One is to install
stuff necessary to create your own plugins, you can uncheck it, but
tweaking the positions of
every single object in the pdf directly. Köszi, Berci!
Best,
Imre Polik
2007/2/16 Mats Bengtsson mats.bengts...@ee.kth.se
The following seems to work:
\time 6/8
\set Timing.beatLength = #(ly:make-moment 3 8)
This should clearly be the default for 6/8 time signatures
My suggestion would be to use pdflatex with the pdfpages package. This
will enable you to include full pdf documents in your latex source
files. Anyway, the only difference between latex and pdflatex (at
least for the end-user) is that one creates pdf the other dvi.
We use it regularly to create
I had the same problem a few days ago in 6/8: consecutive 16th notes
connected only by a single beam. Is there a way to force Lilypond to
connect those with a double beam (assuming they are beamed together at
all)? Or this is simply a bug?
Imre
--
McMaster University
Advanced Optimization Lab
I think that this error propagation effect of the relative notation is
actually beneficial, it makes it much easier to catch a note in the
wrong octave. If you suddenly you get a lot of ledger lines, you see
where the problem starts. And it uses the fewest possible keystrokes.
Imre
--
McMaster
email to bug-lilypond as well. Here's a complete example for the
bug report:
\version 2.11.18
\relative c' {
\time 6/8
c8. d16 e f c8. d16 e f |
\set Timing.beatLength = #(ly:make-moment 3 8)
c8. d16 e f c8. d16 e f |
}
/Mats
Imre Polik wrote:
Hi,
I started using lilypond some weeks ago
Hi,
I started using lilypond some weeks ago, the results look great so
far, but by now I have accumulated a few questions. I'll post them one
by one.
Take a look at the following snippet:
\version 2.10.7
\score {\time 6/8 \relative c' {c8. d16 e f | #(set-time-signature
12 16 '(3 3 3 3)) c8.
From the WinEdt help:
WinEdt is an ASCII and not a UNICODE application.
That's your problem. (My problem too, I've been using Winedt for LaTeX
for over 5 years now.) Try jEdit with the Lily plugin, it is clearly
better than Winedt. (Maybe also for TeX?)
Hope this helps,
Imre