Crash that seems to be about Events when no has been added/removed about mwengine HOT 3 CLOSED

No crashes like this tonight, seems the catch solved it for me!

from mwengine.

Well your observation is correct:

h0SyqJrtBi6w==/base.apk (offset 0x2afc000) (std::__ndk1::__vector_base_common::__throw_out_of_range() const+28)
2022-06-08 11:30:32.966 3233-3233/? A/DEBUG: https://github.com/igorski/MWEngine/issues/8 pc 00000000000cfdf4 /data/app/com.kiefer.llppdrums-m1wLnbt2O-h0SyqJrtBi6w==/base.apk (offset 0x2afc000) (std::__ndk1::vector<MWEngine::BaseAudioEvent*, std::__ndk1::allocatorMWEngine::BaseAudioEvent*>::at(unsigned long)+64)

indicates that the iterator is moving beyond the total vector size, which would hint that something is removed during this operation even if you're not consciously adding/removing events. Out of interest what are the properties that are being changed on the instrument (as this might affect event positioning), maybe you can share some pseudo-code of your implementation and how you are timing / invoking this randomization ?

Either way, I pushed some code in 188d32f which makes the Sequencer use a different event iterator approach which should catch out of range errors, this might help your case.

from mwengine.

Properties randomized are:

• muted/unmuted
• waveform
• attack time using instrument.getAdsr().setAttackTime(atkTime)
• decay time using instrument.getAdsr().setDecayTime(dcyTime)

The events on these instruments represents drums and I made this a long time ago. I see now I start by setting sustain and release to 0. Don't remember why but probably just to keep it simple. Can this cause problems?

I'll try the new code tonight! This is not something I can reproduce on demand but I should at least get a feel for if it helps or not.

from mwengine.