cables DocumentationHow To UseWorking with filesKeyboard ShortcutsUser Interface WalkthroughBeginner TutorialBeginner 1: Drawing A CircleBeginner 2: TransformationsBeginner 3: ColorMore TransformationsIntermediateImage CompositionsPost-Processing 3D ScenesExporting 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 full PatchExport a ZIP fileExternal triggers / functionsUsing variablesPreviewing / uploading exported cables patchesExamples for EmbeddingPermissionsUsersPatchesTeamsOpsMultiplayerPatchlistsCoding OpsCreating AttachmentsGeneral op/Port CallbacksPortsMultiPortsArray PortsBoolean portsInteger Number PortsObject PortsString portsTrigger PortsFloating Point Number PortsGUI/UI attributesHello Op - Part 1LibrariesDeveloping OpsRenaming / Creating a new versionCreating Viz OpsGuidelinesObject PortsPatching Ops / SubPatchOpsWriting ShadersWeb Audio Op DevelopmentDeveloping CablesRepositoriesSet up local environmentScriptsHow to work with forksGenerated DocumentationUsing standalone to develop cablesCables StandaloneGeneralCoding OpsSharing opsUsing NPMImport/ExportStandalone - FAQLightingLightsShadowsWorking With AudioBasic Audio SetupWorking with EffectsReal-Time Audio Analyzation & Audio VisualizationOffline Audio Visualization & AnalyzationCommunicationcables APIOptimizing Performance In PatchesTools for debugging your patchHow to optimize cables patches with the Performance opHow to optimize cables patches with the ProfilerCommon pitfalls with the "usual suspects"Optimizing arraysDebugging Shaders with ShaderInfoFAQAudio in web browsersHow to make demoscene demos with cables.glEmbeddingHow to integrate my cables patch into my CMS (webflow/wix/squarespace/...)?How to remove grey rectangles on touch (mobile)?Why doesn't the DownloadTexture op work on iOS?How to disable page scrolling on mobile?Mobile tippsHow to run exported patches on your local machineTransparent CanvasFeatures and SupportHow to contribute code to cablesWill there be support for (animated) GIFs?Can i use a website as a texture?Screenshots and Video recordingHow to report a bug in cablesHow can I share a patch to get help?How can I support cables?Video playback in cablesGeneral questionsWhat is dev.cables.glHTML And CSS In CablesJavascript Frameworkscordova / phonegapelectronreactvuejsLicenses and paymentWhat license do i need to use cables?Will I have to pay for it in the future?How is my work licensed when using cables?Does cables support midi and OSC?Patch PermissionsMy User Profile & Social MediaShadertoyCables at schools and universitiesTechnical questionsWebGL1 and WebGL2
cables Documentation  ⟩  Permissions  ⟩  Multiplayer

Multiplayer

Cables offers the possibility to simultaneously work on patches, using the multiplayer feature.

Users that have at least "Read Only" access to the patch, through collaboration or teams, can join a multiplayer session in any patch.

There are currently three levels of access in a multiplayer session, only the "Pilot" can make changes seen by all other "Participants"

Non-Participant

If you are in a patch and there is a multiplayer-session going on, you can continue editing the patch (given you have the proper permissions) or you can:

  • see who is currently in your patch, either in a session or as a non-participant
  • join the multiplayer-session and become a participant
  • start a multiplayer-session if none exists, yet
  • chat with other people in the patch (i.e. to start a multiplayer-session)

Participant

join

Once you join a multiplayer session, you will become a "Participant". As such you can:

  • see the cursors of all participants in the session
  • see area-marking of all participants in the session
  • follow the changes of the pilot, see updates in selected ops, parameter changes and the renderer
  • request the "pilot seat"
  • re-sync your patch with the state of the pilot, if it went out of sync
  • leave the session

Pilot

join

Starting a multiplayer-session will make you the "Pilot". If you join a session later, you can request the pilot-seat to make changes to the patch.

As a pilot you are able to:

  • add and select ops and make changes to the parameters
  • navigate the patch (pan, drag, go into subpatches, ...) and participants will follow you
  • accept or decline requests for the pilot seat (requests will be automatically accepted after 20 seconds to prevent lock-outs with people going "afk")
  • revert the patch (for everyone) to the last saved state
Found a problem? Edit this file on github and contribute to cables!