Re: modular markup and arguments
On 11/07/2013 12:31 AM, Paul Morris wrote: Bric wrote So, can one throw in conditionals? (1) Can one, for instance, check/manifest the pitch and duration of '#the-music' ? And based on those values are, write something or not? (2) And how DOES one write something extra? For example, add a note, or add a \markup (again, conditionally, perhaps). I tried adding variants of the following... Check out these snippets: http://lsr.dsi.unimi.it/LSR/Item?id=82 http://lsr.dsi.unimi.it/LSR/Item?id=83 They show examples of how to add things to the music (on the input side) using scheme. Doing it conditionally would then be the next step. (3) Is #the-music an object, with properties and stuff, and how does one access/modify those properties? This should help with this: http://lilypond.org/doc/v2.16/Documentation/extending/displaying-music-expressions OK. I've read through the above. I haven't done much with adding things to the music on the input side like you are wanting. I have mostly customized what's output by conditionally modifying grob properties. These are two different sides or angles... For example, NoteHead.color is a grob property and you could conditionally change it based on a note's pitch using scheme, for example: http://lsr.dsi.unimi.it/LSR/Item?id=572 I have SOME understanding of the advanced snippet code The other two you referred to seem to be vital to my quest - http://lsr.dsi.unimi.it/LSR/Item?id=82 http://lsr.dsi.unimi.it/LSR/Item?id=83 Development is moving insanely fast here. I just compiled 2.17.29, and there's already 2.17.95 I guess I need to build the latest frescobaldi, locally(?), so it's in step with the latest lilypond? Some feedback on the snippet database: It has a sort by date option, but the dates are not showing. I think it would be of some benefit to manifest the dates. Also, to juxtapose the code and its rendered result, on the same page, would also be good (save a lot of time, in the long run) So, obviously, just to add a ^markup to the music function is not trivial. I'm gathering that (text) markup belongs to an event function, rather than a music function, and the two can't be integrated ... although, that doesn't sound likely, off the top of my head, given the power and flexibility of this environment. I have lots of other reflections but will post this for now. thanks! ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: modular markup and arguments
Am 07.11.2013 11:19, schrieb Bric: Development is moving insanely fast here. I just compiled 2.17.29, and there's already 2.17.95 That's simply because 2.17.95 is regarded as a beta for the upcoming 2.18 release, and they are counting towards 100 ... I guess I need to build the latest frescobaldi, locally(?), so it's in step with the latest lilypond? No. Frescobaldi just _uses_ LilyPond. If you have set up to run LilyPond simply by 'lilypond' you can just use Frescobaldi to compile your score. But you can also set up Frescobaldi to use different versions of LilyPond (in the Preferences Dialog). Using the latest Frescobaldi from its Git source is generally not a bad idea (if you know that you are using a development version. OTOH _if_ you are using it from Git you can always checkout the latest stable version). HTH Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: modular markup and arguments
Bric b...@flight.us writes: Development is moving insanely fast here. I just compiled 2.17.29, and there's already 2.17.95 Which is the next release after 2.17.29. We are getting close to releasing 2.18, and the versioning reflects that. I guess I need to build the latest frescobaldi, locally(?), so it's in step with the latest lilypond? Frescobaldi is an editor. Some of its special previewing functionality might require newer versions of LilyPond, and some of its syntax highlighting might get confused by large jumps in versions, but its fundamental operation does not get between user and LilyPond. So being in step should not be of much importance. So, obviously, just to add a ^markup to the music function is not trivial. I'm gathering that (text) markup belongs to an event function, rather than a music function, and the two can't be integrated ... although, that doesn't sound likely, off the top of my head, given the power and flexibility of this environment. Markups can't be added to general music expressions (what would c1 \\ d2 ^hi even mean?). But in this case you can just attach it to an empty chord starting with the music expression, like ^markup text #the-music ... -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: modular markup and arguments
On 11/07/2013 05:57 AM, David Kastrup wrote: Bric b...@flight.us writes: So, obviously, just to add a ^markup to the music function is not trivial. I'm gathering that (text) markup belongs to an event function, rather than a music function, and the two can't be integrated ... although, that doesn't sound likely, off the top of my head, given the power and flexibility of this environment. Markups can't be added to general music expressions (what would c1 \\ d2 ^hi even mean?). But in this case you can just attach it to an empty chord starting with the music expression, like ^markup text #the-music ... Fascinating! That worked. When I add your empty chord structure, I get one single insertion of the markup, per single invocation of the function (even though it gets applied to multiple notes). (If the ^\markup... comes before #the-music, it's on the first note of the set of notes; if after, it follows the set of notes). So... this is all quite amazing and powerful.But the interplay between the multiplicity of notes, and the singularity of \markup is something to finesse further. Because, what I am observing sort of defies my earlier idea of conditionally checking every note, its properties, and, based on a boolean, inserting or not inserting a markup. If the markup is inserted only once per invocation of the function, then what I was thinking would be impossible. But, i would guess, there's some way to do multiple insertions of markup, per function instantiation. thanks. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [ANNOUNCE] Frescobaldi included in MacPorts!
Dear Philippe and Hraban, could you both please send me (privately) the log files of the failing upgrade/install? MacPorts should tell you where to find it in the error message. I would like to fix the compilation of portmidi. If this will not be possible I'll make it optional. Best wishes. Davide ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hemiola indication
Well, I've now tried 2.17.29 and this example doesn't print the first or the
last ligature. And still giving the infinity/nan warnings. Does it work with
you?
\version 2.17.29
\language english
\score {
\new Staff
\relative c' {
\time 3/2
\[ c1 \] \[ f2~ | f \] \[ c' b \] |
\[ c2 b \] \[ a~ | a\] \[ g1 \]
}
}
Best regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
-
Thursday, October 31, 2013, 11:21:10 AM, you wrote:
Kieren,
To continue...
My tiny examples print OK in 2.17. But my original file doesn't. So it needs
more exploration, which I don't have time for at the moment. WIll try later.
Best regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
-
Sunday, October 20, 2013, 7:32:59 PM, you wrote:
Hi Peter,
All three print fine here (2.17).
Maybe try this with 2.16 (which I don't have):
\version 2.16.2
\language english
sopranoVoice = \relative c'' {
\key c \major
\numericTimeSignature
\time 3/2
{ \[ d2 ef \] \[ f | g \] \[ f1*15/16 s16 \]}
}
\score {
\new Staff { \sopranoVoice }
}
Hope this helps!
Kieren.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hemiola indication
Peter Toye wrote
Well, I've now tried 2.17.29 and this example doesn't print the first or
the last ligature. And still giving the infinity/nan warnings. Does it
work with you?
\version 2.17.29
\language english
\score {
\new Staff
\relative c' {
\time 3/2
\[ c1 \] \[ f2~ | f \] \[ c' b \] |
\[ c2 b \] \[ a~ | a\] \[ g1 \]
}
}
this example is different from the ones above where the \relative pitch was
c'' - and then it compiles without complaints!
(Kieren's example also fails when you change/lower the octave)
can you add a bug report - thanks!
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Hemiola-indication-tp152695p153504.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: modular markup and arguments
Bric wrote So... this is all quite amazing and powerful.But the interplay between the multiplicity of notes, and the singularity of \markup is something to finesse further. So far we're just adding a markup before or after the whole string of music we're passing to the music function. To do something with each of the various parts of that string of music (adding something or changing something conditionally) is a taller order. Here are a couple more snippets that show a way to do this using music-map. http://lsr.dsi.unimi.it/LSR/Snippet?id=538 http://lsr.dsi.unimi.it/LSR/Item?id=773 (especially the colorizeOutOfRange part) But these are both modifying properties rather than adding something new like a markup. You do realize that you are jumping right into deep water here? :-) Is there something specific you're trying to accomplish? There might be an easier way to do it... -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/modular-markup-and-arguments-tp153423p153505.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hemiola indication
and here's a kind of workaround: http://lilypond.1069038.n5.nabble.com/Ligaturebrackets-not-printed-after-line-break-tt80392.html#a80393 Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Hemiola-indication-tp152695p153506.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [ANNOUNCE] Frescobaldi included in MacPorts!
Am 2013-11-07 um 12:44 schrieb flup2 phili...@philmassart.net: Hello, I don't know if this could help: the only dependencies problem I had with the MIDI part was that 'aubio' didn't compile with OS X 10.9 (making the 'sudo port upgrade outdated' unusable). 'aubio' is part of the dependencies of 'portmidi', but the outdated version works (it's only the upgrade that's impossible now). Of course, if you re-installed Macports, I'm afraid you deleted the old version of 'aubio' port :( Sorry, but that looks to me like a problem of port midi with Apple’s CoreFoundation; aubio is not listed as a dependency of portmidi: :info:build In file included from In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_audio_portmidi/portmidi/work/portmidi/porttime/ptmacosx_mach.c:5/System/Library/Frameworks/CoreAudio.framework/Headers/HostTime.h: :info:build In file included from :31: :info:build In file included from /System/Library/Frameworks/CoreAudio.framework/Headers/CoreAudioTypes.h:28: :info:build In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFBase.h:68/System/Library/Frameworks/CoreAudio.framework/Headers/HostTime.h:31: :info:build In file included from /System/Library/Frameworks/CoreAudio.framework/Headers/CoreAudioTypes.h:28: :info:build In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFBase.h: :info:build In file included from //Developer/Headers/FlatCarbon/MacTypes.h:1: :info:build :68: :info:build In file included from //Developer/Headers/FlatCarbon/MacTypes.h:In file included from /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:191: :info:build In file included from /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:19: :info:build In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:: :info:build 39In file included from : :info:build /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:39: :info:build /System/Library/Frameworks/CoreFoundation.framework/Headers/CFArray.h:49:1/System/Library/Frameworks/CoreFoundation.framework/Headers/CFArray.h:: error: unknown type name 'CF_IMPLICIT_BRIDGING_ENABLED' :info:build 49:1: error: unknown type name 'CF_IMPLICIT_BRIDGING_ENABLED' :info:build CF_IMPLICIT_BRIDGING_ENABLED :info:build ^ :info:build CF_IMPLICIT_BRIDGING_ENABLED :info:build ^ :info:build /opt/local/bin/cmake -E cmake_progress_report /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_audio_portmidi/portmidi/work/portmidi/CMakeFiles 8 :info:build [ 30%] Building C object pm_common/CMakeFiles/pmjni.dir/__/pm_mac/readbinaryplist.c.o :info:build cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_audio_portmidi/portmidi/work/portmidi/pm_common /usr/bin/clang -Dpmjni_EXPORTS -pipe -Os -I/opt/local/include -arch x86_64 -DNDEBUG -arch x86_64 -fPIC -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_audio_portmidi/portmidi/work/portmidi/pm_common -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_audio_portmidi/portmidi/work/portmidi/porttime -I//Developer/Headers/FlatCarbon -I//System/Library/Frameworks/JavaVM.framework/Headers-o CMakeFiles/pmjni.dir/__/pm_mac/readbinaryplist.c.o -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_audio_portmidi/portmidi/work/portmidi/pm_mac/readbinaryplist.c :info:build /System/Library/Frameworks/CoreFoundation.framework/Headers/CFArray.h:50/System/Library/Frameworks/CoreFoundation.framework/Headers/CFArray.h:50:18:18: error: expected ';' after top level declarator: error: expected ';' after top level declarator :info:build :info:build CF_EXTERN_C_BEGIN :info:build ^ :info:build CF_EXTERN_C_BEGIN :info:build ^ :info:build /System/Library/Frameworks/CoreFoundation.framework/Headers/CFArray.h:74:47: error: unknown type name 'CFAllocatorRef' :info:build typedef const void *(*CFArrayRetainCallBack)(CFAllocatorRef allocator, const void *value); :info:build ^ :info:build /System/Library/Frameworks/CoreFoundation.framework/Headers/CFArray.h:74:47: error: unknown type name 'CFAllocatorRef' :info:build typedef const void *(*CFArrayRetainCallBack)(CFAllocatorRef allocator, const void *value); :info:build ^ :info:build /System/Library/Frameworks/CoreFoundation.framework/Headers/CFArray.h:75:41: error: unknown type name 'CFAllocatorRef' :info:build typedef void(*CFArrayReleaseCallBack)(CFAllocatorRef allocator, const void *value); :info:build
lines.ly
Following up on David Kastrup's align.ly example: Try lines.ly as filename and compile with Lilypond. That's another really nice one too :-) -- MT ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond - bitcoin donations?
David Kastrup d...@gnu.org writes: Scott Miller scottli...@gmail.com writes: Does the lilypond project accept bitcoin donations? Ok, this is not The LilyPond project as such, but if you want to support my (full-time) work on LilyPond specifically, you can try so using the address 1Kw7HZMd8L52BCL9vEjSxdPG4p3phRvtQF but please don't transfer any large amounts without first trying something small and waiting for feedback since I have no idea yet whether this will work. Well, looks like it does. And it might be a good idea to verify the PGP signature on this mail if you have the possibility before attempting anything. Yup... -- David Kastrup signature.asc Description: PGP signature ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond - bitcoin donations?
David, I'd like to donate and contribute towards your LilyPond work, but I don't understand what you mean when you write: ...you can try so using the address 1Kw7HZMd8L52BCL9vEjSxdPG4p3phRvtQF Can you give me a quick guide on how to donate this way, using the process you're describing? BitCoin? Is it different for those of us living in the US? Thanks, Ben David Kastrup wrote Scott Miller lt; scottlinux@ gt; writes: Does the lilypond project accept bitcoin donations? Ok, this is not The LilyPond project as such, but if you want to support my (full-time) work on LilyPond specifically, you can try so using the address 1Kw7HZMd8L52BCL9vEjSxdPG4p3phRvtQF but please don't transfer any large amounts without first trying something small and waiting for feedback since I have no idea yet whether this will work. And it might be a good idea to verify the PGP signature on this mail if you have the possibility before attempting anything. -- David Kastrup ___ lilypond-user mailing list lilypond-user@ https://lists.gnu.org/mailman/listinfo/lilypond-user signature.asc (203 bytes) lt;http://lilypond.1069038.n5.nabble.com/attachment/153459/0/signature.ascgt; - composer | sound designer LilyPond Tutorials (for beginners) -- http://bit.ly/bcl-lilypond -- View this message in context: http://lilypond.1069038.n5.nabble.com/lilypond-bitcoin-donations-tp153440p153514.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Polyrythmic exercices with two gridline on the top and bottom of a score with two rythmics voices
Hi here,
I try to do an exercice partition for working on polyrythms with two
simultaneous rythms.
I have a score with two voice, for the two rythme of the polyrythm.
I want a gridline on the top, giving the pulse of the top-voice and a
another gridline in a different collor for emphasis the pulse of the second
rythm-voice.
There is a bug there and I don't knox how to solve it ;)
Here is my code:
\version 2.12.0
#(set-global-staff-size 30)
#(set-default-paper-size a4 'landscape)
global = {
\time 12/4
}
\layout {
\context {
\Staff
\override Staff.VerticalAxisGroup #'minimum-Y-extent = #'(4 . -4)
%\override GridPoint.Y-extent = #'(4 . -4)
\override TupletNumber #'transparent = ##t
\override TupletBracket #'bracket-visibility = ##f
\consists Grid_point_engraver
gridInterval = #(ly:make-moment 1/12)
\remove Time_signature_engraver
\remove Clef_engraver
}
\context {
\Score
\consists Grid_line_span_engraver
% center grid lines horizontally below note heads
\override NoteColumn.X-offset = #-0.5
\override NonMusicalPaperColumn #'line-break-permission = ##f
}
ragged-right = ##t
}
\score {
\new ChoirStaff {
\relative c''
\new Staff {
\time 12/4
% hides staff and notes so that only the grid lines are visible
\hideNotes
\override Staff.BarLine.transparent = ##t
\override Staff.StaffSymbol.line-count = #0
% dummy notes to force regular note spacing
\once \override Score.GridLine.thickness = #4.0 \once \override
Score.GridLine.color = #red
\times 12/4 { c4 c c }
\once \override Score.GridLine.thickness = #4.0 \once \override
Score.GridLine.color = #red
c4 c c c c c c c c c c c
\once \override Score.GridLine.thickness = #4.0 \once \override
Score.GridLine.color = #red
c4 c c c c c c c c c c c
}
\new Staff \with { instrumentName = \markup \center-column {Ex:
5 6 } } \new Voice { \voiceOne \relative c'' { \time 12/8
r4 e r r e r r e e r r e | e e r e~ e e e~ e r e~ e e | r e e e r r e r
e r e e | } } \new Voice { \voiceTwo \relative c' { \global
f4 r r f r f f r f r f f | r f f r f r r f f r r f | f~ f f f f r f~ f r
f~ f r |} }
\new Staff {
\time 12/4
% hides staff and notes so that only the grid lines are visible
\hideNotes
\override Staff.BarLine.transparent = ##t
\override Staff.StaffSymbol.line-count = #0
% dummy notes to force regular note spacing
\once \override Score.GridLine.thickness = #4.0 \once \override
Score.GridLine.color = #blue
c4 c c c c c c c c c c c
\once \override Score.GridLine.thickness = #4.0 \once \override
Score.GridLine.color = #blue
c4 c c c c c c c c c c c
\once \override Score.GridLine.thickness = #4.0 \once \override
Score.GridLine.color = #blue
c4 c c c c c c c c c c c
}
}
}
Best and thanks
Ewen
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Polyrythmic-exercices-with-two-gridline-on-the-top-and-bottom-of-a-score-with-two-rythmics-voices-tp153516.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond - bitcoin donations?
SoundsFromSound soundsfromso...@gmail.com writes: David, I'd like to donate and contribute towards your LilyPond work, but I don't understand what you mean when you write: ...you can try so using the address 1Kw7HZMd8L52BCL9vEjSxdPG4p3phRvtQF Can you give me a quick guide on how to donate this way, using the process you're describing? BitCoin? Is it different for those of us living in the US? Have you ever used BitCoin? If so, you have a wallet (on your personal computer, or on some webservice which acts as a bank without the guarantees, so letting it hold large amounts is probably not the best idea). Your wallet is represented by a private key (losing it means losing the wallet and its content) which better be backed up somewhere, and by the related total BitCoin transaction on the BitCoin network (losing _that_ is pretty much impossible). Amounts are transferred from wallet to wallet via transactions, and those are made out to BitCoin addresses connected to a wallet. The above address is connected to my wallet. BitCoin is its own currency with its own fluctuations determined by demand and availability. For example, a year ago a BitCoin was worth about €10, a month ago €100, 1.5 days ago €180, half a day ago €220. Transferring BitCoins is easy, fast and basically without cost. Exchanging them for real money comparatively cheap (basically, this is done on market places working somewhat like stock exchanges). The high fluctuations make it somewhat unpredictable. Yet if you exchange bitcoins reasonably fast, you are not likely to incur large losses. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
