Table of Contents

Instructions

What are considered to be the main weak points of ScopeSync currently?

• Requires Max for Live, VST Host / DAW
• Also requires Java to be installed
• ScopeSync will use the communication method, i.e. via audio channels.
  Slightly fiddly to set up, as it needs digital audio connections to be used (typically ASIO).
• It's unidirectional, i.e. changing values in Scope loses the sync
• Control update frequency is "only" 690Hz (one update per control every 1.5ms) at best (assuming 44.1kHz sample rate). Although this is fantastic for regular automation tasks, it means it won't support audio-rate modulation.
• Release notes and highlights (wellis released this in github » bcmodular » scopesync » releases)

What is next for ScopeSync?

• Build an implementation that uses some form of inter-process communication so the DAW and Scope can talk to each other directly. This is at proof of concept stage now.
• CMS-1 is the first "non Modular" Scope device using ScopeSync.
  ScopeSync had been developed by W. Ellis, Sharc and J. Brandt but for this device heavily expanded by Will alone.
  
  check out cwmodular, and follow in Forum ...

Will I be able to run ScopeSync on a Mac?

• We hope so, although neither Will nor Simon has a Mac, so hasn't been able to test it. There is no reason why ScopeSync shouldn't be able to function across an ADAT connection (for instance) and Ableton is a popular DAW on Macs.
• If anyone fancies helping out, it should be easy to build an Audio Unit version of the VST plugin.