MOTUnation.com

BKK-OZ wrote:I agree about the lack of mixer window undo being a pain. Yes, you can lock a mix, yes you can use automation, but why the hell can't you just simply undo?

You can set DP to make back ups every minute if this is that big a problem

toodamnhip wrote:

BKK-OZ wrote:I agree about the lack of mixer window undo being a pain. Yes, you can lock a mix, yes you can use automation, but why the hell can't you just simply undo?

You can set DP to make back ups every minute if this is that big a problem

Or MOTU could facilitate mixer undos.

BTW, I do that (backups). But why should I have to reload a saved version, just to undo some tweaks?
It is just nonsense to me that mixer adjustments can't be rolled back.
Yes, I know the work arounds, but why do we have to,work around such a quirk?

BKK-OZ wrote:

toodamnhip wrote:

BKK-OZ wrote:I agree about the lack of mixer window undo being a pain. Yes, you can lock a mix, yes you can use automation, but why the hell can't you just simply undo?

You can set DP to make back ups every minute if this is that big a problem

Or MOTU could facilitate mixer undos.

BTW, I do that (backups). But why should I have to reload a saved version, just to undo some tweaks?
It is just nonsense to me that mixer adjustments can't be rolled back.
Yes, I know the work arounds, but why do we have to,work around such a quirk?

While undo in the mixer would be a good thing another way to help in this scenario is if DP had mixer snapshots. You like a mixer setup and take a snapshot. Also give the user the option of having DP do automatic snapshots on a user set interval like autosave does. That way you don't have to reload a whole session but just go back and reload a specific snapshot.

[/quote] Or MOTU could facilitate mixer undos.

BTW, I do that (backups). But why should I have to reload a saved version, just to undo some tweaks?
It is just nonsense to me that mixer adjustments can't be rolled back.
Yes, I know the work arounds, but why do we have to,work around such a quirk?[/quote]
While undo in the mixer would be a good thing another way to help in this scenario is if DP had mixer snapshots. You like a mixer setup and take a snapshot. Also give the user the option of having DP do automatic snapshots on a user set interval like autosave does. That way you don't have to reload a whole session but just go back and reload a specific snapshot.
[/quote]




This isn’t going to happen until the day DP gets it’s snap shot automation bugs fixed with waves and other companies. I have been a staunch advocate of such for yrs..There’s some progress, then an update breaks snap shot..over and over..big problem. "Auto snap shot" or "auto mix save” ANYTHING...would be a disaster.

musicman691 wrote: While undo in the mixer would be a good thing another way to help in this scenario is if DP had mixer snapshots. You like a mixer setup and take a snapshot. Also give the user the option of having DP do automatic snapshots on a user set interval like autosave does. That way you don't have to reload a whole session but just go back and reload a specific snapshot.

You can do this in a way. The manual describes how to copy a snapshot from one place in the timeline to another. You can use the same process to copy settings from anywhere to anywhere. In effect your entire project serves as a store of snapshots, almost infinite in number.

This is the second little bug I have found while using comping mode. It could be that comping mode has a few problems, or, it could be general DP 9 early bugs and since I am comping as my 1st major task, these bugs a re showing in comping...lol..
Either way....

When I create an new editing point split in a sub comp track using option click, and then hit UN Do, often,...... DP does NOT un do the edit point I just created.

It just stays there. Sometimes hitting un do again does the trick, sometimes not. Something isn’t right.

The most important reason why UNDO is indispensable regardless of other techniques for avoiding data loss, is that it lets you see what you've done, whether intentional or a slip of the mouse (or not noticing you had focus somewhere when you thought you were working in an entirely different app or window).

I often use the UNDO feature as a sanity check to see what operations I've done -- especially if I'm quickly trying out things and backing them out (I can get lost after a lot of back-and-firths).

Saying there are other ways to avoid data loss is basically saying one shoe fits all. We all have different types of projects and different work styles, Redundancy is what I love about DP, and is the first app where I saw that implemented on a grand scale. It went on to inform my own GUI design principles where I work, and I constantly show DP to co-workers as inspiration.

I can only guess that UNDO for the Mixer window would be EXTREMELY difficult to implement. Possibly precisely because of how it would have to interact with automation features.

mhschmieder wrote: I can only guess that UNDO for the Mixer window would be EXTREMELY difficult to implement. Possibly precisely because of how it would have to interact with automation features.

I will add this in support of your hypothesis that undo in the mixer would be a pain or at least cumbersome. I have noticed a very strange thing about UNDO when it comes to Muted MIDI notes. 1) I highlighted 2 bars of MIDI notes in one track, in the TO window. All the MIDI notes muted.
2) I hit UNDO and it did;t undo the whole muting, it un-did one note at a time. In other words, if there were 25 MIDI notes in the section that I muted with one click over an area of the Tom it took TWENTY FIVE undo’s to uno that ONE maneuver.

