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 for Cables Standalone VersionExport a ZIP fileExternal triggers / functionsUsing variablesPreviewing / uploading exported cables patchesExamples for EmbeddingPermissionsUsersPatchesTeamsOpsMultiplayerPatchlistsCoding OpsCreating AttachmentsGeneral op/Port CallbacksPortsDynamic PortsArray 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 DocumentationLightingLightsShadowsWorking 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  ⟩  FAQ  ⟩  General questions  ⟩  What is dev.cables.gl

What is dev.cables.gl

The most recent release of cables will always be on cables.gl and you can check the features and fixes in that release in our changelog.

While we are working on a new release we constantly push changes to dev.cables.gl, sometimes a few times a day.

This gives you the ability to work with the latest, hottest features in cables and test your patches before the next release.
While we keep a solid eye on backwards-compatibility, feel free to report any breaking changes through discussions.

The version on dev.cables.gl might be buggy, not polished yet and the server might be down at certain times.
Do not rely on new features being exactly as they are on the development version before release...things might change.

We try to have everything on dev.cables.gl in the next release.
There is no guarantee on that though, as some things might need more time, work, love and testing and others might be removed again entirely as we decided otherwise. Do not count on things on dev.cables.gl!

Log in to dev.cables.gl using your cables credentials. All your patches will be in the same state.
You can find ops that are currently developed in the Ops.Dev-Namespace for you to test, explore and take a sneak-peek. If you use any of these in your patches, you will not be able to open these patches on "live" anymore...usually until the next release.

Doing things this way gives us the possiblity to ask for feedback on new features, find bugs that we didn't think of early and also test new features with bigger patches and a bigger audience.

Found a problem? Edit this file on github and contribute to cables!