headers
Graham Percival | 1 Jul 2007 02:22
Picon

Re: \betweenLilyPondSystem : strange behaviour

Jean-Charles wrote:

> It seems to me that as long as there is no "header" section in the 
> lilypond environment, the first two systems get sticked together.
> Uncommenting the header line makes it work correctly.
> 
> 
> ======== sticky.lytex =========
> \documentclass[a4paper,12pt]{book}
> \usepackage[frenchb]{babel}
> \newcommand{\betweenLilyPondSystem}[1]{\linebreak \vspace{36pt}}
> \begin{document}
> \begin{lilypond}
> %  \header {title = " "}
>   {c'1\( e'( c'~ \break c' d) e f \break c' d) e f\)}
> \end{lilypond}
> \end{document}
> =================================
> 
> 
> Is this my fault or not ?

I suspect that this is a real bug, but I would still like an example 
which is --> as small as possible <--.

- can you reproduce this bug without the frenchb bable command?  I'm 
certain that you can, so please remove this line.

- can you reproduce this bug wihout any ties or slurs?  I'm not certain 
about this; if you can, then remove all those marks.
(Continue reading)

Permalink | Reply | 2 comments |
headers
codesite-noreply | 1 Jul 2007 02:25
Picon
Favicon

Issue 387 in lilypond: tabstaff \set commands create a TabStaff context

Issue 387: tabstaff \set commands create a TabStaff context
http://code.google.com/p/lilypond/issues/detail?id=387

New issue report by gpermus:
%% the \set TabStaff  commands below create a TabStaff if there's
%% no TabStaff (ie when \new TabStaff is commented out)
%% IMO, these commands should just do nothing.

\version &quot;2.10.1&quot;
frag =  {
e'1  \set TabStaff.minimumFret = #3
g'1  \set TabStaff.minimumFret = #0
e'1
}

\score {
&lt;&lt;
 &lt;&lt; \new Staff { \frag } &gt;&gt;
 % &lt;&lt; \new TabStaff { \frag } &gt;&gt;  % uncommenting this line it works ok.
&gt;&gt;
} 

Attachments:
	bar.preview.png  3.5 KB 

Issue attributes:
	Status: Accepted
	Owner: gpermus
	Labels: Type-Defect Priority-Low
(Continue reading)

Permalink | Reply | 0 comments |
headers
Graham Percival | 1 Jul 2007 02:26
Picon

Re: dealing with tabstaff commands when no tabstaff is defined

Thanks, entered as
http://code.google.com/p/lilypond/issues/detail?id=387

Cheers,
- Graham

hernan gonzalez wrote:
> I have a score that uses TabStaff; the voices include here and there
> some tab-related commands (eg.   \set TabStaff.minimumFret ). If I
> choose to  not output the TabStaff (commenting out that staff from the
> main score definition), lilypond get badly  confused with the
> tabstaff-related commands it finds.
> 
> Test case:
> With Lilypond 2.10.23 (Win)
> 
> %%%%%%%%%%%%%%%%%%%%%
> \version "2.10.1"
> frag =  {
> e'1  \set TabStaff.minimumFret = #3
> g'1  \set TabStaff.minimumFret = #0
> e'1
> }
> 
> \score {
> <<
>  << \new Staff { \frag } >>
>  % << \new TabStaff { \frag } >>  % uncommenting this line it works ok.
>  >>
> }
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jean-Charles | 1 Jul 2007 13:07
Picon

Re: \betweenLilyPondSystem : strange behaviour

Le 01.07.2007 02:22, Graham Percival disait :
> Jean-Charles wrote:
> 
>> It seems to me that as long as there is no "header" section in the 
>> lilypond environment, the first two systems get sticked together.
>> Uncommenting the header line makes it work correctly.
>>
> 
> I suspect that this is a real bug, but I would still like an example 
> which is --> as small as possible <--.
> 
> - can you reproduce this bug without the frenchb bable command?  I'm 
> certain that you can, so please remove this line.
> 

It seems that something unreadable broke compilation as soon as I didnot 
explicit babel.

> - can you reproduce this bug wihout any ties or slurs?  I'm not certain 
> about this; if you can, then remove all those marks.
> 

The result is:
============ sticky-systems.lytex ==========
\documentclass[a4paper,12pt]{book}
\newcommand{\betweenLilyPondSystem}[1]{\linebreak \vspace{36pt}}
\begin{document}
\begin{lilypond}
%  \header {title = " "}
   {c'1 \break c' \break c'}
(Continue reading)

Permalink | Reply | 1 comment |
headers
Nicolas Sceaux | 1 Jul 2007 19:25
Face
Picon
Favicon

volta brackets displayed on all staves

Hi

Using lilypond from git HEAD, with the following snippet, volta brackets
are displayed above every staves:

\version "2.11.27"
\new StaffGroup <<
  \new Staff { \repeat volta 2 { g'1 g' g' } \alternative { g' g' } }
  \new Staff { c'1 c' c' c' d' }
>>

nicolas
Permalink | Reply | 501 comments |
headers
codesite-noreply | 1 Jul 2007 21:40
Picon
Favicon

Issue 388 in lilypond: lilypond-book \betweenlilypondsystem does not apply to first system break if no header

Issue 388: lilypond-book \betweenlilypondsystem  does not apply to first system break if no header
http://code.google.com/p/lilypond/issues/detail?id=388

New issue report by gpermus:
% if there is no header, then \betweenlilypondsystem does not apply
% to the very first system break

\documentclass[a4paper,12pt]{book}
\newcommand{\betweenLilyPondSystem}[1]{\linebreak \vspace{36pt}}
\begin{document}
\begin{lilypond}
%  \header {title = &quot; &quot;}
  {c'1 \break c' \break c' }
\end{lilypond}
\end{document} 

Attachments:
	bar.pdf  19.2 KB 

Issue attributes:
	Status: Accepted
	Owner: gpermus
	Labels: Type-Defect Priority-Medium

--

-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
(Continue reading)

Permalink | Reply | 0 comments |
headers
Graham Percival | 1 Jul 2007 21:40
Picon

Re: \betweenLilyPondSystem : strange behaviour

Thanks, this issue has been added as
http://code.google.com/p/lilypond/issues/detail?id=388

Cheers,
- Graham

Jean-Charles wrote:
> Le 01.07.2007 02:22, Graham Percival disait :
>> Jean-Charles wrote:
>>
>>> It seems to me that as long as there is no "header" section in the 
>>> lilypond environment, the first two systems get sticked together.
>>> Uncommenting the header line makes it work correctly.
>>>
>>
>> I suspect that this is a real bug, but I would still like an example 
>> which is --> as small as possible <--.
>>
>> - can you reproduce this bug without the frenchb bable command?  I'm 
>> certain that you can, so please remove this line.
>>
> 
> It seems that something unreadable broke compilation as soon as I didnot 
> explicit babel.
> 
>> - can you reproduce this bug wihout any ties or slurs?  I'm not 
>> certain about this; if you can, then remove all those marks.
>>
> 
> The result is:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Graham Percival | 1 Jul 2007 21:43
Picon

Re: volta brackets displayed on all staves

Thanks, this issue has already been reported,
http://code.google.com/p/lilypond/issues/detail?id=366&can=2&q=volta

Cheers,
- Graham

Nicolas Sceaux wrote:
> Hi
> 
> Using lilypond from git HEAD, with the following snippet, volta brackets
> are displayed above every staves:
> 
> \version "2.11.27"
> \new StaffGroup <<
>   \new Staff { \repeat volta 2 { g'1 g' g' } \alternative { g' g' } }
>   \new Staff { c'1 c' c' c' d' }
> 
> nicolas
> 
> 
> _______________________________________________
> bug-lilypond mailing list
> bug-lilypond <at> gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-lilypond
>
Permalink | Reply | 502 comments |
headers
hernan | 1 Jul 2007 22:07
Picon
Gravatar

TabStaff and partcombine do not seem to work together

>just to convince the clever php guy at http://post.gmane.org/post.php that im
not top posting... 
> 

-----------------------------------------------------------------------

Here goes a test case

\version "2.10.1"
melodia = \transpose c c' \partcombine { e4 g g g  }{e4 e e e }
\score
{
    <<
        \new Staff
        {    
            \set Staff.printPartCombineTexts = ##f 
            \melodia
        }
        \new TabStaff { \melodia } % commenting out this line works ok
    >>
}
Permalink | Reply | 501 comments |
headers
Mats Bengtsson | 2 Jul 2007 19:05
Picon
Picon
Favicon

Re: dealing with tabstaff commands when no tabstaff is defined

A simple workaround would be to do the property setting higher up
in the context hierarchy, for example at the Score level, which means
that they will be inherited to all TabStaff contexts (if there are any):
\set Score.minimumFret = #3

   /Mats

Quoting Graham Percival <gpermus <at> gmail.com>:

> Thanks, entered as
> http://code.google.com/p/lilypond/issues/detail?id=387
>
> Cheers,
> - Graham
>
>
> hernan gonzalez wrote:
>> I have a score that uses TabStaff; the voices include here and there
>> some tab-related commands (eg.   \set TabStaff.minimumFret ). If I
>> choose to  not output the TabStaff (commenting out that staff from the
>> main score definition), lilypond get badly  confused with the
>> tabstaff-related commands it finds.
>>
>> Test case:
>> With Lilypond 2.10.23 (Win)
>>
>> %%%%%%%%%%%%%%%%%%%%%
>> \version "2.10.1"
>> frag =  {
>> e'1  \set TabStaff.minimumFret = #3
(Continue reading)

Permalink | Reply | 1 comment |

Gmane