I am wondering why it is designed that way by the way? I guess DP cannot differentiate between HOW those 25 notes were muted. It just “remembers” 25 notes being muted and needs 25 undos...seems very strange and even may be something MOTU should re-program if you ask me. But as this related to the mixer window, wow, I could see incremental mixer change undo’s being seriously cumbersome.
By the way, can anyone else verify what I wrote? Mute a section of MIDI in the TO and hit undo and see if the whole section comes back or just one MIDI note at a time.

toodamnhip wrote:if there were 25 MIDI notes in the section that I muted with one click over an area of the Tom it took TWENTY FIVE undo’s to uno that ONE maneuver.

Hmmm... I just went to my "test" project, and MIDI Note mute worked fine, and Undo undid multiple notes. If you drag the mute tool over several notes at once, or select multiple notes and then apply mute, undo reverses the entire operation. If you mute a set of notes one at a time, then you have to undo them one at a time. That is exactly what it should do. I noticed though that dragging over notes with the Mute tool is somewhat hit and miss -- it often misses some of the notes in the area addressed.

Incidentally, checking Logic's MIDI Mute tool to compare, it doesn't Undo at all. You drag it over one or more note or click on them on at a time to mute them. To unmute you repeat the same operation. The Undo history does not show the Mute operation and Undo does not affect the mute state of the notes at all.

toodamnhip wrote:

mhschmieder wrote: I can only guess that UNDO for the Mixer window would be EXTREMELY difficult to implement. Possibly precisely because of how it would have to interact with automation features.

I will add this in support of your hypothesis that undo in the mixer would be a pain or at least cumbersome. I have noticed a very strange thing about UNDO when it comes to Muted MIDI notes. 1) I highlighted 2 bars of MIDI notes in one track, in the TO window. All the MIDI notes muted.
2) I hit UNDO and it did;t undo the whole muting, it un-did one note at a time. In other words, if there were 25 MIDI notes in the section that I muted with one click over an area of the Tom it took TWENTY FIVE undo’s to uno that ONE maneuver.

I am wondering why it is designed that way by the way? I guess DP cannot differentiate between HOW those 25 notes were muted. It just “remembers” 25 notes being muted and needs 25 undos...seems very strange and even may be something MOTU should re-program if you ask me. But as this related to the mixer window, wow, I could see incremental mixer change undo’s being seriously cumbersome.
By the way, can anyone else verify what I wrote? Mute a section of MIDI in the TO and hit undo and see if the whole section comes back or just one MIDI note at a time.

Just so you know for other times, there is an Undo window in DP. It allows you to manage branched undos, and do things such as undo 25 events with a single click.

I always have the undo window open. It's a huge timesaver. I usually know exactly where I want to undo back to, and rather than hitting cmd-z a bunch of times until I'm there, I simply click 1 line and get back to working. If for some reason I want to go back after a bunch of work, then forward along that previous undo path, I can! It's awesome.

I tend to use the new window space for track selector but yes, it is an I tend to use the new window space for track selector but yes, it is A handy when do you have open

Robert Randolph wrote:I always have the undo window open. It's a huge timesaver. I usually know exactly where I want to undo back to, and rather than hitting cmd-z a bunch of times until I'm there, I simply click 1 line and get back to working. If for some reason I want to go back after a bunch of work, then forward along that previous undo path, I can! It's awesome.

I'm so jealous. For some odd reason that nobody's been able to figure out yet, branched UNDO has never worked on my system. No branches appear, no matter what I do. (and yes, I know how to set it) This is an ongoing problem of a decade or so. I know it's weird, and maybe a clean install of the whole OS would fix everything, but I'm not going to do that, so I'll live with it until I find a way.

But I REALLY want branched UNDO to work.

Shoosh

Shooshie wrote:

Robert Randolph wrote:I always have the undo window open. It's a huge timesaver. I usually know exactly where I want to undo back to, and rather than hitting cmd-z a bunch of times until I'm there, I simply click 1 line and get back to working. If for some reason I want to go back after a bunch of work, then forward along that previous undo path, I can! It's awesome.

I'm so jealous. For some odd reason that nobody's been able to figure out yet, branched UNDO has never worked on my system. No branches appear, no matter what I do. (and yes, I know how to set it) This is an ongoing problem of a decade or so. I know it's weird, and maybe a clean install of the whole OS would fix everything, but I'm not going to do that, so I'll live with it until I find a way.

But I REALLY want branched UNDO to work.

Shoosh

I you use "branched undo" a lot, like 10, 000 times, it provides a nice shade for your studio clients. And occasionally, you might find a peach growing on one of the branches...but that’s very rare