Re Yet another midi2ly - HELP (Antonio PALAMA')

There are two meta-events missing, Device Name and Program Name, that were defined in Recommended Practice (RP-019). They are: FF 09 len textDEVICE NAME FF 08 len text PROGRAM NAME Both are similar to the TEXT meta event in contruct. For details of their use see www.midi.org. The d

Re: [PATCH] Tablatures and beams

Ok, new patch coming: > Stems pointing upwards collide with the fret numbers. Fixed. This patch includes your suggestion (in define-grobs.scm) and a similar change (\override Stem...) in engraver-init.ly. I've tested this patch with different font-sizes (set-global-staff-size) and I can't find an

Re: [PATCH] Tablatures and beams

... and here's the patch :-) Erlend On Tue, 11 Jan 2005 01:51:52 +0100, Erlend Aasland <[EMAIL PROTECTED]> wrote: > Ok, new patch coming: > > > Stems pointing upwards collide with the fret numbers. > Fixed. > > This patch includes your suggestion (in define-grobs.scm) and a > similar change (\o

Re: Boxed rehersal marks

Well well, I need to test my patches better: format-mark-box-numbers need attached patch to produce correct result. Regards, Erlend Aasland On Tue, 4 Jan 2005 16:34:52 +0100, Erlend Aasland <[EMAIL PROTECTED]> wrote: > Hello > > I find myself using boxed rehersal marks all the time. Instead of

Re: [PATCH] Tablatures and beams

> > fret numbers on string. I've tried several font sizes and it seems to > > work perfect. > Good; but I'm not satisfied yet. Hmmm, me neither: Stems pointing upwards collide with the fret numbers. I've grepped around a bit and found the tablature-stem-attachment-function, but it does not help muc

Using \partcombine and \lyricsto

[EMAIL PROTECTED] writes: > Hi, list. I'm working on tweaking \partcombine so that it can be used > with \lyricsto for the purpose of typesetting hymns more easily. The Cool! > problem is that after \partcombine, the melody line (to which a lyric > should be set) may be split between three (mor

Re: [PATCH] Tablatures and beams

[EMAIL PROTECTED] writes: > Ok, I've made a new Y-offset-callback that seems to correctly place > fret numbers on string. I've tried several font sizes and it seems to > work perfect. Good; but I'm not satisfied yet. Your function is partially duplicating Staff_symbol_referencer::callback(), and d

Wikipedia-Test

Hi, I just installed a test wiki on http://132.187.3.68/wiki/index.php in which you can test the extension I wrote. I am sorry, the server is a little slow, but I hope that you can see how easy it is to embed notes in the wiki -- just hit 'edit' to view the source. Is there interest in this for

Re: how to make a lilypond fragment without any notes in it?

simply add a hide note : \begin{lilypond} { \key g \major s4 } \end{lilypond} and it would work. Regards, Aurèle Alex Hunsley wrote: I'm writing what the lilypond docs call a 'musicological' document - a latex doc with lilypond rendered items inside it. I'm using lilypond-book for this task (the

Using \partcombine and \lyricsto

Hi, list. I'm working on tweaking \partcombine so that it can be used with \lyricsto for the purpose of typesetting hymns more easily. The problem is that after \partcombine, the melody line (to which a lyric should be set) may be split between three (more?) separate voice contexts. Re-setting a

Re: override-auto-beam-settings

Hi Jan (and others), Thanks for your answer. > Ruud van Silfhout writes: > > > This is translated by convert-ly into > > \layout { \context { \Voice #(override-auto-beam-setting '(end * * * *) > > 1 4) } } > > for version 2.4.2. This looks quite reasonable to me > > It is, only this (a SCM ex

Re: [PATCH] Tablatures and beams

Ok, I've made a new Y-offset-callback that seems to correctly place fret numbers on string. I've tried several font sizes and it seems to work perfect. Perhaps we should have a pair of functions to ease choosing between printing on/above strings? Maybe \printFretNr{On|Above}Strings? Anyway, patch

Re: UTF8 and (La)TeX backend?

> BTW, is there an option to wrap the CFF as ASCII data? The binary > data not only confuses dvips, it also slows down emacs tremendously. Yes, this is possible. See below how it looks like -- it's a CID font, not a CFF, but you should get the idea. Details can be found in Adobe's 5001.DSC_Spe

Re: lilypond/Documentation/user examples.itely

I both agree and disagree! My main objections are: - I normally use a separate identifier for annotations like tempo changes ("Andante", ...) that should only appear on the top of the full score but in all the individual parts. Of course, such a thing can also be done with \tag commands, but