[sc-users] Re: file writing with lilypond 2.18 and 2.19 fails on windows 10 (SC 3.7.2)

[jamshark70@xxxxxx]

Thanks for the messages. They are indeed helpful.

> PATH: C:/Users/Clemente/Documents/Scanned Music/SCWIN10/inicios tumbando
piano chords.scd

".scd" is a SuperCollider file, not a Fomus ".fms" file. SC tries to
determine the path of the code that was executing when the error occurred.
This is completely irrelevant to the path that was passed to File.

> f.fileName_("/Users/Pbind")

Glancing quickly at the Fomus class, I see that fileName is used as a path
and filename prefix. So it will try to create files like
C:/Users/Pbindxxxxxxx.fms. I'm quite certain that Windows will not allow you
to write arbitrary files directly into /Users. So, the fact that file
writing failed here is not surprising.

You should make sure the directory given in this path really exists, and
that you have write access to it.

> f.fileName_("/Users/Clemente/Desktop/Pbind")
> Now there is no error displayed on SC now but the .fms file is created,

So, you've provided a valid path, and the _FileWrite error disappears.

> however the .ly file is not created.

https://github.com/smoge/superfomus/blob/master/Classes/Fomus.sc#L110

format("fomus %.fms -o %.ly", f, f).runInTerminal;

On my Linux machine, runInTerminal is properly implemented. In Windows:

	runInTerminal {
		"String:runInTerminal - sorry this method has not yet been implemented for
windows.".error;
	}

So, the Fomus quark is currently incompatible with Windows, because it uses
a technique to run external programs that SC does not support in Windows.

You can try changing runInTerminal to unixCmd instead.

This should have posted an error message -- so you should have seen some
sign of something wrong, more than just that the file didn't exist.

> The lilypond error is:
> # -*-compilation-*-
> Procesando «C:/Users/Clemente/Desktop/Pbind.fms»
> Analizando...
> C:/Users/Clemente/Desktop/Pbind.fms:2:17: error: syntax error, unexpected
> '/', expecting \header 

Asking LilyPond to interpret a Fomus file is indeed guaranteed to produce
errors, because Fomus syntax is totally different. ".fms" != ".ly"

> It's very strange, since I believe I didn't have this problem before (I' m
> pretty sure I actually did not have this problem even on win 10 on this
> exact machine where I'm testing now).

I don't see how it could have worked before. The Fomus quark uses a method
that isn't implemented for Windows, simple as that.

hjh



--
Sent from: http://new-supercollider-mailing-lists-forums-use-these.2681727.n2.nabble.com/SuperCollider-Users-New-Use-this-f2676391.html

_______________________________________________
sc-users mailing list

info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/