Packages

package root

Definition Classes: root

package de

Definition Classes: root

package sciss

The interfaces are grouped into the following packages:

Welcome to the Mellite API documentation.

The interfaces are grouped into the following packages:

de.sciss.synth is the ScalaCollider base package, with things like computation Rate, AddAction, and DoneAction.
de.sciss.synth.ugen contains the ScalaCollider UGen documentation
de.sciss.lucre.synth is the base package for the transactional layer for ScalaCollider, with things like de.sciss.lucre.synth.Bus, Buffer, Node, and Server.
de.sciss.synth.proc is the SoundProcesses base package, with things like Proc, Timeline, Folder, AuralSystem, Scheduler, Transport, and Workspace
de.sciss.synth.proc.graph are UGen abstractions added by SoundProcesses, such as ScanIn and ScanOut.
de.sciss.mellite.gui is the base package for the Mellite graphical user interface.
de.sciss.fscape is the FScape base package
de.sciss.fscape.graph contains the FScape UGen documentation
de.sciss.fscape.lucre is the base package for the transactional layer for FScape, with things like FScape and additional UGens.

The Lucre transactional object model:

de.sciss.lucre.stm is the base package for transactions, with things like Obj, Txn, Sys, and Cursor
de.sciss.lucre.artifact is the base package for file system artifacts, with classes Artifact and ArtifactLocation
de.sciss.lucre.expr is the base package for expression types such as IntObj, DoubleObj, etc.

Other useful packages:

de.sciss.synth.io for reading and writing audio files
de.sciss.osc for general Open Sound Control interfaces

Definition Classes: de

package synth

Definition Classes: sciss

object Ops

Importing the contents of this object adds imperative (side-effect) functions to resources such as synths, buses, buffers.

Importing the contents of this object adds imperative (side-effect) functions to resources such as synths, buses, buffers. In general these reflect the OSC messages defined for each object, and send them straight to the server. For example, a Synth has function newMsg which returns an OSC message to instantiate the synth of the server. After importing Ops, you will be able to directly launch a synth using SynthDef.play or Synth.play. You will be able to directly allocate and read buffers, and so forth.

The reason why these functions are separated from the rest of the API is to allow other frameworks such as SoundProcesses to avoid side-effects which they handle differently (e.g., using STM).