Re: Next round on frescobaldi dependencies

[lists]

Hi all,

I must add some more confusion to this issue.

I just had the opportunity to install a new OS from scratch and did (exactly) 
the following:
* Install Ubuntu MATE 17.10 from DVD 
* sudo apt update 
* sudo apt upgrade 
* sudo apt install etckepper (definitely not related to all of this, 
but just for sake of completeness) 
* sudo apt install frescobaldi 

This gave me a *working* installation of Frescobaldi, including LilyPond 2.18.2 
and both the PDF and the SVG viewer working properly

After making the frescobaldi and python-ly Git repositories available (and 
installing Git itself) I could invoke frescobaldi directly wtih
PYTHONPATH=$PYTHONPATH:/path/to/python-ly python3 /path/to/frescobaldi

which gave me a working "development" version of Frescobaldi.

I haven't yet figured out how to add a menu entry for the Git installation (it 
seems the package manager installation "shadows" the other one), but I have to 
state that I *did* successfully install Frescobaldi 3 on a clean Ubuntu 17.10 
installation without *any* dependency problems.

Urs

28. Dezember 2017 08:55, "Andrew Bernard" )> schrieb:
Hello Urs and all,
 Following your excellent instructions on the dependenicies, always difficult 
to work out, especially when detail is missing, I am immediately presented with 
the same old core dump on startup, as per usual. I am using Ubuntu 17.10, 
kernel 4.13.0-21-generic (not that the kernel would make a difference!).
 Clearly there are deeper dependencies and issues at play here. I would not 
have imagined a python program could be so troublesome, and so difficult to 
understand and fix. I guess it is due to the complexity of the Qt ecosystem 
world. 
I remain stuck on Mint 18 for F at the moment therefore. Annoying, as all my 
other work is on Ubuntu 17. 
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Is anyone maintaining midi2ly?

[David Kastrup]

Michael Ellis  writes:

> David Kastrup wrote:
>
>- I get correct PDF output on 2.21.0 but a nonsensical wash of bar
>checks that appear to cater to 2/4 throughout.
>
> Thanks for testing it, David.  What options did you use for midi2ly and
> lilypond?

None.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Is anyone maintaining midi2ly?

[Michael Ellis]

David Kastrup wrote:

   - I get correct PDF output on 2.21.0 but a nonsensical wash of bar
   checks that appear to cater to 2/4 throughout.

Thanks for testing it, David.  What options did you use for midi2ly and
lilypond?  My command lines were:

./midi2ly.py -o meter.ly -n -V 1 meter.midi
lilypond meter.ly

I only got one bar check complaint when LP processed meter.ly which
contains:

TrackA = {
  \numericTimeSignature\time 4/4  c'4 d'4 e'4 f'4  |  % orig
  \numericTimeSignature\time 2/4  g'8 a'8 g'8 g'8 a'8 g'8 c''4  |  % orig
  \numericTimeSignature\time 6/8  c''4 g'8 a'8 g'8 g'8 a'8 g'8  |  % orig
  \numericTimeSignature\time 2/4  c''4 c''4 r2  |  % orig
}

It was on the 6/8 line in the above which contains 8 eighth-notes.

I'll try upgrading to 2.21 and see if that makes any difference.


On Sat, Dec 30, 2017 at 5:15 PM David Kastrup  wrote:

> Michael Ellis  writes:
>
> > Hi, It's been a few years since my last post here.  I'm wondering about
> the status of
> > midi2ly.  I just tried the version that came with 2.18.2 and it seems to
> handle meter
> > changes incorrectly.  Here's a short example produced from a midi file
> imported into
> > MuseScore 2.1
> >
> > msc2-meter-example.png
> >
> > and here's the result of processing what midi2ly produced from the same
> file
> >
> > ly-meter-example.png
> >
> > The MuseScore output is correct and matches the tempo and meter items
> > embedded in the original midi file (attached).  I've also verified with
> 2 different
> > DAW's (Reaper and Logic X) that the midi file is imported correctly.
> >
> > The application that produced the midi file is called tbon. It's a
> shorthand notation
> > language I wrote for projects where fast notation entry is more
> important than
> > having the full capabilities of LilyPond.  If you're curious about tbon,
> go to
> > https://github.com/Michael-F-Ellis/tbon . The README has a link to a
> live online
> > demo.
> >
> > I'd really rather use LP than MuseScore for the times when I want to
> engrave the
> > output from tbon since LP still produces better looking scores, imo, but
> not being
> > able to handle meter changes is a showstopper.
>
> I get correct PDF output on 2.21.0 but a nonsensical wash of bar checks
> that appear to cater to 2/4 throughout.
>
> --
> David Kastrup
>
-- 
Write music faster with Tbon.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Change the text within a volta

