I'm already working with Ripple Editing all the time and it saves me so much time.
For example a digitazed tape with 3 hours is for 2 hours empty. I only need to cut at the end of the recorded hour and the hole with the 2 empty hours is also deleted. The next tape recording does not follow after a hole of 2 hours, because the hole is deletet. The next tape recording comes directly behind it.
But I notice that there must be the possibility to quickly turn it on and off. With the absolutely necessary of a feedback if the function is on or off. Because I constantly have to turn it off and on at work.
The shortcut for on and off is fine - but the feedback if "on or off" is missing.

THambrecht
The shortcut for on and off is fine - but the feedback if "on or off" is missing.

+1

I'm really interested in the upcoming pen support and it has the potential to change the way I work. 
 
What hardware will I need?
 
Currently I have a desktop PC with two Dell monitors that are not touch enabled. However I do have an iPad Pro and today at work a colleague discussed duet which allows an iPad to be used as a second monitor for a PC. If I got a pen would this work with Sonar?

I also noticed that this early release update has totally fixed another very annoying problem I was having. I am not sure this was intended, but I am very happy about it.
 
The problem: When chopping up real recorded audio drum tracks for quantizing, selecting all the clips, then pressing "Q" for quantize, SONAR would lose the selection and only quantize one or two "columns." I would have to close SONAR down completely, start up again, then I would get one chance to get it to work correctly.
 
Now: It works as expected every time. This is a huge relief! Also it seems more responsive and snappier. This update is a very huge one and is making a massive difference for me. Thank you Cakewalk!

tonydude
I'm really interested in the upcoming pen support and it has the potential to change the way I work. 
 
What hardware will I need?

http://forum.cakewalk.com/FindPost/3610878
 

I've really enjoyed reading this thread...it's interesting to see what is coming in the May release and I'll be very excited when I get it.
 
Maybe an idea to consider moving back to using names for the updates.
 
Today it is June and I'm looking forward to the May update... Perhaps using numbers raises expectations and you possibly don't need the pressure...
 
Keep up the good work
 
 
Marko

The problem is not the name but the timing of the release. It may be clearer if the releases were timed for the beginning of the month instead of the end. This way any updates for the release would also occur in the same month.

scook
It may be clearer if the releases were timed for the beginning of the month instead of the end.

I'm not sure I see a difference.
 
Also, I think Cakewalk deliberately called the releases this year by number, i.e. "2017.05" instead of "May 2017". It's the fifth release in 2017. The fact it arrives in June (theoretically) just means this one took a bit longer to bake. I'm fine with that...