[SCM] supercollider/master: supernova compile fix on x86

[Felipe Sateler]

On Wed, Dec 26, 2012 at 3:14 PM, Dan S <danstowell+debmm at gmail.com> wrote:
> 2012/12/26 Felipe Sateler <fsateler at debian.org>:

>>  Could you elaborate a
>> bit on the relationship between sc-server and sc-supernova? Is
>> supernova picked up automatically when installed? Or is some
>> configuration necessary?
>
> No it's not picked up automatically, it's intentionally the user's
> choice which to use. The user either manually boots their preferred
> server from the commandline, or (more usually) executes either
> "Server.scsynth" or "Server.supernova" to set the session default from
> within sclang.
>
> During an ordinary SuperCollider session, users can logically group
> synths into "Group" containers, or "ParGroup" containers. This
> reflects the order-or-execution on the server, and the API is the same
> for both executables; however, if you're using supernova then items
> within a "ParGroup" are parallelised.

This clarifies it, thanks. But now I'm confused. In my experiments
with sc what is done is s.boot (no mention of scsynth). Is this
because the default is scsynth?

I tried googling for a reference we can link in the package
description, but I found none. So I guess we could add the following
to the description:

This package contains the multiprocessor aware and parallelization
capable synthesis server supernova. Use of this server is enabled via
a Server.supernova call before starting the server.


--

Saludos,
Felipe Sateler