The following string is used in all Strata data regions. It is the base for all rendered file names in all of the REAPER projects:
CategoryFull=;Category=;SubCategory=;CatID=;UserCategory=;VendorCategory=;SourceID=Historical Firearms;UserData=;Explanations=;Synonyms=;OpenTier=;
The following example shows a string that uses values from a Historical Firearms subproject named Pistol Muzzleloader. The highlighted text between the equals signs (=) and semicolons (;) are the values to use in various REAPER wildcards, used when rendering to files and when rendering metadata.
CategoryFull= GUNS-ANTIQUE ;Category= GUNS ;SubCategory= ANTIQUE ;CatID= GUNAntq ;UserCategory=;VendorCategory= _Pistol Muzzleloader- ;SourceID= Historical Firearms ;UserData=;Explanations= Old black powder weapons, muskets. ;Synonyms= muzzleloader, musket, black powder, flintlock, longrifle, fire lance ;OpenTier= 18th Century-Muzzleloader-50Cal ;
The data region name string is generated in the collection SoundBook, a downloadable spreadsheet available with the collection files. For example, in the Historical Firearms SoundBook, open the REAPER File Name and MetaData Region Formula sheet for details.
The REAPER Render to File settings use wildcards from the data region to determine the output file name. REAPER wildcards begin with a $ symbol. All subprojects use the following wildcards:
$region(CatID)[;]$region(UserCategory)[;]$region(VendorCategory)[;]$region_$author_$region(SourceID)[;]$region(UserData)[;]
You can see the filename and wildcards in the REAPER Render to File window:
 |
File name with wildcards: $region(Category)[;]/$region(SubCategory)[;]/$region(CatID)[;]$region(UserCategory)[;]$region(VendorCategory)[;]$region_$author_$region(SourceID)[;]$region(UserData)[;]. The resulting destination folders and generated file name are displayed in the Render To text box, below the File name text box. |
If you modify both the Render to File Filename Formula and the Data Region(s), you can set up Strata subprojects to name files automatically with your own convention using the same techniques that Strata uses.
You can modify the existing UCS naming setup. For example, you can replace the CreatorID with your own initials. This is set in the Author field of the Project Setting/Notes tab. Or you can change the SourceID part of the filename, which is found in the Data Region SourceID section.
If you have not already chosen a naming convention for your project, we strongly recommend using the UCS. It is a combination of human and machine-readable, with significant flexibility. It is quickly becoming a global standard that many audio designers are familiar with. It is also supported in multiple languages.
Was this page helpful?
Need Support?
Questions? Problems? Need more info? Contact us, and we can help!
Visit our Support pageTell us about your project. We're here to help.
Register your project and we'll help you get started with no strings attached!
Get started with Wwise