• SONAR
  • Major "Jamaica Plain" SONAR Update Now in the Cakewalk Command Center! (p.6)
2015/10/18 03:33:15
beltrom
bvideo
msorrels
Will patch points work with MIDI tracks?  Doesn't look like it, but I really would love to be able to send one MIDI track to multiple soft synths.  And combine MIDI tracks without having to use a MIDI loopback device.  If not now, perhaps in the future?
 
...


Yes, this ^ will be very nice!




+1
2015/10/18 07:30:52
Boydie
Did anyone else go through the process of "oh no, I am going to have to update my templates and change my workflow with aux tracks etc." and then get really excited about having to update all of their templates with aux tracks and routing!!!!

This is an awesome release and I can't wait for the 1 year review of the subscription model to add up all of the added features, bug fixes, workflow enhancements etc. and compare it with a point release - I think we are already way beyond previous comparisons

Do you think we have already progresses 2 or 3 versions?
2015/10/18 07:37:55
gswitz
I'm really excited about this. It makes me wonder if I will still want the Bus pane, but I think I'll probably leave the master there.
 
Aim assist will cross into the bus pane?
 
On page 6 of this
http://static.cakewalk.com.s3.amazonaws.com/cakewalk/news-archive/Welcome-to-the-October-2015-SONAR-update.pdf
It looks like Aux 1 routes into a patch-point then back to aux 1. When I look closer, it looks like Aux 1 Send is routing back to Aux 1. Wow, that's interesting. Isn't this in danger of being a feedback loop?
2015/10/18 08:04:21
BobF
gswitz
On page 6 of this
http://static.cakewalk.com.s3.amazonaws.com/cakewalk/news-archive/Welcome-to-the-October-2015-SONAR-update.pdf
It looks like Aux 1 routes into a patch-point then back to aux 1. When I look closer, it looks like Aux 1 Send is routing back to Aux 1. Wow, that's interesting. Isn't this in danger of being a feedback loop?




On the left, bottom box, Aux 1 is the selected destination shown in a Send ...
 
I did a double-take on that the first time I looked at it too
2015/10/18 08:37:12
Noel Borthwick [Cakewalk]
That is a bus sending to an aux track.
Any destination that could cause feedback is automatically excluded in the UI.
2015/10/18 08:42:11
BobF
Noel Borthwick [Cakewalk]
That is a bus sending to an aux track.
Any destination that could cause feedback is automatically excluded in the UI.



How long do you plan to tease us with pics before we get to kick the tires and drive it around the block?
2015/10/18 09:41:18
MarioD
beltrom
bvideo
msorrels
Will patch points work with MIDI tracks?  Doesn't look like it, but I really would love to be able to send one MIDI track to multiple soft synths.  And combine MIDI tracks without having to use a MIDI loopback device.  If not now, perhaps in the future?
 
...


Yes, this ^ will be very nice!




+1




A BIG +1
2015/10/18 10:22:03
Doktor Avalanche
Doktor Avalanche
From ezine:
 
Deleting a track will not remove associated Patch Points, so that undo and redo can
work. However, loading a project removes any unused patch points.
 
So will from Sonar menu - Edit -> History-> Clear (Undo history) remove unused patch points?



Still have that question.
 
The other thing I was thinking about, surely the best way around that is just to mark for deletion here, then undo/redo should work (Sonar would simply unmark or mark for deletion when doing undo/redo). There could be an option in preferences to change behaviours (i.e. delete immediately or until project starts, or don't delete at all for some reason).
2015/10/18 11:00:24
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. 
2015/10/18 11:20:36
Anderton
Doktor Avalanche
From ezine:
 
Deleting a track will not remove associated Patch Points, so that undo and redo can
work. However, loading a project removes any unused patch points.
 
So will from Sonar menu - Edit -> History-> Clear (Undo history) remove unused patch points?



They're actually two separate things; the eZine statement relates to what happens to patch points when you delete tracks. Patch points by themselves are basically input and output assignments, which traditionally have not been included as events in the undo history. So like other input/output assignments, almost all patch point management is done manually. The "what happens if you delete a track with patch points" is more like a special case that's accommodated. 
 
For example, suppose you add a patch point input to a track (we'll call it Track X). You assign several outputs to it. Then you de-assign those outputs and save the project. You might think that because nothing is assigned to Track X's patch point, the patch point will be deleted but that's not the case. If you re-open the project, that patch point will remain because you might want to assign something to it.
 
Now suppose you retain an output assigned to Track X, but de-assign Track X's patch point input. Track X now becomes an audio track because it no longer has a patch point input. If you save the project and re-open it, because the patch point still exists as an output (even though it's not assigned to anything), it will still exist and if you want, you can re-assign the Track X input to it.
 
However, if you de-assign the patch point input to Track X, and de-assign the output going to it, then save the project, when you re-open the project the patch point will no longer be available because nothing refers to it. If you want to re-patch the output to Track X, you would need to create a new patch point. So with a few exceptions, you can basically think of patch points as being very similar to input and output assignments.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account