Suggestions for next DP update

For seeking technical help with Digital Performer and/or plug-ins on MacOS.

Moderator: James Steele

Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
User avatar
FMiguelez
Posts: 8266
Joined: Sun Oct 24, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Body: Narco-México Soul/Heart: NYC

Re: Suggestions for next DP update

Post by FMiguelez »

James Steele wrote:
ccrane wrote:
chaim wrote: • my long time request, a solo button in the SE, by each track.
Such a simple, tremendously useful function.
God bless 'em, but I just don't think MOTU gets it - I mean, 7 versions in and no solo in SE? :shock:
As an alternative option, I'm pretty sure you can use a keyboard shortcut to engage Solo Mode, and then you can click the play enable buttons to designate which tracks are soloed or even option click the play button of one particular track to solo just that track.
Agreed.
That's what I do. The shortcut for Solo Mode is all one needs.
Mac Mini Server i7 2.66 GHs/16 GB RAM / OSX 10.14 / DP 9.52
Tascam DM-24, MOTU Track 16, all Spectrasonics' stuff,
Vienna Instruments SUPER PACKAGE, Waves Mercury, slaved iMac and Mac Minis running VEP 7, etc.

---------------------------

"In physics the truth is rarely perfectly clear, and that is certainly universally the case in human affairs. Hence, what is not surrounded by uncertainty cannot be the truth." ― Richard Feynman
User avatar
ccrane
Posts: 214
Joined: Mon Apr 02, 2007 6:15 pm
Primary DAW OS: MacOS
Location: Florida

Re: Suggestions for next DP update

Post by ccrane »

James Steele wrote:As an alternative option, I'm pretty sure you can use a keyboard shortcut to engage Solo Mode, and then you can click the play enable buttons to designate which tracks are soloed or even option click the play button of one particular track to solo just that track.


This is a real good tip James. Thanks. I would still prefer a dedicated button but this can work.
I've been hesitant to option click on a track in solo mode only because when I mistakenly did that while not in solo mode the results were not pretty! Just need to get used to it I guess. :)
newrigel

Re: Suggestions for next DP update

Post by newrigel »

I use a Mac because of the graphical user interface. If I want to keep my hands glued to a keyboard, I'll use DOS. It would be nice to see DP utilize more of the GUI that makes the Mac so nice to use. Sure, if your a keyboardist your used to typing and are more into that but there are tons of people who'd rather not have to type shortcuts to do something.
User avatar
James Steele
Site Administrator
Posts: 22792
Joined: Fri Oct 15, 2004 10:01 pm
Primary DAW OS: MacOS
Location: San Diego, CA - U.S.A.
Contact:

Re: Suggestions for next DP update

Post by James Steele »

newrigel wrote:I use a Mac because of the graphical user interface. If I want to keep my hands glued to a keyboard, I'll use DOS. It would be nice to see DP utilize more of the GUI that makes the Mac so nice to use. Sure, if your a keyboardist your used to typing and are more into that but there are tons of people who'd rather not have to type shortcuts to do something.
As usual you state your opinion forcefully. However if you choose only to click buttons with a mouse for everything then you're only slowing yourself down in many cases. Keyboard shortcuts can save a lot of time if you have them committed to memory. Watch really good video editors. You won't see them marking edit points with a mouse.
JamesSteeleProject.com | Facebook | Instagram | Twitter

Mac Studio M1 Max, 64GB/2TB, macOS Sequoia 15.5 Public Beta 2, DP 11.34, MOTU 828es, MOTU 24Ai, MOTU MIDI Express XT, UAD-2 TB3 Satellite OCTO, Console 1 Mk2, Avid S3, NI Komplete Kontrol S88 Mk2, Red Type B, Millennia HV-3C, Warm Audio WA-2A, AudioScape 76F, Dean guitars, Marshall amps, etc., etc.!
newrigel

Re: Suggestions for next DP update

Post by newrigel »

