Skip to main content
Whatcha need to Know?
Table of Contents
< All Topics
● Knowledge Base · Main

Collections Ultra

Virtual folders for the SFX you reach for constantly. Not bound to any database — Collections stay visible across DB switches.

Collections are virtual folders for the SFX you reach for constantly. Think of them as a holding tank that’s always available regardless of which database is active.

  • Collections are not attached to any database — they stay visible across DB switches. This is by design.
  • Build any folder structure, or import a template via Import Folder Structure (folders only, or folders with files).
  • Show Collections Folder reveals where Collections are saved on disk — useful for sharing or syncing between machines.
  • Export a Collection to hand off pulled sounds to someone else.
Collections node
Because Collections aren’t database-bound, you can switch databases and they remain visible. The trade-off: clicking a Collection folder only shows files that exist in the current database in the Results List.

Collection options

Collection options menu

Right-click a Collection file, folder, or the root node to see context-appropriate options. The three-dot icon on the root reveals the menu shown here.

Show Contents is the most important one. Since the Results List can only show records bound to the current database, you’ll only see records from that DB when clicking a Collection folder. Individual files always click through fine.

When a Collection has been exported and transferred, transferred files appear dimmed. Right-click and mark them Un-Transferred to copy them again on next export.

  • Make Root Collection — promote a folder to its own top-level Collection.
  • Remove Offline Media — recursively prunes entries whose source file no longer exists on disk.
  • Import Legacy Collection File — load legacy 5.x .col / .lib files.