Cheers, hmm, unfortunately it happens with any project, really. I even reproduced it with the init saw preset just now, without changing anything. If unlucky, it can happen right off the bat when you first load Surge. But these are the steps of what I just did:
1) Load Live 10
2) Load Surge on a track, no need to touch its contents afterwards
3) Record a short clip in the arrangement with some noodling (using init preset here)
4) Duplicate the track 3-4 times so that you have multiple Surges ready to play in the project
5) Save the project
6) Close the project ("New Live Set" in Live's File menu)
7) Open the project and try playing back what's there
If you repeat 6-7, there's a high probability some instances load bad and the project sounds like in my second example clip up there. Just now, I got it to corrupt the plugin states on two Surge instances on the second reload attempt like this ^
Anyway, sorry for the semi-off-topic, this is in no way to discourage OSCer trying Surge
... I think it's great in any case. Just a warning on these current betas, to those who happen to be using them in Live 10. As mentioned, it seems this happens just in that one, and in Reaper and Live 8 it's clean.
