Hi Joe, thanks for the feedback and thanks for running the latest beta.
There are a lot of points here, some seem related to use case / potentially the installation (especially the oscillators one).
If you could drop a message to email@example.com it'd be great for us to dig into these in a bit more detail with you and potentially arrange a phone call.
Documentation is high on the agenda and should be out early next week once the next development plan is implemented. (we've been focused full steam ahead with the latest release planning) - I've been sure to add your point about thee warnings to our list of development tasks!
I will take time this afternoon to do a much better job of testing and documenting this, including pictures and steps needed to recreate the issues.
Often (as I am sure you know) just the task of documenting a 'bug' reveals that it is not a bug after all but a End User Malfunction.
I am a full time software developer and I hate it when one of my users sends in a bug report that does not have enough details to actually help chase down the problem.
Just got one this morning I got a email, entire message: 'New changes do not work correctly, please FIX asap!!!!!'
This was on a release with about 8 new features and a dozen bug fixes....SMH.
It’s still buggy, I bought it and it crashed and now will not load, crashes on boot up, buyer beware….
Seems very buggy and unfinished.
I am not sure if it is just my installation, OR me not understanding the program.
I have full read the documentation but it does not seem to be kept current with releases.
At that point it had taken me about 2 hours to setup and I was too annoyed to continue "testing".
I am using the beta release, going to roll back this afternoon and will update this with any changes or improvements.