file writing with lilypond 2.18 and 2.19 fails on windows 10 (SC 3.7.2)

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

file writing with lilypond 2.18 and 2.19 fails on windows 10 (SC 3.7.2)

clemente_rc
This post was updated on .
Hello,

I get an error while doing this on windows 10:

(
p=Pbind(
        \note, Prand([1, 2, 3, 4], 8),
        \dur, 0.25
)
)

f= Fomus(p.asStream, 8)
f.fileName_("/Users/Clemente/Desktop/Pbind")//here is my windows desktop
path
f.ly

the Pbind.fms is created but not the lilypond file as it is used to be.


I remember not have had issues with the same example on windows 10, but I
believe I had SC3.6 installed back then. I've uninstalled and reinstalled
lilypond v 2.16 through 2.19 with no success.

I believe it has to do with some administrator privileges now on win 10, but
who knows?, thanks! RC



Reply | Threaded
Open this post in threaded view
|

Re: file writing with lilypond 2.18 and 2.19 fails on windows 10 (SC 3.7.2)

ddw_music
clemente_rc wrote

> I get an error while doing this on windows 10:
>
> (
> p=Pbind(
>         \note, Prand([1, 2, 3, 4], 8),
>         \dur, 0.25
> )
> )
>
> f= Fomus(p.asStream, 8)
> f.fileName_("/Users/Clemente/Desktop/Pbind")//here is my windows desktop
> path
> f.ly
>
> the Pbind.fms is created but not the lilypond file as it is used to be.

Hint for asking technical questions: If you ever find yourself writing "I
get an error," that's a red flag for you to stop, copy the entire error
text, and paste it into your message.

If the fms file is created, then the path is OK. So it must be some other
problem. But, without the error text, nobody can even begin to guess.

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: http://www.listarc.bham.ac.uk/marchives/sc-users/
search: http://www.listarc.bham.ac.uk/lists/sc-users/search/
Reply | Threaded
Open this post in threaded view
|

Re: file writing with lilypond 2.18 and 2.19 fails on windows 10 (SC 3.7.2)

clemente_rc
Sorry, I didn't paste the first error message because I did not get it any
longer,

if I do this:

(
 p=Pbind(
        \note, Prand([1, 2, 3, 4], 8),
        \dur, 0.25
)
)

f= Fomus(p.asStream, 8)
f.fileName_("/Users/Pbind")//here is the windows path I used to have


I now get the fomus file at the desired path (I reinstalled back lilypond
2.16), but when I want to do this:
f.ly

the lilypond file doesn't appear and there is no longer an error, it simply
doesn't happen anything. Now if I open the file with lilypond itself I get
the following error:

# -*-compilation-*-
Procesando «C:/Users/Pbind.fms»
Analizando...
C:/Users/Pbind.fms:2:16: error: syntax error, unexpected '/'
lily-exe-path =
                /Applications/LilyPond.app/Contents/Resources/bin/lilypond
C:/Users/Pbind.fms:6:6: error: syntax error, unexpected '+', expecting
SCM_FUNCTION or SCM_IDENTIFIER or SCM_TOKEN or '='
 time
      +  duration 0.25 pitch 63;
C:/Users/Pbind.fms:0: advertencia: no se ha encontrado ninguna instrucción
\version, escriba

\version "2.16.2"

para disponer de compatibilidad en el futuro
error fatal: archivos que han fallado: "C:\\Users\\Pbind.fms"


So, I insist I've tried now this on win 10, I have another Windows 7 machine
and I tried and there is no problem. I hope now that I am being more
precise. Thanks. RC.



--
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: http://www.listarc.bham.ac.uk/marchives/sc-users/
search: http://www.listarc.bham.ac.uk/lists/sc-users/search/
Reply | Threaded
Open this post in threaded view
|

Re: file writing with lilypond 2.18 and 2.19 fails on windows 10 (SC 3.7.2)

clemente_rc
In reply to this post by ddw_music
Hello, I got the original error message on another win10 machine

For this:
(
p=Pbind(
        \note, Prand([1, 2, 3, 4], 8),
        \dur, 0.25
)
)

f= Fomus(p.asStream, 8)

