Module previews can be expensive to create, especially in a large plugin collection. Deep Cache replaces the active module browser with a browser that can prepare those previews incrementally and reuse saved images. Its purpose is to reduce the work needed when you open the browser or scroll to another part of your collection.
Deep Cache is a utility for Rack’s interface. It has no knobs, buttons, inputs, or outputs, and it does not process audio or CV. The bars, count, database readout, and lights are indicators. Right-click the module panel to change its settings.
One module is enough. Add Deep Cache anywhere in the rack. No neighboring module or cable is required. It activates automatically when it can take ownership of the browser. Keep it in your template patch if you want it available whenever that template is loaded.
Caching does not make the selected instrument’s DSP run faster. It prepares the pictures used to browse modules; adding a module still creates a real instance of that instrument.
Automatic operation
From preview to saved image
1. Recover existing previews
On activation, Deep Cache checks its saved database for matching previews. Valid images can be loaded and prepared for display without constructing the original preview widget again. Images that are not currently eligible for display can remain deferred until needed.
2. Build what is missing
Missing or outdated previews are scheduled for construction. Rack preview widgets must be created on the UI thread, so Deep Cache spreads this work across frames under the selected UI work budget.
3. Render the rasters
The preview is rendered into a reusable image. This second stage is called framebuffer warming. A completed build and a display-ready raster are separate milestones, which is why the panel has two progress bars.
4. Keep the result
Completed images are saved in a lossless compressed database and reused in later sessions. Planning and database work run in the background; graphics creation and uploads still require Rack’s UI and graphics context.
The browser remains usable while work is underway. A first pass through a large library can take time and consume memory and graphics resources. Later sessions benefit from the saved images, but loading, decoding, and graphics upload still take time.
Plugin updates and changes to relevant rendering settings can make cached images outdated. Deep Cache refreshes affected previews. Rack panel-theme changes keep an existing image visible while its replacement is prepared; changes to Leviathan’s rendered palette refresh the affected Leviathan previews.
Read the panel
Progress at a glance
The panel summarizes work by plugin. A plugin can contain many module models, so these counts will differ from the module-level totals in Cache statistics. The bars describe the current work pass rather than a fixed count of every module you own.
BUILDS · violet bar
Percentage of plugin build groups completed. The number beneath the bar is the completed-plugin count. Building prepares preview widgets; it does not by itself mean every resulting image is ready.
RASTERS · cyan bar
Percentage of plugin groups whose preview images have finished framebuffer warming. This stage turns constructed previews into the images used by the cache.
DATABASE · status readout
Shows the database state, its ready-plugin count, and database size in MB. During loading or updating, the count can show ready plugins against a target. This size is separate from RAM and graphics-memory use.
PLAN / WARM / READY / ERR
Amber PLAN indicates planning; blue WARM indicates warming; green READY indicates a completed cache pass. Red ERR flags a cache/database error, an inactive duplicate, or a browser ownership conflict. Read the database status and context menu to distinguish them.
Database and ownership states
Readout
Meaning
EMPTY
No database content is currently reported. This can appear before initial work begins.
LOADING / UPDATING
Recovering saved images or updating the cache with prepared previews.
READY
The database is ready. This readout describes storage; the separate bars and lights describe preview preparation.
COMPACTING / CANCELING
Reclaiming obsolete database space or stopping database work.
READ ONLY / MEMORY ONLY
Persistent writing is unavailable to this instance. It can use a readable snapshot where available and keep newly prepared previews in memory.
STANDBY
Stoermelder MB owns the browser. Deep Cache waits and activates automatically when MB is removed.
DUPLICATE
Another Deep Cache in this Rack scene owns the browser. This copy is inactive.
CONFLICT
Another plugin replaced the browser after Deep Cache activated. Deep Cache stops background work.
ERROR
The database encountered an error. Check Rack’s log for details.
Right-click the module
The context menu
These are Deep Cache’s module-specific controls. Inactive or conflicting instances show an explanation in place of the normal controls.
Menu item
Function
Rebuild cache
Clears current previews, requests a reset of the persistent archive, and starts a fresh pass. Use this when you need to regenerate images. It repeats the initial preparation work and can affect the shared database.
Enable multi-brand filters
Enabled by default. The browser’s Brand menu lets you toggle several brands and show their combined results. Disable it for one brand at a time. Turning it off with several brands selected retains one selected brand.
Cache resolution → 100% / 200%
100% is the default canonical image scale, independent of browser zoom. 200% creates sharper images when enlarged, with roughly four times as many uncompressed pixels. Changing this shared setting invalidates the cache identity and starts regeneration.
UI work budget → 0.5 / 1 / 2 / 4 / 8 ms
Default: 2 ms. Controls how much time incremental UI work aims to use per processing pass. A smaller value spreads work out; a larger value allows more work before yielding. It is a cooperative budget: a single slow third-party preview can exceed it.
Cache statistics
A read-only breakdown of progress, resident resources, memory estimates, failures, and preview-construction times. See below.
Understanding Cache statistics
Completed is progress through the current model-level work plan. Resident records counts cache records held in memory; Resident previews counts resident or framebuffer-ready model previews; Framebuffer-ready counts previews ready at the image stage. These describe different resources and need not match.
Volatile QOI is compressed image data retained in memory. Retained RGBA is uncompressed pixel data still held by the cache. Pending upload RGBA is pixel data waiting for graphics upload. Estimated GPU RGBA estimates graphics image memory. These figures describe separate parts of the pipeline and are not a measurement of Rack’s total memory use.
Failed counts failed previews. Average construction and Maximum construction report preview-widget construction times in milliseconds; they do not measure audio processing or the total time to load the database.
Everyday browsing
Your collection, with cached previews
Open the module browser as usual. Deep Cache provides search, Brand and Tags filters, Favorites, Unhide, Reset filters, sorting, browser zoom, a result count, and a Library link. The Slugs menu is a reference mapping plugin identifiers to their displayed brands.
Search matches module and plugin names and identifiers, descriptions, and tag aliases. With multi-brand filtering enabled, a module can match any selected brand; it must also match the search, selected tags, and other active filters. Select All brands to clear the brand restriction. Reset filters clears the browser’s filters, not the preview database.
Browser zoom changes the size of displayed cards. Cache resolution changes the source image detail. Enlarging a 100% cached image does not automatically regenerate it at 200%.
Right-click a browser card for its model menu. Deep Cache adds Save image… when a cached raster is available, with PNG, QOI, TGA, and BMP file options. A failed card also offers Retry Deepcache preview. Hovering a failed card shows the reported failure reason.
Removing Deep Cache restores the previous browser when it still owns the browser. Its saved preview database remains available for a later session. If another browser plugin has taken ownership, Deep Cache preserves that replacement chain.
Persistence
What survives a session
The preview database lives under <Rack user>/Leviathan/Deepcache, using a compressed image pack and an index. It is shared storage outside your patch. Saving a patch does not embed the preview database.
Cache resolution is a plugin-level setting saved in that folder’s settings.json. It is shared by Deep Cache instances rather than recalled per patch. UI work budget and Enable multi-brand filters are saved with the module in the patch.
One Deep Cache can own each Rack scene’s browser. Separate Rack Pro DAW instances can each have an active owner while sharing the same database location. Only one archive writer can update that database at a time; other instances can work from a read-only snapshot and keep missing previews in memory.
Normal updates can leave superseded image data in the pack. Automatic compaction reclaims that space once its thresholds are reached, so the disk size may not immediately shrink after previews are replaced. Graphics-context recreation can also require images to be uploaded again without requiring a full rebuild.
Troubleshooting
When something needs attention
The panel has no clickable controls
This is expected. Right-click the module to open its settings. Progress bars, counts, and lights only report status.
The first pass is slow or the interface hesitates
A large collection needs time to prepare. Try a lower UI work budget to spread the work across more frames. Individual plugin preview constructors can still stall a frame because they cannot be interrupted by the budget. A larger budget may shorten preparation at the cost of more UI work per pass.
BUILDS finishes before RASTERS
Preview construction and image rendering are separate phases. Allow the raster stage to finish. Consult Cache statistics to compare resident previews with framebuffer-ready images.
One preview fails
Hover the browser card to read the failure reason, then right-click it and choose Retry Deepcache preview. A failure can be isolated to one plugin’s preview. Use Rebuild cache only when you want to regenerate the wider cache.
The panel says STANDBY, DUPLICATE, or CONFLICT
Right-click the module for the ownership explanation. STANDBY waits for Stoermelder MB to be removed. DUPLICATE means another Deep Cache already serves this scene; the inactive copy can be removed. CONFLICT means a later browser replacement caused Deep Cache to stop background work. Resolve which module should own the browser before reactivating Deep Cache.
The database is READ ONLY or MEMORY ONLY
Another instance may hold the writer lock, or persistent storage may be unavailable. Previews can still be prepared in memory. Check other Rack instances and Rack’s log if this persists when only one instance is running.
Images look outdated or too soft
Allow automatic refresh after plugin or theme changes. Use Rebuild cache if images still need regeneration. For enlarged browser cards, 200% Cache resolution provides more detail and increases storage and graphics-memory requirements.
Reference
Deep Cache
VCV Rack 2 · 4 HP · Utility · no parameters, patch inputs, or patch outputs · module slug: Deepcache.
Checked against the local Deepcache module, browser implementation, archive implementation notes, and panel artwork. Menu labels and available behavior can differ between releases.