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.

As I said previously, "Bear in mind anything you can do with Patch Points and Aux Tracks is already doable without them. What they offer is a variety of alternative workflows." Here's one example. I do a lot of multiband processing, which requires creating sends from one track to feed four buses if I'm splitting the signal into four bands. If I do multiband processing on several tracks, this adds a lot of "bus clutter" to the bus pane for what are essentially track-oriented functionality.
 
With patch points, it's much simpler. The track output would go to a patch point. The inputs for the four audio tracks with the necessary processors would be fed by the same patch point - no send required to distribute the track output to four other tracks. Because the original track doesn't feed the master, it won't be heard and there are no rpre/post setting considerations.
 
Two other advantages are that the four tracks with the processors can go into record mode to end up with four distinct audio tracks, and the whole thing can be put in a Track Folder so the collection of tracks can be minimized when not needed.

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

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

What you can do for now is ignore the bus pane completely if you want because you can work entirely in Track View.
 
I expect that what I'll end up doing is using the conventional buses for conventional busing applications (e.g., adding reverb to a bunch of different tracks, with different input levels and panning) and Aux Tracks for track-oriented functionality that would be enhanced by busing.

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 

+1 Yaay!  I can go make music again!!! 
Thank you Bakers!
So when is this going to drop?

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.

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

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.

arlen2133
So when is this going to drop?

Before the end of the month.