... as Marsha Brady once said, "Something suddenly came up."

Moderator: James Steele
wished that was the case timeline...Timeline wrote:Most of the blips created during a fader ride is caused by the CPU being over taxed while updating.
Yes we could use an averaging feature that lets you smooth fader update continuos data in a way that works instead of guessing.
Sounds like this:bOing wrote:Not sure if it was mentioned but as a quick doubling option I sometimes "duplicate" a track - killing the audio but keeping the setup.
I couldn't get command-shift-D to work.
(is that right, I'm not near my sweetie right now.)
That's the frustrating thing, so many little time savers have been introduced in the competition, and not in DP. Most of the things that bug me seem like they would be so simple to fix. It really seems like no one is looking at workflow and ergonomics, just "features".wurliuchi wrote:I hope someday MOTU will take care of most of these nagging, little issues that slow things down or just get in the way or feel and look unprofessional. There's getting to be a pretty long list of them, and each new version adds more it seems. I should write them down when I come across them, but I never do. I just think, "Oh, yeah, that stupid thing" and move on
Quite frankly, a lot of them should have been taken care of long ago. They don't seem like they would be that hard to correct. I understand there's no real money in fixing this stuff, but it needs to be done. Seeing these things carry over from version to version is getting old.
He said calmly.
Exactly, bb.bongo_x wrote:That's the frustrating thing, so many little time savers have been introduced in the competition, and not in DP. Most of the things that bug me seem like they would be so simple to fix. It really seems like no one is looking at workflow and ergonomics, just "features".wurliuchi wrote:I hope someday MOTU will take care of most of these nagging, little issues that slow things down or just get in the way or feel and look unprofessional. There's getting to be a pretty long list of them, and each new version adds more it seems. I should write them down when I come across them, but I never do. I just think, "Oh, yeah, that stupid thing" and move on
Quite frankly, a lot of them should have been taken care of long ago. They don't seem like they would be that hard to correct. I understand there's no real money in fixing this stuff, but it needs to be done. Seeing these things carry over from version to version is getting old.
He said calmly.
bb
When you're talking.carrythebanner wrote:Sounds like this:bOing wrote:Not sure if it was mentioned but as a quick doubling option I sometimes "duplicate" a track - killing the audio but keeping the setup.
I couldn't get command-shift-D to work.
(is that right, I'm not near my sweetie right now.)
Why isn't the key binding for Duplicate Tracks working with DP or AudioDesk under Tiger (10.4)?
Had to change one of my customs yesterday because I found out that the new comping commands had used it up.martian wrote:that ones simple - CHANGE the default binding..... I have no idea why it's D dinna work... but I changed it to shift option D and bingo
better moan about something you CANT change