1 I am moving this thread to the Sonar forum. The Cakewalk folks have expressed that they would like each issue to be maintained in a separate thread, rather than combining multiple issues into a single thread, such as this thread. They work on these issues independently, most of the time, and some needed development for some similar updates or fixes may require changes to different sections of code, or may be harder to implement than others, so some fixes may get split across multiple maintenance cycles. This is particularly more likely now, with a monthly development and release schedule to adhere to, rather than the 2 or 3 times in a year, as it used to be.
2. I checked your links above - and actually moved the first of those 2 links to the Problem Reports forum, leaving a placeholder where it originated.
3. For the second link above, while there is a CWBRN number generated for the issue, the issue itself does not appear to have yet been confirmed by others, so I updated the thread with the info that it needed confirmation and then it would get moved to Problem Reports.
So - yes - please please please keep each issue in a separate thread, as for whatever reasons this is how the Cakewalk senior folks and the developers have indicated it works best for their purposes - which will benefit us greatly too, with potentially more development work able to be done for a given month - due to keeping the Problem Reports forum clean and ordered as it helps them the most. :)
Bob Bone