We’re chugging along on my iPhone interactive sound-thingy – and have a system implemented with several events being triggered. But there seems to be small performance "dips" when the events are started. I’m fairly sure, that they are loaded into memory by using
result = group->loadEventData(FMOD_EVENT_RESOURCE_SAMPLES, FMOD_EVENT_DEFAULT);
but still… should I be using "sounds" instead – where are the pro’s and cons?
- popgoblin asked 9 years ago
An Event is part of the Designer API, which sits on top of the Ex API (of which Sound and Channel are members). Basically when you play an Event it may make multiple Channels from multiple Sounds (and also do fancy stuff with parameters, FX, etc). You want to use Events if you like the Designer tool and the perf hit is worth the gain in content creator productivity. If you want to keep it super lean/fast, only use the Ex API.
Please login first to submit.