I use ⌘S religiously. I just think that having a GUI and having to type goes against the grain a bit, don't you? There's some who can fly with a mouse just as fast as anyone doing key commands. Depends what you do but for basic operations like a mute, having to reach over to the keyboard takes time. If I move a physical fader, the same exact thing is reflected within the GUI, no?
I'd rather be in the sequence editor actually manipulating the visual data (because that's where your going to inevitably end up to fine tune the fader move) so I go there and there isn't a key command for that. By the time you go over to your fader box, I already drawn it in and it's perfect. The Mac was the computer that took the industry by storm because of the GUI... it's the macs strength! What's wrong with incorporating more graphical options within the GUI instead of having to go reach for a keyboard to type a menu command??
Like I said, if I want to type commands... I'll use DOS!
And this has nothing to do with my opinion and ideals... it has to do why the Mac OS took over the computer world with the GUI! I want more graphical ways to manipulate data instead of reaching over and typing. Sure have an option, but don't kill what the GUI stands for.
You guy's were talking about a mute function... put a button in there. Why should I have to go type? And the video editors I know (myself included) don't type to edit video.
You like to type... good for you. Everyones different and like I said, I use command-s religiously.
User avatar
James Steele
Site Administrator
Posts: 22792
Joined: Fri Oct 15, 2004 10:01 pm
Primary DAW OS: MacOS
Location: San Diego, CA - U.S.A.
Contact:

Re: Suggestions for next DP update

Post by James Steele »

newrigel wrote:I use ⌘S religiously. I just think that having a GUI and having to type goes against the grain a bit, don't you? There's some who can fly with a mouse just as fast as anyone doing key commands.
I'd like to see this actually PROVEN than merely forcefully asserted. I think you're quite wrong about this. Someone with a command of shortcut keys can easily outrun someone clicking onscreen buttons. I also don't know what video editors you claim use a mouse, but the ones I know are professionlals working on television and film projects both on Avid and FCP.

To use a more obvious example... when you wish to start or stop playback after performing an edit, do you move the mouse cursor over to the CP, position it over the Play button and click, or do you just hit the space bar? You tell me which is faster?

Or say I have a sequence playing back and I'm currently at measure 100 and I want to jump to measure 15? ".15[enter]" on the numeric keypad locates to that spot in one second. How long to do that by using your mouse? Even IF you had a marker there-- and you don't-- positioning the cursor accurately in an open marker window (if it is open) will take that much time if you're fast. But you don't have a marker there-- and you're currently playing back and measure 15 is no longer visible on the timeline. Explain to me how you'll accomplish with dragging and clicking a mouse or other pointing device FASTER than typing ".15[enter]" in a second or a little less.

Perhaps you don't like using a keyboard and you're not very good at typing. But bringing up the DOS operating system as some sort of argument that keyboard shortcuts are not often faster than using a pointing device makes no sense. A GUI is a useful thing and makes computers easier to use but not necessarily faster to use. There are many things that can be done more quickly via a command line interface (if you are familiar with it and KNOW HOW TO TOUCH TYPE).

By the way, do you post messages to this board by typing, or would it be faster for you to enter your entire post using MouseKeys? I mean typing is so "DOS" isn't it?
JamesSteeleProject.com | Facebook | Instagram | Twitter

Mac Studio M1 Max, 64GB/2TB, macOS Sequoia 15.5 Public Beta 2, DP 11.34, MOTU 828es, MOTU 24Ai, MOTU MIDI Express XT, UAD-2 TB3 Satellite OCTO, Console 1 Mk2, Avid S3, NI Komplete Kontrol S88 Mk2, Red Type B, Millennia HV-3C, Warm Audio WA-2A, AudioScape 76F, Dean guitars, Marshall amps, etc., etc.!
newrigel

Re: Suggestions for next DP update

Post by newrigel »

James Steele wrote:
newrigel wrote:I use ⌘S religiously. I just think that having a GUI and having to type goes against the grain a bit, don't you? There's some who can fly with a mouse just as fast as anyone doing key commands.
I'd like to see this actually PROVEN than merely forcefully asserted. I think you're quite wrong about this. Someone with a command of shortcut keys can easily outrun someone clicking onscreen buttons. I also don't know what video editors you claim use a mouse, but the ones I know are professionlals working on television and film projects both on Avid and FCP.

