Using fmod 2.01.05:
I have been working on a project that has been working fine. About a month ago I updated from 2.01. XX (cant remember - an earlier version at least), to 2.01.05.
Since then I have been starting to get weird snapshot behaviour. It might be caused by the update, it might not.
Basically snap shots seem to be affecting each other.
I have snap shot X and snap shot Y.
When triggering snap shot X, snap shot Y is being triggered as well, without ever being triggered from code. The two snapshots are following the exact same on/off pattern along with the exact same fade in /out time, even though I set them different and even though one snapshot should not be triggered at all.
If I look in the reference viewer, I can see that snap shot X is not referenced from anywhere. (only code).
This has started happening on multiple snap shots all of the sudden.
I’m wondering if you might have any ideas if I am doing something wrong or if there is an unstability in fmod currently regarding that problem?
In the last update I know FMOD would crash when changing snap shots, so maybe this could be related? In this version, routing sound from one track to another track within an event is broken, maybe snapshots are being weird as well?
I can see the snap shot behaving weird (as described above) in the snapshot activity monitor in the profiler.
Right now, I cannot use newly added snapshots at all. Even if i call the from code, they dont trigger. They only trigger (unwanted) at the same time when a certain other snapshot is being triggered. This happens across different snapshots.