Skip to content

Latest commit

 

History

History
224 lines (179 loc) · 11.7 KB

README.md

File metadata and controls

224 lines (179 loc) · 11.7 KB

Capy Canvas

Capy Canvas

Linux · Android · iPad · Windows · macOS · Web

Website · Download · Try in your browser · Artist guide · Engineering

Capy Canvas is free, GPU-accelerated painting and photo editing software.

This project started from the simple idea of using GPU shaders to simulate physical media. Equations that model graphite rubbing on paper, or ink soaking into the page. Wrapped in a customizable UI that can be as minimal or complex as you like.

We want artists to build their own tools. We envision a world where painters build their own brush engine, and photographers write their effect shaders. While software may be AI generated, the tools should be used by humans. Artists shouldn't have to wait for a software company to decide that their idea is worth building.

That is why Capy Canvas is open source and forever free, and we want this to be a community of builders and creatives.

Sketch

My first foray into the digital art world (like many others) was with Procreate over a decade ago. Back when the apple pencil first came out, it was magic. Even though the hardware was slow by today's standards, it was so well done that it gave a real pen-to-paper feeling.

This was the first time a drawing app was fully optimized for a mobile device, using predictive pen tracking and GPU powered brush+rendering engines. Then they dropped a clean and minimalist UI on top of it, which then became the industry standard for all modern drawing apps.

The Sketch workspace is a tribute to our roots. The place where everyone starts out.

An ink drawing of a train beneath a large tree in Sketch, with the drawing filling the screen and tools at the edges. An ink drawing of a train beneath a large tree in Sketch, with the drawing filling the screen and tools at the edges.

Paint

Once you get into proper comic/manga work, the simple tools don't cut it anymore. Lasso fill is your best friend, and you learn to live with the necessary evil of masks.

There are many tools out there for professional illustration workflows, CSP and medibang are often what people learn first. And they are great, easy-to-use and inuitive software. All you have to do is follow the process and it usually turns out OK.

While they are true workhorses, they are slow, built for an era where all rendering and compositing was done on the CPU instead of the GPU. So they never were able to match the powerful, realistic paintbrush engines in modern apps like Fresco and Rebelle.

The Paint workspace brings simulated physical media to digital illustration.

An oil painting of a house by the sea at sunset in Paint, with brushes, colors and layers beside the canvas. An oil painting of a house by the sea at sunset in Paint, with brushes, colors and layers beside the canvas.

Photo

Mobile devices are becoming more capable every day. It seems like OLED screens are everywhere, and my old phone saves its images in P3 HDR format by default. SRGB is a thing of the past.

To this date, the only painting app that properly supports wide gamut HDR is Krita. HDR is a complicated beast and is hard to get right. When you publish HDR and wide-gamut images online, you need to control the gain mapping so that it still looks good on SDR devices. Of course no photo editor is complete without the all of the basics (proofing, effect chains, the whole enchilada)

The Photo workspace enables stunning visuals for a new generation of wide-gamut screens.

A terrarium photograph in Photo, with the subject saved as a selection layer above the photo. A terrarium photograph in Photo, with the subject saved as a selection layer above the photo.

Tools

Area Tools and operations
Brushes Pencil, charcoal, ink, bristle, watercolor, oil and airbrush; pressure and tilt, paper grain, textured tips and color mixing.
Layers Groups, clipping layers, layer masks, blend modes, editable color and gradient fills, and selection layers.
Selections Rectangle, ellipse, lasso, polygon, contiguous color and tonal range; Quick Mask, feathering and saved selections.
Effects Linked non-destructive effect chains, adjustment layers and effect masks; Curves, Levels, color grading, blur, sharpening, halftone and painterly effects.
Retouching Clone Stamp, Healing and Spot Healing, dodge and burn, blending and liquify.
Color sRGB, Display P3, Adobe RGB and ProPhoto RGB; ICC profiles, 8/16-bit SDR, 16/32-bit float HDR, print proofing and gamut warnings.
Drawing and transforms Reference-layer fills, Enclose and Fill, gradients, rulers, crop, resize, perspective and mesh warp.
Workspace Docked or floating panels, tab groups, configurable toolbars and shortcuts, saved layouts and Zen mode.

Building the engine

We wanted to build the fastest brush and rendering engine we could, aiming for 120+ frames per second with brushes thousands of pixels wide. And we want that response with physical paint, live effects and HDR too.

We took our cue from game engines. The brush engine and layer compositor are built around shaders, on top of wgpu. Wet paint stays on the GPU as the brush picks it up and mixes it into the next part of the stroke. The effects run there too, and compatible adjustments can share a shader instead of each writing out another image.

Of course a fast brush is only part of it. There may be hundreds of layers to combine after every stroke. We update the parts that changed and keep the rest. And a layer with a few marks on it only needs paint storage for those areas. This matters when the same engine has to fit on a tablet.

We also want a brush or effect someone builds on Linux to work on the other platforms. The shared engine is written in Rust and compiles for all of them, including the browser. Each native app uses its platform's own controls around that engine.

There is still performance work to do. The measurements show where we meet the targets and where we don't. The engineering whitepaper goes into the design, including color and HDR.

Contributing

The idea of artists building their own tools is something we want people to actually try. For an effect shader, the Tent Blur example is a place to start. It defines a filter and its controls in JSON and WGSL, without adding a Rust kernel. The extension guide covers how to load it. Building a new brush engine involves the shared code; the brush guide points to that.

We also need help with interface design and testing the app with actual drawings. If a tool gets in the way of how you work, tell us what you were trying to do.

Development

Capy Canvas is in development. Linux and web are the most complete versions; we're bringing the other ports up to the same level. Painting requires a hardware GPU.

The download page lists available builds. To build from source, choose a platform in the developer guide. It also covers the checks to run when making changes.

Package layout

Shared Rust crates and platform clients

Shared code lives in crates/, native clients and the browser app in apps/.

Package Responsibility
layer-core Artwork, undoable edits and .capy files.
layer-engine Pen input, brush dynamics and stroke generation.
layer-ui Shared tools, commands, editor state and layout.
layer-workspace Saved workspace layouts.
layer-color Color profiles and photo codecs.
layer-render Engine-to-renderer contract.
layer-render-wgpu GPU painting, effects and composition.
layer-host Shared native integration.
layer-bench GPU benchmarks and brush previews.

License and branding

Original code and non-brand assets are licensed under MIT or Apache-2.0, your choice. Contributions to those parts are submitted under both licenses unless agreed otherwise.

The Capy Canvas and Capy Atelier names and capybara artwork have separate branding terms. Modified versions need their own branding unless you have permission. Dependencies retain their own licenses; see third-party notices.