To use a more obvious example... when you wish to start or stop playback after performing an edit, do you move the mouse cursor over to the CP, position it over the Play button and click, or do you just hit the space bar? You tell me which is faster?

Or say I have a sequence playing back and I'm currently at measure 100 and I want to jump to measure 15? ".15[enter]" on the numeric keypad locates to that spot in one second. How long to do that by using your mouse? Even IF you had a marker there-- and you don't-- positioning the cursor accurately in an open marker window (if it is open) will take that much time if you're fast. But you don't have a marker there-- and you're currently playing back and measure 15 is no longer visible on the timeline. Explain to me how you'll accomplish with dragging and clicking a mouse or other pointing device FASTER than typing ".15[enter]" in a second or a little less.

Perhaps you don't like using a keyboard and you're not very good at typing. But bringing up the DOS operating system as some sort of argument that keyboard shortcuts are not often faster than using a pointing device makes no sense. A GUI is a useful thing and makes computers easier to use but not necessarily faster to use. There are many things that can be done more quickly via a command line interface (if you are familiar with it and KNOW HOW TO TOUCH TYPE).

By the way, do you post messages to this board by typing, or would it be faster for you to enter your entire post using MouseKeys? I mean typing is so "DOS" isn't it?
I'm not talking about hitting play... everyone knows that. I'm talking about the arcane key command sequences to do a process.
FWIW, I don't type my post... I use dragon naturally speaking. I can type fine but still, I hate reaching for a keyboard when I can just mouse over to a mute button. I use a computer because I put my energies into my vocal work and I use the mac to do music production because I like the synonymous relationships between the two... I have secretaries to type and do those things.
Do you have to type a command to manipulate a tape transport? How about touching a solo button on a console. We were discussing the mute function and you'd rather type a command... on a console, there's a button. I think DP's features should be more consistent throughout the UI. Why in the SE should one type a key command to do something when in another window there's a button? It's ill-consistency within the GUI and I think (and obviously others too) that having to type a command (when in another window you don't) is inconsistent implementation. I'm not the one who said anything about it because I could care less but the one's wanting these features shouldn't have to even touch a keyboard if it's somewhere else in the GUI... they just want to mute some tracks. I don't think you can keep track of all those commands and if you can... your focus is on other things obviously.
User avatar
FMiguelez
Posts: 8266
Joined: Sun Oct 24, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Body: Narco-México Soul/Heart: NYC

Re: Suggestions for next DP update

Post by FMiguelez »

newrigel wrote: I'm not talking about hitting play... everyone knows that. I'm talking about the arcane key command sequences to do a process.
FWIW, I don't type my post... I use dragon naturally speaking. I can type fine but still, I hate reaching for a keyboard when I can just mouse over to a mute button.
You still have to reach for the mouse, find the pointer (if you have a big multi-monitor setup), move the mouse, click on the menus and find the right command.

With a shortcut, it takes you a fraction of the time.
newrigel wrote:I use a computer because I put my energies into my vocal work and I use the mac to do music production.
We do that too, only faster.

I know you can take this, so I'll just say it:
It seems you believe we (shortcut users) lose the focus on our music because we are thinking of the shortcuts. But this NEVER happens. We know them by heart and can recall them effortlessly without even thinking about them... they just come naturally the same way you move your arm or stand up: you just do it without thinking about it.
Just like you press Command-S -and not go to the Edit Menu and select Save- Same concept... why not extend that to the rest of the DP stuff?

It's not that we shortcut users concentrate less on our music and more on the commands. It's not that we don't pay attention to our music or get distracted by computer details...
We do the same like you, only faster.

