<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">Am 29.07.2018 um 18:50 schrieb
<a class="moz-txt-link-abbreviated" href="mailto:liebrecht@grossmann-venter.com">liebrecht@grossmann-venter.com</a>:<br>
</div>
<blockquote type="cite"
cite="mid:e13e914c7d5818b20c0c097b9c423a7c@grossmann-venter.com">Urs,
<br>
<br>
Thanks for thy kind and detailed answer.
<br>
There is currently NO commercial software I could find that can
intermingle TeX and Musical Nortation.
<br>
</blockquote>
<br>
Ah, now I get the connection to your other posts on the Frescobaldi
list ;-)<br>
<br>
<blockquote type="cite"
cite="mid:e13e914c7d5818b20c0c097b9c423a7c@grossmann-venter.com">I
am really thankful that you guys did this.
<br>
Now if only you have a midi interface that could play the Notation
in the document by means of player buttons, but I understand that
doesnt exist yet.
<br>
Frescobaldi does that, but unfortunately cannot add text inline to
scores creating a document.
<br>
<br>
I might want to create such a frontend for lyluatex.
<br>
</blockquote>
<br>
A solution to this is probably not that far-fetched, but in order to
get there you have to either get to a clear understanding of what
you want to achieve or - if you actually have that - communicate it
clearly so we all know where we want to get. I think you have a very
valid use case here that would be good to support.<br>
<br>
I *think* what you will want is to have the score examples
accompanied by *links* (in whatever graphical form, as plain text
links or as fancy graphic buttons). These links should point to
either the MIDI files created by LilyPond, *or* to audio files that
have been generated from these MIDI files in advance. I can think of
no other suitable concept of having a "document" play back the score
examples. If I'm missing anything please correct me.<br>
<br>
Here's what has to be done to achieve that goal. Please create an
issue at <a class="moz-txt-link-freetext" href="https://github.com/jperon/lyluatex/issues">https://github.com/jperon/lyluatex/issues</a> and copy as much
information as possible/useful from this thread. I would not want to
continue discussion here because it really isn't a "luatex" issue
but relates to lyluatex and LilyPond directly:<br>
<ul>
<li>lyluatex has to make LilyPond also produce the MIDI files
beside the scores.<br>
This has not been implemented yet, but should be a minor thing
to do (and as said, I find this a valuable use case)</li>
<li>lyluatex will then (automatically) produce poth a
<unique-hash-name>.pdf and a
<same-unique-hash-name>.midi file in the cache directory</li>
<li>With the 'raw-pdf' option lyluatex will return that calculated
base name instead of directly including the score as an image.</li>
<li>From there you can create a macro that will include the image
and create a link to the midi file.<br>
This can be done with standard LaTeX means<br>
</li>
<li>Or you can add a hook in between to call another external
program to generate the corresponding audio file and link to
that.<br>
This would probably be (much) easier to program in Lua, since
Lua is present anyway.<br>
</li>
</ul>
<br>
<blockquote type="cite"
cite="mid:e13e914c7d5818b20c0c097b9c423a7c@grossmann-venter.com">
<br>
I will take your concerns noted below seriously.
<br>
It is just difficult to figure out the differences between
<br>
luatex, lyluatex, lualatex and which interfaces with lillypond for
someone new to luatex (I am an old-time LaTeX/TeX user though )
<br>
So I will step on your toes for a while unintentionally.
<br>
<br>
<br>
Are you going to remove lyluatex.tex file in future ?
<br>
The reason I ask is that I want to learn lyluatex by studying the
code creating the manual, so I will have to add all the other
packages in the headers of the TeX file.
<br>
If I am not supposed to have it let me know, but the manual does
EXACTLY what I want so it THE example file for me. It has
everything by design.
<br>
</blockquote>
This last assumption is on spot.<br>
And no, we're not going to remove that file.<br>
<br>
In the development repository we author the manual in a Markdown
file, and it is compiled through Pandoc. But the make rule for
producing the CTAN upload the Markdown file is compiled to the
corresponding .tex file. So that lyluatex.tex file is an official
part of the CTAN package (and I would assume that it is also copied
*somewhere* into your texlive installation).<br>
<br>
<br>
<blockquote type="cite"
cite="mid:e13e914c7d5818b20c0c097b9c423a7c@grossmann-venter.com">
<br>
If I am allowed to use it and you have the time and patience...
<br>
1) Are only the packages listed n the header needed to compile the
manual ?
<br>
</blockquote>
<br>
You should also look into the the lyluatex.sty file since that also
loads a number of packages. But AFAIK there are no *special*
packages needed that aren't available in regular TeX Live (I just
don't know what happens if you haven't installed texlive-full).<br>
<br>
<blockquote type="cite"
cite="mid:e13e914c7d5818b20c0c097b9c423a7c@grossmann-venter.com">2)
Are there any other unforseen issues compiling it you know of that
could save me time before I delve into it myself ?
<br>
</blockquote>
<br>
From what I can see in your communications I'm not 100% confident
you have set up LilyPond properly already.<br>
lyluatex does its work by calling LilyPond as an external command,
so that has to be a) installed and b) found by lyluatex.<br>
If you don't have a working environment I suggest downloading the
current development version from
<a class="moz-txt-link-freetext" href="http://lilypond.org/development.html">http://lilypond.org/development.html</a> (they are not at all "unstable"
in the case of LilyPond) and installing it (I don't know what OS you
are having).<br>
<br>
If you are on a UNIX OS and can run "lilypond --version" after the
installation everything should be fine, but if you have to specify
any other command line you have to provide this to lyluatex through
the [program={path/to/lilypond/executable}] option.<br>
<br>
If you still have errors after that please report with more details
- we have tried to make the error handling as informative as
possible - but do so on the lyluatex issue tracker, not here.<br>
<br>
<blockquote type="cite"
cite="mid:e13e914c7d5818b20c0c097b9c423a7c@grossmann-venter.com">
<br>
This is possibly the best music typeset software that I have seen
in my life.
<br>
I cannot think of anything that can beat it.
<br>
Enormous !!!
<br>
Hope the Universities at least will use it and stop teaching
people to be Joe-mousepusher.
<br>
</blockquote>
<br>
Having literally spent years with this topic I can't give you too
much hope about this :-(<br>
<br>
Best<br>
Urs<br>
<br>
<blockquote type="cite"
cite="mid:e13e914c7d5818b20c0c097b9c423a7c@grossmann-venter.com">
<br>
<br>
Thanks
<br>
<br>
On 2018-07-29 12:28, Urs Liska wrote:
<br>
<blockquote type="cite">Am 29.07.2018 um 17:59 schrieb
<a class="moz-txt-link-abbreviated" href="mailto:liebrecht@grossmann-venter.com">liebrecht@grossmann-venter.com</a>:
<br>
<blockquote type="cite">a) Ok good to know that explains the
compiling problems fundamentally.
<br>
If the manual were a lyluatex file it would have been one of
the greatest tutorials right there.
<br>
What I tried to compile is the manual in the zip download here
<br>
<a class="moz-txt-link-rfc2396E" href="https://ctan.org/pkg/lyluatex?lang=en">"https://ctan.org/pkg/lyluatex?lang=en"</a>
<br>
Which seemed to be the lyluatex code, but I am seemingly
mistaken.
<br>
</blockquote>
<br>
No, you're not mistaken. I wasn't aware of the fact that the
script
<br>
preparing the CTAN upload actually produced that lyluatex.tex
file.
<br>
<br>
<blockquote type="cite">
<br>
b) Ok
<br>
<br>
c) Ok I saw that, but where that was mentioned there was no
direct compile instruction. The option --shell-escape was
mentioned in the body text and there was no direct compile
command.
<br>
If
<br>
"lualatex --shell-escape somefile.tex"
<br>
were in the instructions I did not have to ask this question,
but it is absent.
<br>
Would be a good idea to add that.
<br>
</blockquote>
<br>
I'll try to keep that in mind. It would be great if you could
open an
<br>
issue on the Github issue tracker at
<br>
<a class="moz-txt-link-freetext" href="https://github.com/jperon/lyluatex/issues">https://github.com/jperon/lyluatex/issues</a> about it.
<br>
<br>
<blockquote type="cite">
<br>
<br>
Question:
<br>
1) Since I cannot compile the manual and use that to learn
lyluatex, (my preferred latex way to learn is just to work
through the code compiling the manual. (Last 20+ more years
taught me that is by far the best way.)
<br>
Is there an indepth lyluatex manual that is compilable with
luatex ?
<br>
</blockquote>
<br>
This .tex file *is* compilable with lualatex (not luatex!).
<br>
Please first try the other things I told you about, and if that
<br>
doesn't work please post more details about the errors. But this
is
<br>
not a luatex issue, so this list may not be right place to
discuss.
<br>
Please either subscribe to the lilypond-user mailing list or
open an
<br>
issue on the issue tracker.
<br>
<br>
<blockquote type="cite">2) Is there an archive with lots of
lyluatex document examples combining both text and musical
notaion in the document ?
<br>
</blockquote>
<br>
lyluatex is actually brand new, so there is no such archive
(yet).
<br>
<br>
HTH
<br>
Urs
<br>
</blockquote>
</blockquote>
<br>
</body>
</html>