Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MetaSound Prefix? MS_ or A_? #97

Open
shaunrandall opened this issue Aug 29, 2023 · 2 comments
Open

MetaSound Prefix? MS_ or A_? #97

shaunrandall opened this issue Aug 29, 2023 · 2 comments

Comments

@shaunrandall
Copy link

My personal preference is MS_ but don't mind either way.

MS_
Pros:

  • Most prefixes follow UE naming.
  • Its unique

Cons:

  • MSPresets is a popular naming convention for Quixel so could generate some confusion/

A_
Pros:

  • They function similar to Sound Cues
  • One character on already long names

Cons:

  • Metasounds can do a lot more than cues so might not be the most appropriate
@EnricoPietrocola
Copy link

Personally, I use MS, but I am now thinking of doing MSS for Metasound Sources and MSP for Metasound Patches.
This allows me to look for all Metaasounds with MS, and differentiate easily in the search between sources and patches when I need to.

Metasound and Audio/SoundBases are in my opinion different enough to have this difference, I usually look for either Audio files or Metasounds, rarely both of them together, so I will likely keep naming my assets like this

@EnricoPietrocola
Copy link

P.s. I'll probably look for further differentiation between MetaSound Preset and Patches, will be interesting to know other sound people opinion on these

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants