Although I know that he knows, I would like to remind to Noel that we all expect to appear in the control bar something, a button or a flash or anything else, that alerts that Ripple Edit is still active.

+1

And autocrossfade.

In my opinion, It's like leaving the lights on in your car. you turned them on, so why don't you turn them off when your done driving ?
BUT... I do understand not everybody works like me or I don't work like everyone else so I can indeed respect your opinions. I just think there's more important things we could use as far as development hours are concerned.

i know i've had to hit "undo" after mangling my project because i forgot Ripple Edit was still on.  but man, isn't Ripple Edit awesome, compared to the old days?

wetdentist
... but man, isn't Ripple Edit awesome, compared to the old days?

You got that right!

Ripple edit one feature of Platinum (and now CbB) I think of when people (sometimes with pride, apparently) say they are still on X3 or less.  But boy do we need that on screen indicator.  I'm hoping they are looking at adding it for the November (or December) update.

Adding and programming a button to show enabled/disabled in C++ wouldn't require hours. It would need no other functionality than to toggle when ripple edit is toggled. Status lights are a common engineering practice, especially when time passes between uses or different people use the same system (in this case a project). Car lights are not the best analogy, since they are visual indicators already, and that is really the point of the OP. I am confused how this is any different than interleave, input echo, or armed status, and those are by track.

chuckebaby
In my opinion, It's like leaving the lights on in your car. you turned them on, so why don't you turn them off when your done driving ?

Indeed, there is not a single new automobile that one can purchase that will not give the driver an audible alert it the headlights have not been switched off if they attempt to exit the cockpit without doing so.
 
I can tell you that given the choice between flying in a jetliner designed so that the pilot had to remember which position they left the buttons in vs. one with indicator lights on the buttons, I will choose not to ride in the one where they devoted more engineering resources to the "more important" matters. :-)
 
Seriously, from a systems analysis viewpoint, I look at the likelihood of the user being distracted by intermediate tasks (such as mixing, editing, driving, unloading groceries, answering txt messages, whatever) and the consequences of the control being left in the wrong position (car battery being drained, hundreds of editing decisions being lost).
 
It seems like something with dire consequences if forgotten. There can be so many distractions in my studio, a project with 20 or more tracks, each track with multiple takes, effects, automation. It's just one less thing to have to worry about or keep track of. One can just glance up at the control bar to check if it's on or off, like Snap.
 
And while I really do hate to armchair program, my guess is that making some pixels change color depending on the state of a function somewhere in the program is not very expensive in terms of development resources.

I think it's like putting your car in reverse. After you've finished going backwards, you automatically put the car back into first gear, or drive if you're in an automatic. You don't need an audible reminder that you've been in reverse, you just remember that you've been going backwards, 'cause it's such an awesome feature that your car can actually now go backwards, after only having forward gears for so long.

Euthymia
Indeed, there is not a single new automobile that one can purchase that will not give the driver an audible alert it the headlights have not been switched off if they attempt to exit the cockpit without doing so.
 

 
Good point.
 

Euthymia
I can tell you that given the choice between flying in a jetliner designed so that the pilot had to remember which position they left the buttons in vs. one with indicator lights on the buttons, I will choose not to ride in the one where they devoted more engineering resources to the "more important" matters. :-)
 

 
Were not talking safety matters here...though we are splitting hairs, partially my fault.
I would rather have pitch control any day than a blinker for ripple edit.
 
Trust me I feel for you guys, I was the one who came up with the idea about putting the indicator light in the control bar (in its own module).
I just happen to believe those others DAWs out there are coming up with cutting edge technology and here we are looking for a way to invent a light ?
I can see it your way, too bad you cant see it mine