FoscIOManager:openFile: path does not exist

[sarcman]

a = FoscNote(60, 1/4);
a.show;

I get the following error in SuperCollider on an Apple M1:

ERROR: FoscIOManager:openFile: path does not exist: /Users/name/Library/Application Support/SuperCollider/fosc-output/0001.pdf.
CALL STACK:
Object:reportError
arg this = "FoscIOManager:openFile: path..."
Nil:handleError
arg this = nil
arg error = "FoscIOManager:openFile: path..."
Thread:handleError
arg this =
arg error = "FoscIOManager:openFile: path..."
Object:throw
arg this = "FoscIOManager:openFile: path..."
Meta_FoscIOManager:openFile
arg this =
arg path = "/Users/name/Library/A..."
Fosc:show
arg this =
arg paperSize = nil
arg staffSize = nil
arg includes = nil
var illustrateEnvir =
var path = "/Users/name/Library/A..."
Interpreter:interpretPrintCmdLine
arg this =
var res = nil
var func =
var code = "a.show;"
var doc = nil
var ideClass =
Process:interpretPrintCmdLine
arg this =

---

The 0001.ly file created within fosc-output contains the following:

\version "2.24.1"
\language "english"

\include "/Users/name/Library/Application Support/SuperCollider/Extensions/fosc/stylesheets/default.ily"

\score {
{
c'4
}
}

---

[n-armstrong]

That's odd indeed! There's a few internal mechanisms that rely on calls to Platform.userExtensionDir to get and set key file paths. Just to check before we move on -- do you really have a user account and corresponding directory called 'name'? As that's what is being returned by the call to Platform.userExtensionDir.

[sarcman]

Hi !
no, I simply replaced my "account-name" with "name" in a text editor for simplicity

Btw, Lilypond seems to work fine on its own via the terminal

[n-armstrong]

I'm not sure that I understand what you're doing. The error dump in your first message shows that FoscIOManager is looking for files in "/Users/name/...", which obviously don't exist. If you're editing the filepaths independently then you're likely to break dependencies that are generated internally.

Where have you placed the 'fosc' directory? Is it in the same location that SC returns when you call Platform.userExtensionDir?

[sarcman]

Forgive me if I haven't made it clear.

FoscIOManager is looking for a pdf file to open which should live in:
"/Users/name/Library/Application Support/SuperCollider/fosc-output/"

The lilypond file (0001.ly) gets created within the fosc-output folder without an issue it seems,
however the pdf file isn't created, hence FoscIOManager complains that it has nothing to open

The fosc folder lives inside the Extensions foler:
/Users/name/Library/Application Support/SuperCollider/Extensions

[n-armstrong]

Yes, I can see that much. What I'm trying to understand is your comment from a couple of post's back which suggested that you had edited some of the file paths. Or is it the case that you've only edited them for what you're posting here, and that the file path is correct (i.e. something different to '/Users/name') in all of the error dumps and the \include section of the ly file?

[n-armstrong]

The other possibility -- assuming that the filepaths are not being changed -- is that Fosc.lilypondPath hasn't been set correctly. This would mean that the PDF never gets generated from the LY file. Could you run the following snippet and send back the post output?:

FoscIOManager.runLilypond("%/0001.ly".format(Fosc.outputDirectory));

[sarcman]

I see. The file paths are correct.

The latest code snippet returns -> false

[n-armstrong]

OK, we've found the issue! If you look in the 'Configure Fosc' subsection in the 'Installation' part of the README, you'll see a bit on setting Fosc.lilypondPath in your SC startup file. This is the only bit of manual configuration that you need to do, but it has to be done properly for Fosc to be able to compile lilypond files. The key thing is that the path is set to the lilypond executable that you're using. If you're not sure where it is, you should be able to locate it by running this in a terminal: which lilypond

[sarcman]

Fosc.lilypondPath = "/opt/local/bin/lilypond"; This path has been set in the startup.scd file, and Fosc seems happy to call LilyPond, as Fosc.lilypondVersion; returns -> 2.24.1

[n-armstrong]

Great. That means that your example from the start of the thread should work now.

[sarcman]

Well, the path had been set from the start ! But it throws the error even though Fosc is able to call LilyPond.
The pdf file cannot be created for some reason.

[n-armstrong]

Hmm, that's odd. What happens when you call: Fosc.lilypondPath

[sarcman]

-> /opt/local/bin/lilypond

[n-armstrong]

And what happens when you run the following from a terminal (with the correct user path substituted):

/opt/local/bin/lilypond "/Users/name/Library/Application Support/SuperCollider/fosc-output/0001.pdf"

[n-armstrong]

Sorry, that should have been:

/opt/local/bin/lilypond "/Users/name/Library/Application Support/SuperCollider/fosc-output/0001.ly"