cables is under heavy development.
There might be one or another bug, please let us know about it!
cables DocumentationHow To UseWorking with filesKeyboard ShortcutsUser Interface WalkthroughBeginner TutorialBeginner 1: Drawing A CircleBeginner 2: TransformationsBeginner 3: ColorMore TransformationsintermediateImage CompositionsPost-Processing 3D Scenescommunicationcables APICommunication with an Arduino via SerialCommunicating with Arduino over MQTTExporting And EmbeddingHow to serve files externally and fix CORS headersExporting PatchesExport using the cables command line interfaceExport via IframeExport creating a standalone executableExport to github (pages)Export and deploy to netlifyExport a ZIP fileExternal triggers / functionsUsing variablesPreviewing / uploading exported cables patchescoding opsCreating AttachmentsGeneral op/Port CallbacksPortsDynamic PortsArray PortsBoolean portsInteger Number PortsObject PortsString portsTrigger PortsFloating Point Number PortsGUI/UI attributesHello Op - Part 1LibrariesDeveloping OpsGuidelinesObject PortsWriting ShadersWeb Audio Op DevelopmentHTML and CSS in cablesLightingLightsShadowsWorking with audioBasic Audio SetupWorking with EffectsReal-Time Audio Analyzation & Audio VisualizationOffline Audio Visualization & AnalyzationFAQEmbeddingHow to integrate my cables patch into my CMS (webflow/wix/squarespace/...)?getting a warning when running the patch in electronHow to remove grey rectangles on touch (mobile)?Why doesn't the DownloadTexture op work on iOS?How to disable page scrolling on mobile?Mobile tippsTransparent CanvasFeatures and SupportHow to contribute code to cablesWill there be support for (animated) GIFs?How to report a bug in cablesGeneral questionsLicences and paymentWhat licence do i need to use cables?Will I have to pay for it in the future?How is my work licenced when using cables?Does cables support midi and OSC?ShadertoyTechnical questionsUI / EditorGuide to VR in cablesWebGL1 and WebGL2

Web Audio Op Development

The Web Audio ops available in cables closely wrap the audio nodes of the Web Audio API.

For convenience you can also access tone.js, a powerful Web Audio library, which makes certain things like timing easier.

Building Web Audio ops

Create a new op and make sure to include the following line at the top of your patch, just below your op-name definition: = "MyNewWebAudioOp";
// now window.audioContext is set and you can use all of the Web Audio nodes

Building tone.js-compatible ops

Building tone.js-compatible ops / wrapper is as straightforward as creating normal Web Audio ops. There are a few things you need to take care of:

Create a new empty op, give it a name, save the op and patch, refresh the browser (yes, this needs to be fixed), press ESC to add your newly created op to the patch, then select the op and code-tab on the right of the window. If you don’t see it you need to resize the panes accordingly.

Now select tone.js, click Add, save your patch and reload the page.

In order to use tone.js there is one thing left to do: In your op-code add the following line below your op-name definition, it should look like this:

// now you can use all Web Audio nodes / tone.js functions

help cables get better and edit this file on github