Re: \hideNotes in TabStaff (was: Re: Temporary polyphonic passages inTabStaff)
Trevor Daniels schrieb: Oscar van Eijk wrote Wednesday, January 27, 2010 1:39 PM Another one though; also in the original sample you might have seen I use \hideNotes. Thet doesn't seem to have any affect in the TabStaff. As a workaround I made set the transparent property of TabNoteHead to ##t. Is this a known issue or were my expectations incorrect? \hideNotes and \unHideNotes are designed to work only with ordinary staves and voices. In TabStaff they will hide stems, beams, dots, etc (if these are being displayed) but not the fret labels from TabNoteHead. Maybe they should, or are there situations where you would want to hide notes in the normal staff but not in TabStaff or vice versa? I have not used \hideNotes very often, but as we want to use the input both for normal staves and tablature staves without tweaking too much, I think it would make sense to include the functionality into \hideNotes, but it seems that this would not be straightforward, as, for example, \revert Stem #'transparent would make the tablature stems visible, too. Marc Setting the transparent property will work fine, but you may find the underlying staff lines are whited out in releases after 2.13.6 or thereabouts unless you also set the whiteout property of TabNoteHead to #f. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \hideNotes in TabStaff
Federico Bruni schrieb:
Il giorno Wed, 27 Jan 2010 14:39:40 +0100
Oscar van Eijk oscar.van.e...@oveas.com ha scritto:
Another one though; also in the original sample you might have seen I
use \hideNotes. Thet doesn't seem to have any affect in the TabStaff.
As a workaround I made set the transparent property of TabNoteHead to
##t. Is this a known issue or were my expectations incorrect?
If you want to hide notes both in Staff and in TabStaff you can use
this command (maybe the name is not so appropriate, choose what you
prefer):
hideFretNumber = {
\once \override TabNoteHead #'transparent = ##t
\once \override TabNoteHead #'whiteout = ##f
\once \override NoteHead #'transparent = ##t
\once \override Stem #'transparent = ##t
\once \override NoteHead #'no-ledgers = ##t
\once \override Accidental #'transparent = ##t
}
In the tablature mailing list they are discussing the idea of adding
such a command:
hideTabNoteHead = {
\once \override TabNoteHead #'transparent = ##t
\once \override TabNoteHead #'whiteout = ##f
}
http://n2.nabble.com/Re-tie-bug-in-2-13-10-td4291079.html#a4291079
Marc (or Carl), can you make a summary of what's happening?
We discussed this idea, and for now, it is best to include this definition
in the file concerned (or to define a common file ready for inclusion) on
the user's side.
Marc
Thanks,
Federico
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond as MediaWiki extension does not print in Extension:Collection
2010/1/27 Oscar van Dillen oscarvandil...@gmail.com: on my website I found that Lilypond as MediaWiki extension does not print music notation, just code, to the pdf in Extension:Collection http://www.mediawiki.org/wiki/Extension:Collection Lilypond does work fine when using printable version such as can be seen here http://www.oscarvandillen.com/Triad?printable=yes should I rather tell the collection programmers at http://www.mediawiki.org/wiki/Extension:Collection/Wishlist Yes, please. If that extension shows only the LilyPond source code of snippets but the normal page view and the printable view show these snippets processed and converted to PNG, it surely means that LilyPond is not called to process these snippets from Extension:Collection. By the way, for a decent printing quality, the PDF generation should not be left to the user browser but should be done on the server side (using PDF snippets generated by LilyPond), like what openstreetmap.org does. This regards standard printable view as well as the extension Collection. Best, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: evince and textedit
Op dinsdag 26 januari 2010 schreef Federico:
Hi,
I'm trying to adapt the configuration explained here:
http://lists.gnu.org/archive/html/lilypond-user/2007-06/msg00185.html
I'd like to set Frescobaldi as editor, so I've changed the line in the
script as follows (I've copied from the preferences of Okular, where
this works):
frescobaldi --smart --line %l --column %c
but it launches Frescobaldi with an empty file.
If I use this line instead:
frescobaldi ${LINENUM}:${STARTPOS} ${FILENAME}
it launches Frescobaldi, opens the right file (but it does not point
to a specific note (just the beginning of the file)
plus a strange second file which can't be read and looks empty.
As others already pointed out, you have to insert the variables on the correct
spot on the Frescobaldi command line:
frescobaldi --smart --line ${LINENUM} --column ${STARTPOS} ${FILENAME}
will work. The option --smart tells Frescobaldi to translate cursor positions
automatically when you edit the document without running LilyPond again.
(The Okular setting did not need the filename, because it's appended
automagically by Okular.)
If I try this, Frescobaldi opens and crashes:
frescobaldi --smart --line %l --column %c +${LINENUM}:${STARTPOS}
${FILENAME}
Thanks for telling this :-) It's not a real crash, but Python exiting with an
error message about invalid integer literal (happened when line or column
arguments are not numbers). I changed Frescobaldi to ignore invalid
line/column arguments and just start up normally.
best regards,
Wilbert Berendsen
--
Frescobaldi, LilyPond editor for KDE: http://www.frescobaldi.org/
Nederlands LilyPond forum: http://www.lilypondforum.nl/
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond as MediaWiki extension does not print in Extension:Collection
On Thu, Jan 28, 2010 at 1:26 PM, John Mandereau john.mander...@gmail.comwrote: 2010/1/27 Oscar van Dillen oscarvandil...@gmail.com: on my website I found that Lilypond as MediaWiki extension does not print music notation, just code, to the pdf in Extension:Collection http://www.mediawiki.org/wiki/Extension:Collection Lilypond does work fine when using printable version such as can be seen here http://www.oscarvandillen.com/Triad?printable=yes should I rather tell the collection programmers at http://www.mediawiki.org/wiki/Extension:Collection/Wishlist Yes, please. If that extension shows only the LilyPond source code of snippets but the normal page view and the printable view show these snippets processed and converted to PNG, it surely means that LilyPond is not called to process these snippets from Extension:Collection. By the way, for a decent printing quality, the PDF generation should not be left to the user browser but should be done on the server side (using PDF snippets generated by LilyPond), like what openstreetmap.org does. This regards standard printable view as well as the extension Collection. Best, John thank you very much! with the help of your analysis, i now filed a bug to this collection, hoping it will be fixed in the near future. it is here http://code.pediapress.com/wiki/ticket/775 very best, oscar -- oscarvandil...@gmail.com www.oscarvandillen.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.13.11-1: Y-offset for RehearsalMark?
У нд, 2010-01-24 у 18:27 +0100, Alexander Kobel пише:
Hi, Dmytro,
correct me if I'm wrong, but this looks like the A is actually higher
than the other two, and has it's baseline exactly 1 staff-space unit
above the top staff-line. So I guess the Y-offset is calculated w.r.t.
the center staff line in 2.13 (Joe: is this a bug?), and you probably
have to increase the values by 2.
For what you actually wanted, I recommend you use
'outside-staff-padding, though.
Well, it's a pity, i can not use 'outside-staff-padding for what i
actually wanted so far :-)
When Lyrics is above Staff then 2.13.11 raises both \tempo and \mark
too high, and i need some way to drop them down.
First, short snippet (some lines are commented out, i will turn them on
later, to demonstrate what i really want):
% --8-
%
% Both MetronomeMark and RehearsalMark
% are parts of Score context (accordingly to the doc)
%
melody = \relative c'' {
% A:
% \override Score.MetronomeMark #'outside-staff-padding = #-2
% B:
% \override Score.MetronomeMark #'Y-offset = #-2
\tempo Tempo I
c c c c
% C:
% \override Score.RehearsalMark #'outside-staff-padding = #-2
% D:
% \override Score.RehearsalMark #'Y-offset = #-2
\mark\default
c c c c
c' c c c
}
lyric = \lyricmode {
\repeat unfold 6 { _ }
\repeat unfold 6 { la }
}
\new Staff = staff { \new Voice = melody { \melody } }
\new Lyrics \with { alignAboveContext = staff } \lyricsto melody \lyric
% --8-
Sorry, four images follow :-(13.3kB) total
So, lilypond 2.12 places tempo and mark correctly (in quotes, because
i don't know really what is correctly everything from my point
of view of course), while lilypond 2.13.11 raises both tempo and mark
_because of lyrics_, placing baseline nearly in the middle of lyrics'
height, the result is on the image named marks--none.png.
Not a problem, i used to use negative 'Y-offset to drop'em down... let's
try both ways...
First of all, i've uncommented lines A and C to set
'outside-staff-padding to some negative value (-2) --- no effect, at all
(marks--padding.png).
Then i've commented them out and uncommented lines B and D to set
'Y-offset to some negative value (-2) --- great! partial success ---
i have mark dropped down but it has no effect on tempo
(marks--offset.png).
Finally i have achieved good enough result uncommenting _both A and B
for tempo_ (marks--good-enough.png) --- so having three overrides (A, B
and D) uncommented.
So... I guess it's rather subnormal :-)
So, what is _the proper way_ to drop down marks (MetronomeMark and
RehearsalMark)?
Not both by the same command, but both by a single command would be
great.
Cheers,
Alexander
--
Dmytro O. Redchuk
attachment: marks--none.pngattachment: marks--padding.pngattachment: marks--offset.pngattachment: marks--good-enough.png___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond as MediaWiki extension does not print in Extension:Collection
On Thu, Jan 28, 2010 at 3:11 PM, Oscar van Dillen oscarvandil...@gmail.comwrote: On Thu, Jan 28, 2010 at 1:26 PM, John Mandereau john.mander...@gmail.comwrote: 2010/1/27 Oscar van Dillen oscarvandil...@gmail.com: on my website I found that Lilypond as MediaWiki extension does not print music notation, just code, to the pdf in Extension:Collection http://www.mediawiki.org/wiki/Extension:Collection Lilypond does work fine when using printable version such as can be seen here http://www.oscarvandillen.com/Triad?printable=yes should I rather tell the collection programmers at http://www.mediawiki.org/wiki/Extension:Collection/Wishlist Yes, please. If that extension shows only the LilyPond source code of snippets but the normal page view and the printable view show these snippets processed and converted to PNG, it surely means that LilyPond is not called to process these snippets from Extension:Collection. By the way, for a decent printing quality, the PDF generation should not be left to the user browser but should be done on the server side (using PDF snippets generated by LilyPond), like what openstreetmap.org does. This regards standard printable view as well as the extension Collection. Best, John thank you very much! with the help of your analysis, i now filed a bug to this collection, hoping it will be fixed in the near future. it is here http://code.pediapress.com/wiki/ticket/775 very best, oscar -- oscarvandil...@gmail.com www.oscarvandillen.com hmm, as it turns out, pediapress refuses to fix this, the reasons given are: You can install and use this extension in your wiki, but it is currently not available in Wikipedia. Many people would love to use this extension in Wikipedia and other large-footprint wikis that they have no control over. However, in its current form, this is unfortunately impossible due to security concerns. This extension is using Lilypond's safe mode, which according to the documentation does not detect resource overuse. It is still possible to make the program hang indefinitely, for example by feeding cyclic data structures into the backend. Therefore, if using LilyPond on a publicly accessible webserver, the process should be limited in both CPU and memory usage. This extension is therefore not used in Wikipedia because it is considered a hazardous denial-of-service vector. is this correct, that lilypond has this security issue as stated; and is it possible to make the program hang indefinitely? thanks in advance and all the best, oscar -- oscarvandil...@gmail.com www.oscarvandillen.com ** The information contained in this message is confidential and may be legally privileged. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, dissemination, or reproduction is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. Although this message and any attachments are believed to be free of viruses, no responsibility can be accepted for any loss or damage arising in any way from receipt or use thereof. ** ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond as MediaWiki extension does not print in Extension:Collection
Hi Oscar,
is this correct, that lilypond has this security issue as stated;
I'm no security expert, but this issue has been discussed at length several
times on the Lilypond lists (-user and -dev), so check the archives.
and is it possible to make the program hang indefinitely?
Probably... what about
\repeat unfold 1000 { \repeat unfold 1000 { \repeat unfold
1000 { \repeat unfold 1000 { c128 } } } }
Worse, of course, is to write in a Scheme function -- which Lilypond would of
course attempt to execute -- which simply calculated pi to infinite precision.
=)
Cheers,
Kieren
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.13.11-1: Y-offset for RehearsalMark?
Dmytro O. Redchuk wrote: So, what is _the proper way_ to drop down marks (MetronomeMark and RehearsalMark)? Not both by the same command, but both by a single command would be great. Just an idea (untested): Have you tried to remove Mark_engraver and Metronome_mark_engraver from the Score context and place them into the topmost Staff context? Then, 'outside-staff-padding should not push them above the Lyrics, IIRC. Cheers, Alexander ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.13.11-1: Y-offset for RehearsalMark?
У чт, 2010-01-28 у 15:55 +0100, Alexander Kobel пише:
Dmytro O. Redchuk wrote:
So, what is _the proper way_ to drop down marks (MetronomeMark and
RehearsalMark)?
Not both by the same command, but both by a single command would be
great.
Just an idea (untested): Have you tried to remove Mark_engraver and
Metronome_mark_engraver from the Score context and place them into the
topmost Staff context? Then, 'outside-staff-padding should not push
them above the Lyrics, IIRC.
Yes, thank You.
% -8---
\layout {
\context {
\Score
\remove Metronome_mark_engraver
\remove Mark_engraver
}
\context {
\Staff
\consists Metronome_mark_engraver
\consists Mark_engraver
}
}
% -8---
With this section both marks are places right above the staff. And i can
move them up with 'outside-staff-padding, and setting it to 2 already
moves them (so, 2 is measured not from the middle line?..).
But, anyway, in this example i'm using only one Staff, so this means
that *in any case* (regardless one-staff or multi-stave system) i need
to remove and re-attach those engravers to get 'outside-staff-padding
working for marks --- really?
I believe i've missed something again :-)
Well, since it is 'outside-*staff*-padding, it is related to Staff,
obviously. It's normal.
If i wish to have every staff having its own separate metronome marks
--- something strange, probably,-) ---i need to use two commands to move
them vertically. If i wish to have every staff having its own
RehearsalMarks --- i need to use 'Y-offset.
Looks like that.
Thank You :-)
If You have any other ideas regarding this issue --- please, let me
know :-)
ps. I believe Metronome_mark_engraver should really be in a Score
context and should be movable with either 'outside-staff-padding or
'Y-offset, but not both. So i must be still missing something.
Cheers,
Alexander
--
Dmytro O. Redchuk
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.13.11-1: Y-offset for RehearsalMark?
Hi Dmytro, ps. I believe Metronome_mark_engraver should really be in a Score context and should be movable with either 'outside-staff-padding or 'Y-offset, but not both. So i must be still missing something. If you turn off collision detection for MetronomeMarks, wouldn't that solve the problem? Just a thought-experiment. Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond as MediaWiki extension does not print in Extension:Collection
Le jeudi 28 janvier 2010 à 15:48 +0100, Oscar van Dillen a écrit : You can install and use this extension in your wiki, but it is currently not available in Wikipedia. Many people would love to use this extension in Wikipedia and other large-footprint wikis that they have no control over. However, in its current form, this is unfortunately impossible due to security concerns. This is not a reason not to support LilyPond processing as a option that is switchable by a configuration file accessible only to the website administrator, which would be disabled by default. is this correct, that lilypond has this security issue as stated; and is it possible to make the program hang indefinitely? Adding to Kieren's example, think that LilyPond user interface is a programming language, so it is hard to avoid these problems, that's the workaround that consists of limiting CPU and memory usage is recommended. Even with normal use of such an extension, you need much CPU power and free memory, which is surely not available on many servers running MediaWiki. Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.13.11-1: Y-offset for RehearsalMark?
У чт, 2010-01-28 у 10:19 -0500, Kieren MacMillan пише: Hi Dmytro, ps. I believe Metronome_mark_engraver should really be in a Score context and should be movable with either 'outside-staff-padding or 'Y-offset, but not both. So i must be still missing something. If you turn off collision detection for MetronomeMarks, wouldn't that solve the problem? Just a thought-experiment. Well.. Thanks. This takes some time :) I'll ask google. Kieren. -- Dmytro O. Redchuk ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.13.11-1: Y-offset for RehearsalMark?
Dmytro O. Redchuk wrote: But, anyway, in this example i'm using only one Staff, so this means that *in any case* (regardless one-staff or multi-stave system) i need to remove and re-attach those engravers to get 'outside-staff-padding working for marks --- really? From the viewpoint of vertical spacing, I guess the lyrics are considered as a second staff. So I'm afraid I think the answer is yes. Well, since it is 'outside-*staff*-padding, it is related to Staff, obviously. It's normal. If i wish to have every staff having its own separate metronome marks --- something strange, probably,-) ---i need to use two commands to move them vertically. If i wish to have every staff having its own RehearsalMarks --- i need to use 'Y-offset. Well, I'm not quite sure of this one. 'outside-staff-padding should already be enough. Did you test this? (I didn't, to be honest.) If I understand you correctly, you're confusing staff and system. By default, the Mark_engraver sits in the Score context, which contains elements and settings common for all objects inside a system. By default, Marks are only printed once, so they're naturally placed there, and printed on top of _all_ staves in the system (by staves, I also mean lyrics, chords, ... - essentially all contexts that can be contained in a score). AFAIU, if you add the Mark_engraver to a staff, 'outside-staff-padding should only be applied to the very staff the engraver is attached to. HTH, Alexander ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.13.11-1: Y-offset for RehearsalMark?
У чт, 2010-01-28 у 16:54 +0100, Alexander Kobel пише: Dmytro O. Redchuk wrote: But, anyway, in this example i'm using only one Staff, so this means that *in any case* (regardless one-staff or multi-stave system) i need to remove and re-attach those engravers to get 'outside-staff-padding working for marks --- really? From the viewpoint of vertical spacing, I guess the lyrics are considered as a second staff. So I'm afraid I think the answer is yes. Yes, i see. If i wish to have every staff having its own separate metronome marks --- something strange, probably,-) ---i need to use two commands to move them vertically. If i wish to have every staff having its own RehearsalMarks --- i need to use 'Y-offset. Well, I'm not quite sure of this one. 'outside-staff-padding should already be enough. Did you test this? (I didn't, to be honest.) What exactly? If i move engraver to Staff context, yes, 'outside-staff-padding is enough, i can move marks up and down. If I understand you correctly, you're confusing staff and system. By default, the Mark_engraver sits in the Score context, which contains elements and settings common for all objects inside a system. By default, Marks are only printed once, so they're naturally placed there, and printed on top of _all_ staves in the system (by staves, I also mean lyrics, chords, ... - essentially all contexts that can be contained in a score). AFAIU, if you add the Mark_engraver to a staff, 'outside-staff-padding should only be applied to the very staff the engraver is attached to. Yes, it's clear, thanks. I, probably, should say: by default Mark_engraver is attached to Score and 'Y-offset works nice (for RehearsalMarks, for now, the future is unclear), while 'outside-staff-padding does not work --- to get it working i need to re-attach Mark_engraver to Staff. So, my offsets should be increased by two :-) Thank You! HTH, Alexander -- Dmytro O. Redchuk ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.13.11-1: Y-offset for RehearsalMark?
У чт, 2010-01-28 у 18:06 +0200, Dmytro O. Redchuk пише: Yes, it's clear, thanks. I, probably, should say: by default Mark_engraver is attached to Score and 'Y-offset works nice (for RehearsalMarks, for now, the future is unclear), while 'outside-staff-padding does not work --- to get it working i need to re-attach Mark_engraver to Staff. ... while MetronomeMarks can be moved by overriding *both* 'Y-offset and 'outside-staff-padding. (By default --- and this is normal --- they're attached to Score.) This (moving with two overrides) is, anyway, looks strange?-) I am optimistic --- i still believe i've missed something :-) Will dig... tomorrow, i hope. -- Dmytro O. Redchuk ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
slashed note heads for chords
Hi all,
is it possible to use slashed note heads for chords to indicate the rhythm of a
strumming pattern? This is what I have tried so far:
\version 2.13.10
chordsI = \chordmode {c1 }
chordsII = { c e g c e1 }
\relative c' {
\new Voice \with {\consists Pitch_squash_engraver }
{
\chordsI
\chordsII
\improvisationOn
\chordsI
\chordsII
\improvisationOff
\override NoteHead #'style = #'slash
\chordsI
\chordsII
}
}
In the resulting pdf all slashed notes are doubled (or – not surprisingly – all
note heads of a chord are slashed). I found a hint in the mail archive that
\improvisationOn expects single notes
(http://www.mail-archive.com/lilypond-user@gnu.org/msg50248.html). If
\improvisationOn accepted chords, strumming patterns could be achieved very
easily using \chordmode. The only solution I can think of right now is to use
(additional) single notes after \improvisationOn. But then I would have to
manually turn all the single notes into chords again if I wanted to engrave
normal note heads instead of slashed note heads in a different edition. Is
there a workaround for this problem?
Thanks for your help!
patrick
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
[lilypond-book] link to midi files, automagically
I'm trying to help a guy in a forum.
He would like to be able to click on a music fragment and listen to the
midi file.
So far I've been able to create just a text link to midi ex post, i.e.
after running lilypond-book and seeing where the file is and which
weird name it has.
I use the hyperref package and something like this:
\href{run:path/to/file.midi}{listen to the music!}
If the book has few fragments this workflow is feasible.
But if you have a hunderd of fragments, it becomes an hassle.
So there's any way to track these midi files easier?
Second, and less important, question.
I'd like the music fragment itself to be clickable (instead of a text).
How can I achieve that?
Thanks for your help!
Federico
--
http://gnurag.net/blog/
http://fsfe.org/
http://groups.fsf.org/wiki/LibrePlanetItalia
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond as MediaWiki extension does not print in Extension:Collection
2010/1/28 John Mandereau john.mander...@gmail.com Le jeudi 28 janvier 2010 à 15:48 +0100, Oscar van Dillen a écrit : You can install and use this extension in your wiki, but it is currently not available in Wikipedia. Many people would love to use this extension in Wikipedia and other large-footprint wikis that they have no control over. However, in its current form, this is unfortunately impossible due to security concerns. This is not a reason not to support LilyPond processing as a option that is switchable by a configuration file accessible only to the website administrator, which would be disabled by default. is this correct, that lilypond has this security issue as stated; and is it possible to make the program hang indefinitely? Adding to Kieren's example, think that LilyPond user interface is a programming language, so it is hard to avoid these problems, that's the workaround that consists of limiting CPU and memory usage is recommended. Even with normal use of such an extension, you need much CPU power and free memory, which is surely not available on many servers running MediaWiki. Best, John thank you kieren and john, things have become much more clear to me after this thread so far. i will ponder on how to perhaps make it run a bit more safely on my website, and keep on using it, as lilypond is relatively userfriendly, very powerful, and essential there :-) fyi to the pediapress people i wrote, to conclude ticket #775 i mentioned earlier: still, in my humble opinion, not including lilypond in the pdf rendering extension:collection is a missed chance for pediapress as well, since to me it seems to concern its field of business, and a possible venture into a whole new field: open source music printing. but i will not push the issue further at this point (and leave this ticket closed). i think however pediapress is missing out on an opportunity, but this is also a matter of choices of priority, and we may vary in this of course. i personally believe it would be more than worth the efforts to tackle this all the best, oscar -- oscarvandil...@gmail.com www.oscarvandillen.com ** The information contained in this message is confidential and may be legally privileged. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, dissemination, or reproduction is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. Although this message and any attachments are believed to be free of viruses, no responsibility can be accepted for any loss or damage arising in any way from receipt or use thereof. ** ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
\partcombine and positioning of soloText, soloIIText and aDueText
Anyone know how to tweak/adjust the positioning of the 3 text values associated with \partcombine? Specifically, I'd like to have an override at the beginning of my musical expression that puts soloIIText below the staff while leaving soloText above the staff. Thanks, Randy -- View this message in context: http://old.nabble.com/%5Cpartcombine-and-positioning-of-soloText%2C-soloIIText-and-aDueText-tp27366742p27366742.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Second tempo mark in a full score
I'm using LilyPond 2.12.3 to compile a work for orchestra, and would like to have the tempo indications in the full score show up both above the flutes and above the first violins. Using the \tempo command, LilyPond automatically places the indication only above the flutes. I've looked through the layout object section of the Backend in the Internals Reference, but nothing there seems applicable. Can someone point me in the right direction to solving this? Thanks! Nick Baskin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Second tempo mark in a full score
See section 1.8.1, Writing Text, in the Selected Snippets section under Printing marks on every staff. You don't have to use every staff, you can pick and choose which ones you want. On 29.01.2010, at 04:34, Nick Baskin wrote: I'm using LilyPond 2.12.3 to compile a work for orchestra, and would like to have the tempo indications in the full score show up both above the flutes and above the first violins. Using the \tempo command, LilyPond automatically places the indication only above the flutes. I've looked through the layout object section of the Backend in the Internals Reference, but nothing there seems applicable. Can someone point me in the right direction to solving this? Thanks! Nick Baskin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
