Encountered this today. Firmware 0.3.8
So I set up yesderday for a track I have been working on for a couple of days a kind of master cue (cue 13), that just prompted start that cue (3, till its end), then this one (2, till its end), then this one (1, infinite loop). All fine.
Today, after boot up (my template in only empty tracks with no engines and stereo fx on each track) and reloading my project, and lauching my master cue 13, I ran into the following: PP crashes at the moment it starts a new cue. The first two time it was upon switching from 3 to 2 (I say switching, but it is still actually a sequence of start commands from cue 13). Then it successfuly passed the cue 2, but then crashed when switching to cue 1. Tried a couple of times.
What may be relevant is that if I ditn’t use the (master) cue 13 but just manually switch cues, it is all fine, no crash. So it’s really when the switching of cue is commanded by the start command of the “master” cue.
Shutdown the pp, reboot, no more success. Then I tried the “restart firmware” way instead and this time it was ok (but maybe not relevant, considering what comes next). And after being ok the first time, it never crashes again, which seems to point towards something that happens (or not) on either startup or project loading.
So after a session, I shut down the pp. Go back to it later on, same thing: repeated crashes on cue switching. This time the “restart firmware” didn’t make a difference, so it was probably luck the first time. Only after a number of unsuccessful attemps, it finally works fine (and keeps working fine). Just for the sake of testing, shut down pp again, same story : have to retry a couple of times to get it not to crash on switching. Etc…
More details : CPU around 60% - 70%. Track 1 : external. Track 2 : quad engine (percussive synths) and fxs. Track 3: quad engine (samples on all for engines) and fxs. Track 4: nothing. Track 5 : no sound engine, fx for sends.