6 Aug
2004
6 Aug
'04
8:17 a.m.
Hello,
I trying my first steps with Supercollider. Build and install
went without any probles, and I learned just enough elisp to
get scel running in emacs.
Now the problem seems to be that sclang and scsynth do not
talk to each other. How is the sclang -> scsynth UDP link
configured ? There is no option in sclang to set the port
number it sends to so probably this is fixed. OTOH, scsynth
requires a port number for the -u option, but what should
this be ?
TIA,
--
Fons
9 Aug
9 Aug
1:21 p.m.
Alfons Adriaensen <fons.adriaensen(a)alcatel.be> writes:
Now the problem seems to be that sclang and scsynth do
not
talk to each other. How is the sclang -> scsynth UDP link
configured ?
It is automatically brought up if you call s.boot.
There is no option in sclang to set the port number it
sends to so
probably this is fixed.
No, the second argument to Server-boot is an optional
NetAddr instance, which you can use to connect to some server
running on a non-standard port or even on a remote host (not localhost).
OTOH, scsynth requires a port number for the -u
option, but what
should this be ?
As I said above, you usually don't start scsynth yourself, you
usually let sclang bring it up for you:
(
s.local.boot;
)
For more details, look at the Server and ServerOptions helpfile
(use C-c C-h in an Emacs SCEL buffer to access the helpfiles).
--
CYa,
Mario | Debian Developer <URL:http://debian.org/>
.''`. | Get my public key via finger mlang(a)db.debian.org
: :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
`. `'
`-
10 Aug
10 Aug
8:06 a.m.
On Mon, Aug 09, 2004 at 05:06:10PM +0200, Mario Lang wrote:
It is automatically brought up if you call s.boot.
Thanks for your reply, and yes, that's what I found out.
For more details, look at the Server and ServerOptions
helpfile
(use C-c C-h in an Emacs SCEL buffer to access the helpfiles).
The help items in the sclang menu don't seem to work. They
want a directory 'SuperCollider/help', and there is no 'help'
directory at all in what I co'd from CVS. Also "Show server
panels" prints the command name in the minibuffer, and that's all.
Is there a list of all the available classes, their methods and
paramters ? The only thing I found is a 5 year old PDF document
on SC2. Most of the examples in this text do no work at all -
probably a lot has changed between SC2 and SC3.
It really seems SC is the tool I've been waiting for, so I will
spend whatever time and effort required in order to learn to
master it. But starting from the little documentation that I
was able to find is a bit hard :-(
In the longer term, I'd like to be able to write programs that
use scsynth directly as a 'synthesizer server'.
--
Fons
8:34 a.m.
On Tue, 10 Aug 2004 11:50:59 +0200
Alfons Adriaensen <fons.adriaensen(a)alcatel.be> wrote:
The help items in the sclang menu don't seem to
work. They
want a directory 'SuperCollider/help', and there is no 'help'
directory at all in what I co'd from CVS. Also "Show server
panels" prints the command name in the minibuffer, and that's all.
The Help files files should be in SuperCollider3/build/Help in the
source distribution afaik
flo
--
Palimm Palimm!
http://affenbande.org/~tapas/
9:30 a.m.
On Tue, Aug 10, 2004 at 12:29:25PM +0200, Florian Schmidt wrote:
The Help files files should be in
SuperCollider3/build/Help in the
source distribution afaik
If that's 'Help' with a capital H then I'll have to look again.
Noticing the error from the help command, I tried to find out
where the help files had been installed:
find / -name help 2>/dev/null
and found nothing for SuperCollider.
Thaks for the hint.
--
Fons
9:43 a.m.
On Tue, 10 Aug 2004 13:15:01 +0200
Alfons Adriaensen <fons.adriaensen(a)alcatel.be> wrote:
On Tue, Aug 10, 2004 at 12:29:25PM +0200, Florian
Schmidt wrote:
Yep it's a captial H :) The install target in the linux makefile does
not seem to put the Help files into a systemwide location like
/usr/local/share/SuperCollider3/Help. I think i will write a mail to
the SC3 list pointing this out.
Flo
--
Palimm Palimm!
http://affenbande.org/~tapas/
The Help files files should be in
SuperCollider3/build/Help in the
source distribution afaik
If that's 'Help' with a capital H then I'll have to look again.
Noticing the error from the help command, I tried to find out
where the help files had been installed: 
10:31 a.m.
On Tue, Aug 10, 2004 at 11:50:59AM +0200, Alfons Adriaensen wrote:
Thanks for your reply, and yes, that's what I
found out.
you need to set the elisp variable `sclang-help-directory' to
point to the rtf help files in the CVS sources, e.g.
(setq sclang-help-directory "~/src/SuperCollider3/build/Help")
you can set it either in ~/.emacs or graphically via M-x
sclang-customize
For more details, look at the Server and
ServerOptions helpfile
(use C-c C-h in an Emacs SCEL buffer to access the helpfiles).
The help items in the sclang menu don't seem to work. They
want a directory 'SuperCollider/help', and there is no 'help'
directory at all in what I co'd from CVS. Also "Show server panels" prints the command
name in the
minibuffer, and that's all.
the linux GUI stuff is not in CVS yet, you can get it here:
http://www.cs.tu-berlin.de/~kerstens/sc_linux.html
Is there a list of all the available classes, their
methods and
paramters ? The only thing I found is a 5 year old PDF document
on SC2. Most of the examples in this text do no work at all -
probably a lot has changed between SC2 and SC3.
SC2 tutorials are fine for learning about syntax and basics,
but the interface to sound generation has changed a lot
indeed.
It really seems SC is the tool I've been waiting
for, so I will
spend whatever time and effort required in order to learn to
master it. But starting from the little documentation that I
was able to find is a bit hard :-(
the help files in the distribution are actually pretty
extensive, you just have to know how to access them :)
pressing C-c C-h in an sclang-buffer in emacs lets you enter a
help topic (with tab completion) with a supplied default when
the cursor is over a documented identifier. the help topic
`Help' links to many other documents.
there are also shortcuts to dig around in the class library
(finding method implementations etc.), all of which can be
found in a little scel tutorial on the site above.
In the longer term, I'd like to be able to write
programs that
use scsynth directly as a 'synthesizer server'.
then the help topics `Server-Command-Reference' and
`Synth-Definition-File-Format' are your friends ...
hth,
<sk>
11:42 a.m.
On Tue, Aug 10, 2004 at 02:24:26PM +0200, stefan kersten wrote:
<Lots of very useful info>
I know what to do this evening... :-)
Had a quick look at your website. The SCUM stuff looks great,
can't wait to try this out. Also followed the link to Dave's
tutorial - if only I had found this a bit sooner... :-)
Apart from the little problems you and other list members
already solved, I should say the build and install process
really worked flawlessly, which is by no means evident for
a ported application. Thanks a lot for you work.
--
Fons
7401
days inactive
7405
days old
linux-audio-dev@lists.linuxaudio.org
7 comments
4 participants
participants (4)
-
Alfons Adriaensen -
Florian Schmidt -
Mario Lang -
stefan kersten