//So far I get ok:

-> a Pbind
->  time +  duration 0.25 pitch 62;
 time +  duration 0.25 pitch 64;
 time +  duration 0.25 pitch 64;
 time +  duration 0.25 pitch 63;
 time +  duration 0.25 pitch 62;
 time +  duration 0.25 pitch 64;
 time +  duration 0.25 pitch 62;
 time +  duration 0.25 pitch 61;

It's ok for:
f.fileName_("/Users/Pbind")

->  time +  duration 0.25 pitch 62;
 time +  duration 0.25 pitch 64;
 time +  duration 0.25 pitch 64;
 time +  duration 0.25 pitch 63;
 time +  duration 0.25 pitch 62;
 time +  duration 0.25 pitch 64;
 time +  duration 0.25 pitch 62;
 time +  duration 0.25 pitch 61;

But when creating the .ly file, I get:

ERROR: Primitive '_FileWrite' failed.
Failed.
RECEIVER:
Instance of File {    (00000153D838C0A8, gc=3C, fmt=00, flg=00, set=02)
  instance variables [1]
    fileptr : nil
}
PATH: C:/Users/Clemente/Documents/Scanned Music/SCWIN10/inicios tumbando
piano chords.scd
CALL STACK:
        MethodError:reportError   00000153D74925C8
                arg this = <instance of PrimitiveFailedError>
        Nil:handleError   00000153D742AF28
                arg this = nil
                arg error = <instance of PrimitiveFailedError>
        Thread:handleError   00000153D74690E8
                arg this = <instance of Thread>
                arg error = <instance of PrimitiveFailedError>
        Object:throw   00000153D73ED258
                arg this = <instance of PrimitiveFailedError>
        Object:primitiveFailed   00000153D7252B38
                arg this = <instance of File>
        Fomus:write   00000153D74E1E28
                arg this = <instance of Fomus>
                var file = <instance of File>
        Fomus:ly   00000153D74AF4A8
                arg this = <instance of Fomus>
        Interpreter:interpretPrintCmdLine   00000153D87D9DB8
                arg this = <instance of Interpreter>
                var res = nil
                var func = <instance of Function>
                var code = "f.ly"
                var doc = nil
                var ideClass = <instance of Meta_ScIDE>
        Process:interpretPrintCmdLine   00000153D74EB218
                arg this = <instance of Main>
^^ The preceding error dump is for ERROR: Primitive '_FileWrite' failed.
Failed.
RECEIVER: a File


Notice that the path on error display does not correspond to the one I
assigned, but it's another path a had previously used.

I restart SC, run the test again and I get:

ERROR: Primitive '_FileWrite' failed.
Failed.
RECEIVER:
Instance of File {    (00000291C506AE58, gc=B8, fmt=00, flg=00, set=02)
  instance variables [1]
    fileptr : nil
}
PATH: C:/Users/Clemente/Downloads/test.scd
CALL STACK:
        MethodError:reportError   00000291C3F141B8
                arg this = <instance of PrimitiveFailedError>
        Nil:handleError   00000291C33CAD48
                arg this = nil
                arg error = <instance of PrimitiveFailedError>
        Thread:handleError   00000291C2C3B0B8
                arg this = <instance of Thread>
                arg error = <instance of PrimitiveFailedError>
        Object:throw   00000291C35CD708
                arg this = <instance of PrimitiveFailedError>
        Object:primitiveFailed   00000291C2ACE178
                arg this = <instance of File>
        Fomus:write   00000291C3DC2BE8
                arg this = <instance of Fomus>
                var file = <instance of File>
        Fomus:ly   00000291C4082B28
                arg this = <instance of Fomus>
        Interpreter:interpretPrintCmdLine   00000291C3F94018
                arg this = <instance of Interpreter>
                var res = nil
                var func = <instance of Function>
                var code = "f.ly"
                var doc = nil
                var ideClass = <instance of Meta_ScIDE>
        Process:interpretPrintCmdLine   00000291C2DC5708
                arg this = <instance of Main>
^^ The preceding error dump is for ERROR: Primitive '_FileWrite' failed.
Failed.
RECEIVER: a File



Notice again that the path has changed.

