It creates the R2R.idx or similar cache files that act as a roadmap for the DAW. How the Cache Builder Works
Without the Cache Builder, Reason would open to an empty rack because the "registry" of these extensions is missing. The Cache Builder performs the following steps: the Rack Extension folder for new content. Decodes the info.js or manifest files within each RE. Builds a centralized cache file. Links the extensions to the R2R virtual driver/emulator. Troubleshooting Common Issues team r2r reason rack extension cache builder exclusive
When you install a Rack Extension in an R2R environment, you typically place the folder in a specific directory (usually C:\ProgramData\Propellerhead Software\Rack Extensions ). It creates the R2R
When using Team R2R’s custom environment, the software bypasses the standard phone-home verification. However, Reason still needs to "see" and "index" these extensions to load them into the rack. The is an exclusive utility developed by R2R to manually compile the metadata and registry info that Reason requires to recognize local RE files. Why is it "Exclusive"? Decodes the info