Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Some things to consider:
EXA could probably provide a default tagging system, but the very next request would be to allow custom tags. Consider an EDM musician, for example, who has no need for most of those default categories, and would rather tag based on some other specific characteristics.
Soundfonts create another challenge, because they can contain several different (and highly varied) sound collections within them. I tried to avoid these ones, but there are a couple default Soundfonts like this (I can think of two in the "synth" section, for example). For these, you'd probably want to apply tags to the individual "presets" within the Soundfont file.
Here's a crazy idea: would it be helpful if EXA could automatically find "similar sounds" for you? EXA would need to keep some kind of "audio profile" for each file, and would then find the best similarity matches for the current sound. That way, if you have a sound that's close to what you want, you could quickly check to see if you have one that's a bit closer.
Custom tags may not be necessary in the initial feature, but I would at least need to ensure that the tagging system can support them in the future.
Assuming tags can be nested, then you'd probably navigate into the tags using the same "sounds" menu structure that exists now. With this approach, the tags would behave like an alternative folder system. This creates an organization system that can be changed/revised without affecting the way sounds are referenced (via file path) in layouts, bundles, and multiplayer.
let's start a google sheet, where we list all current samples with their file pathes and then add a column for instrument tag and another for instrument family tag. Then we can work all together on it and make change suggestion comments, if we disagree on something.
We could also add one column, where we can write our names behind the samples, if we want to give the sample a thumb up. and another column for thumb down. Then we can use some math formula to get the stats later.
Any help appreciated
Yep, you can do that! The easiest way is to place your files into the "My Documents/EXA-VR" directory -- there are are "Soundfonts" and "Samples" folders within that directory.
You can also tell EXA to look at specific directories on your computer. There is an "AppSettings.json" file in EXA's installation files. Please see this comment for notes on where to find it, and how to change it.