diff --git a/docs/PatchFormat/main.md b/docs/PatchFormat/main.md index 02893be7..bd7bcf2f 100644 --- a/docs/PatchFormat/main.md +++ b/docs/PatchFormat/main.md @@ -33,7 +33,7 @@ For example, the `HelloWorld.cmajorpatch` contains: "version": "1.0", "name": "Hello World", "description": "The classic audio Hello World", - "manufacturer": "Sound Stacks Ltd", + "manufacturer": "Cmajor Software Ltd", "category": "generator", "isInstrument": false, "source": "HelloWorld.cmajor" diff --git a/docs/QuckStart/main.md b/docs/QuckStart/main.md index 410828c5..e042e1ba 100644 --- a/docs/QuckStart/main.md +++ b/docs/QuckStart/main.md @@ -32,7 +32,7 @@ This command will prompt you to select the name of a new `.cmajorpatch` file. It #### `Cmajor: Find example patches` -This command will take you to the Cmajor repository where you can find our example patches. You can either clone the [whole repository](https://github.com/SoundStacks/cmajor) from github, or just download specific examples from the [examples](https://github.com/SoundStacks/cmajor/tree/main/examples/patches) folder. +This command will take you to the Cmajor repository where you can find our example patches. You can either clone the [whole repository](https://github.com/cmajor-lang/cmajor) from github, or just download specific examples from the [examples](https://github.com/cmajor-lang/cmajor/tree/main/examples/patches) folder. #### `Cmajor: Export patch as JUCE plugin` @@ -42,7 +42,7 @@ This will prompt you for a folder in which to create a new JUCE project containi ## Installing the Cmajor command-line tools -On the Github releases page, you'll find [downloadable binaries for Mac and Windows](https://github.com/SoundStacks/cmajor/releases). These provide: +On the Github releases page, you'll find [downloadable binaries for Mac and Windows](https://github.com/cmajor-lang/cmajor/releases). These provide: - The command-line tool (`cmaj` or `cmaj.exe`) which provides a compiler, utilities and can load and run Cmajor patches. - The redistributable libraries (`CmajPerformer.dll` or `libCmajPerformer.so`) which are needed if you're building your own native app which embeds the Cmajor JIT engine. @@ -52,7 +52,7 @@ On the Github releases page, you'll find [downloadable binaries for Mac and Wind The `cmaj` command can create, build, test and run patches, as well as perform code-generation of C++ and plugin projects, and various other tasks. -To install, just [download](https://github.com/SoundStacks/cmajor/releases) and unzip the executable into a location of your choice, and you can run it from a terminal. +To install, just [download](https://github.com/cmajor-lang/cmajor/releases) and unzip the executable into a location of your choice, and you can run it from a terminal. For help, run: @@ -78,7 +78,7 @@ While running a patch, the console app will detect any file changes and recompil ## Loading patches in your DAW with the Cmajor VST/AU plugin -In our [binary releases](https://github.com/SoundStacks/cmajor/releases), you'll find an installer for our plugin, which can be loaded into most DAWs like any other plugin. +In our [binary releases](https://github.com/cmajor-lang/cmajor/releases), you'll find an installer for our plugin, which can be loaded into most DAWs like any other plugin. When you create an instance of this plugin in a DAW, you can drag-and-drop a `.cmajorpatch` file onto the plugin's GUI to make it load that patch. diff --git a/docs/StandardLibrary/main.html b/docs/StandardLibrary/main.html index 04577e6c..a430edf9 100644 --- a/docs/StandardLibrary/main.html +++ b/docs/StandardLibrary/main.html @@ -26,7 +26,7 @@

namespace std

-

namespace std::audio_datacode +

namespace std::audio_datacode


These structures are useful for representing chunks of audio data with a known sample-rate. They're useful types when you're declaring an external variable which is going to hold audio file data or generated waveform data.
Note that duck-typing is used for the types of externals which contain audio data, so you can use your own classes as long as they contain a couple of fields which can hold the frame data and a sample rate. If you need a struct for audio data with more than 2 channels, you can just declare your own type using an appropriately-sized vector for the frames.
@@ -228,7 +228,7 @@

std.envelopes

-

namespace std::envelopescode +

namespace std::envelopescode


Utilities for calculating and applying static and dynamic gain levels.
@@ -312,7 +312,7 @@

std.filters

-

namespace std::filterscode +

namespace std::filterscode

@@ -1943,7 +1943,7 @@

std.frequency

-

namespace std::frequencycode +

namespace std::frequencycode


Contains DFT implementations for complex and real numbers
The buffers can be either float32 or float64 (or complex32/complex64). Buffer sizes must be a power of 2.
@@ -1986,7 +1986,7 @@

std.intrinsics

-

namespace std::intrinsicscode +

namespace std::intrinsicscode


This namespace contains placeholders and reference implementations of basic functions.
The compiler treats the intrinsics namespace as a special-case, allowing its functions to act as if they're in the global namespace.
When running code, the JIT engines are free to replace the implementation of intrinsic functions with optimised alternatives if possible, although many of the functions in here also provide reference implementations to be used as a fallback when no native version is available.
@@ -2351,7 +2351,7 @@

