From 96ecc6099ed34c8de76f9a866833a22f11153679 Mon Sep 17 00:00:00 2001 From: Andrew Belt Date: Tue, 8 May 2018 08:59:40 -0400 Subject: [PATCH] README changes --- Core.md | 18 +++++++++--------- Introduction.md | 2 +- README.md | 3 ++- 3 files changed, 12 insertions(+), 11 deletions(-) diff --git a/Core.md b/Core.md index 4fece89..a8aae32 100644 --- a/Core.md +++ b/Core.md @@ -4,7 +4,7 @@ The *Core* plugin is actually not a plugin at all. It's built in to the Rack application itself, but you can add Core modules to your rack just like normal modules. ### Audio -![](images/Core/Audio.m.png) +![Core Audio](images/Core/Audio.m.png) The *Audio* module merges the virtual Rack world with the physical hardware world. The **INPUT** section sends up to 8 Rack signals to a hardware audio device for playback, and the **OUTPUT** section sends up to 8 hardware signals into Rack. @@ -13,7 +13,7 @@ The **INPUT** section sends up to 8 Rack signals to a hardware audio device for - Core Audio on Mac - WASAPI and ASIO on Windows - ALSA on Linux -- [VCV Bridge](#Bridge) (described in a below section) on all OS's, although there are no Bridge plugins for Linux at this time +- VCV Bridge (described in a below section) on all OS's, although there are no Bridge plugins for Linux at this time After a driver is selected, a particular **device** can be chosen for the driver. If the device has more than 8 inputs or outputs, you can select the desired range of outputs, offset by a factor of 8. @@ -30,38 +30,38 @@ Note: Using multiple Audio modules is experimental and may crash Rack or render Most DAWs avoid this feature entirely by restricting audio to a single input and a single output device for stability reasons, but if using multiple audio devices in Rack works with your configuration, more power to you! ### MIDI-1 -![](images/Core/MIDI-1.m.png) +![Core MIDI-1](images/Core/MIDI-1.m.png) *Coming soon* ### MIDI-4 -![](images/Core/MIDI-4.m.png) +![Core MIDI-4](images/Core/MIDI-4.m.png) *Coming soon* ### MIDI-CC -![](images/Core/MIDI-CC.m.png) +![Core MIDI-CC](images/Core/MIDI-CC.m.png) *Coming soon* ### MIDI-Trig -![](images/Core/MIDI-Trig.m.png) +![Core MIDI-Trig](images/Core/MIDI-Trig.m.png) *Coming soon* ### Blank -![](images/Core/Blank.m.png) +![Core Blank](images/Core/Blank.m.png) Useful for adding space between modules in your rack. You can resize the panel by dragging the edges horizontally, with a minimum size of 2HP. ### Notes -![](images/Core/Notes.m.png) +![Core Notes](images/Core/Notes.m.png) Useful for adding patch notes, section titles for organization, instructions, and author information to your patches. You can copy and paste text with Ctrl+C and Ctrl+V. -### Bridge +### VCV Bridge Rack is a standalone DAW-like application and not a VST/AU plugin because of the major limitations of these formats. It is common to think of physical modular synthesizers as entire self-contained DAWs, and many people use Rack as a complete DAW to compose music and build patches without other software. diff --git a/Introduction.md b/Introduction.md index cef1c40..c92ef34 100644 --- a/Introduction.md +++ b/Introduction.md @@ -2,6 +2,6 @@ The VCV Rack manual is under active development. -You can contribute at https://github.com/VCVRack/manual. +Edit this manual at https://github.com/VCVRack/manual. [PDF download](VCV-Rack-manual.pdf) diff --git a/README.md b/README.md index 36509ac..2953176 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,8 @@ The scope of the manual is the VCV Rack application. It does not include individ ### Contributions Send a pull request to this repository with your edits. -Major changes like new pages and sections are welcome, as well as minor fixes like grammar, spelling, and reorganization. +Major changes like new pages and complete overhauls are welcome, as well as minor fixes like grammar, spelling, and reorganization. +Your PR will be accepted if it is a net positive benefit to readers. ### Building