Noel Borthwick [Cakewalk
]
Yes I was able to reproduce the blank module issue today when doing some mixing. The last PC module on my buses stopped drawing. It appears to be just a GUI layout redraw bug of some sorts. The module is not really missing but the UI stops painting properly. Closing and reopening the project fixed it for me.
Its not a serious issue but definitely annoying. We'll fix it for sure once we nail a recipe for whats causing it - don't worry.
Noel, I'm pretty sure I also saw the blank module thing, or perhaps it was just the header (or a partial header) of a module that wasn't actually in collapsed state, as the first module in Pro Channel at least once. This happened in the context of playing around with the Console Emulator on a project, and doing a lot of switching between tracks and buses to add it in, tweak it, and change its position in the signal chain. I might note that I never saw this issue in X1 Producer Expanded. (Note, though, that I may have only seen this issue in X2 with the Console Emulator, so, if it turned out to be specific to that, it, of course, could not have happened in X1 Producer Expanded.)
Some additional "fuzzy observations" ("fuzzy" on account of I have not yet been able to come up with reproduction recipes, and thus some of the observations may not be quite accurate):
It seems to frequently be the case that Pro Channel doesn't scroll as expected. When this happens, clicking on the header for a Pro Channel module doesn't restore the scroll function. The only surefire way to restore scrolling is to click on somewhere in the body of the module (e.g. between knobs or touching a knob), after which scrolling functionality is restored. My expectation here is that even just having the mouse over a Pro Channel module, without even clicking anywhere, should allow scrolling.
Another frequent occurrence has been that changing the focus between different tracks and/or buses sometimes results in the Pro Channel's staying on the previous track or bus that had the focus. It seems that the key is to click on the track or bus a second time to get the focus to change. However, it may also be that clicking on the track or bus header, as opposed to somewhere in the body of the track or bus strip, also may not change the Pro Channel module visible in the Inspector.
I've also had at least three (probably more) crashes in the context of playing with the Console Emulator and doing the above-described shifting around between different tracks and buses to turn modules on and off and shift their position around. Unfortunately, none of the crashes I experienced were the type that SONAR trapped in order to be able to send the information to Cakewalk. Trying to create a simple project to recreate the crashes (since they were frequent -- at least 3 in the space of a half an hour at one point yesterday) has thus far not reproduced the problem, either. The one thing I noted when looking at the Event Editor's listing for the three crashes I checked was that one of them mentioned a problem in NTDLL.DLL, and the other two said "unknown" for the area of the crash. To put this in context, the only crashes in recent memory that I've had with X1 were related to having multiple instances of KONTAKT active in a project (there was no KONTAKT at all in the project that was crashing on me yesterday -- I've had a longstanding problem through multiple versions of SONAR and KONTAKT, where using multiple concurrent instances of KONTAKT in a project will frequently crash SONAR, especially when recording to one of those instances, though I think it may also have happened during playback at times; the workaround is to freeze all but one instance to avoid crashes and try to use the multi-timbral capabilities to minimize the inconvenience of having to keep freezing and unfreezing instances while refining an arrangement). The same was true for SONAR 8.5 (and probably SONAR 8 as well, at least once I moved to x64 -- I used to get more frequent crashes under x86 due to bumping up against the 2 GB application memory space limitations thanks to large softsynths).
One other thing I've seen in the same context is bus (and I think probably also track) controls becoming unresponsive (I'm talking about in the bus controls in Track View rather than in the Inspector), where, for example, you try click-dragging on the output fader or clicking on a Solo button and nothing happens.
The net from my observations is to suspect some issue in the area of sychronizing focus changes with redraws, but perhaps also some even more insidious focus-related issues that may cause the loss of context (i.e. as in the case of not being able to manipulate controls) and which could ultimately lead to the non-trappable crashes.
Needless to say, if I find any recipes, and/or get any usable crash dumps, I will provide them as soon as possible.
Rick