newrigel wrote: I don't think you can keep track of all those commands and if you can... your focus is on other things obviously.
Believe me. I can. I know by heart hundreds of shortcuts, and not only for DP, but for EVERY app I use. And I NEVER have to make an effort to remember them.
I don't have to "keep track of them"... I just know them. This happens even if I didn't want to learn them. If I don't know the shortcut, I mouse around until I find the command in the menus. At that point I take note of the shortcut in my brain that is included at the right of the command. Press Esc and invoke the command with the shortcut. Next time I will know it. If not, repeat until it is learnt (one or two more tries tops).

Harley, I'm sorry to tell you this, my friend. You know I totally respect you and I always read with great interest your posts. You DEFINITELY know your stuff... But:

I can tell you I'd SMOKE you (or any mouse-moving user) easily (in DP-operation speed). You with your quick mouse moves and I with my shortcuts... you'd be left in the dust, my friend.
We talked about this in a similar thread, and I gave you the floppy disk VS SSD example.
If we were measuring the speed of the DP user/operator, you would be a floppy and we would be the SSD!

What do you want? Change a velocity? Command-2. Bam! Done. Next?

No offense intended, Harley!

Now, imagine how much faster YOU'd work if you started implementing the shortcuts into your workflow... You'd be flying with them!

And the next step would be QuickKeys... The guys here who use that with DP would smoke ME and my shortcuts!
Last edited by FMiguelez on Sat Jun 26, 2010 3:08 pm, edited 1 time in total.
Mac Mini Server i7 2.66 GHs/16 GB RAM / OSX 10.14 / DP 9.52
Tascam DM-24, MOTU Track 16, all Spectrasonics' stuff,
Vienna Instruments SUPER PACKAGE, Waves Mercury, slaved iMac and Mac Minis running VEP 7, etc.

---------------------------

"In physics the truth is rarely perfectly clear, and that is certainly universally the case in human affairs. Hence, what is not surrounded by uncertainty cannot be the truth." ― Richard Feynman
User avatar
James Steele
Site Administrator
Posts: 22792
Joined: Fri Oct 15, 2004 10:01 pm
Primary DAW OS: MacOS
Location: San Diego, CA - U.S.A.
Contact:

Re: Suggestions for next DP update

Post by James Steele »

newrigel wrote:I'm not talking about hitting play... everyone knows that. I'm talking about the arcane key command sequences to do a process.
Well, as it turns out my entire reply got lost as I somehow got logged out. Firstly, I didn't know you weren't talking about hitting play. You seemed very much against the use of the keyboard and brought up DOS, etc. to sort of ridicule the idea. My bringing up the spacebar was probably similarly absurd, but it makes the point that a mouse is not going to necessarily be the fastest way to accomplish a task. On top of it, your use of the word "arcane" is prejudicial and it doesn't apply. If these "arcane" key commands accomplish a task more quickly than using a mouse, and I gave you concrete examples, then they should be called "modern" since we like to think of things that are "more efficient and faster" as "modern". So I'll call them "modern" key commands if you don't mind.

FWIW, I don't type my post... I use dragon naturally speaking. I can type fine but still, I hate reaching for a keyboard when I can just mouse over to a mute button. I use a computer because I put my energies into my vocal work and I use the mac to do music production because I like the synonymous relationships between the two... I have secretaries to type and do those things.
I wasn't aware that you had an office staff and not one, but two or more secretaries at your disposal. Unfortunately, I don't. And I'm not talking about something like just a mute button. Obviously a graphical button is going to be useful at times. It all depends on the context. But there are plenty of times where using a key command will be faster. I gave you examples of that.

Do you have to type a command to manipulate a tape transport? How about touching a solo button on a console. We were discussing the mute function and you'd rather type a command... on a console, there's a button.
Again, we were talking about the SOLO function. I have nothing against a solo button per se, however I merely offered what I think is a quite workable option. You can invoke Solo mode (with a key command if you like) and then the play buttons essentially become solo buttons. Until MOTU implements something like that, which might take months, years, or it might never happen... I offered a possible method of getting around this. And as far as a "tape transport"... I'm talking about DP's transport and I gave you an example already of how using the keyboard can locate to a particular measure far more quickly than using a mouse or trackball alone.