std.levels

-

namespace std::smoothingcode +

namespace std::smoothingcode

@@ -2496,7 +2496,7 @@

Functions

-

namespace std::levelscode +

namespace std::levelscode

@@ -2677,7 +2677,7 @@

Functions

-

namespace std::pan_lawcode +

namespace std::pan_lawcode

@@ -2705,7 +2705,7 @@

std.matrix

-

namespace std::matrixcode +

namespace std::matrixcode


This namespace contains various matrix manipulation functions.
@@ -2763,7 +2763,7 @@

std.midi

Various utilities for handling raw MIDI data.
-

namespace std::midicode +

namespace std::midicode


The classes in the standard library which deal with synthesisers have been designed to avoid raw MIDI messages, and instead to work with strongly-typed event objects for note-ons/offs, pitch-bends, etc, which are vastly more usable than a 3-byte code that was designed for a 1980s serial link.
@@ -3231,7 +3231,7 @@

std.mixers

-

namespace std::mixerscode +

namespace std::mixerscode


These processors can be used to mix various combinations of audio streams together with static or dynamic gains.
@@ -3428,7 +3428,7 @@

std.noise

-

namespace std::noisecode +

namespace std::noisecode


These processors can be used to generate various flavours of noise.
@@ -3662,7 +3662,7 @@

std.notes

-

namespace std::notescode +

namespace std::notescode


These structs are used for events that model the start/stop/control of notes that are playing in synthesisers.
Unlike sending raw MIDI around, these are strongly typed and use floating point data so are far nicer to work with.
The objects include a channel ID field, so that a multi-channel input device can indicate which events should be applied to each of the active notes that are being played.
@@ -3927,7 +3927,7 @@

std.oscillators

-

namespace std::oscillatorscode +

namespace std::oscillatorscode


These utility functions and processors provide oscillators such as sine, square, triangle and sawtooth.
@@ -4737,7 +4737,7 @@

std.random

-

namespace std::randomcode +

namespace std::randomcode


If you're writing code that needs to be cryptographically secure, then this is not the random number generation library that you want. The target audience for these classes are those who need quick-and-dirty RNGs for noise generation and similar non-critical tasks.
When seeding RNGs, the processor.id and processor.session values are very useful:
    @@ -4820,7 +4820,7 @@

    std.timeline

-

namespace std::timelinecode +

namespace std::timelinecode


This namespace contains various types and functions for dealing with tempos, positions and events that describe DAW-style timelines.
@@ -5011,7 +5011,7 @@

std.voices

-

namespace std::voicescode +

namespace std::voicescode


This module demonstrates a simple voice-allocation algorithm.
The way it's structured is that you pass an incoming stream of note events to the voice allocator processor, and it redirects them to an array of destination processors which each handle a single voice.
The voice allocators use the channel property of the incoming events to group them together, and take care of ensuring that each target voice only receives the events from one channel at a time.
diff --git a/docs/TestFileFormat/main.md b/docs/TestFileFormat/main.md index 49865f74..3fe8ac67 100644 --- a/docs/TestFileFormat/main.md +++ b/docs/TestFileFormat/main.md @@ -72,7 +72,7 @@ To quickly disable a test, insert the token `disabled` in front of the test dire ## Built-in Test Functions -There's a built-in library of standard test functions, and you can have a closer look at their implementations in [cmaj_test_functions.js](https://github.com/SoundStacks/cmajor/blob/main/tests/cmaj_test_functions.js). +There's a built-in library of standard test functions, and you can have a closer look at their implementations in [cmaj_test_functions.js](https://github.com/cmajor-lang/cmajor/blob/main/tests/cmaj_test_functions.js). The main functions include: @@ -291,7 +291,7 @@ void f (XX& x) {} You can write your own javascript test functions at the start of the test file, and invoke them on a `##` line. -If writing your own tests, it's probably helpful to look at how the standard ones are implemented, in [cmaj_test_functions.js](https://github.com/SoundStacks/cmajor/blob/main/tests/cmaj_test_functions.js). +If writing your own tests, it's probably helpful to look at how the standard ones are implemented, in [cmaj_test_functions.js](https://github.com/cmajor-lang/cmajor/blob/main/tests/cmaj_test_functions.js). The underlying javascript API used for managing the test status looks like this: diff --git a/docs/Tools/CppAPI/main.md b/docs/Tools/CppAPI/main.md index db23e592..903f99f4 100644 --- a/docs/Tools/CppAPI/main.md +++ b/docs/Tools/CppAPI/main.md @@ -18,7 +18,7 @@ The two main folders to look at for this are: (There is also a lower-level COM-based API in `include/cmajor/COM` which you can use if you like, but it's probably better to ignore them and stick to the API wrapper classes that expose the same things as idiomatic C++ classes). -There are some example projects demonstrating simple use of the C++ API: see the [examples/native_apps](https://github.com/SoundStacks/cmajor/tree/main/examples/native_apps) folder. +There are some example projects demonstrating simple use of the C++ API: see the [examples/native_apps](https://github.com/cmajor-lang/cmajor/tree/main/examples/native_apps) folder. ## Main API classes