Re: [Denemo-devel] Font of Lyric verses
These seem to work: 2 new buttons for me! Joe ;LyricFontItalic (d-InsertTextInVerse "\n\\override Lyrics.LyricText.font-shape = #'italic \n" ) (d-SetSaved #f) ;LyricFontNormal (d-InsertTextInVerse " \n\\revert Lyrics.LyricText.font-shape \n" ) (d-SetSaved #f) ;From Command ;InsertHyphenBetweenSyllables On 02/10/2019 20:59, Joe Wilkinson via Denemo-devel wrote: \override Lyrics.LyricText.font-shape = #'italic and \revert Lyrics.LyricText.font-shape are in the learning manual!! Joe On 02/10/2019 20:43, Richard Shann wrote: On Wed, 2019-10-02 at 19:53 +0100, Burgess Hill Community Food Bank wrote: Hi Richard, I wanted to typeset my chorus in italic, and thought I would explore the Lyrics >> ChangeFont process as a shortcut to delving into Lilypond. It seems to have no effect; no markup added to Lyrics, and no change of font. When I try that I get asked for a font name (default "Times") and it inserts \override LyricText.font-name = #"Times" the font size one inserts \override LyricText.font-size = #-4 and the font size gets tiny. There doesn't seem to be an italic, but you could look up the syntax ... Richard ___ Denemo-devel mailing list Denemo-devel@gnu.org https://lists.gnu.org/mailman/listinfo/denemo-devel ___ Denemo-devel mailing list Denemo-devel@gnu.org https://lists.gnu.org/mailman/listinfo/denemo-devel
Re: [Denemo-devel] Font of Lyric verses
\override Lyrics.LyricText.font-shape = #'italic and \revert Lyrics.LyricText.font-shape are in the learning manual!! Joe On 02/10/2019 20:43, Richard Shann wrote: On Wed, 2019-10-02 at 19:53 +0100, Burgess Hill Community Food Bank wrote: Hi Richard, I wanted to typeset my chorus in italic, and thought I would explore the Lyrics >> ChangeFont process as a shortcut to delving into Lilypond. It seems to have no effect; no markup added to Lyrics, and no change of font. When I try that I get asked for a font name (default "Times") and it inserts \override LyricText.font-name = #"Times" the font size one inserts \override LyricText.font-size = #-4 and the font size gets tiny. There doesn't seem to be an italic, but you could look up the syntax ... Richard ___ Denemo-devel mailing list Denemo-devel@gnu.org https://lists.gnu.org/mailman/listinfo/denemo-devel
Re: [Denemo-devel] Font of Lyric verses
On Wed, 2019-10-02 at 19:53 +0100, Burgess Hill Community Food Bank wrote: > Hi Richard, > > I wanted to typeset my chorus in italic, and thought I would explore > the > Lyrics >> ChangeFont process as a shortcut to delving into Lilypond. > > It seems to have no effect; no markup added to Lyrics, and no change > of > font. When I try that I get asked for a font name (default "Times") and it inserts \override LyricText.font-name = #"Times" the font size one inserts \override LyricText.font-size = #-4 and the font size gets tiny. There doesn't seem to be an italic, but you could look up the syntax ... Richard ___ Denemo-devel mailing list Denemo-devel@gnu.org https://lists.gnu.org/mailman/listinfo/denemo-devel
[Denemo-devel] Font of Lyric verses
Hi Richard, I wanted to typeset my chorus in italic, and thought I would explore the Lyrics >> ChangeFont process as a shortcut to delving into Lilypond. It seems to have no effect; no markup added to Lyrics, and no change of font. :-( Joe ___ Denemo-devel mailing list Denemo-devel@gnu.org https://lists.gnu.org/mailman/listinfo/denemo-devel
Re: [Denemo-devel] Proof-reading Denemo Scores
Hi Richard, I use a tablet for this purpose, because I can put it on the music stand of my piano or take it to a practice room. I just transfer the exported PDF to the tablet. I haven't tried Denemo's PDF proof reading feature yet, though I guess that will be handy. Probably, you can use your page turner on a tablet as well, and other products exist decidedly designed for tablets (either by Bluetooth or USB), though I haven't tried any yet. Andreas ___ Denemo-devel mailing list Denemo-devel@gnu.org https://lists.gnu.org/mailman/listinfo/denemo-devel
Re: [Denemo-devel] Proof-reading Denemo Scores
Just an observation: Many of our Mandolin Orchestra use iPads - only some are bigger iPad Pro - with foot-pedals. They claim that though the display is smaller they can see it just as well as it is backlit. So size may not matter; what we need is Denemo for iPad/Android, I rather fancy something like a Gvido - 2 A4 "Kindle-paper technology" screens side by side (readable in sunlight!), but can't justify the £1500 cost! Joe On 02/10/2019 17:42, Richard Shann wrote: One useful way of proof-reading a score is to actually play from it - this may involve an entire music group getting together and normally I scribble something on the score to record anything I want to alter. Later I look through the (paper) score and find the place in the Denemo score and make the alteration. However, the advent of lighter, less power-hungry screens and tiny computers suggests playing directly from a digital display. One of the advantages that could flow from that would be to mark places in the score much more quickly (just by tapping on the spot, of clicking with a mouse if not using a touchscreen). Then a little bit of programming would mean that you could open the PDF from within the Denemo program and immediately see and - again with a single click - navigate to the place to make the alteration. These thoughts occurred to me because I came across a score which I couldn't see a way to typeset so that I could both easily read it and avoid page-turning while playing. This is one of the things that playing directly from a digital display could avoid - page turning could be done via some additional interaction, for example foot-pedals. I looked around at what was available and decided to write something myself as it is pretty simple stuff. The result was a 764 line program which is currently to be found here: http://git.savannah.gnu.org/gitweb/?p=denemo.git;a=blob_plain;f=tools/pageturner.c;hb=HEAD It is a completely stand-alone program but when I had finished it the idea of using it to proof-read scores occurred to me and I realised I could read the annotations and position the cursor for editing from within Denemo, so I bundled the source code in the "tools" section of the Denemo source code. As a bonus, the overnight build has created an executable for use from Windows operating systems which appears to be completely functional. (The executable is called pageturner.exe and lives with all the other executable stuff in the bin subdirectory - it really needs a batch script at the top level to run it with ease.) As it happens, Denemo already has a proof-reading facility: that one is for PDF files which you have sent off somewhere to be proof-read and come back with PDF annotations. So I've enhanced that code so that if you open a PDF with an associated annotations file (as created by the pageturner program) then you can navigate and edit from that. As for the pageturner program itself, there were several ways to write this but I reasoned that the best use of the (expensive) screen resource would be to use a single page and turn the top half over on the page turn signal, turning the rest after either a separate signal or automatically after a few seconds' delay or, indeed, immediately. I found a suitable pedal keyboard DecentGadget® PC USB Foot Control Keyboard Action Switch Pedal HID Fußpedal which has three pedals. These could be set to go forward one page, backward one page and to complete the lower half of a turned page. I'm not so sure about a suitable screen, though. I've experimented so far with an ordinary 17" monitor turned on its side. The aspect ratio is quite reasonable (it would be possible to make the page size to match from within Denemo) and my (limited) experimentation with that set-up makes me think it would work ok if it were lighter and slimmer. I didn't yet buy the foot-pedals as unless I can find a screen it would be pointless. One of the things I realised trying out the pageturner program is that there is a real advantage to being able to place annotations on the page not just for proof reading. The default annotation is the eyeglasses sign, "O^O", which is usually scribbled in by orchestral musicians at points where there is something tricky to watch for. But adding reminder accidentals or remarks are also possible. One such is a statement at the end of a repeat to say how many pages to turn back to find the repeat start. If anyone would like to try out the pageturner program I would welcome feedback on how it works for them. Richard ___ Denemo-devel mailing list Denemo-devel@gnu.org https://lists.gnu.org/mailman/listinfo/denemo-devel ___ Denemo-devel mailing list Denemo-devel@gnu.org https://lists.gnu.org/mailman/listinfo/denemo-devel
[Denemo-devel] Proof-reading Denemo Scores
One useful way of proof-reading a score is to actually play from it - this may involve an entire music group getting together and normally I scribble something on the score to record anything I want to alter. Later I look through the (paper) score and find the place in the Denemo score and make the alteration. However, the advent of lighter, less power-hungry screens and tiny computers suggests playing directly from a digital display. One of the advantages that could flow from that would be to mark places in the score much more quickly (just by tapping on the spot, of clicking with a mouse if not using a touchscreen). Then a little bit of programming would mean that you could open the PDF from within the Denemo program and immediately see and - again with a single click - navigate to the place to make the alteration. These thoughts occurred to me because I came across a score which I couldn't see a way to typeset so that I could both easily read it and avoid page-turning while playing. This is one of the things that playing directly from a digital display could avoid - page turning could be done via some additional interaction, for example foot-pedals. I looked around at what was available and decided to write something myself as it is pretty simple stuff. The result was a 764 line program which is currently to be found here: http://git.savannah.gnu.org/gitweb/?p=denemo.git;a=blob_plain;f=tools/pageturner.c;hb=HEAD It is a completely stand-alone program but when I had finished it the idea of using it to proof-read scores occurred to me and I realised I could read the annotations and position the cursor for editing from within Denemo, so I bundled the source code in the "tools" section of the Denemo source code. As a bonus, the overnight build has created an executable for use from Windows operating systems which appears to be completely functional. (The executable is called pageturner.exe and lives with all the other executable stuff in the bin subdirectory - it really needs a batch script at the top level to run it with ease.) As it happens, Denemo already has a proof-reading facility: that one is for PDF files which you have sent off somewhere to be proof-read and come back with PDF annotations. So I've enhanced that code so that if you open a PDF with an associated annotations file (as created by the pageturner program) then you can navigate and edit from that. As for the pageturner program itself, there were several ways to write this but I reasoned that the best use of the (expensive) screen resource would be to use a single page and turn the top half over on the page turn signal, turning the rest after either a separate signal or automatically after a few seconds' delay or, indeed, immediately. I found a suitable pedal keyboard DecentGadget® PC USB Foot Control Keyboard Action Switch Pedal HID Fußpedal which has three pedals. These could be set to go forward one page, backward one page and to complete the lower half of a turned page. I'm not so sure about a suitable screen, though. I've experimented so far with an ordinary 17" monitor turned on its side. The aspect ratio is quite reasonable (it would be possible to make the page size to match from within Denemo) and my (limited) experimentation with that set-up makes me think it would work ok if it were lighter and slimmer. I didn't yet buy the foot-pedals as unless I can find a screen it would be pointless. One of the things I realised trying out the pageturner program is that there is a real advantage to being able to place annotations on the page not just for proof reading. The default annotation is the eyeglasses sign, "O^O", which is usually scribbled in by orchestral musicians at points where there is something tricky to watch for. But adding reminder accidentals or remarks are also possible. One such is a statement at the end of a repeat to say how many pages to turn back to find the repeat start. If anyone would like to try out the pageturner program I would welcome feedback on how it works for them. Richard ___ Denemo-devel mailing list Denemo-devel@gnu.org https://lists.gnu.org/mailman/listinfo/denemo-devel
Re: [Denemo-devel] Check Score bug
On Wed, 2019-10-02 at 09:47 +0100, Richard Shann wrote: > On Fri, 2019-09-27 at 15:41 +0100, Joe Wilkinson wrote: > > Hi Richard, > > Welcome back! > > Check Score seems to be behaving oddly. Test.denemo typesets > > [...] > > Check score reports the same error as the first case. > > So it seems to depend on how the two 2/4 bars are created; > > retrospective division is not approved of!! > > It is a problem with the caching of the time signatures - I've filed > a > bug report. Saving & reloading the score fixes the cache. > Thanks! This email got out-of-sync, the bug is now fixed. Richard ___ Denemo-devel mailing list Denemo-devel@gnu.org https://lists.gnu.org/mailman/listinfo/denemo-devel
