irvin
At this pace, Sonar is great value - hell, if this continues I will not hesitate to renew my yearly subscription when the time comes. In all honesty (and I'm not a fanboy), it feels like we're getting major upgrades every month. 

Agreed. However to me, what's equally important are the fundamental optimizations and fixes to long-standing problems like the VX-64 and Channel Tools popping issue. Although the only "third party" update has been to Strum, that's okay with me...it's finally given me time to pay more attention to the Blue Tubes plug-ins to find out what they can do  

This update looks amazing!
 
Thank you Bakers. Truly appreciate all your hard work and dedication to our beloved Sonar.

I've been holding off installing/registering my recent upgrade to Platinum until the October update comes out...Should I assume it will be within the next couple days since they released the notes on it?

Assume nothing. I'm surprised they leaked the newsletter, though, but I'll be pleasantly surprised if it shows up before Oct 31.

@Craig I understood that,did read the ezine but with respect both the questions still stand. I'm looking at this more programmatically, and particularly to undo.

Doktor Avalanche
@Craig I understood that,did read the ezine but with respect both the questions still stand. I'm looking at this more programmatically, and particularly to undo.

What I meant by "Patch points by themselves are basically input and output assignments, which traditionally have not been included as events in the undo history" I mean they react the same way. So if you make a whole bunch of patch point assignments and clear history, I'm quite sure they'll still be there.
 
I don't understand the second question about marking for deletion. Remember that the same basic rules apply to patch points as other I/O assignments, so I guess we'll need to wait for the official update to discover particular points of differentiation.

That's a fair point, if input and output is not part of undo events across the board then that is a feature request. Same with sends I believe.

All looks good, but a question - I get the how a patch point works, but why would they be necessary? Can anyone give me a real world example of why such a thing would be useful? This is not to criticise the concept, I woudl just like to understand mroe about why it would be a useful thing?

At its simplest it means you can pretty much feed anything anywhere - so you could have your tracks going to an AUX track (ie BUS) pane
 
It also looks like you can have multiple "patch points" on the same track (rather than just the one "output")

joden
All looks good, but a question - I get the how a patch point works, but why would they be necessary? Can anyone give me a real world example of why such a thing would be useful? This is not to criticise the concept, I woudl just like to understand mroe about why it would be a useful thing?

It won't affect me too much as I use sends and busses in the traditional way but for example you could use a bus to trigger a side chain or parallel process one element of your drum sound using an aux track without having to create two buses