I do change the path to my desktop:

(
p=Pbind(
        \note, Prand([1, 2, 3, 4], 8),
        \dur, 0.25
)
)

f= Fomus(p.asStream, 8)
f.fileName_("/Users/Clemente/Desktop/Pbind")   //here is my windows desktop
path
f.ly

& I get:

-> a Pbind
->  time +  duration 0.25 pitch 62;
 time +  duration 0.25 pitch 63;
 time +  duration 0.25 pitch 62;
 time +  duration 0.25 pitch 62;
 time +  duration 0.25 pitch 63;
 time +  duration 0.25 pitch 63;
 time +  duration 0.25 pitch 64;
 time +  duration 0.25 pitch 63;

->  time +  duration 0.25 pitch 62;
 time +  duration 0.25 pitch 63;
 time +  duration 0.25 pitch 62;
 time +  duration 0.25 pitch 62;
 time +  duration 0.25 pitch 63;
 time +  duration 0.25 pitch 63;
 time +  duration 0.25 pitch 64;
 time +  duration 0.25 pitch 63;

->  time +  duration 0.25 pitch 62;
 time +  duration 0.25 pitch 63;
 time +  duration 0.25 pitch 62;
 time +  duration 0.25 pitch 62;
 time +  duration 0.25 pitch 63;
 time +  duration 0.25 pitch 63;
 time +  duration 0.25 pitch 64;
 time +  duration 0.25 pitch 63;

Now there is no error displayed on SC now but the .fms file is created,
however the .ly file is not created.



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
lily-exe-path =
                /Applications/LilyPond.app/Contents/Resources/bin/lilypond
C:/Users/Clemente/Desktop/Pbind.fms:2:43: error: syntax error, unexpected
'/', expecting '='
lily-exe-path = /Applications/LilyPond.app
                                          /Contents/Resources/bin/lilypond
C:/Users/Clemente/Desktop/Pbind.fms:6:7: error: syntax error, unexpected
'+', expecting '.' or '=' or ','
 time
      +  duration 0.25 pitch 62;
C:/Users/Clemente/Desktop/Pbind.fms:6:32: error: carácter o combinación
abreviada no definida: ;
 time +  duration 0.25 pitch 62
                               ;
C:/Users/Clemente/Desktop/Pbind.fms:7:32: error: carácter o combinación
abreviada no definida: ;
 time +  duration 0.25 pitch 63
                               ;
C:/Users/Clemente/Desktop/Pbind.fms:8:32: error: carácter o combinación
abreviada no definida: ;
 time +  duration 0.25 pitch 62
                               ;
C:/Users/Clemente/Desktop/Pbind.fms:9:32: error: carácter o combinación
abreviada no definida: ;
 time +  duration 0.25 pitch 62
                               ;
C:/Users/Clemente/Desktop/Pbind.fms:10:32: error: carácter o combinación
abreviada no definida: ;
 time +  duration 0.25 pitch 63
                               ;
C:/Users/Clemente/Desktop/Pbind.fms:11:32: error: carácter o combinación
abreviada no definida: ;
 time +  duration 0.25 pitch 63
                               ;
C:/Users/Clemente/Desktop/Pbind.fms:12:32: error: carácter o combinación
abreviada no definida: ;
 time +  duration 0.25 pitch 64
                               ;
C:/Users/Clemente/Desktop/Pbind.fms:13:32: error: carácter o combinación
abreviada no definida: ;
 time +  duration 0.25 pitch 63
                               ;
C:/Users/Clemente/Desktop/Pbind.fms:1: advertencia: no se ha encontrado
ninguna instrucción \version, escriba

\version "2.19.55"

para disponer de compatibilidad en el futuro
error fatal: archivos que han fallado:
"C:\\Users\\Clemente\\Desktop\\Pbind.fms"



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).


Well I hope the displayed messages can help. Thanks. RC




--
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: http://www.listarc.bham.ac.uk/marchives/sc-users/
search: http://www.listarc.bham.ac.uk/lists/sc-users/search/
Reply | Threaded
Open this post in threaded view
|

Re: file writing with lilypond 2.18 and 2.19 fails on windows 10 (SC 3.7.2)

