|
Hi,
thanks for the fast response!
Everything worked fine, even the patch command without extra
installation (don't know what happened before)
Like you I was able to make the video from "Wolf_Resignation"and
"JSBI1" from here:
http://lilypond.1069038.n5.nabble.com/Video-generation-bash-script-keeps-sync-in-spite-of-tempo-changes-td194245.html
The only thing missing was the color of the active notes.
As far as I understand the files, the wanted color is set in the
mkvideo-lily-diff:
+
+/MKVIDcolor { 0.7 0.0 1.0 } def % color to use
+ %
Is that right?
And do I have to activate the color-change somewhere? Or is there
maybe something else wrong?
Thanks a lot!
Am 04.11.2017 um 22:55 schrieb Karlin
High:
On
11/4/2017 2:25 PM, christian wrote:
I have a question concerning patching scm
and ps files:
Can anyone tell me where to find them? I'm not that firm with
this
and couldn't find them after searching quite a while.
The other thing is: Do I have to install something to use the
patch command?
I get an error message "unknown command"
To reiterate, The Knut Petersen mkvideo files are available in
this lilypond-user posting:
https://lists.gnu.org/archive/html/lilypond-user/2017-07/msg00234.html
I think this feature shows great promise. Further exploring this
is high on my LilyPond to-do list. But at this point, getting set
up for the mkvideo features seems to me like a "void your
warranty" operation. Great fun, but ideally try it on a separate
copy of lilypond if you still want to have the standard,
unmodified version available. That could involve downloading one
of the Linux source or binary packages, or doing a Git clone or
checkout. All available here:
http://lilypond.org/development.html
You shouldn't need to find the scm and ps files individually. The
patch command will do that itself if properly directed. By
observing the diff file...
https://lists.gnu.org/archive/html/lilypond-user/2017-07/txtZbTxhQPWxz.txt
...you can see everything that will be changed by the patch
command:
--- ./origscm/output-ps.scm 2016-11-21 05:26:10.894702197 +0100
+++ ./scm/output-ps.scm 2017-07-20 06:35:48.233783884 +0200
@@ -204,10 +204,11 @@
The file with the +++ before it is the one being changed. Below
that, the @@ shows the starting point in the file, then any line
with a - minus sign is being removed, and the ones with a + plus
sign are being added.
Now, check if the patch command is available on your system.
address@hidden:~$ whereis patch
patch: /usr/bin/patch /usr/share/man/man1/patch.1.gz
If it just says "patch:" with no file path, then I expect it needs
installation, maybe something like this...
address@hidden:~$ sudo apt-get install patch
...or however you are used to installing Debian packages.
Then, find the directory containing the LilyPond files. If you
just downloaded and extracted it, you can run the search from that
directory instead of doing "cd /" first.
address@hidden:~$ cd /
address@hidden:/$ sudo find -name output-ps.scm
On my system, the output includes this:
./mnt/sdb1/LilyDevOS/lilydevos-0.1/home/dev/lilypond-git/scm/output-ps.scm
./mnt/sdb1/lilyvideo/lilypond/usr/share/lilypond/current/scm/output-ps.scm
Yours will be different. The level above the last directory is the
place to be. When you can run the ls command and get this...
fonts ly ps python scm vim
...you are there, and ready to run patch. If you had the diff file
in the home directory, maybe something like this:
$ patch -p 1 < ~/mkvideo-lily-diff
That should change everything that needs changing for this. All
instructions here are subject to correction by list members with
greater Linux and LilyPond skills.
Follwing Knut's instructions, I was able to get the
Wolf_Resignation video produced, but none of my own projects yet.
Knut? This thing really needs a Tiny Example. Could you make a
video project with just a C-major scale or something? I love
looking at other people's lilypond code for picking up tips and
inspiration, but in this case my mediocre lilypond skills got
drowned while trying to understand all the different \book outputs
at the end. I couldn't easily tell which code was needed for video
projects and which was just the Knut Petersen standard for coding
style and project structure.
|