I think DP's features should be more consistent throughout the UI. Why in the SE should one type a key command to do something when in another window there's a button? It's ill-consistency within the GUI and I think (and obviously others too) that having to type a command (when in another window you don't) is inconsistent implementation. I'm not the one who said anything about it because I could care less but the one's wanting these features shouldn't have to even touch a keyboard if it's somewhere else in the GUI... they just want to mute some tracks.
Again, I have nothing against mute buttons. We weren't talking about them. And all the stuff about consistency... I'm not sure what you mean. You can invoke SOLO mode with a key command in any window. And you don't have to use it. But if you'd rather use a button, fine. Go ahead. But to bring up DOS and slam use of key commands as somehow backward or "arcane" is silly. And as I pointed out, I know professional video editors who do film and television on both Avid and FCP, and the way they become fast and efficient is by using keyboard shortcuts whenever possible. If they limited themselves to using JUST the GUI and a pointing device and clicking they'd be sunk. It's not even a contest. These are people who must produce in a stressful, time-sensitive environment and these keyboard commands are ingrained. As you pointed out, you don't go up to the File menu, click it, then choose "Save" from the menu do you? You've pretty much mastered ⌘S by now. What made you memorize that one? It's because you use it frequently and it's faster than the mouse. You can extrapolate that and you make my point for me.

I don't think you can keep track of all those commands and if you can... your focus is on other things obviously.
It's hard not to see the "your focus is on other things obviously" part of your response here as anything other than a condescending and subtle insult. You mean to say that you're focused on the music itself, yes? And it must stand to reason that I am not?

Let's use another concrete example here. You want to use the scissors tool on a soundbite. Do you take your attention off the soundbite, locate the toolbar, position the mouse over the scissor tool, click it, then move your cursor back to the soundbite, position the cursor at the edit point and then click? Or perhaps it might be better to just use your left hand and hold down the "C" key, position the cursor, and click?

What about muting a soundbite? Should you mouse over to the toolbar again, click the Mute tool, mouse back to the soundbite and click? Or just hold down the "X" key and click on the soundbite?

There's no need to keep track of "all those commands"... HOWEVER... if there is a editing operation you find yourself doing often, a little bit of time invested up front to memorize that key command is going to help you work much faster. So nobody's saying learn them all... learn the ones for operations you do frequently and I guarantee you will save time over using a mouse or trackball alone.

And back to your assertion that learning key commands isn't "focusing" in the right area... presumably not focusing on the music itself. If editing is by its nature a left brain activity that takes your focus off the music, is it not better to get a mundane editing task over with as quickly as possible so that your brain gets back out of edit mode (left brain) and back to the big picture and the music itself (right brain)? Use of key commands for operations you do often will let you work faster once you know them and will give you MORE time back for focusing on the music itself.
JamesSteeleProject.com | Facebook | Instagram | Twitter

Mac Studio M1 Max, 64GB/2TB, macOS Sequoia 15.5 Public Beta 2, DP 11.34, MOTU 828es, MOTU 24Ai, MOTU MIDI Express XT, UAD-2 TB3 Satellite OCTO, Console 1 Mk2, Avid S3, NI Komplete Kontrol S88 Mk2, Red Type B, Millennia HV-3C, Warm Audio WA-2A, AudioScape 76F, Dean guitars, Marshall amps, etc., etc.!
newrigel

Re: Suggestions for next DP update

Post by newrigel »

I can use a strait saw or a circular saw... in the end, the result's the same.
Forcing KC's on a user is ridiculous in a GUI music application because people use a Mac for a simplistic way to achieve what they want, their not data entry professionals!
Take a person who uses physical desks and or tape decks... put a picture of a tape deck on the screen and a keyboard with the commands printed on it... which do you think is going to get the better result? I'm talking autonomous reaction.
User avatar
James Steele
Site Administrator
Posts: 22792
Joined: Fri Oct 15, 2004 10:01 pm
Primary DAW OS: MacOS
Location: San Diego, CA - U.S.A.
Contact:

