Library Settings

Everything you import into Vizloom — songs, visuals, templates and collections — lives inside the Vizloom Library, which is backed by a local database. The Settings dialog, opened from the gear icon in the top-right of the UI, is where you configure that library.

Library Location

You can change the library's database location from Settings. This lets you point Vizloom at different databases, each with its own visuals library, templates and songs collections — for example a dedicated library for live gigs on an external SSD, and a separate one for experiments on your laptop.

Relocate Missing Files

If you move your audio files or visuals folder on disk, Vizloom will lose track of them. The Relocate Missing Files controls in Settings repair those broken references in one pass instead of fixing them song by song. There are two separate flows:

• Songs — scans the library for songs whose audio files are no longer at their stored path, and lets you point Vizloom at the new location.
• Visuals — does the same for visuals whose video or image-sequence files have moved.

Maximum Worker Threads

Vizloom does its heavy lifting, such as decoding the frames of your visuals and importing media, on background worker threads. The Maximum Worker Threads option in the Application Settings limits how many of them can run at the same time. By default Vizloom uses all the threads your hardware supports except one, which is kept free for a smoother experience; that is also the highest value the setting accepts.

Note: If you are observing freezes and frequent frame drops, try reducing this number.

Video Memory for Visuals

Higher values render faster, since more frames can be kept loaded at a time. Lower values are safer on machines where the estimate turns out to be too generous.

Note: If renders come out with missing frames, or the app becomes unstable / crashes while rendering, try reducing this number.