Fomus on Ubuntu

[Peter O'Doherty-2]

Hi,
I get the error

>>> Error: don't know how to open "fomus.ly" 

when I try to run the Fomus example.

I don't get

>>> Error: Fomus: can't find FOMUS library

as Fomus is properly installed (libfomus.so is in /usr/local/lib).

Can someone please assist?

Many thanks,
Peter

On Sun, 2010-12-05 at 11:11 -0500, Joel Matthys wrote:

> I can't get FOMUS to work with the new Grace on Ubuntu 10.04.
> 
> When I open the example file and try to evaluate the first example, I
> get
> >>> Error: Fomus: can't find FOMUS library
> >>> Error: don't know how to open "fomus.ly" 
> 
> _______________________________________________
> Cmdist mailing list
> Cmdist at ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist

_______________________________________________
Cmdist mailing list
Cmdist@...
http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist

[Heinrich Taube]

hi - what version of Grace and Fomus are you using?  information for  
both should be visible in the herald when you start the app. did you  
build from sources our are you using a binary release?


On Aug 19, 2011, at 3:41 AM, Peter O'Doherty wrote:

> Hi,
> I get the error
> >>> Error: don't know how to open "fomus.ly"
> when I try to run the Fomus example.
>
> I don't get
> >>> Error: Fomus: can't find FOMUS library
> as Fomus is properly installed (libfomus.so is in /usr/local/lib).
>
> Can someone please assist?
>
> Many thanks,
> Peter
>
>
> On Sun, 2010-12-05 at 11:11 -0500, Joel Matthys wrote:
>
> > I can't get FOMUS to work with the new Grace on Ubuntu 10.04.
> >
> > When I open the example file and try to evaluate the first  
> example, I
> > get
> > >>> Error: Fomus: can't find FOMUS library
> > >>> Error: don't know how to open "fomus.ly"
> >
> > _______________________________________________
> > Cmdist mailing list
> > Cmdist at ccrma.stanford.edu
> > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist
>
>
>
>
> --
> //=============================
> -> Peter O'Doherty
> -> http://www.peterodoherty.net
> -> mail@...
> //=============================
> _______________________________________________
> Cmdist mailing list
> Cmdist@...
> http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist

_______________________________________________
Cmdist mailing list
Cmdist@...
http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist

[Peter O'Doherty-2]

Hi Heinrich,

On 08/19/2011 02:07 PM, Heinrich Taube wrote:
> hi - what version of Grace and Fomus are you using?

This is what the console shows after starting the .Grace binary in my
~/cm/cm/bin directory:


Grace 3.8.0 [svn:1946] (c) 2011 Rick Taube
JUCE v1.52.110 (c) 2011 Julian Storer
S7 Scheme 1.86 (11-May-11) (c) 2011 William Schottstaedt
  /\\\
---\\\---------
----\\\--------
----/\\\------- Common Music 3.8.0
---/--\\\------
--/----\\\-----
  /      \\\/


My version of Fomus is: FOMUS 0.1.15-alpha.

> information for both should be visible in the herald when you start
> the app. did you build from sources our are you using a binary release?


To be honest, I can't remember. I think I built from sources.
Thanks,
Peter

>
>
> On Aug 19, 2011, at 3:41 AM, Peter O'Doherty wrote:
>
>> Hi,
>> I get the error
>> >>> Error: don't know how to open "fomus.ly"
>> when I try to run the Fomus example.
>>
>> I don't get
>> >>> Error: Fomus: can't find FOMUS library
>> as Fomus is properly installed (libfomus.so is in /usr/local/lib).
>>
>> Can someone please assist?
>>
>> Many thanks,
>> Peter
>>
>>
>> On Sun, 2010-12-05 at 11:11 -0500, Joel Matthys wrote:
>>
>> > I can't get FOMUS to work with the new Grace on Ubuntu 10.04.
>> >
>> > When I open the example file and try to evaluate the first example, I
>> > get
>> > >>> Error: Fomus: can't find FOMUS library
>> > >>> Error: don't know how to open "fomus.ly"
>> >
>> > _______________________________________________
>> > Cmdist mailing list
>> > Cmdist at ccrma.stanford.edu
>> > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist
>>
>>
>>
>>
>> --
>> //=============================
>> -> Peter O'Doherty
>> -> http://www.peterodoherty.net
>> -> mail@...
>> //=============================
>> _______________________________________________
>> Cmdist mailing list
>> Cmdist@...
>> http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist
>
>

--
//=============================
->  Peter O'Doherty
->  http://www.peterodoherty.net
->  mail@...
//=============================

_______________________________________________
Cmdist mailing list
Cmdist@...
http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist

[Heinrich Taube]

ok then perhaps you didnt enable fomus when you built from source.  
assuming you installed fomus in /usr/local do this:

cd cm
rm -r obj bin
premake --verbose --target gnu --sndlib /PATH/TO/SNDLIB  --fomus /usr/
local
make
bin/Grace &


see the readme for other build options.

ill make a binary 8.3.0 release in the next few days.


> To be honest, I can't remember. I think I built from sources.
> Thanks,
> Peter

_______________________________________________
Cmdist mailing list
Cmdist@...
http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist

[Heinrich Taube]

On Aug 19, 2011, at 7:18 AM, Peter O'Doherty wrote:

> Grace 3.8.0 [svn:1946] (c) 2011 Rick Taube
> JUCE v1.52.110 (c) 2011 Julian Storer
> S7 Scheme 1.86 (11-May-11) (c) 2011 William Schottstaedt

yes you didnt build the c sources with fomus option enabled, if you  
had you would see it listed in the herald.
i would also install a new sndlib before reloading and do an 'svn  
update'  in the cm directory -- the latest svn version is 1953

to install a sndlib do

mv sndlib /tmp
wget ftp://ccrma-ftp.stanford.edu/pub/Lisp/sndlib.tar.gz
tar -zxf sndlib.tar.gz
configure CC=g++
make
rm *.so

you dont need to do a 'make install' for grace, just spedify the path  
to the sndlb dir you just comiled to premake

cd cm
premake ...  --sndlib /path/to/sndlib
make


_______________________________________________
Cmdist mailing list
Cmdist@...
http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist

[Peter O'Doherty-2]

Great, thanks. It's working perfectly now.
Regards,
Peter


On 08/19/2011 03:00 PM, Heinrich Taube wrote:

>
> On Aug 19, 2011, at 7:18 AM, Peter O'Doherty wrote:
>
>> Grace 3.8.0 [svn:1946] (c) 2011 Rick Taube
>> JUCE v1.52.110 (c) 2011 Julian Storer
>> S7 Scheme 1.86 (11-May-11) (c) 2011 William Schottstaedt
>
> yes you didnt build the c sources with fomus option enabled, if you
> had you would see it listed in the herald.
> i would also install a new sndlib before reloading and do an 'svn
> update'  in the cm directory -- the latest svn version is 1953
>
> to install a sndlib do
>
> mv sndlib /tmp
> wget ftp://ccrma-ftp.stanford.edu/pub/Lisp/sndlib.tar.gz
> tar -zxf sndlib.tar.gz
> configure CC=g++
> make
> rm *.so
>
> you dont need to do a 'make install' for grace, just spedify the path
> to the sndlb dir you just comiled to premake
>
> cd cm
> premake ...  --sndlib /path/to/sndlib
> make
>
>
>

--
//=============================
->  Peter O'Doherty
->  http://www.peterodoherty.net
->  mail@...
//=============================

_______________________________________________
Cmdist mailing list
Cmdist@...
http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist

[Heinrich Taube]

ahh those words are like music to my ears ;)

On Aug 19, 2011, at 8:31 AM, Peter O'Doherty wrote:

> Great, thanks. It's working perfectly now.
> Regards,
> Peter
>

_______________________________________________
Cmdist mailing list
Cmdist@...
http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist

[Peter O'Doherty-2]

This won't be music to your ears, I'm afraid, but please permit me one
further set-up question.

I've selected Timidity(1) from the Audio/Midi Out menu.

ports()

gives me:

{{"midi.port" {0 -> "Midi Through" #f} {1 -> "OSS sequencer" #f} {2 ->
"TiMidity {1}" #t} {3 -> "TiMidity {2}" #f} {4 -> "TiMidity {3}" #f} {5
-> "TiMidity {4}" #f} {0 <- "Midi Through" #f} {1 <- "Juce Midi Output"
#f}}}

So I do
send("mp:open", out: 2)
then
send("mp:midi", 0, .5, 60, .5, 0)

but this throws the error:
#<unspecified>

What am I doing wrong?

Thanks again.
Peter



On 08/19/2011 03:50 PM, Heinrich Taube wrote:

> ahh those words are like music to my ears ;)
>
> On Aug 19, 2011, at 8:31 AM, Peter O'Doherty wrote:
>
>> Great, thanks. It's working perfectly now.
>> Regards,
>> Peter
>>
>
>

--
//=============================
->  Peter O'Doherty
->  http://www.peterodoherty.net
->  mail@...
//=============================

_______________________________________________
Cmdist mailing list
Cmdist@...
http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist

[Heinrich Taube]

On Aug 19, 2011, at 2:52 PM, Peter O'Doherty wrote:

> What am I doing wrong?

maybe you aren't doing anything wrong -- i remember on linux i had to  
do some sort of port connection in jack., ie in addtino to selectin a  
port in cm.  im sorry but i cant even remember the name of the jack  
app i had to use to do this,  'jackctrl' or someting?  then the dialog  
itself was a bit confunsion --  sorry it was all rather complicated  
and i cant remember but i think you need to do the jack stuff after  
you started cm

you might find it easier to forget the midi port connecting and just  
write a midi file instead and then use cm's (shell ) function to  
start timidity with the file name. i think there might even be a file  
hook that  you can use to do this automatically after the file is  
written.


_______________________________________________
Cmdist mailing list
Cmdist@...
http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist

[Peter O'Doherty-2]

On 08/19/2011 11:58 PM, Heinrich Taube wrote:

> On Aug 19, 2011, at 2:52 PM, Peter O'Doherty wrote:
>
>> What am I doing wrong?
>
> maybe you aren't doing anything wrong -- i remember on linux i had to
> do some sort of port connection in jack., ie in addtino to selectin a
> port in cm.  im sorry but i cant even remember the name of the jack
> app i had to use to do this,  'jackctrl' or someting?  then the dialog
> itself was a bit confunsion --  sorry it was all rather complicated
> and i cant remember but i think you need to do the jack stuff after
> you started cm
>
> you might find it easier to forget the midi port connecting and just  
> write a midi file instead and then use cm's (shell ) function to  
> start timidity with the file name. i think there might even be a file
> hook that  you can use to do this automatically after the file is
> written.

Got it working now. Just needed to connect JuceMidi to FluidSynth in
QjackCtl (the app you were thinking of) to hear midi.
Thanks again,
Peter


--
//=============================
->  Peter O'Doherty
->  http://www.peterodoherty.net
->  mail@...
//=============================

_______________________________________________
Cmdist mailing list
Cmdist@...
http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist

[Peter O'Doherty-2]

On 08/19/2011 11:58 PM, Heinrich Taube wrote:

> On Aug 19, 2011, at 2:52 PM, Peter O'Doherty wrote:
>
>> What am I doing wrong?
>
> maybe you aren't doing anything wrong -- i remember on linux i had to
> do some sort of port connection in jack., ie in addtino to selectin a
> port in cm.  im sorry but i cant even remember the name of the jack
> app i had to use to do this,  'jackctrl' or someting?  then the dialog
> itself was a bit confunsion --  sorry it was all rather complicated
> and i cant remember but i think you need to do the jack stuff after
> you started cm
>
> you might find it easier to forget the midi port connecting and just  
> write a midi file instead and then use cm's (shell ) function to  
> start timidity with the file name. i think there might even be a file
> hook that  you can use to do this automatically after the file is
> written.

One more question.

I'm probably missing something really simple but what do I need to add
to this simple example to enable midi output as well as fomus?

process examp1 (n, r)
   repeat n
   send( "fms:note", dur: r, pitch: between(48, 73))
   wait r
end

sprout( examp1(16, 1/2), "fomus1.ly")

I've tried various combinations, including using variables such as the
example below but I can't seem to get it to work.

process examp1 (n, r)
   repeat n
   variable pitch = between(48, 73)
   send("fms:note", dur: r, pitch: between(48, 73))
   send("mp:midi", dur: r, key: pitch)
   wait r
end

sprout( examp1(16, 1/2), "fomus1.ly")

Thanks,
Peter


--
//=============================
->  Peter O'Doherty
->  http://www.peterodoherty.net
->  mail@...
//=============================

_______________________________________________
Cmdist mailing list
Cmdist@...
http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist

[Heinrich Taube]

im pretty sure the issue is that the scheduler runs in faster-than  
real time for files and real-time for ports. since you have  a mix of  
both file and port its not going to work.
there are several alternatives.

1. the best way to do this is to tell fomus to write BOTH a .mid and  
and .ly file . this is how you do that:

process examp1 (n, r)
   repeat n
   send( "fms:note", dur: r, pitch: between(48, 73))
   wait r
end

sprout( examp1(16, 1/2), "fomus1.ly" , output: {"ly" "mid" } )

the advantage is that fomus will do a lot of work on the midi output  
so that it matches the score. simply sending data to the midi port  
yourself wont include those huersitics.

2. i think you can probably send to a midi port and also to a fomus  
score you open by hand, and then close the fomus score by hand after  
the midi processing is over. im not sure why you would want to do  
this...



On Aug 20, 2011, at 7:20 AM, Peter O'Doherty wrote:

> One more question.
>
> I'm probably missing something really simple but what do I need to add
> to this simple example to enable midi output as well as fomus?
>
> process examp1 (n, r)
>   repeat n
>   send( "fms:note", dur: r, pitch: between(48, 73))
>   wait r
> end
>
> sprout( examp1(16, 1/2), "fomus1.ly")
>
> I've tried various combinations, including using variables such as the
> example below but I can't seem to get it to work.
>
> process examp1 (n, r)
>   repeat n
>   variable pitch = between(48, 73)
>   send("fms:note", dur: r, pitch: between(48, 73))
>   send("mp:midi", dur: r, key: pitch)
>   wait r
> end
>
> sprout( examp1(16, 1/2), "fomus1.ly")
>
> Thanks,
> Peter
>
>
> --
> //=============================
> ->  Peter O'Doherty
> ->  http://www.peterodoherty.net
> ->  mail@...
> //=============================
>
> _______________________________________________
> Cmdist mailing list
> Cmdist@...
> http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist

_______________________________________________
Cmdist mailing list
Cmdist@...
http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist

[Peter O'Doherty-2]

Many thanks, yet again!


On 08/21/2011 02:24 PM, Heinrich Taube wrote:

> im pretty sure the issue is that the scheduler runs in faster-than
> real time for files and real-time for ports. since you have  a mix of
> both file and port its not going to work.
> there are several alternatives.
>
> 1. the best way to do this is to tell fomus to write BOTH a .mid and
> and .ly file . this is how you do that:
>
> process examp1 (n, r)
>   repeat n
>   send( "fms:note", dur: r, pitch: between(48, 73))
>   wait r
> end
>
> sprout( examp1(16, 1/2), "fomus1.ly" , output: {"ly" "mid" } )
>
> the advantage is that fomus will do a lot of work on the midi output
> so that it matches the score. simply sending data to the midi port
> yourself wont include those huersitics.
>
> 2. i think you can probably send to a midi port and also to a fomus
> score you open by hand, and then close the fomus score by hand after
> the midi processing is over. im not sure why you would want to do this...
>
>
>
> On Aug 20, 2011, at 7:20 AM, Peter O'Doherty wrote:
>
>> One more question.
>>
>> I'm probably missing something really simple but what do I need to add
>> to this simple example to enable midi output as well as fomus?
>>
>> process examp1 (n, r)
>>   repeat n
>>   send( "fms:note", dur: r, pitch: between(48, 73))
>>   wait r
>> end
>>
>> sprout( examp1(16, 1/2), "fomus1.ly")
>>
>> I've tried various combinations, including using variables such as the
>> example below but I can't seem to get it to work.
>>
>> process examp1 (n, r)
>>   repeat n
>>   variable pitch = between(48, 73)
>>   send("fms:note", dur: r, pitch: between(48, 73))
>>   send("mp:midi", dur: r, key: pitch)
>>   wait r
>> end
>>
>> sprout( examp1(16, 1/2), "fomus1.ly")
>>
>> Thanks,
>> Peter
>>
>>
>> --
>> //=============================
>> ->  Peter O'Doherty
>> ->  http://www.peterodoherty.net
>> ->  mail@...
>> //=============================
>>
>> _______________________________________________
>> Cmdist mailing list
>> Cmdist@...
>> http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist
>
>

--
//=============================
->  Peter O'Doherty
->  http://www.peterodoherty.net
->  mail@...
//=============================

_______________________________________________
Cmdist mailing list
Cmdist@...
http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist