The biggest priority for me would be greater efficiency with VI's at low buffer settings.
Sidechain support of AU's
Automatable track mute/solo with MIDI CC's.
Overall stability.
What I DON'T want:
More included VI's
More included Plugins
There are plenty of 3rd party VI's and plugins that are much better than the ones that DP provides, many of them free.
DP6 Wishlist
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.
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.
DP6 Wishlist
G5 Dual 1.8, 4GB Ram 10.4.8, DP 5.11
-
emulatorloo
- Posts: 3227
- Joined: Mon Jan 03, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: Iowa
http://www.motu.com/other/feedback
--------
suggestions@motu.comSuggestion Box
This is a drop box to send your product related wish-lists. Got a great feature idea for Digital Performer? Send it here.
--------
-
monkey man
- Posts: 14081
- Joined: Fri Apr 22, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: Melbourne, Australia
Re: DP6 Wishlist
So... if DP provided higher quality plugs you wouldn't have to splash out on the 3rd party stuff, no?dubwon wrote:What I DON'T want:
More included VI's
More included Plugins
There are plenty of 3rd party VI's and plugins that are much better than the ones that DP provides, many of them free.
I certainly hope MOTU ups the ante as far as included plug quality goes.
Apart from the monetary savings to be had, the reliability that generally comes with included plugs can't be beat.
Poor dubwon... surely there'll be more VIs?
It seems inevitable, and that the first six were exactly that... the first six!
Still, if they're loaded with presets, boast improved efficiency and save yet more 3rd party purchases to boot, that would be a good thing too, no?
Mac 2012 12C Cheese Grater, OSX 10.13.6
MOTU DP8.07, MachFive 3.2.1, MIDI Express XT, 24I/O
Novation, Yamaha & Roland Synths, Guitar & Bass, Kemper Rack
Pretend I've placed your favourite quote here
Thank you for the link to suggestions@motu.com. I will be sure to email them.
I believe every effort should be made to make the DAW efficient, stable and crash-free before efforts are made to expand the functionality. This is a basic principle that many software developers do not subscribe to and that is hard to understand from a user perspective.
My desire is that MOTU focus improvements from the ground up. It seems to me that resources spent on developing plug-ins comes at the expense of improving basic functionality.
Also it seems that adding basic functions like track mutes would take alot less resources than making another plugin. Same goes for AU sidechain support.
Third parties can make more plugins. Third parties cannot improve the basic functionality of DP, that is MOTU's job.
I believe every effort should be made to make the DAW efficient, stable and crash-free before efforts are made to expand the functionality. This is a basic principle that many software developers do not subscribe to and that is hard to understand from a user perspective.
My desire is that MOTU focus improvements from the ground up. It seems to me that resources spent on developing plug-ins comes at the expense of improving basic functionality.
Also it seems that adding basic functions like track mutes would take alot less resources than making another plugin. Same goes for AU sidechain support.
Third parties can make more plugins. Third parties cannot improve the basic functionality of DP, that is MOTU's job.
G5 Dual 1.8, 4GB Ram 10.4.8, DP 5.11
I'm with you and totally agree, but unfortunately the ratio of those who will purchase a program for features versus those who purchase a program for stability is much higher. And not many companies care if you abandon their software because they've already got your money. The profit margin for updates and upgrades is far less than converting new users to buy their program. Most people buy software for the features, not stability. MOTU's not terrible in this regard, but DP is such a monsterous program it would take a serious overhaul to work out all the bugs. One I'd love to see, but not convinced will ever happen. Honestly, I'd like to see a streamlined version focused on MIDI and recording without all the bells and whistles that could be purchased separately in modules as needed like Digi does with PTLE... but not crippled like PTLE. There's just so much I don't use in DP that creates a ton of bloat and I'd rather have the option of purchasing it separately or at least disabling it if not needed.dubwon wrote:I believe every effort should be made to make the DAW efficient, stable and crash-free before efforts are made to expand the functionality. This is a basic principle that many software developers do not subscribe to and that is hard to understand from a user perspective.
My desire is that MOTU focus improvements from the ground up. It seems to me that resources spent on developing plug-ins comes at the expense of improving basic functionality.
Also it seems that adding basic functions like track mutes would take alot less resources than making another plugin. Same goes for AU sidechain support.
Third parties can make more plugins. Third parties cannot improve the basic functionality of DP, that is MOTU's job.
MacBook Pro Quad 2.4GHz i7 • 10.12 • 16G RAM • DP 9 • MOTU 896HD Hybrid, Apogee Duet, & MOTU Micro Lite MIDI interface • Waves Platinum, Studio Classics Collection, Abbey Road, etc... • Fabfilter Pro-Q2 • Soundtoys FX • IK Amplitube 3, Ampeg, and TRacks 3 • Altiverb 7 • Slate Digital Everything Bundle • Stylus RMX • Komplete 10 • SampleTank 3 • Arturia V Collection • M-Audio Axiom 49
-
Mr_Clifford
- Posts: 2430
- Joined: Mon Apr 17, 2006 5:56 pm
- Primary DAW OS: MacOS
- Location: Sunshine Coast, QLD, Australia
- Contact:
Perhaps something akin to DigiDesign's PTLE Factory Bundle might be a way forward. That way you could purchase DP with just the basic utility plug-ins (like what is ther now) or you buy a slightly more expensive version which comes with some extra 3rd party plug-ins & VI's.
DP 9.52 Mac Pro 10.14.6 RME fireface800. Sibelius. Dorico 4
Ya know-- as horrifying as that sounded, I gotta say that you're are probably right. Certainly, stability is a major factor for me when I buy any kind of software-- but the word 'stability' is not one that is often used in marketing campaigns. It's the features that catch the eye for those shopping for a DAW-- and perhaps those who favor stability from the outset are indeed in the minority.Splinter wrote:... Most people buy software for the features, not stability. ...
I'm not saying that it's "right", only that this very well may be quite "true".
Wow.
6,1 MacPro, 96GB RAM, macOS Monterey 12.7.6, DP 11.33
I like features!
Gimmee more features!
Like --
I can't think of anything else right now. For the most part, DP suits my needs as is.
Although I'd love it if MachFive 2 came bundled with a DP6 purchase.
Gimmee more features!
Like --
- ••• More frame rates!
••• New and improved plugin effects! MWEQ set the bar. Let's get all the bread-and-butter plugs to that level!
••• Native Broadcast WAV file format! It's an industry standard, after all!
••• More precise metering (a la Inspector XL or Ozone)
••• Auto delay compensation for outboard gear insert mixing! If PT can do it, we should too!
I can't think of anything else right now. For the most part, DP suits my needs as is.
Although I'd love it if MachFive 2 came bundled with a DP6 purchase.
Last edited by chrispick on Thu May 24, 2007 1:07 pm, edited 4 times in total.
Yes-- updated frame rates
updated GUI in Consoles for greater stability, ease of use, and tighter VI control
vertical scaling in TO
more accurate QS display and other notation basics like slurs and a graphics refreshing.
some feature that prevents the MIDI Editor from jumping to the top of its track list whenever tracks are deselected-- and the ability to have no tracks selected in the MIDI Editor while selecting new tracks for editing. Currently, one must first select the new track, then scroll to the unwanted track to deselect it. Lots of needless scrolling going on.
Some feature that allows for horizontal score scrolling in QS without automatic vertical adjustments.
with a closed track folder, using the up or down arrows will always cause the the TO's track columns to jump needlessly to the topmost tracks (where all the tracks cannot be viewed at once) as you move the record enable button through a closed track folder. This can be averted by opening all closed track folders, but this also defeats the purpose of having the folders. Scrolling with the up/down arrows forces the user to scroll with the mouse as the window reorients itself.
a sleathier audio engine that allows for lower buffers to be used without choking
key commands for sub menu items such as 'Region> Change Duration> SCALE' (and many others which can only be accessed via mouse/menu searching)
updated GUI in Consoles for greater stability, ease of use, and tighter VI control
vertical scaling in TO
more accurate QS display and other notation basics like slurs and a graphics refreshing.
some feature that prevents the MIDI Editor from jumping to the top of its track list whenever tracks are deselected-- and the ability to have no tracks selected in the MIDI Editor while selecting new tracks for editing. Currently, one must first select the new track, then scroll to the unwanted track to deselect it. Lots of needless scrolling going on.
Some feature that allows for horizontal score scrolling in QS without automatic vertical adjustments.
with a closed track folder, using the up or down arrows will always cause the the TO's track columns to jump needlessly to the topmost tracks (where all the tracks cannot be viewed at once) as you move the record enable button through a closed track folder. This can be averted by opening all closed track folders, but this also defeats the purpose of having the folders. Scrolling with the up/down arrows forces the user to scroll with the mouse as the window reorients itself.
a sleathier audio engine that allows for lower buffers to be used without choking
key commands for sub menu items such as 'Region> Change Duration> SCALE' (and many others which can only be accessed via mouse/menu searching)
6,1 MacPro, 96GB RAM, macOS Monterey 12.7.6, DP 11.33
-
Kubi
Can't you simply option-click on the new track you wish to edit, thereby selecting it and deselecting all others in the process? Or am I misunderstanding what you want to do?Frodo wrote:(...)and the ability to have no tracks selected in the MIDI Editor while selecting new tracks for editing. Currently, one must first select the new track, then scroll to the unwanted track to deselect it. Lots of needless scrolling going on.
-
Kubi
••• WAY ditto on the sidechain capability for AUs... pretty much my number one at this point...
••• Ditto on the frame rates...
••• Buffer size visible in the control panel - I hate having to open the Configure Hardware Driver window, only to find out I already reset the buffer, and then having to wait for the VIs to reload...
••• Optional solo button and mini-fader in the Sequencer window
••• in fact, optional single fader to the left of each track in the seq window, complete with plug-in slots, sends etc., visible when set to large or larger, and...
••• a setting to auto-resize the selected track in the sequencer window to large or jumbo, and all others to small or mini - this could really supercharge the SeqEditor, making it the only window I'd need for 90% of the time...
••• key command to move track selection up and down the list, in both the tracks overview and sequencer windows (visible tracks only in the case of the latter)
••• option to change the main window content in the Consolidated window from i.e. Sequence Editor to MIDI Editor via key command - I guess I could use window sets for that...
••• Ditto on MIDI ctrl option for mutes. I also like the idea of a mute tool for individual MIDI notes, nice for developing grooves etc.
More to come...? But Boy, having listed all that, DP5 is, well, the sh*t. The new slip n slide tools alone are just so incredibly useful...
And ditto on the plugs, no need to focus on that from my point of view... I have plenty, and they work fine.
••• Ditto on the frame rates...
••• Buffer size visible in the control panel - I hate having to open the Configure Hardware Driver window, only to find out I already reset the buffer, and then having to wait for the VIs to reload...
••• Optional solo button and mini-fader in the Sequencer window
••• in fact, optional single fader to the left of each track in the seq window, complete with plug-in slots, sends etc., visible when set to large or larger, and...
••• a setting to auto-resize the selected track in the sequencer window to large or jumbo, and all others to small or mini - this could really supercharge the SeqEditor, making it the only window I'd need for 90% of the time...
••• key command to move track selection up and down the list, in both the tracks overview and sequencer windows (visible tracks only in the case of the latter)
••• option to change the main window content in the Consolidated window from i.e. Sequence Editor to MIDI Editor via key command - I guess I could use window sets for that...
••• Ditto on MIDI ctrl option for mutes. I also like the idea of a mute tool for individual MIDI notes, nice for developing grooves etc.
More to come...? But Boy, having listed all that, DP5 is, well, the sh*t. The new slip n slide tools alone are just so incredibly useful...
And ditto on the plugs, no need to focus on that from my point of view... I have plenty, and they work fine.
-
Mr_Clifford
- Posts: 2430
- Joined: Mon Apr 17, 2006 5:56 pm
- Primary DAW OS: MacOS
- Location: Sunshine Coast, QLD, Australia
- Contact:
control+page up/down moves selected tracks up and down the list.Kubi wrote: key command to move track selection up and down the list, in both the tracks overview and sequencer windows (visible tracks only in the case of the latter)
shift+opt+up/down moves the selection up and down
Was either of those what you're after?
DP 9.52 Mac Pro 10.14.6 RME fireface800. Sibelius. Dorico 4
-
Tritonemusic
- Posts: 2745
- Joined: Fri Oct 15, 2004 10:01 pm
- Primary DAW OS: MacOS
I agree w/op--more plugins aren't what I'm looking for...oh, how i lie. not entirely true!
a) *good* va drum kit
b) distortion/tube/amp emu
Here's some thoughts...some of it may be doable already, but if it is, then the process could be improved...
a) Comprehensive MIDI mapping w/out using MIDI plugins. Let me define MIDI maps at the global project level, at the insturment level (if I've selected a given insturment) and at the track level (a given instance). Let me right click on any control, click "Learn", hit a knob, and that's that.
a1) ahhh...right click...
a2) tooltips?
b) Keyboard splits..
c) Integrated patch management vis-a-vis unisyn. We have consoles, lets build a library so that if I say 'oi! MKS-50!' that console pops up without me having to build a pg programmer from scratch.
d) vi / MIDI / loop cataloger db ala kore but better. Let me press a button, and have my entire patch memory not only downloaded on to my computer for cataloging, but also record a series of notes for demo purposes. This way I can scroll through sounds of a MIDI or vi insturment without having it on and patched up in the patch bay if I so choose.
d2) Better drum track handling. Let me define a drum track as such--separate from a MIDI or audio track. let me set it up as a single virtual insturment omposed of multiple insturments. So if I want the kick to be channel1 from the analog synth, hihat open/closed to be from the model 12 and snares note C# from a groovebox/sampler/rompler, let me define that in a single interface. Naturally, I build this kit from the catalog of drum components I've got. If I want to use 4 romplers, an analog an model 12, so be it! Maybe I can browse by kit--hmm, let me see what drums this rompler has--or by sound: show me all snares,...
Also, let me enter variable length patterns for each element of the kit, so my kick consists of one measure, hihat of two measures and snare of four measures, and DP figures it out. Let me name these patterns, and lets store these inside the kiot; the input sequence MIDI track would dictate which pattern to play when..
Also, DP should recognize if an insturment is not multi-timbural, then I cant use that insturment in other parts of the track; if is multi-timbural, then that channel is somehow locked so my crunchy rompler hihats stay that way--I can't plop that rompler down elsewhere.. Then let me switch the patterns on the fly, either at a piece level (swapping out the one measure kick beat for a three measure fill) or at an insturment level (switch to a new set of patterns for each piece in the kit). Probably a good idea if I can group patterns too across the entire kit (not at a piece level though). For each piece in the kit, hide the implementation, so that all i see is the name I define, and perhaps a few knobs I slap down that route to hardware/vi behind the scenes.
d3) lets extend the concept to layered insturements. perhaps i can make a layered folder, then any MIDI/vi insturments I place in there gets treated as the same MIDI insturment for MIDI in / audio out purposes. so where a drum track assigss one note to each layered insturement, this concept has has every insturment sharing all notes--or maybe some kind of split definition. let me define invidiual sends/inserts for each layered sound, and also let me define kobs for the folder level, which can communicate perhaps different cc messages to different insturments but from the same knob. Maybe I want a volume knob, or a knob that does resonance for half the insturments and cut off for the other half. Let me save this virtual rack of sorts...
e) A proper step sequencer that I can setup multiple patterns for, feed that into insturments, vi or external MIDI. then let me define MIDI controls to change aspects of the step sequencer (eg right click, 'learn' etc). Also, instead of referring to patterns by bank and letter, let me name them and select from a drop dow box.
f) skinnable consoles
f1) nrpn/rpn transmissions from consoles. i was majorly bummed out to discover I couldn't rig up MOTU's own vi's to a console.
g) auto freeze: if I go to bounce a track, and it IS ALL unfrozen vi/MIDI tracks, do a freeze--but hidden, perhaps call it 'recording arrangements'--then bounce, and I'm never the wiser.
h) programmable note creation. Not Karma, but...well, karma?
i) I'm sure I' missing this somehow, but a new record mode for MIDI tracks that allows me to record only one given cc/note/etc easily.
j) if nothing else, when I load model 12, and I have a MIDI track pointed to the mode 12, therum kit patc should reflect automatically model 12.
I'd often thought about drawing up my MIDI sequencer, but haven't the time so....not sure any of this makes sense to other folks, but to me, it would be great! Don't get me wrong, I love DP, but I think these items, oriented towars a more...err...limited?
user / musician would go a long ways to sharpening the DP knife edge to a contemporary point.
apologize for the length, spelling and grammer errors. It's late and I'm too tired too correct...but some ideas in case anyone is listening!
a) *good* va drum kit
b) distortion/tube/amp emu
Here's some thoughts...some of it may be doable already, but if it is, then the process could be improved...
a) Comprehensive MIDI mapping w/out using MIDI plugins. Let me define MIDI maps at the global project level, at the insturment level (if I've selected a given insturment) and at the track level (a given instance). Let me right click on any control, click "Learn", hit a knob, and that's that.
a1) ahhh...right click...
a2) tooltips?
b) Keyboard splits..
c) Integrated patch management vis-a-vis unisyn. We have consoles, lets build a library so that if I say 'oi! MKS-50!' that console pops up without me having to build a pg programmer from scratch.
d) vi / MIDI / loop cataloger db ala kore but better. Let me press a button, and have my entire patch memory not only downloaded on to my computer for cataloging, but also record a series of notes for demo purposes. This way I can scroll through sounds of a MIDI or vi insturment without having it on and patched up in the patch bay if I so choose.
d2) Better drum track handling. Let me define a drum track as such--separate from a MIDI or audio track. let me set it up as a single virtual insturment omposed of multiple insturments. So if I want the kick to be channel1 from the analog synth, hihat open/closed to be from the model 12 and snares note C# from a groovebox/sampler/rompler, let me define that in a single interface. Naturally, I build this kit from the catalog of drum components I've got. If I want to use 4 romplers, an analog an model 12, so be it! Maybe I can browse by kit--hmm, let me see what drums this rompler has--or by sound: show me all snares,...
Also, let me enter variable length patterns for each element of the kit, so my kick consists of one measure, hihat of two measures and snare of four measures, and DP figures it out. Let me name these patterns, and lets store these inside the kiot; the input sequence MIDI track would dictate which pattern to play when..
Also, DP should recognize if an insturment is not multi-timbural, then I cant use that insturment in other parts of the track; if is multi-timbural, then that channel is somehow locked so my crunchy rompler hihats stay that way--I can't plop that rompler down elsewhere.. Then let me switch the patterns on the fly, either at a piece level (swapping out the one measure kick beat for a three measure fill) or at an insturment level (switch to a new set of patterns for each piece in the kit). Probably a good idea if I can group patterns too across the entire kit (not at a piece level though). For each piece in the kit, hide the implementation, so that all i see is the name I define, and perhaps a few knobs I slap down that route to hardware/vi behind the scenes.
d3) lets extend the concept to layered insturements. perhaps i can make a layered folder, then any MIDI/vi insturments I place in there gets treated as the same MIDI insturment for MIDI in / audio out purposes. so where a drum track assigss one note to each layered insturement, this concept has has every insturment sharing all notes--or maybe some kind of split definition. let me define invidiual sends/inserts for each layered sound, and also let me define kobs for the folder level, which can communicate perhaps different cc messages to different insturments but from the same knob. Maybe I want a volume knob, or a knob that does resonance for half the insturments and cut off for the other half. Let me save this virtual rack of sorts...
e) A proper step sequencer that I can setup multiple patterns for, feed that into insturments, vi or external MIDI. then let me define MIDI controls to change aspects of the step sequencer (eg right click, 'learn' etc). Also, instead of referring to patterns by bank and letter, let me name them and select from a drop dow box.
f) skinnable consoles
f1) nrpn/rpn transmissions from consoles. i was majorly bummed out to discover I couldn't rig up MOTU's own vi's to a console.
g) auto freeze: if I go to bounce a track, and it IS ALL unfrozen vi/MIDI tracks, do a freeze--but hidden, perhaps call it 'recording arrangements'--then bounce, and I'm never the wiser.
h) programmable note creation. Not Karma, but...well, karma?
i) I'm sure I' missing this somehow, but a new record mode for MIDI tracks that allows me to record only one given cc/note/etc easily.
j) if nothing else, when I load model 12, and I have a MIDI track pointed to the mode 12, therum kit patc should reflect automatically model 12.
I'd often thought about drawing up my MIDI sequencer, but haven't the time so....not sure any of this makes sense to other folks, but to me, it would be great! Don't get me wrong, I love DP, but I think these items, oriented towars a more...err...limited?
user / musician would go a long ways to sharpening the DP knife edge to a contemporary point.apologize for the length, spelling and grammer errors. It's late and I'm too tired too correct...but some ideas in case anyone is listening!