The ScopeSync128A module provides 128 controls which can be controlled between Scope BCModular (shell) and Native Standalone Application or VST Plugin (module panel). You can create your own panel!
Usage
High resolution control system for linking DAWs to Scope. For full details, visit scopesync.co.uk
The data portion of the ScopeSync communication stream (contains control values). Should be connected via a digital audio channel to the Left output channel of a ScopeSync DAW plugin
The destination portion of the ScopeSync communication stream (contains references to controls). Should be connected via a digital audio channel to the Left output channel of a ScopeSync DAW plugin
128pipe was added with CLMs in mind. You could have a patch with a single SS128A and multiple CLMs. The Yellow pipe would at least in theory make it easier to connect the CLM contents to the SS128A. What you suggest however as a use might well work too.
pipe is for controls at the Scope side independent of SCOPESYNC automation. Examples of this might be VU meters / clip LEDs or if you wanted to use multiple SCOPESYNC instances in a patch and call up other UI windows from controls on the main SCOPESYNC UI. The means to do this is available via the CP<->Host pipe of the SS128A which is itself tapped into 8 of the 16 available ScopeLocal connections.
MIDI messages from the ScopeSync stream. If multiple Scope modules are processing a single ScopeSync stream, a MIDI merger must be used to combine the MIDI messages
yayajohn: Right now I have been very happy just using the Scopsync console on the Scope side. It has made making presets a whole lot easier.
I knew this was going to be a big bite to chew for a first timer but I also knew it would keep me involved longer and force me to retain hopefully most of what I learned in the process. My next patch will be smaller.
ScopeSync128A
Description
The ScopeSync128A module provides 128 controls which can be controlled between Scope BCModular (shell) and Native Standalone Application or VST Plugin (module panel). You can create your own panel!Usage
High resolution control system for linking DAWs to Scope. For full details, visit scopesync.co.ukScopeSync Technical Info
ScopeSync FAQs
Type
ScopeSyncModule
Popup
Panel
native standalone application / VST pluginbcmodular example Jump to: Board index » BC Modular Files » BC Modular Patches » FM One
Module Connections
Module Controls
Popup Controls
Panel Controls
native-standalone / vst-pluginScreen
Panel [Template Layouts]
Style Overrides
Panel [Right-click -> Edit Mapped Parameter]
Examples
Panel [Behringer BCF 2000, BCR 2000 - Midi Control]
Wavebank Synth [Modular Synth + ScopeSync]
bcmodular Jump to: Board index » BC Modular Files » BC Modular Patchescwmod: Sharc's Wavebank oscillators in action.
Patch circuit (top to bottom):
- 2 wavebank oscs, possibility to sync them
- pitch mod sources AD, ADSR, MLfo, SineLfo; Pm1 = regular behaviour, PM2 = AT controls PM amount
- Multi Filter
- VCA ADSR settings + Main Vol
- Aux AD env, Distortion, BPM
- Aux ADSR env
- M-LFO (1)
- M-LFO (2); SineLfo rate, a switch to determine if filter cfm2 amount is controled by AT or not, some MVC settings
the latest non-OSC ScopeSync release is used (v0.4.2-beta). More InfoGigantus [Modular Synth + ScopeSync]
bcmodular Jump to: Board index » BC Modular Files » BC Modular Patchesyayajohn: Right now I have been very happy just using the Scopsync console on the Scope side. It has made making presets a whole lot easier. I knew this was going to be a big bite to chew for a first timer but I also knew it would keep me involved longer and force me to retain hopefully most of what I learned in the process. My next patch will be smaller.