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  

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?

@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.

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.

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?

Some applications are discussed on p. 10 through 12 of the ezine.

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?

Hi joden,
For me there are two real uses, one is purely workflow, the other is mostly workflow but a bit more practical.
 
For the first, I really like to use my busses for broad instrument groups and FX sends...things like "Vox", or "Drum kit", or "Acoustic Guitars". Under the current workflow if I have multi-mic'd instruments that becomes tough because in order to have (i.e.) my top- and bottom-mic'd snare drum on a single fader I have to send it to a bus. This update will allow me to send both mics to a single "snare" track which can then go to my "Drum Kit" bus. This is purely a workflow thing, it has no practical purpose beyond me preferring to have a single snare (or kick or whatever) track feeding a drum bus instead of having two snare tracks feeding a snare bus which is then feeding a drum bus.
 
The second purpose is slightly more practical, but still workflow related - with track to track routing I can bounce busses in a different way. If I'm using a CPU intensive or latency inducing reverb, I can now put it on an aux track and bounce it in place, as opposed to bouncing with a bus source and ending up with the reverb output on a new track. This is certainly workflow related as well, but it means that I can have my reverb stay in the same place in the project after bouncing (assuming it was on an aux track) instead of having it be on a new track.
 
Ideally I'd like to see ALL busses converted to new Aux tracks and then just have flexibility on which mixer section they live in, and I'm hopeful that's the future direction here. That way things stay exactly the same for folks that like the current model, but also allow different mixer section setups for folks who want a different setup.
 
Dean

scook

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?

Some applications are discussed on p. 10 through 12 of the ezine.

Yeah I read them but to me, they still did not illuminate it much 

bvideo
Can an aux track be a VocalSync guide track?
Does RFX work on an aux track?

Yes and yes. An Aux Track is just an audio track with a Patch Point input. Of course, it's not the track itself that's a guide track or becomes an RFX region, but the audio within the track.

Can we get a demo project with this update? Thanks... For dummies like me..

Anderton

bvideo
Can an aux track be a VocalSync guide track?
Does RFX work on an aux track?

Yes and yes. An Aux Track is just an audio track with a Patch Point input. Of course, it's not the track itself that's a guide track or becomes an RFX region, but the audio within the track.

Based on your answer in the other thread, it sounds like the audio has to be populated (bounced) into the aux track, not just echoed through it for these purposes. So no such thing as "virtual" audio...

Apparently yes. That's one of the examples described in the e-zine thingy.

maximumpower

Anderton

joden
Yeah I read them but to me, they still did not illuminate it much 

Maybe I should create some Track Templates for the November update that take advantage of the new features.

Y E S ! ! !
 
I mean, yes please. :-)

I offered some for the October release, but never heard back from Cakewalk. I'll try again.

Is Jamaica Plan update available now??  I'm not seeing it in my CCC yet