[Robin Bannister]

nokel81 wrote:
Thank you very much however, my text comes out really weird. 


Consider using manual repeat marks, described in
http://lilypond.org/doc/v2.19/Documentation/notation/long-repeats#manual-repeat-marks

The funny letters you are getting are meant for dynamics, which shares 
its font with volta numbers. To change that you have to get into markup 
mode and apply the command \text.


The last example in this manual repeat section shows how to use a 
variable (in this case voltaAdLib) to benefit from markup mode.



Cheers,
Robin




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Is anyone maintaining midi2ly?

[karl]

David Kastrup:
> Michael Ellis  writes:
...
> > The MuseScore output is correct and matches the tempo and meter items
> > embedded in the original midi file (attached).  I've also verified with 2 
> > different
> > DAW's (Reaper and Logic X) that the midi file is imported correctly.

The midi file matches your msc2-meter-example.png, I can show you
(Michael) a dump if you like.

> > The application that produced the midi file is called tbon. It's a 
> > shorthand notation
> > language I wrote for projects where fast notation entry is more important 
> > than
> > having the full capabilities of LilyPond.  If you're curious about tbon, go 
> > to
> > https://github.com/Michael-F-Ellis/tbon . The README has a link to a live 
> > online
> > demo.

Nice idea to have c--c mean c8. c16 which is much more error prone to 
type.

You could probably change your python program to output lilypond code
directly.

> > I'd really rather use LP than MuseScore for the times when I want to 
> > engrave the
> > output from tbon since LP still produces better looking scores, imo, but 
> > not being
> > able to handle meter changes is a showstopper.
> 
> I get correct PDF output on 2.21.0 but a nonsensical wash of bar checks
> that appear to cater to 2/4 throughout.

And here with 2.19.16.

The bar checks fails because midi2ly puts in barchecks in the wrong 
places, don't know why.

///

Regarding your subject line question, I don't know.
I make my own midi -> ly converter though, currently in an experimental
leap...

Regards,
/Karl Hammar

---
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Is anyone maintaining midi2ly?

[David Kastrup]

Michael Ellis  writes:

> Hi, It's been a few years since my last post here.  I'm wondering about the 
> status of
> midi2ly.  I just tried the version that came with 2.18.2 and it seems to 
> handle meter
> changes incorrectly.  Here's a short example produced from a midi file 
> imported into
> MuseScore 2.1
>
> msc2-meter-example.png
>
> and here's the result of processing what midi2ly produced from the same file
>
> ly-meter-example.png
>
> The MuseScore output is correct and matches the tempo and meter items
> embedded in the original midi file (attached).  I've also verified with 2 
> different
> DAW's (Reaper and Logic X) that the midi file is imported correctly.
>
> The application that produced the midi file is called tbon. It's a shorthand 
> notation
> language I wrote for projects where fast notation entry is more important than
> having the full capabilities of LilyPond.  If you're curious about tbon, go to
> https://github.com/Michael-F-Ellis/tbon . The README has a link to a live 
> online
> demo.
>
> I'd really rather use LP than MuseScore for the times when I want to engrave 
> the
> output from tbon since LP still produces better looking scores, imo, but not 
> being
> able to handle meter changes is a showstopper.

I get correct PDF output on 2.21.0 but a nonsensical wash of bar checks
that appear to cater to 2/4 throughout.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Is anyone maintaining midi2ly?

