Location of generated MIDI file (Frescobaldi 2.13)

[cleon...@gmail.com]

As documented in the Lilypond manual, when I place a \midi { ... } command in a .ly source file LilyPond will generate a MIDI file.

When I started using LilyPond/Frescobaldi, just days ago (Windows 7, Lilypond 2.16.2 , Frescobaldi 2.12) the .mid file was written in the same directory as the .ly source file.

Now, just days later (Lilypond 2.18, Frescobaldi 2.13), when a .mid file is generated it isn't written in the obvious place; alongside the .ly source file.


It so happens that I can still retrieve the MIDI file; Frescobaldi writes a copy of the MIDI file in a subdirectory of the temp/ directory that Frescobaldi is using.
To rescue the file I go to:
c:/users/%username%/appdata/local/temp/frescobaldi-pgsxxu/tmp74o0jt/


I'm guessing this is not a Lilypond issue. Lilypond does generate the MIDI file, and Frescobaldi does catch the Lilypond output. But in my case the generated MIDI file isn't written alongside the .ly source file.

Am I overlooking something? I checked the Frescobaldi preferences, and I don't see one that I could have inadvertendly changed to cause this.

[cleon...@gmail.com]

Correction:
Given the date I probably started out with Frescobaldi 2.11

(Anyway, if something changed it is of course more likely to have changed between releases 2.11 and 2.12 )

[Federico Bruni]

2014/1/2 <cleon...@gmail.com>

It so happens that I can still retrieve the MIDI file; Frescobaldi writes a copy of the MIDI file in a subdirectory of the temp/ directory that Frescobaldi is using.
To rescue the file I go to:
c:/users/%username%/appdata/local/temp/frescobaldi-pgsxxu/tmp74o0jt/

this happens if you haven't saved the file

are you sure that you saved it?

[cleon...@gmail.com]

Federico Bruni wrote:

this happens if you haven't saved the file

Thank you, you've cleared it up.

I save often, but not always. In the Frescobaldi preferences the option 'Save document if possible' is unchecked.

When working on a score, trying things out, I don't save before each compilation. I save from time to time.

For the PDF file it makes no difference; the PDF file is _always_ written, regardless of whether the file was re-saved just before compilation. I expected the same behaviour for the MIDI file.

[Federico Bruni]

2014/1/2 <cleon...@gmail.com>

Are you sure?

Here on Linux the behaviour of Frescobaldi is consistent.

If "Save document if possible" is unchecked:

- if you compile without saving, the ly file and the output files are written in the system temporary directory

-  if you save and compile, the changes affect the files in the directory where you chose to save them

you can test it by looking at the modification time

[cleon...@gmail.com]

Federico Bruni wrote:

Are you sure?

Here on Linux the behaviour of Frescobaldi is consistent.

If "Save document if possible" is unchecked:

- if you compile without saving, the ly file and the output files are written in the system temporary directory

-  if you save and compile, the changes affect the files in the directory where you chose to save them

Ah, yes. Modification time.

By the time I want to open the PDF in a separate PDF viewer (I use Sumatra PDF) the score has been recently saved, and I see the current state.

The behaviour only seemed different because the PDF file is written way more often than the MIDI file.

OK, it's consistent. The PDF file and MIDI file are written to the workspace only when the .ly source file is freshly saved.