Re: LilyDev4 and Guile2.2 ?
I didn't pay attention to the version of guile. Debian has only 2.0 at the moment: https://packages.debian.org/search?keywords=guile-2 If you need 2.2 you must use one of these options: https://www.gnu.org/software/guile/download/ Il giorno mer 12 apr 2017 alle 18:35, Federico Bruni ha scritto: Il giorno mer 12 apr 2017 alle 17:51, Paul ha scritto: Hi all, Having been unsuccessful at getting LilyDev5 running on my laptop using VirtualBox, I'm wondering how it would work to create a virtual machine with LilyDev4 (which is working for me) and then uninstalling guile1.8 and installing guile2.2. Is this a fool's errand? I'm new to this dependency hell business, would be a good induction, maybe too good? Thanks for any advice, -Paul My suggestion is: 1. copy LilyDev4 virtualbox file somewhere (so you can still run LilyDev4 in case of troubles) 2. upgrade it to stretch. There's a tutorial here: https://linuxconfig.org/how-to-upgrade-debian-8-jessie-to-debian-9-stretch Or learn libvirt. I'm happy to help with this if you want to try. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LilyDev4 and Guile2.2 ?
Thanks Federico. I'm debating whether to learn libvirt or take the LilyDev4 upgrade to Debian9 / Guile2.2 path... When looking at this before I tried "Virtual Machine Manager" https://virt-manager.org/ but it didn't work for me (can't remember why now, I didn't go too far into it...). So maybe I should just learn to use libvirt directly. On the one hand VirtualBox is the path of least resistance and would minimize time spent on tooling (at least in short run). On the other hand since you use libvirt, switching to that is probably better over the long-term. -Paul ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LilyDev4 and Guile2.2 ?
2017-04-13 20:11 GMT+02:00 Paul : > Thanks Federico. I'm debating whether to learn libvirt or take the LilyDev4 > upgrade to Debian9 / Guile2.2 path... > > When looking at this before I tried "Virtual Machine Manager" > https://virt-manager.org/ but it didn't work for me (can't remember why > now, I didn't go too far into it...). So maybe I should just learn to use > libvirt directly. > > On the one hand VirtualBox is the path of least resistance and would > minimize time spent on tooling (at least in short run). On the other hand > since you use libvirt, switching to that is probably better over the > long-term. > > -Paul Hi Paul, meanwhile I do most on my host, not in the VB. I compiled guile-1.8 and guile-2.0.14 from the released tarball and 2.2.0 from the guile-repository. Once compiled it's pretty unexpensive to do 'make install' on the guile-version you wish. Also, I have three times the lilypond-repository, each compiled with a different guile-version. So I can check quickly whatever I need with different versions of lilypond/guile. Probably not the way for you, but very convenient in my eyes. Cheers, Harm ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
using run-translator
Hi list,
I am using `ly:run-translator` to analyze a music expression.
If I use << \\ >> simultaneous expressions with voice separator and set
a key signature at the start of the expression, no voice separation is
done and lily gives a bunch of warnings about colliing notes:
%%
% voicify does not work in ly:run-translator, when a keysignature is given
%mymusic = \new Staff { \time 3/4 \key f \major \relative << { bes'4 }
\\ { g8 f } >> }
%mymusic = \new Staff { \key f \major \relative << { bes'4 } \\ { g8 f }
>> }
% this works without a problem
mymusic = \new Staff { \time 3/4 \relative << { bes'4 } \\ { g8 f } >> }
mylayout = \layout {}
#(ly:run-translator mymusic mylayout)
%%
Do I have to consist some special engraver to the layout used in
run-translator? Or do I have to look for something else?
TIA
Jan-Peter
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: using run-translator
Jan-Peter Voigt writes:
> Hi list,
>
> I am using `ly:run-translator` to analyze a music expression.
> If I use << \\ >> simultaneous expressions with voice separator and
> set a key signature at the start of the expression, no voice
> separation is done and lily gives a bunch of warnings about colliing
> notes:
>
> %%
> % voicify does not work in ly:run-translator, when a keysignature is given
> %mymusic = \new Staff { \time 3/4 \key f \major \relative << { bes'4 }
> \\ { g8 f } >> }
> %mymusic = \new Staff { \key f \major \relative << { bes'4 } \\ { g8 f
> }
>>> }
> % this works without a problem
> mymusic = \new Staff { \time 3/4 \relative << { bes'4 } \\ { g8 f } >> }
> mylayout = \layout {}
>
> #(ly:run-translator mymusic mylayout)
> %%
>
> Do I have to consist some special engraver to the layout used in
> run-translator? Or do I have to look for something else?
You should scorify the music expression: a number of stock
transformations including voicification are done when doing that.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LilyDev4 and Guile2.2 ?
On 04/13/2017 02:23 PM, Thomas Morley wrote: Hi Paul, meanwhile I do most on my host, not in the VB. I compiled guile-1.8 and guile-2.0.14 from the released tarball and 2.2.0 from the guile-repository. Once compiled it's pretty unexpensive to do 'make install' on the guile-version you wish. Also, I have three times the lilypond-repository, each compiled with a different guile-version. So I can check quickly whatever I need with different versions of lilypond/guile. Probably not the way for you, but very convenient in my eyes. Hi Harm, Thanks for the info. I thought there were problems with having guile1 and guile2.x installed at the same time? Or is that just if you're relying on package managers? I cloned my working LilyDev4 virtual machine and upgraded it to debian9. The upgrade went fine, but trying to boot into it... same black screen forever after grub screen and 'loading initial ramdisk'... But, using the advanced options on the grub screen I can select Linux 3.16... (instead of 4.9.0...) and it successfully boots. So that's progress. :-) Next step is to install guile2.2 Cheers, -Paul ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
