Craig, please keep explaining things at a very basic level.  On things that I know about I just keep reading as I sometimes I don't know as much as I think I know.  On the other things this dummy needs all the help that I can get.

Thanx and keep up the outstanding work.

Anderton

FCCfirstclass
Craig, also my thanks for http://blog.cakewalk.com/five-reasons-why-patch-points-rock/ being posted.

Glad you enjoy them...of course, as soon as that was posted, I found another application that I wish had been included... 

Don't be shy! Do it.

Not sure why but since this update - having thumbnails enabled when a video is imported seems to make my projects laggy as hell.
 
Mouse pointer sticks when changing zoom amounts - playback takes forever to kick in and stuff like that.
(Shows as non responding in task manager during the lockups - but always comes good after 5-10 sec) 
 
Disabling the video thumbnails fixes the issues right away. Has never been a problem before.
 
Compy is:
Win10 (64bit) - i7 2600K - 2 x GT560 (SLI) - 4 TB of hdd - Saffire Pro 56 - Sonar Platinum + various other irrelevant stuff.
 
Any ideas ???

Razorwit
First thing to keep in mind: This is only a workflow/organization enhancement. I can't think of anything that we can do now that we couldn't before by using a combination of buses and sends. 

Its more than just workflow/organization however. In addition there are quite a few things you could not do earlier with just tracks and buses.
 
1. Record the output of buses or tracks in realtime. This opens up all kinds of dynamic possibilities since you can manipulate faders or parameters while you are recording.
2. You couldn't mix the output of multiple tracks into a new track (which has its own clip data). At least not without a real patch cable.
3. Record as audio the output of external inserts. Only way earlier was using real time bounce but you cant manipulate faders.
4. Record the output of the Matrix track.
5. Record the output of realtime generative VST plugins such as audreio which stream audio from an external network source into SONAR.

Noel Borthwick [Cakewalk]

Razorwit
First thing to keep in mind: This is only a workflow/organization enhancement. I can't think of anything that we can do now that we couldn't before by using a combination of buses and sends. 

Its more than just workflow/organization however. In addition there are quite a few things you could not do earlier with just tracks and buses.
 
1. Record the output of buses or tracks in realtime. This opens up all kinds of dynamic possibilities since you can manipulate faders or parameters while you are recording.
2. You couldn't mix the output of multiple tracks into a new track (which has its own clip data). At least not without a real patch cable.
3. Record as audio the output of external inserts. Only way earlier was using real time bounce but you cant manipulate faders.
4. Record the output of the Matrix track.
5. Record the output of realtime generative VST plugins such as audreio which stream audio from an external network source into SONAR.

 
Hi Noel,
Thanks for chiming in, and I think that's all correct. To be fair though, aside from the realtime stuff, you could do all those things with buses, sends and bouncing. Multiple tracks to a single track - use sends on the tracks you want to sum to get them to a bus and bounce to a track. Audio out of external inputs - bounce again. Record output of Matrix - bounce (I think...could be wrong...I don't use Matrix much).
 
Now, don't get me wrong, I'm a GIANT fan of this update (a thousand thanks again), and the realtime stuff is important, but lots of folks out there are saying things like "remind me what this allows us to do that we couldn't do before with buses and bouncing", and I think the answer is "other than realtime recording of stuff, these results were mostly available before, they're just organized into a better, more flexible workflow now".
 
Again, not really a disagreement, just trying to find a good way to explain it. And, FWIW, I genuinely appreciate your input around these parts.
 
Dean

Razorwit
First thing to keep in mind: This is only a workflow/organization enhancement. I can't think of anything that we can do now that we couldn't before by using a combination of buses and sends. 

Despite recognizing that others want the real-time options, I felt that I didn't really need this enhancement. I stand corrected . Now that I've actually been able to work with it, I've found the workflow enhancements are considerable. I used to drag out multiband processing only on "special occasions" because it really cluttered things up to have all those buses that needed to be part of a track situation in a different part of the console or track view. Bouncing it was also a hassle.
 
Now, I have a template that even though it doesn't store patch points (yet), I'm good to go in seconds, and it folds up neatly into a track folder. That's not the only example; parallel processing is super-simple as well. I've also saved time by doing real-time bounces with track-to-track bouncing of entire mixes because I can tweak while listening as mentioned above, unlike a real-time bounce. I did have a "do we really need this?" prior attitude. Frankly,  I still don't think I absolutely need it...but after working with it for a while, it's turned out to be something I wanted...I just didn't know it.

Anderton

Razorwit
First thing to keep in mind: This is only a workflow/organization enhancement. I can't think of anything that we can do now that we couldn't before by using a combination of buses and sends. 

Despite recognizing that others want the real-time options, I felt that I didn't really need this enhancement. I stand corrected . Now that I've actually been able to work with it, I've found the workflow enhancements are considerable. I used to drag out multiband processing only on "special occasions" because it really cluttered things up to have all those buses that needed to be part of a track situation in a different part of the console or track view. Bouncing it was also a hassle.
 
Now, I have a template that even though it doesn't store patch points (yet), I'm good to go in seconds, and it folds up neatly into a track folder. That's not the only example; parallel processing is super-simple as well. I've also saved time by doing real-time bounces with track-to-track bouncing of entire mixes because I can tweak while listening as mentioned above, unlike a real-time bounce. I did have a "do we really need this?" prior attitude. Frankly,  I still don't think I absolutely need it...but after working with it for a while, it's turned out to be something I wanted...I just didn't know it.

Totally agree. I thought the same too. Now after seeing a use I really like it. I guess one has to see it working to appreciate it. I'm glad those that were so vocal about this did get it. We all benefit.  

LOL. This place gets more like Prime Ministers Questions in the House of Commons (UK) every single day.

Craig, John, every idea needs opponents, to discard it, or to make it stronger.

Adq
Craig, John, every idea needs opponents, to discard it, or to make it stronger.

I like that point of view. I'm going to steal it from you. LOL