ddw_music
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: http://www.listarc.bham.ac.uk/marchives/sc-users/
search: http://www.listarc.bham.ac.uk/lists/sc-users/search/
Reply | Threaded
Open this post in threaded view
|

Re: file writing with lilypond 2.18 and 2.19 fails on windows 10 (SC 3.7.2)

clemente_rc
Thank you, James, as always,

I understand pretty much all what you have pointed out. First of all, I
should say I am working with the SuperFomus class, which I use in the
Extensions folder, and I am attaching the rar file of the class as I use it.

Just to put it in context, why it all came out, it was because I wanted to
upgrade a win7 machine to win10, and all about fomus and lilypond used to
work smoothly before , but it didn't after the upgrade. I've downgraded back
to win7 and it appears that the problem didn't solve. I am struggling with
the issue eventhough I went bach supposedly to the start point. I must say
too, that I am running same examples I'm posting on an old Mac OS 10.5, and
simultaneously on a very simple win7 notebook, and I am getting no issues
there.

That being said, I'm still trying to figure out what's going on, and let me
tell you I'm not good coding. So, now I am keeping it simple and rename my
files and paths, so they do not seem to mingle.
So I am having this running (on a win10 machine):

(
p = Pbind(
        \note, Prand([2,4,9], inf),
        \dur, Prand([0.25, 0.25, 0.5], inf),
);
)

f= Fomus(p.asStream, 4)
f.fileName_("/Users/Clemente/Desktop/Pbind")   //here is my windows desktop
path
f.ly
f.xml
f.midi

After evaluating each line, I get no error messages, but the following:

-> a Pbind
->  time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 62;
 time +  duration 0.5 pitch 64;
 time +  duration 0.25 pitch 69;

->  time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 62;
 time +  duration 0.5 pitch 64;
 time +  duration 0.25 pitch 69;

->  time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 62;
 time +  duration 0.5 pitch 64;
 time +  duration 0.25 pitch 69;

->  time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 62;
 time +  duration 0.5 pitch 64;
 time +  duration 0.25 pitch 69;

loading input file `/Users/Clemente/Desktop/Pbind.fms'...
processing...
writing output file `/Users/Clemente/Desktop/Pbind.mid'...
done
->  time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 62;
 time +  duration 0.5 pitch 64;
 time +  duration 0.25 pitch 69;


Voilá, it seems there is no problem. However of all files supposed to be
created, only the .fms and .midi are actually on the desktop. Now the
visible difference running the code on SC and I remark this, is that what it
used to happen on normal basis was that the message that appears now only
while creating .mid file:

loading input file `/Users/Clemente/Desktop/Pbind.fms'...
processing...
writing output file `/Users/Clemente/Desktop/Pbind.mid'...
done

used to appear for every file created , of course with the corresponding .ly
and .xml file extension.

Running the code on the old win7 machine renders:

 time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 64;

 time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 64;

loading input file `/Users/Clemente/Desktop/Pbind.fms'...
processing...
writing output file `/Users/Clemente/Desktop/Pbind.ly'...
running LilyPond...
 time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 64;

loading input file `/Users/Clemente/Desktop/Pbind.fms'...
processing...
writing output file `/Users/Clemente/Desktop/Pbind.xml'...
done
 time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 64;

loading input file `/Users/Clemente/Desktop/Pbind.fms'...
processing...
writing output file `/Users/Clemente/Desktop/Pbind.mid'...
done
 time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 69;
 time +  duration 0.25 pitch 64;

And everything is created, smoothly!

Now I attempt creating the files on the command line on win10, and I get
what's on the image:
<http://new-supercollider-mailing-lists-forums-use-these.2681727.n2.nabble.com/file/t395665/fomusstopped.png>

which warns that fomus stopped working and that windows will close the
program, so nothing is created.
However if I insist and run the command line again and again until the .ly
file is created on my desktop, eventhough there is an error displayed on the
command line:
<http://new-supercollider-mailing-lists-forums-use-these.2681727.n2.nabble.com/file/t395665/fomussuccess.png>

but the .ly appears fine and the same happens to the .xml one.

