TEZLance,If tracks are visible in the PRV those not in focus are greyed, is this intentional? For this update it says "Color-coding relates tracks to data for easy identification in complex projects". Prior to this update the unfocused visible tracks retained the note color in a dimmed form, which I found particularly helpful! If greyed is intentional, is there any way that there could be a display option in the PRV, the option would be simply "dimmed" or "greyed", and I'd choose dimmed... I would hate to roll back just for this.
TEZLance,For this update it says "Color-coding relates tracks to data for easy identification in complex projects".
pwalpwalmissed opportunity for marketing, all this new prv stuff, should have been in the rolling updates bit (coming soon) or did i miss it?
WallyGSince no one is mentioning the issue of Sonar crashing when reopened with the PRV un-docked, am I correct in assuming that this has been fixed in the final 2017.03 update? There is no mention of it in the "fixes/enhancements".
Lance Riley [Cakewalk]WallyGSince no one is mentioning the issue of Sonar crashing when reopened with the PRV un-docked, am I correct in assuming that this has been fixed in the final 2017.03 update? There is no mention of it in the "fixes/enhancements".That issue was reported from Early Access and has been fixed in the Public Release for SONAR 2017.03. We typically don't include fixes from Early Access in the public announcement because these were not bugs in the previous public release. That issue was fixed between the last updated Early Access build and the public release so it didn't get any mention since we didn't update Early Access a 3rd time before going public but that crashes is resolved in the update.