chuckebaby
Im not sure every one is going to happy about ripple editing as some think.
I know I have my own concerns. im used to working in a certain way, for example cut. paste, copy, exc.
The thought of learning a new implementation is not so appealing to me which is why is was hoping for a fix of delete hole vs ripple editing which to be perfectly honest, im not sure what it will bring.
 
Hence the reason I have never complained about "delete hole", I just split and move data as needed.
Its not a life ending feature (not having delete hole).

I was probably wrong to make any predictions, but I do hope that others find inspiration with ripple editing.
 
It does all depends on what you do, but "delete hole vs. ripple editing" is not really a 'thing'.  When I started with CWPA.4 you were forced to cut, move & paste out the yazoo considering you only had 32 megabytes of RAM. Essentially "delete hole" is just a welcome shortcut as you pretty much said.
 
I checked out (then bought) Reaper because of a freebie that was recommended in the software forum here.  I'd seen the Reaper ripple editing video before in this forum, but I was unaware of how (and how much) I'd actually use it.  Even if I still was in a band and just did straight live recording in Sonar I'd still use it. 
 
 

declan

chuckebaby
Im not sure every one is going to happy about ripple editing as some think.
I know I have my own concerns. im used to working in a certain way, for example cut. paste, copy, exc.
The thought of learning a new implementation is not so appealing to me which is why is was hoping for a fix of delete hole vs ripple editing which to be perfectly honest, im not sure what it will bring.
 
Hence the reason I have never complained about "delete hole", I just split and move data as needed.
Its not a life ending feature (not having delete hole).

I was probably wrong to make any predictions, but I do hope that others find inspiration with ripple editing.
 
It does all depends on what you do, but "delete hole vs. ripple editing" is not really a 'thing'.  When I started with CWPA.4 you were forced to cut, move & paste out the yazoo considering you only had 32 megabytes of RAM. Essentially "delete hole" is just a welcome shortcut as you pretty much said.
 
I checked out (then bought) Reaper because of a freebie that was recommended in the software forum here.  I'd seen the Reaper ripple editing video before in this forum, but I was unaware of how (and how much) I'd actually use it.  Even if I still was in a band and just did straight live recording in Sonar I'd still use it. 
 
 

oh man I hope it didn't seem like I was responding to you personally.
If it did, my apology's. I was referring to a lot of people out there who are waiting on ripple editing.
Myself, I should probably be more open minded and give it a fair share. I tend to jump the gun quite a bit

Anderton
 
@Hermu - Cakewalk does not ignore user bug reports; looking over the list of bug fixes in the eZine provides ample evidence, especially if you follow the forums and keep track of the issues people have reported. However, it is accurate to say Cakewalk either does not, or cannot, act on all user bug reports.

My observation is that the Bug Reports are the first ones addressed. With that said, it seems very obscure bugs one wouldn't even think of or come across daily are fixed, while other problems addressed in the forum (outside the Bug Report Tool) may go ignored, even if they can easily be replicated. The problem I see is that, there's no acknowledgement that the bug is being truly tracked or reviewed. That's frustrating because, users don't have any indication they're being helpful. More, there's issues reported years ago that have still gone untouched and forgotten, even if still replicate-able.

As users, it's hard to say how Cake sets their priority list. Recent threads indicate that the forums are only a small piece of the puzzle. It's obvious that bug reports are another piece and the issues that get discussed here can sometimes lead to quick fixes. But I don't think bug reports are a primary driver.
 
During the last NAMM, Craig Anderton reported that Noel was showing off Sonar using Bluetooth midi input. I'd never seen that as a feature request, but sure enough, it's a new feature in the most recent Sonar release.
 
My observation is that feedback from the early release is the most potent input users have. The majority of issues reported get sorted out quickly. It's a form of real-time bug reporting that seems to work for Cake and the user base.

Just two short remarks:
1. Bugs with workarounds obiviously have a very low priority. For "Delete hole", all you have to do is to fill the hole with clips, then it works as it should.
2. No matter how ripple editing will work, I'm pretty sure that "Delete hole" will nonetheless be a valuable alternative - once it is fixed and can be used without a workaround. Selecting a range and then calling "Delete hole" will be faster than ripple editing in some cases. So, I hope it will be fixed and not just replaced by ripple editing.

ralf
Just two short remarks:
1. Bugs with workarounds obiviously have a very low priority. For "Delete hole", all you have to do is to fill the hole with clips, then it works as it should.
2. No matter how ripple editing will work, I'm pretty sure that "Delete hole" will nonetheless be a valuable alternative - once it is fixed and can be used without a workaround. Selecting a range and then calling "Delete hole" will be faster than ripple editing in some cases. So, I hope it will be fixed and not just replaced by ripple editing.

I'm anxious to see how well the Ripple editing works. I noticed CW removed the Upcoming features from the Sonar page. Not sure what happened, there.