Re: Suggestions for next DP update

Post by James Steele »

newrigel wrote:I can use a strait saw or a circular saw... in the end, the result's the same.
Forcing KC's on a user is ridiculous in a GUI music application because people use a Mac for a simplistic way to achieve what they want, their not data entry professionals!
Take a person who uses physical desks and or tape decks... put a picture of a tape deck on the screen and a keyboard with the commands printed on it... which do you think is going to get the better result? I'm talking autonomous reaction.
I guess you decided to change your original post, which is too bad as it seemed more sensible. Here it is taken from the RSS feed in Mail before you edited it:
I use ⌘S, spacebar and ⌘Z... that's it.
I can use a strait saw to cut or a circular saw... the end result is exactly the same.
And maybe I like to work for it!
So gosh... you want to keep going on this? Fine... I'll play.
newrigel wrote:I can use a strait saw or a circular saw... in the end, the result's the same.
Sure, I guess. The initial discussion seemed to be which is more efficient. You could use a hand saw if you wished too.

Forcing KC's on a user is ridiculous in a GUI music application because people use a Mac for a simplistic way to achieve what they want, their not data entry professionals!
Nobody is forcing key commands on a user... key commands are a useful adjunct to the primary user interface which is the GUI and pointer device. However, if you want to truly do something quickly, keyboard commands will often beat mousing and clicking hands down. I'll use your own words: "a simplistic way to achieve what they want." GUI's are a great convenience and I'm a big fan-- but they aren't necessarily a time saver.

Also, what do you mean "data entry professionals?" "Data entry" is not even remotely analogous to invoking a key command now and again. You use these gross exaggerations and mischaracterizations to support your view. I found your first post in response-- before you edited it-- refreshingly honest. You wrote "maybe you like to work for it." If you prefer to use a method to do something that is less efficient that's your business. It's when you assert that it's just as efficient as keyboard commands in all cases, that I take issue.

Take a person who uses physical desks and or tape decks... put a picture of a tape deck on the screen and a keyboard with the commands printed on it... which do you think is going to get the better result? I'm talking autonomous reaction.
The mouse is going to get the better result during the 15 minutes beginning from when the user first launches the application for the very first time. If the user is going to use the application on an ongoing basis and he might learn for example that the spacebar stops and starts the tape deck and he'll start saving time right away. Learning the key for FWD and RWD will save even more time. He'll also have the benefit of not having to look at a computer monitor to start playback.

I've said that spending a few minutes to learn keyboard commands for things you do frequently can save a lot of time later. And as FM pointed out, these keyboard commands become second nature... "autonomous reaction"... just like you invoking the Save command. Someone who knows even a limited number of key commands is going to work faster than someone who doesn't.

However, if you simply like to stop and smell the roses, or "work for it" as you put it-- that's a personal preference for inefficiency and there are certainly valid arguments for that, but those arguments are philosophical or metaphysical-- not logical. As an example, none of the video editors I know could afford indulging in that luxury, as they'd lose gigs to editors who work faster than they do.
JamesSteeleProject.com | Facebook | Instagram | Twitter

Mac Studio M1 Max, 64GB/2TB, macOS Sequoia 15.5 Public Beta 2, DP 11.34, MOTU 828es, MOTU 24Ai, MOTU MIDI Express XT, UAD-2 TB3 Satellite OCTO, Console 1 Mk2, Avid S3, NI Komplete Kontrol S88 Mk2, Red Type B, Millennia HV-3C, Warm Audio WA-2A, AudioScape 76F, Dean guitars, Marshall amps, etc., etc.!
conleycd
Posts: 371
Joined: Sat Jan 21, 2006 10:45 am
Primary DAW OS: Unspecified

Re: Suggestions for next DP update

Post by conleycd »

Okay... I love DOS and I miss it everyday.

Most pro apps have a combination of good GUI and accessible keyboard short-cuts.

If we are having another wish list post:

I'd like a plug in that I could insert (address) hardware audio in/out with automatic delay compensation.

