Auditioning/profiling encoding and loading settings

[MF_Kitten]

I need to benchmark the CPU load and RAM usage of different encoding and loading settings. When I change from, for example, Vorbis to PCM, does that take effect immediately if I use Live Update or if I simulate a previously recorded profiler session? Or is there something I need to do to “force” the chsnge through?

[li_fmod]

Hi,

@MF_Kitten

When I change from, for example, Vorbis to PCM, does that take effect immediately if I use Live Update or if I simulate a previously recorded profiler session?

In my testing, simply changing Vorbis to PCM while connected through Live Update did not refresh the runtime sample data. The expected PCM memory/CPU difference only appeared after rebuilding the banks and restarting the runtime.

For performance comparisons, I’d also recommend taking a fresh runtime profiler capture for each configuration rather than relying on Simulate.

@MF_Kitten

Or is there something I need to do to “force” the chsnge through?

Rebuilding the banks and restarting the runtime so that the rebuilt banks are reloaded would be the safest way to ensure the new encoding or loading settings are being used before taking the next capture.

Hope this helps.