roundware
merge "speaker" audio with "asset" audio into single universal format
It is worth considering a more universal format for Roundware audio. Technically, there are not many differences between the two and it seems to me that if we had a single model, we could simply have a field that signified if the audio was continuous or momentary i.e. Speaker or Asset.
Asset vs. Speaker Audio
| Asset audio | Speaker audio |
|---|---|
| plays once | loops continuously |
| plays selection of source audio file | plays full file, looped |
| fades in and out based on Audiotracks | attenuates by physical location of user in relation to range shape |
| mono | stereo |
| local source file | can be sourced locally or from any mountpoint online |
| mp3/wav file | mp3 audio stream |
When we start designing for client-side mixing, this should be a part of the discussion.
@subelsky tagging you per previous discussions we have had relating to client-side mixing...would love to hear your thoughts on this.
I definitely agree; ideally we'd eventually move to a scenario where all audio files are treated the same, and all of the features like looping, fading in and out, geofencing, etc, are instead parameters of the "script" of each piece, describing how the assets are used
