CPU-based renderer
Vello CPU is a 2D graphics rendering engine written in Rust, for devices with no or underpowered GPUs.
We also develop Vello, which makes use of the GPU for 2D rendering and has higher performance than Vello CPU. Vello CPU is being developed as part of work to address shortcomings in Vello.
To use Vello CPU, you need to:
RenderContext, a 2D drawing context for a fixed-size target area.set_paint.fill_path, stroke_path, or glyph_run.RenderContext::render_to_pixmap.use vello_cpu::{RenderContext, Pixmap, RenderMode}; use vello_cpu::{color::{palette::css, PremulRgba8}, kurbo::Rect}; let width = 10; let height = 5; let mut context = RenderContext::new(width, height); context.set_paint(css::MAGENTA); context.fill_rect(&Rect::from_points((3., 1.), (7., 4.))); let mut target = Pixmap::new(width, height); // While calling `flush` is only strictly necessary if you are rendering using // multiple threads, it is recommended to always do this. context.flush(); context.render_to_pixmap(&mut target); let expected_render = b"\ 0000000000\ 0001111000\ 0001111000\ 0001111000\ 0000000000"; let magenta = css::MAGENTA.premultiply().to_rgba8(); let transparent = PremulRgba8 {r: 0, g: 0, b: 0, a: 0}; let mut result = Vec::new(); for pixel in target.data() { if *pixel == magenta { result.push(b'1'); } else if *pixel == transparent { result.push(b'0'); } else { panic!("Got unexpected pixel value {pixel:?}"); } } assert_eq!(&result, expected_render);
Feel free to take a look at some further examples to better understand how to interact with Vello CPU's API,
std (enabled by default): Get floating point functions from the standard library (likely using your target's libc).libm: Use floating point implementations from libm.png(enabled by default): Allow loading Pixmaps from PNG images. Also required for rendering glyphs with an embedded PNG.multithreading: Enable multi-threaded rendering.At least one of std and libm is required; std overrides libm.
Overall, Vello CPU is already very feature-rich and should be ready for production use cases. The main caveat at the moment is that the API is still likely to change and not stable yet. For example, we have known plans to change the API around how image resources are used.
Additionally, there are certain APIs that are still very much experimental, including for example support for filters. This will be reflected in the documentation of those APIs.
Another caveat is that multi-threading with large thread counts (more than 4) might give diminishing returns, especially when making heavy use of layers and clip paths.
Performance benchmarks can be found here, As can be seen, Vello CPU achieves compelling performance on both, aarch64 and x86 platforms. We also have SIMD optimizations for WASM SIMD, meaning that you can expect good performance there as well.
If you want to gain a better understanding of Vello CPU and the sparse strips paradigm, you can take a look at the accompanying master's thesis that was written on the topic. Note that parts of the descriptions might become outdated as the implementation changes, but it should give a good overview nevertheless.
This version of Vello CPU has been verified to compile with Rust 1.88 and later.
Future versions of Vello CPU might increase the Rust version requirement. It will not be treated as a breaking change and as such can even happen with small patch releases.
As time has passed, some of Vello CPU‘s dependencies could have released versions with a higher Rust requirement. If you encounter a compilation issue due to a dependency and don’t want to upgrade your Rust toolchain, then you could downgrade the dependency.
# Use the problematic dependency's name and version cargo update -p package_name --precise 0.1.1
Discussion of Vello CPU development happens in the Linebender Zulip, specifically the #vello channel. All public content can be read without logging in.
Contributions are welcome by pull request. The Rust code of conduct applies.
Licensed under either of
at your option.