I'd also like a way on the channel strip (because you can do this with a ton of auxs or even track duplication) for sending a pre-insert aux send somewhere.

Plus... I think DP 8 should come with Mach 5 III Lite.

While I'm at it... I think MOTU interfaces should come with DP lite and scrap the Audiodesk title.

My 2 cents.

C:\>dir
C:\>cd DP 8
C:\DP 8>Motustillrocks.exe

CC
Mac Pro 5 (Early 2009) - 6 - Core, 32 gig RAM, Radeon RX 580. Mojave 10.14.6. DP 10.1
User avatar
FMiguelez
Posts: 8266
Joined: Sun Oct 24, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Body: Narco-México Soul/Heart: NYC

Re: Suggestions for next DP update

Post by FMiguelez »

conleycd wrote: C:\>dir
C:\>cd DP 8
C:\DP 8>Motustillrocks.exe
:P

---
- I want Marker takes.
- I want different kinds of markers.
- I want the QT thing "fixed".
- Tab to transient would be great.
- Time signatures and tempo changes should obey the grid state (on/off) and resolution in at least eight or sixteenth notes, so you don't get TS at X|1|046.
- Fix the issue with VIs losing their connection (MIDI usually) when brought in from Clippings or templates.
- Optional MIDI regions we can name, color-code and abuse.
- Overhaul the Quick Scribe and Notation windows (this would actually be first in my list).

I know I sound like a scratched record with those wishes, but I seem to think the more I wish for that, the more likely it is I'll be surprised by DP 8 implementing it or something :roll:
Last edited by FMiguelez on Sun Jun 27, 2010 5:35 pm, edited 2 times in total.
Mac Mini Server i7 2.66 GHs/16 GB RAM / OSX 10.14 / DP 9.52
Tascam DM-24, MOTU Track 16, all Spectrasonics' stuff,
Vienna Instruments SUPER PACKAGE, Waves Mercury, slaved iMac and Mac Minis running VEP 7, etc.

---------------------------

"In physics the truth is rarely perfectly clear, and that is certainly universally the case in human affairs. Hence, what is not surrounded by uncertainty cannot be the truth." ― Richard Feynman
User avatar
KEVORKIAN
Posts: 1042
Joined: Thu Jul 06, 2006 10:21 pm
Primary DAW OS: MacOS
Location: I'm your Huckleberry

Re: Suggestions for next DP update

Post by KEVORKIAN »

My current wish list:

1) External Instrument plug (with automatic delay compensation) that can be used with Rewire instruments as well as inputs/outputs. (Ableton's plugin got this right, Logic has this wrong)

2) MIDI note mute

3) MIDI Comping/Comp tracks... I can't think of a DAW that does this but man would it be a life save (Even if it was imperfect, and not as elegant as audio comping I'd take it)
dp7.2 || os 10.6.7 || 2x2.8 (eight core) intel mac pro, 16gb ram || metric halo uln-8 || motu traveler || euphonix mc control || waves mercury || abbey road bundle || mh channelstrip || toontrack sd 2.0, ez drummer, drumtracker || addictive drums || drumcore 3 || ni komplete 5 || reason || bidule || altiverb 6 || omnisphere, stylus RMX || melodyne 3.2 || stillwell || soundtoys || nomad factory|| psp || mpressor || dsm ||
User avatar
MIDI Life Crisis
Posts: 26279
Joined: Wed May 18, 2005 10:01 pm
Primary DAW OS: MacOS
Contact:

Re: Suggestions for next DP update

Post by MIDI Life Crisis »

+1 for MIDI comping.

More robust copy protection. Maybe iLock.

I like to type with my feet. It keeps my hands free for my mouse and drinks.

Sawzall beat straight and circular saws but make it hard to hit the mute button.

All key codes should be Bosco.
2013 Mac Pro 2TB/32GB RAM

OSX 10.14.6; Track 16; DP 12; Finale 28

LinkTree (events & peformances)
Instagram
Facebook

MIDI LIFE CRISIS
Post Reply