The Top 10 Most Requested Features

[BKK-OZ]

We've probably hashed this over before, but I got rid of the spikes by maxing out the RAM available for sample data.

If we did, I don't remember - can you clue me in, where does one make that adjustment?
Thanx in advance.

Look over page 104 in the manual.

I have no idea which box my manual is in (1 year on after my last move and I still have not unpacked my storage!). But you were/are right, I did a search here at the 'Nation and we have gone over this topic before. FYI and anyone else out there still having problems with M5, here is a cut-n-paste from a tip I found on MOTU.com:

• The Preload Time defines how much of each sample is pre-loaded into RAM when the program loads. When using a program with a high number of samples on a computer with plenty of RAM to spare, a higher preload size will help play more parts simultaneously.
  
  The Ring Buffer Size is the number of samples reserved for each voice after streaming has begun. A lower value can help eliminate dropouts, but also increases the load on your computer's CPU. A higher value reduces processor strain, but requires more memory.

The rest of the article is here: http://www.motu.com/techsupport/tip-of-the-day#

[pencilina]

Another: A key command to close all open plug in windows or better yet an option to have a single plug in window like in DP 3.

[monkey man]

I may as well bring this up again. The Analysis Tools available with current MOTU hardware should really be included as plug-ins available in DP.

Yes Rads!

If the set doesn't include a spectral readout (I think that's what you call it - like the mini one in MW EQ), then it should! Seems like the basic code's already there...

Also, a stereo-field display would be a welcome (and money-saving) addition to the "mastering suite" along with the multi band comp and limiter I mentioned elsewhere.

[nk_e]

1. Absolute Grid Snapping
2. Absolute Grid Snapping
3. Absolute Grid Snapping
4. Windows Always Float On Top Preference (for VI, Plugins, Quantize, etc.)
5. Windows Always Float On Top Preference
6. Update DP Contol app!!!!
7. A proper Channel Strip integrated into the SE/TO.
8. More pitch flexibility. MachFive IRCAM pitch-shifting/time stretching integrated into DP. The ability to draw in pitch on any audio clip (not just monophonic) to create tape-stop effects, pitch drops, etc.
9. More Loop/Grid-Oriented Features In General. DP has always excelled at the linear/tape machine metaphor. But grid/loop/clip has become so much a part of everything today, that even an old timer like me needs this constantly.
10. Obviously, serious catch-up is needed in the VI department. At least give us a basic version of MachFive. I often need to trigger or loop a short audio clip, or take a piece of audio and play it as an instrument. I would love a super easy-to-use sample playback VI where I could just drop in loops or clips and have things set up as automatically as possible. It should have both a keyboard (loop/truncated/transposed) and drum machine (one shot) interface. NanoSampler needs to be upgraded to at least MiniSampler, if not MachFive Jr.

Babz

YES YES YES TO #9!!!!!!!!!!!

Good lord that would make me happy.

[bayswater]

better yet an option to have a single plug in window like in DP 3.

I don't know DP3, but you can use a single plugin window in DP 8 by changing the channel, insert and plugin selections in the respective drop down menus.

[bolla]

INDEPENDANT L/R VOLUME AND PANNING for Stereo tracks

With any stereo track it should be possible to vary the volume and pan of either channel without having to use Trim.
VEP does it well.
Bolla

[daniel.sneed]

INDEPENDANT L/R VOLUME AND PANNING for Stereo tracks
With any stereo track it should be possible to vary the volume and pan of either channel without having to use Trim.VEP does it well.Bolla

In my actual templates, DP trim plug sits at the very last insert row of all my audio and aux tracks. I achieve some sort of *pre-mix* with all of them, prior any automation task.

[HCMarkus]

Great stuff guys and gals.

I have one more, which I submitted to the MOTU suggestion box a while ago:
A MIDI Lag processor plug in (attack/release/smoothing) would make BC and AT much more useable when controlling volume, filtering and vibrato.

[daniel.sneed]

Ok, Markus.

While we're at it: a complete revamp and extension of the real-time plugin set, which looks very limited to me.
IMHO, it's in the very first DP ball park.

Long ago, I've suggested to Motu to add a real time note-legnth plugin.
My wish is to play live some non percussive VI sounds with percussive pads.
Most of my actual VIs do not offer this type of tweaking.

BTW the actual velocity change seems poor to me, too.

[elcappn]

Another: A key command to close all open plug in windows or better yet an option to have a single plug in window like in DP 3.

Have you tried the "Close All Effect Windows" command? That will close all plug-in windows.

[cleamon]

It would be nice if when you apply a transpose plugin to a MIDI track, that would be reflected in quickscribe. (at least as an option). Apparently, quickscribe is pre-plugin data.

[cowtothesky]

I would like to see a way that you can double click on a VE Pro Instance and instead of it bringing up the server box (where you can raise the instance), it brings up the actual VE Pro Instance. If there is a way to do this, I am unaware of it, and maybe this is something VSL needs to address, rather than MOTU. I would just like to eliminate a step that I tend to do a couple thousand times in a project.

[Shooshie]

It would be nice if when you apply a transpose plugin to a MIDI track, that would be reflected in quickscribe. (at least as an option). Apparently, quickscribe is pre-plugin data.

Print the plugin. Or render it or whatever they call it. There's a menu item for that. Then it will be the same everywhere.

Quickscribe, MIDI Graphic Editor, and Event List are all the same data. Well... QS has more notation, lyrics, and so forth, but the notes are the same data you see everywhere else. I'm not saying it couldn't be done. It's just not separate data.

Shoosh
[edit: DOH! Of course it IS separate. Otherwise you couldn't do enharmonics.]

[bolla]

Cross fades

Say you have a favourite fade curve that looks like the local slippery dip.
It would be great to be able to save this as a user curve so you can recall it.


Cheers, Bolla

[Guitar Gaz]

I must admit when I saw this thread I didn't expect so much requesting to do with plugins which, to be honest, are external to DP and Motu. I was concentrating on the practicalities of the look and the size of buttons and screens etc which tend to affect my workflow. Its also a question of what can Motu do to make DP itself better - so I can understand if they concentrate on that and less on the issue with externals and plugins. Personally if they make loads of changes to deal with all the requests to do with handling of plugins, but ignore the basic gripes about functionality and look (full screen mode a case in point) I would not be so happy. Guess it show that everyone has different priorities and issues and different things which act like the drip drip water torture effect. Don't know how Motu will process requests or whether an update will be anything more than a fix (did I mention full screen mode already?).