On Jun 6, 2017, at 15:30, Kieren MacMillan
wrote:
>
>> I guess what you are saying is that if the parts to be combined are each
>> context-specced-music, use those contexts.
>
> Exactly.
The part combiner can also route events to “shared”, “solo”, and “null”
contexts. If you took the step yo
Hi all,
> Got what?
Hmmm… Looks like the list didn't accept my screenshot… =(
Anyway, it was a fatal error.
I have apparently fixed it (?) by uninstalling and doing the whole procedure
again from scratch.
Thanks,
Kieren.
Kieren MacMillan, composer
‣ website:
On 07.06.2017 01:27, Kieren MacMillan wrote:
Hello all,
I'm trying to set up LilyDev.
Running Mac OS X 10.12.5 on an iMac with 16GB RAM.
1. Downloaded the most recent VirtualBox — no problem.
2. Installed VirtualBox — no problem.
3. Launched VirtualBox — no problem.
4. Created my LilyDev vir
Hello all,
I'm trying to set up LilyDev.
Running Mac OS X 10.12.5 on an iMac with 16GB RAM.
1. Downloaded the most recent VirtualBox — no problem.
2. Installed VirtualBox — no problem.
3. Launched VirtualBox — no problem.
4. Created my LilyDev virtual box (as per docs) — no problem.
5. Tried
Hi Carl,
Thanks for the quick response.
> I guess what you are saying is that if the parts to be combined are each
> context-specced-music, use those contexts.
Exactly.
> If they are not, use the default contexts.
In that case, wouldn't parameterized (rather than internally hardcoded) names
h
On 6/6/17 12:45 PM, "lilypond-devel on behalf of Kieren MacMillan"
wrote:
>Hello all,
>
>I'm looking at make-directed-part-combine-music, and wondering why the
>voice names are hard-coded ("one" and "two")Š
>
>It seems to me that if a Voice context passed to partcombine is already
>named, that na
Hello all,
I'm looking at make-directed-part-combine-music, and wondering why the voice
names are hard-coded ("one" and "two")…
It seems to me that if a Voice context passed to partcombine is already named,
that name should be honoured by partcombine. Only if the context is not already
named s
