I think I can do what you want in MusiXTeX with the ossia philosophy.
I used the tuplet package, but it seems if I want to shorten the tuplet
length the gap which accomodates the '3' diseappears.
Regards,
Jean-Pierre Coulon cou...@obs-nice.fr\input musixtex
\input tuplet
Jill-Jênn VIE wrote:
Is there a way in PMX (or, I bet, rather MusiXTeX) to put the well-known
swing tempo indication:
http://totalguitarist.com/lessons/reading/notation/guide/notes-and-
rhythm/swung-8th-notes.gif ?
Afraid I don't quite have enough time this morning to try it myself, but in
Here is another way of achieving it (with PSTricks):
---
\input pstricks\relax
\input pst-node\relax
\input musixtex\relax
\input musixlyr\relax
\setlyrics{solo}{%
No-bo-dy knows the trou-ble I see No-bo-dy knows my sor-row}
\assignlyrics{1}{solo}
\setsongraise{1}{2\internote}
Bob Tennent wrote:
Last November, Dirk Laurie suggested that we should be porting the M-
Tx/PMX/musixtex/musixflx toolchain to LuaTeX. I won't review his arguments
here, but I'm pleased to report that Nikhil Helferty, a student here, has
successfully converted musixflx.c (version 0.83.3) to
|i had, in fact, vaguely thought of making musixflx into a separate ctan
|package (it's already separate from musixtex in the distributions,
|brought in by their requirement directives[*]).
|
|doing that would involve breaking your structure, but i think it would
|add clarity to the
| It should be functionally identical to musixflx.c (up to round-off
|error).
|
|Is this just a throw-away line or are there actual systemic differences
|in the precision of the floating point variables used? Floating point
|calculations are a CPU function - it would be beneficial if the
On Sun, Apr 10, 2011 at 12:55:58PM +0200, David Allsopp wrote:
Bob Tennent wrote:
It should be functionally identical to musixflx.c (up to round-off error).
Is this just a throw-away line or are there actual systemic differences in
the precision of the floating point variables used?
7 matches
Mail list logo
