Lance,
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.

Thanks for the update

I haven't installed it yet though. Given that it sounds like there are a couple of minor niggles I think I will wait for the next release...

synkrotron
Thanks for the update

I haven't installed it yet though. Given that it sounds like there are a couple of minor niggles I think I will wait for the next release...

rolling releases = endless minor niggles.  You will never upgrade.
 
Old way = major niggles stay for years.

After update, VST Scanner found 12 new VSTs.
What are those? I can not figure it out.

Cakewalk did not include any additional plug-ins with this release but there are a few installed with the SONAR core. These show up as new.

Thanks for the info!

Pingkachu
VST3 instruments missing in latest update except Rapture Pro and Z3TA+2. C:\program files\common files\vst3 is in preferences, have pushed reset and rescan button (ticked rescan failed and existing plugins). I have also checked plugin manager.
Audio VST3 plugins are fine. Worked in previous update. Does anybody have this?

I had this on a previous update

The update defaulted my PLUGIN BROWSER to the category "Cakewalk plugins". Try checking this and choose a different category then hopefully all of your plugins will show

jmcecil
rolling releases = endless minor niggles.  You will never upgrade.
 
Old way = major niggles stay for years.

That is so true, and I realise that. It's just that I am a big user of the PRV and I'd rather that calm down first. If there were other fixes and enhancements in this release I would install right now.

Like I said... No rush

Cheers

andy

My VST 3 scanning issue is fixed and was perhaps caused by unnecessary extra file paths for scanning added upon upgrade. I have deleted all unnecessary VST file paths from registry and hope it not happens again. If not I will post next month.

synkrotron

jmcecil
rolling releases = endless minor niggles.  You will never upgrade.
 
Old way = major niggles stay for years.

That is so true, and I realise that. It's just that I am a big user of the PRV and I'd rather that calm down first. If there were other fixes and enhancements in this release I would install right now.

I recommend installing the update...any "minor niggles" are IMHO teeny compared to the benefits the new PRV brings. You can always roll back if you want. 
 
Whenever there's an update, there are typically three main issues:
 

• Some kind of minor bug that early access and the beta didn't catch
• People noticing things they hadn't noticed before that don't relate to the update
• Something gets changed (e.g., a preference) that needs to be restored

 
The first one is the only one that may require a rollback, but even then, there has been only one update (I think it was November) where the update seemed sketchy enough that I waited for the next one. Every other time I just went and updated, and have never had to rollback. In my experience, the benefits of updates outweigh any drawbacks; the only time I get "snagged" was when the Read Cache preference was changed to off (don't know for sure it was the update, though) and I started getting dropouts on playback. I checked it and all was well again.