> I was thinking of something as simple as using the number of beats
> per minute (\tempo ... ) and the the number of beats per bar to work out
> the elapsed time. Obviously this gets more complicated when taking
> tempo changes into account and any partial bars
and repeat sections, which can get
Mats Bengtsson ee.kth.se> writes:
>
> Unfortunately, it may be quite difficult to implement without changing
> major parts of LilyPond, since currently the MIDI generation and the
> printed output are done completely separately, one after the other,
> whereas they would have to be done joint
James Bailey googlemail.com> writes:
> For MacOSX, the program Mighty MIDI can start playback at a
> particular measure and beat.
The tip to use Mighty Midi (I tried it) is perfect for my use as the bars
are numbered by default. Thanks
___
lilypo
On 07.12.2009, at 16:35, Peter Dingley wrote:
I was searching for a way to print out midi elapsed time
in my score to be able to easily start the midi file
at the location I am currently working on. At the moment
I write these in by hand but they change as I
make changes to the music in other
On 07.12.2009, at 16:35, Peter Dingley wrote:
I was searching for a way to print out midi elapsed time
in my score to be able to easily start the midi file
at the location I am currently working on. At the moment
I write these in by hand but they change as I
make changes to the music in other
Unfortunately, it may be quite difficult to implement without changing
major parts of LilyPond, since currently the MIDI generation and the
printed output are done completely separately, one after the other,
whereas they would have to be done jointly to be able to implement your
feature reques
I was searching for a way to print out midi elapsed time
in my score to be able to easily start the midi file
at the location I am currently working on. At the moment
I write these in by hand but they change as I
make changes to the music in other locations. As far as I
could see, there is no w