[Michael Ellis]

Hi, It's been a few years since my last post here.  I'm wondering about the
status of midi2ly.  I just tried the version that came with 2.18.2 and it
seems to handle meter changes incorrectly.  Here's a short example produced
from a midi file imported into MuseScore 2.1

[image: msc2-meter-example.png]

and here's the result of processing what midi2ly produced from the same file

[image: ly-meter-example.png]

The MuseScore output is correct and matches the tempo and meter items
embedded in the original midi file (attached).  I've also verified with 2
different DAW's (Reaper and Logic X) that the midi file is imported
correctly.

The application that produced the midi file is called *tbon*. It's a
shorthand notation language I wrote for projects where fast notation entry
is more important than having the full capabilities of LilyPond.  If you're
curious about tbon, go to https://github.com/Michael-F-Ellis/tbon . The
README has a link to a live online demo.

I'd really rather use LP than MuseScore for the times when I want to
engrave the output from tbon since LP still produces better looking scores,
imo, but not being able to handle meter changes is a showstopper.

Thanks,
Mike
-- 
Write music faster with Tbon.



meter.midi
Description: MIDI audio
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Change the text within a volta

[Wols Lists]

On 30/12/17 18:48, nokel81 wrote:
> Thank you very much however, my text comes out really weird. I have set my
> font- name to "sans" but that doesn't seem to help.
>  
> 
I think the problem(s) I had were

1) the default font was only numbers, hence having to set the font to
something with the alphabet, and
2) yes I also had the problem with the weird letters.

Fonts in lilypond give me grief. It could be you haven't actually got
sans, so it's selecting the closest match which is the fonts it uses for
music text like forte, sforzando etc, which is why you have the weird
italic.

I'll have to let someone else talk you through that, but it clearly is a
font problem :-(

If you care to search the list archives, the piece is Radetzky March so
if you search for posts of mine about Radetzky, you'll find the
thread(s) where people helped me.

Cheers,
Wol


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Change the text within a volta

[nokel81]

Thank you very much however, my text comes out really weird. I have set my
font- name to "sans" but that doesn't seem to help.
 



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fixed vertical spacing within staff-group

[Eby Mani]

Hi Malte, the reason why i did not include the minimal working(4 to 10 
measures), is the output looks good, without spacing issues. I have tried your 
suggestion and it is not fixing the spacing issue. I will mail the full file, 
so that you can see the problem. Thanks.


On Fri, 29/12/17, Malte Meyn  wrote:

 Subject: Re: fixed vertical spacing within staff-group
 To: lilypond-user@gnu.org
 Date: Friday, 29 December, 2017, 5:21 PM
 
 
 
 Am 29.12.2017 um 05:30 schrieb Eby Mani:
 > Hi,
 > 
 > How to set fixed vertical spacing within
 staff-group ?.
 
 Hi,
 
 please always give a minimal
 working (and compilable) code example that 
 shows what you are doing currently.
 
 > I have tried the following in \layout {
 \context } section. Vertical spacing keep on varying if
 there are beams, ledger lines or cross-staff notation. Even
 tried with padding=#0. Without the StaffGrouper, spacing is
 somewhat ok(but i feel little more spacing is required),
 except the cross-staff part.
 > 
 > \override
 StaffGrouper.staff-staff-spacing.padding = #2
 > \override
 StaffGrouper.staff-staff-spacing.basic-distance =
 #6
 
 Have a look at http://joramberger.de/files/LilypondSpacing.pdf
 Because 
 you didn’t provide code, I
 cannot test, but I think, something like the 
 following might work:
 
 \override
 StaffGrouper.staff-staff-spacing.padding = #-inf.0
 \override
 StaffGrouper.staff-staff-spacing.stretchability = 0
 \override
 StaffGrouper.staff-staff-spacing.basic-distance = 10
 \override
 StaffGrouper.staff-staff-spacing.minimum-distance = 10
 
 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 https://lists.gnu.org/mailman/listinfo/lilypond-user
 

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user