Re: About Timing_translator
Neil Puttock a écrit :
On 4 March 2010 22:14, Philippe Hezaine philippe.heza...@free.fr wrote:
Sorry to carry on a monologue but...
I can even say that when I only write a single time signature like 3/4 in a
single variable the resulting TimeSig in midicomp is 4/4 yet.
Can you post a sample file?
No, I don't want! For the next release the Gigsaw will integrate
randomization. Kudos to Brett Stahlman who gives me a gvim function
which works flawlessly so far. What a song and dance! You'll be able to
destroy all the stuff! You're so strong. :-P
Well! Seriously see below. ( And keep in mind the randomization is a
real thing now)
This reminds me of an old thread,
http://lists.gnu.org/archive/html/bug-lilypond/2009-02/msg00144.html,
where I couldn't verify the bug.
One thing to note is that the Time_signature_performer lives in the
Score context (unlike the Time_signature_engraver), so if you move it
to the Staff context (with the Timing_translator), you should see
separate time signatures in the midi output if you're typesetting
polymetric music.
Regards,
Neil
Keep cool. For standard midi output midicomp shows the right TimeSig.
The interesting thing is when you use Timing-translator in a *midi*
block. It seems layout block is not relevant.
There are 2 examples: the .ly file is written in 3/4.
1. Timing-translator-ex-min-1-midi-block
In this sample:
\context {
% \Score
% \remove Timing_translator
}
is commented out
and
\context { \DrumStaff
\consists Timing_translator
}
is active. I get the midicomp ascii file with a 4/4 TimeSig. (line 6)
2. Timing-translator-ex-min-2-midi-block
Here all is active
\midi {
\context {
\Score
\remove Timing_translator
tempoWholesPerMinute = #(ly:make-moment 110 4)
}
\context { \DrumStaff
\consists Timing_translator
}
}
and I get an ascii file without TimeSig. However if you look at the
timestamps you'll see 4 beats. (They start from 00 to 03.)
Notice the barcheck is commented out. Perhaps it's significant.
If you want others samples with a different config don't hesitate to
ask, it's so easy for me to get these ascii files. I'm your servant.
As I said previously I hope it isn't a bug. Anyway midi output is OK.
As if it was the most natural thing in the world Lilypond do all the
maths with brilliance.
Oh please, if you destroy all the stuff send me a post! :)
--
Phil.
Timing-translator-ex-min-1-midi-block.asc
Description: PGP signature
\version 2.12.2
#(ly:set-option 'delete-intermediate-files #t)
pulse = \drummode {
\time 3/4
\tempo 4 = 110
bd_\ff cymca_\mp8 r8 ss_\fff cab_\fff16 cab16_\mf cab8_\ff ss_\fff cab_\sf16 cab16_\mf r8 %|
bd8_\ff r8 r2 %|
\bar |.
}
\score {
\new DrumStaff
\new DrumVoice { \pulse }
\layout {
}
\midi {
\context {
% \Score
% \remove Timing_translator
tempoWholesPerMinute = #(ly:make-moment 110 4)
}
\context { \DrumStaff
\consists Timing_translator
}
}
}
Timing-translator-ex-min-2-midi-block.asc
Description: PGP signature
\version 2.12.2
#(ly:set-option 'delete-intermediate-files #t)
pulse = \drummode {
\time 3/4
\tempo 4 = 110
bd_\ff cymca_\mp8 r8 ss_\fff cab_\fff16 cab16_\mf cab8_\ff ss_\fff cab_\sf16 cab16_\mf r8 %|
bd8_\ff r8 r2 %|
\bar |.
}
\score {
\new DrumStaff
\new DrumVoice { \pulse }
\layout {
}
\midi {
\context {
\Score
\remove Timing_translator
tempoWholesPerMinute = #(ly:make-moment 110 4)
}
\context { \DrumStaff
\consists Timing_translator
}
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: About Timing_translator
On 4 March 2010 22:14, Philippe Hezaine philippe.heza...@free.fr wrote: Sorry to carry on a monologue but... I can even say that when I only write a single time signature like 3/4 in a single variable the resulting TimeSig in midicomp is 4/4 yet. Can you post a sample file? This reminds me of an old thread, http://lists.gnu.org/archive/html/bug-lilypond/2009-02/msg00144.html, where I couldn't verify the bug. One thing to note is that the Time_signature_performer lives in the Score context (unlike the Time_signature_engraver), so if you move it to the Staff context (with the Timing_translator), you should see separate time signatures in the midi output if you're typesetting polymetric music. Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: About Timing_translator
On Tue, Mar 9, 2010 at 12:00 AM, Neil Puttock n.putt...@gmail.com wrote: This reminds me of an old thread, http://lists.gnu.org/archive/html/bug-lilypond/2009-02/msg00144.html, where I couldn't verify the bug. Wow, impressive. Thanks for digging that up :) Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: About Timing_translator
Philippe Hezaine a écrit :
Philippe Hezaine a écrit :
Hi,
In the Gigsaw's process I use Timing_translator in midi block like this:
\midi {
\context {
\Score
%%%\remove Timing_translator
tempoWholesPerMinute = #(ly:make-moment 100 4)
}
\context { \Staff
\consists Timing_translator
}
\context { \DrumStaff
\consists Timing_translator
}
}
and use midicomp to get the specific midi file. I've made a lot of tests
with different time signature and unimaginable polymetric score and I
*always* see the time signature to be 4/4 18 8 in midicomp's header,
whatever I write in MY-SONG.ly. I'm more than very interested in this
information. I'm feeling the Lily's math calculation in this case are
*always* processed from a quarter note within a 4/4. I mean in this case
Lilypond digests all the math with a 'concatenation' when it outputs
midi file. (I hope you understand me). Logical, nifty... GNU...
basically! Is someone can definitively confirm this impression? Or
points me on a deeper source? I'd want to avoid a bad surprise later.
Thanks.
May be I can ask in a different way:
For instance I write a polymetric score with 5/8, 7/16 and 3/4 time
signatures. In the Gigsaw's midi block I don't remove Timing_translator
in the Score context but activate it in Staff and Drumstaff contexts. So
for the partition Lilypond takes in account time signatures but for
output midi it assembles all the stuff in a 4/4 and does the maths. Am I
right when I say it *always* does that with my configuration in midi
block? So I believe.
Could someone confirm my hypothesis? (which is not a flight of fancy)
Sorry to carry on a monologue but...
I can even say that when I only write a single time signature like 3/4
in a single variable the resulting TimeSig in midicomp is 4/4 yet.
It recall me my primary try with Lilypond, you know, when you type
{ a b c d e f g a } in your first .ly file and you see a scale of
quarter notes. By default Lilypond prints a quarter value.
I hope my configuration activates a kind of this default behaviour for midi.
I'm especially hoping it isn't a bug.
I will be annoyed, frustrated because I plan to use this feature in the
Gigsaw.
--
Phil.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
About Timing_translator
Hi,
In the Gigsaw's process I use Timing_translator in midi block like this:
\midi {
\context {
\Score
%%%\remove Timing_translator
tempoWholesPerMinute = #(ly:make-moment 100 4)
}
\context { \Staff
\consists Timing_translator
}
\context { \DrumStaff
\consists Timing_translator
}
}
and use midicomp to get the specific midi file. I've made a lot of tests
with different time signature and unimaginable polymetric score and I
*always* see the time signature to be 4/4 18 8 in midicomp's header,
whatever I write in MY-SONG.ly. I'm more than very interested in this
information. I'm feeling the Lily's math calculation in this case are
*always* processed from a quarter note within a 4/4. I mean in this case
Lilypond digests all the math with a 'concatenation' when it outputs
midi file. (I hope you understand me). Logical, nifty... GNU...
basically! Is someone can definitively confirm this impression? Or
points me on a deeper source? I'd want to avoid a bad surprise later.
Thanks.
--
Phil.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: About Timing_translator
Philippe Hezaine a écrit :
Hi,
In the Gigsaw's process I use Timing_translator in midi block like this:
\midi {
\context {
\Score
%%%\remove Timing_translator
tempoWholesPerMinute = #(ly:make-moment 100 4)
}
\context { \Staff
\consists Timing_translator
}
\context { \DrumStaff
\consists Timing_translator
}
}
and use midicomp to get the specific midi file. I've made a lot of tests
with different time signature and unimaginable polymetric score and I
*always* see the time signature to be 4/4 18 8 in midicomp's header,
whatever I write in MY-SONG.ly. I'm more than very interested in this
information. I'm feeling the Lily's math calculation in this case are
*always* processed from a quarter note within a 4/4. I mean in this case
Lilypond digests all the math with a 'concatenation' when it outputs
midi file. (I hope you understand me). Logical, nifty... GNU...
basically! Is someone can definitively confirm this impression? Or
points me on a deeper source? I'd want to avoid a bad surprise later.
Thanks.
May be I can ask in a different way:
For instance I write a polymetric score with 5/8, 7/16 and 3/4 time
signatures. In the Gigsaw's midi block I don't remove Timing_translator
in the Score context but activate it in Staff and Drumstaff contexts. So
for the partition Lilypond takes in account time signatures but for
output midi it assembles all the stuff in a 4/4 and does the maths. Am I
right when I say it *always* does that with my configuration in midi
block? So I believe.
Could someone confirm my hypothesis? (which is not a flight of fancy)
--
Phil.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
