Just sharing a thought…
I consider myself to be a casual user of Cantabile, unlike many of the posters who are professional musicians. I have used Cantabile2 and migrated to Cantabile3, and read this forum daily. It seems to me that there are a number of users who struggle with the key concepts of Cant3, e.g. states, set lists, bindings, embedded racks, etc. and may get put off at fully appreciating the great things Cantabile3 can do, even for the casual keyboardist. I recall wondering about when I should be using a song versus a set list, and how to best organize a playlist of 20 midi songs that I play along with for a casual session in my studio.
One thing that I really like about the forum, is that several of the real experts, e.g. Neil, Torsten, and others, often take the time to talk about a specific example of what they are trying to do and how Cant3 is used to make it happen. Until I read a forum post recently, I hadn’t though about the advantages of putting instrument groups into separate racks, i.e. organs in one rack, strings in another, horns in a 3rd rack, then embedding those racks as needed.
If I were a newbie to Cantabile, I believe I would greatly benefit from reading about examples of using Cant3 to make life simpler. My suggestion would be to gather up the helpful examples of using Cant3 many of which are buried in the forum comments and put them into some sort of separate forum or document that all users of Cantabile can review and benefit from. In addition, perhaps other users that are successfully using Cantabile can post their “real-life” examples and how they setup Cantabile to provide a solution.
I realize Brad is heavily involved making the product better, so there isn’t a “staff” person to do something like this, but if someone would setup a process for a forum or a document, I could help by copying the “use cases” I find in various forum comments into the designated place.
Again… just a thought to help newcomers trying out Cantabile to see more easily how flexible and useful the product can be.