MIDI player plays old file after engraving

[GoogleCodeExporter]

Es gibt noch ein Problem mit dem MIDI-Player. Wenn ich die Musik engrave, sagt 
mir das Log-Fenster:

"MIDI-Ausgabe nach »es ist gut 004.midi«..."

Wenn ich dann das MIDI mit dem build-in player abspielen lassen will, wird das 
alte MIDI-file vor dem engraven gespielt. Erst wenn ich speichere und dann 
engrave spielt der build-in player das aktuelle MIDI ab.

Ich nutze Debian Squeeze, Lilypond 2.12.3 und Frescobaldi 1.9.5.

----------

There seems to be a problem with the MIDI-player. Wenn I engrave des Music, the 
LOG says:

"MIDI-output to >es ist gut 004.midi<"

When I try to play the new file with the build-in player, the player takes the 
old MIDI before engraving. When I save first before engraving, it works. Is 
this a bug o r do I something wrong?

I use Debian Squeeze, Lilypond 2.12.3 and Frescobaldi 1.9.5.

Original issue reported on code.google.com by kropp@koelnklassik.de on 22 Dec 2011 at 11:09

[GoogleCodeExporter]

I forgot ... I engrave with Ctrl+M with default preferences.

Original comment by kropp@koelnklassik.de on 22 Dec 2011 at 11:16

[GoogleCodeExporter]

When the MIDI player is playing while a new engraving job finishes, the MIDI 
file is not immediately replaced; as that would disrupt the playing.

If no MIDI file is playing, the new MIDI file (if created) is loaded 
immediately.

But if you restart the MIDI file (so that it goes to the beginning) it is 
immediately reloaded if a new file has been created.

Original comment by wbsoft on 22 Dec 2011 at 1:19

[GoogleCodeExporter]

This has been fixed, will be in Frescobaldi 2.0.2! Thanks for reporting!

Please report issues with Frescobaldi 2 in the GitHub issue tracker:
https://github.com/wbsoft/frescobaldi/issues

Original comment by wbsoft on 14 Jan 2012 at 6:51

• Changed state: Fixed