So, to keep it short... on win10 I finnally did it, but there is too much
workaround to do it, and with error messages which were not there before.
So, is there any clue, why is this happening?
Thanks, RC



SuperFomus.rar
<http://new-supercollider-mailing-lists-forums-use-these.2681727.n2.nabble.com/file/t395665/SuperFomus.rar>  



--
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: http://www.listarc.bham.ac.uk/marchives/sc-users/
search: http://www.listarc.bham.ac.uk/lists/sc-users/search/
Reply | Threaded
Open this post in threaded view
|

Re: file writing with lilypond 2.18 and 2.19 fails on windows 10 (SC 3.7.2)

ddw_music
clemente_rc wrote

> Now I attempt creating the files on the command line on win10, and I get
> what's on the image:
> &lt;http://new-supercollider-mailing-lists-forums-use-these.2681727.n2.nabble.com/file/t395665/fomusstopped.png&gt;
>
> which warns that fomus stopped working and that windows will close the
> program, so nothing is created.
> However if I insist and run the command line again and again until the .ly
> file is created on my desktop, eventhough there is an error displayed on
> the
> command line:
> &lt;http://new-supercollider-mailing-lists-forums-use-these.2681727.n2.nabble.com/file/t395665/fomussuccess.png&gt; 
> but the .ly appears fine and the same happens to the .xml one.

If the "fomus" command itself is behaving erratically, from the command line
without any involvement from SuperCollider, then it isn't an SC issue
anymore. You should follow up with the fomus community.

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: http://www.listarc.bham.ac.uk/marchives/sc-users/
search: http://www.listarc.bham.ac.uk/lists/sc-users/search/
Reply | Threaded
Open this post in threaded view
|

Re: file writing with lilypond 2.18 and 2.19 fails on windows 10 (SC 3.7.2)

clemente_rc
Yes, that's definitely a conclusion I arrived to, just today. Anyway, at least you helped me to figure that out, thanks again. Regards, RC


On Wednesday, December 20, 2017, 5:34:11 PM CST, <[hidden email]> wrote:


clemente_rc wrote
> Now I attempt creating the files on the command line on win10, and I get
> what's on the image:
> &lt;<a href="http://new-supercollider-mailing-lists-forums-use-these.2681727.n2.nabble.com/file/t395665/fomusstopped.png>" target="_blank">http://new-supercollider-mailing-lists-forums-use-these.2681727.n2.nabble.com/file/t395665/fomusstopped.png>
>
> which warns that fomus stopped working and that windows will close the
> program, so nothing is created.
> However if I insist and run the command line again and again until the .ly
> file is created on my desktop, eventhough there is an error displayed on
> the
> command line:
> &lt;<a href="http://new-supercollider-mailing-lists-forums-use-these.2681727.n2.nabble.com/file/t395665/fomussuccess.png> " target="_blank">http://new-supercollider-mailing-lists-forums-use-these.2681727.n2.nabble.com/file/t395665/fomussuccess.png>
> but the .ly appears fine and the same happens to the .xml one.

If the "fomus" command itself is behaving erratically, from the command line
without any involvement from SuperCollider, then it isn't an SC issue
anymore. You should follow up with the fomus community.

hjh



--

_______________________________________________
sc-users mailing list

Reply | Threaded
Open this post in threaded view
|

Re: file writing with lilypond 2.18 and 2.19 fails on windows 10 (SC 3.7.2)

bbarros
In reply to this post by ddw_music
On 12/19/17 22:47, [hidden email] wrote:
>
> 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.

I will try to change it, although I don't have a windows machine to test
the change.


_______________________________________________
sc-users mailing list

info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
search: http://www.listarc.bham.ac.uk/lists/sc-users/search/
Reply | Threaded
Open this post in threaded view
|

Re: file writing with lilypond 2.18 and 2.19 fails on windows 10 (SC 3.7.2)

clemente_rc
Wow, that sounds great, I could test it!


On Saturday, December 23, 2017, 11:08:49 AM CST, Bernardo Barros <[hidden email]> wrote:


On 12/19/17 22:47, [hidden email] wrote:
>
> 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.

I will try to change it, although I don't have a windows machine to test
the change.