Bug reports and confirmed bugs do't equal instability
May I was not understood properly.
1. Public betas are for finding bugs. There is absolutely no reason to avoid them like the plague.
2. Before installing a beta or any other firmware ALWAYS do a backup.
3. Never install a beta before a critical performance, be it gig, audition, rehearsal.
4. If you encounter a bug: send a bug report. If it affects your performance badly: roll back to the previous supported version.
That said, with 'stable' I obviously mean you won't break anything in your profiler when installing the beta. I get the impression more and more people are "afraid" to install a beta and put it through its paces. In the end this will lead to much longer tgimes to get a beta release-ready which would be quite unfortunate IMO.
This is so true Ingolf A public beta is for people to use and find bugs I used the latest PB release this weekend for 2 gigs and not 1 issue so far. I did have to recalibrate my exp pedals for them to work again but other than that no issue. More people should test these releases so it can be elevated to release level quicker
i would like to add that reading the readme file that comes with a public beta is mandatory. The 3.1.2 document clearly states that performances made with the current public beta are not compatible with older versions.