Suggestions for DP 6.0.3

[mike_o]

I want to see MOTU implement the ability to use the AU version of a plugin even when a MAS version is present, at the moment this is not possible. see here.

http://www.motunation.com/forum/viewtop ... =9&t=34161

now, on top of that.

#1. I want to split the consolidated window into 4 major parts, you can almost do this now, but not in the way that I mean. I would like to have the track view in the upper left, seq view in the upper right, mixer in the lower left and the lower right square would be changed amongst data windows, track inspector, sounbite window etc. Opening the sidebar windows is close, but they cannot display some windows.

#2. I would like to be able to view the mixing board and the v-rack at the same time in separate windows. also to be able to send automation data to the VI on the MIDI track, as it is now you must insert an audio track along with the MIDI track and assign the automation for the vi on th audio track, this creates a lot of extra tracks when using the v rack and automation.

#3. !!!UPDATE THE PLUGINS!!!* some of DP's older gen plugs are just not quite up to snuff. the trigger plug is the absolute worst audio to MIDI trigger I have ever used.
*the masterworks EQ, leveler, compressor and Proverb have all been great to me, however, the MW limiter is horrible, it adds distortion to everything, even with light use, please fix that, bring it up to the transparency level of the Wavearts final plug 5 or something similar.(thats what I use in place of the MW limiter, it never distorts or adds artifacts unless you slam it down to a ridiculous level.)

(Back when I transitioned from Studio Vision Pro to DP, #4 is the one that broke my heart.)

#4. when creating or editing MIDI CC# data in the graphic editor, why are we only given like 7 or 8 CC # options to start with? I know that you can type in any MIDI CC # you want, but it's annoying to try and remember all the parameter #'s for all my different hardware. back in SVP you could type up a parameter name list for each hardware instrument you had, assign the MIDI CC # name list to the proper hardware channel, and then any time you opened up the graphic editor for a track on that hardware channel it would display the entire list, all 0-127 according to your own custom written names. (like CC#40 Filter 1, CC# 42 Filter 2 etc..). this was great for my virus rack and my nord rack.(basically offer a full MIDI CC# list in the graphic editor similar to the VI parameter lists in the seq editor, but with custom name lists per hardware channel)

#5. and yes of course, fix any bugs, tighten up the system overall, what everyone else said all over again from me
thats all for right now

[Armageddon]

.

I think MOTU has been playing catch-up with the rest of the DAWs.

I agree they should concentrate on cleaning up ALL the bugs before implementing more features. The thing is that they have to hurry, because they are behind one cycle. IOW, if they get rid of all the bugs in the next version (say DP 6.3), they would have to immediately start thinking about new features for DP 6.5. Otherwise, they will never lead with innovation... they will keep playing catch-up.

That's just it: I don't think DP necessarily needed to catch up. Outside of their handling of VIs, which should have been the entire focus of this version, DP is what it is, that's why I assume we gravitate towards it rather than ProTools or Logic. They had a decent thing going in 5, and I think many of us can agree that we'd have been extremely happy with a 6 that more or less looked and behaved like 5 did, except handling VIs more efficiently. Everything about 6 so far feels like it's only halfway finished, from the still-wobbly pre-rendering issues to the questionable new plugs to the GUI. If we have to turn pre-rendering off just to use our VIs, we might as well be using 5.1.3, which still seems to be a hell of a lot more stable by comparison. Unfortunately, as I keep saying, if I had to use DP for a film-scoring gig right now, I'd absolutely be forced to go back to 5.1.3; I just can't risk losing that much time and work to a program that crashes at the drop of a hat and has so many issues to work around, especially on a deadline.

[FMiguelez]

Unfortunately, as I keep saying, if I had to use DP for a film-scoring gig right now, I'd absolutely be forced to go back to 5.1.3; I just can't risk losing that much time and work to a program that crashes at the drop of a hat and has so many issues to work around, especially on a deadline.

And that's exactly why I STILL use DP 4.61 and Panther in my main work station. It is ridiculously stable and reliable

But man, I do need those track folders and the take comping features...

BTW, I've been following your Pro Verb thread closely. GREAT discussion. Those are the kind of threads that make this board so good (and the civl and friendly members too, of course). I've learnt SO MUCH from this site

[jlaudon]

ONe thing I would love to see would be that in the graphic MIDI editor, when editing controller 64 (sustain) at the bottom (line mode mainly), it would be great to see it go down to '0', not '1', which means I manually have to highlight and change values...

[FMiguelez]

ONe thing I would love to see would be that in the graphic MIDI editor, when editing controller 64 (sustain) at the bottom (line mode mainly), it would be great to see it go down to '0', not '1', which means I manually have to highlight and change values...

Hmmmmm... that's odd. Can you explain with more detail what you mean? It works fine here

[jlaudon]

Actually I think the controller 64 editing problem is something that has happened in DP5/6 - it was ok in DP4.61 if I recall reading from another post recently.

[csiaudio]

I would like to see the follow changes:

In the Sequence window where the track information is I would like to have an indication as to what is the 'Input' and what is the 'Output'.

For those of us that manually draw in volume adjustments I would like to see an improvement in the tools to draw them in. The 'multi' tool functions are cumbersome at best requiring you to be 100% exactly on the line to move it otherwise it switches to a different tool. At least give us the option to not have the tool switch to something else. Pro Tools has this function down pat - very easy to use allowing for extremely quick draws, and isn't that the goal, simplicity?

Would love the 'Configure Hardware Driver' info displayed somewhere other that having to go to the pull down.

Would love to have a session 'Default' buffer size setting for every new session so when you open big sessions after a session where the buffer was set really low the big session doesn't have such a difficult time opening.

Would love it so that I can read exactly which plugin is inserted on a track read out. For example I use a ton of UAD plugins and for my Neve plugins, which I have a few, all I can read is 'UAD Ne...' - I have no idea what Neve that is. And the 'Show Help Tags' is extremely annoying to have on all the time thus allowing you to put the mouse over the insert allowing it to be readable. Maybe this function could be made into a quick key command thus allowing it to be assigned to do this function instead of having it either 'on' or 'off'.

[csiaudio]

.

I think MOTU has been playing catch-up with the rest of the DAWs.

I agree they should concentrate on cleaning up ALL the bugs before implementing more features. The thing is that they have to hurry, because they are behind one cycle. IOW, if they get rid of all the bugs in the next version (say DP 6.3), they would have to immediately start thinking about new features for DP 6.5. Otherwise, they will never lead with innovation... they will keep playing catch-up.

I have to agree with that although I have found DP6 quite stable in most regards. DP is a very good DAW platform however on the downside their plugins are marginal at best (most of them are quite old and dated). Their 'Spectral' pitch change and time compression has very limited use, unlike Pro Tools Elastic which is AMAZING. DP's included VI's are also marginal IMO. But on the other hand I do have to say if DP wasn't a good package I wouldn't use it, so that does say something. I hate the plugin (RTAS) limitation of Pro Tools and many third party VST's for Pro Tools have difficulties...and I personally have had nothing but terrible stability issues with Pro Tools on two totally different systems that demonstrated the exact same issues. I would be interested in seeing if Pro Tools 8 is any better - they finally lifted the track count limitations which was plain stupid.

I don't think MOTU's software team is very creative in thinking outside of the box. I see enhancements to the software which tend to be more common sense changes but that's really about it. I realize Digidesign has much deeper pockets and thus a larger development team but the technology that they are coming out with, like the Elastic feature, are what is going to put a much greater divide between DAW software in the future. I hope MOTU can keep up.

[Shooshie]

I don't think MOTU's software team is very creative in thinking outside of the box.

Well, when you consider that in many cases MOTU created the box you're trying to escape, perhaps that's true. But it's not quite the way you meant it. There are many, many tools in DP which I consider ingenious, and while other younger DAW-makers have had time to rethink them and copy them in a different way, I still find that I prefer MOTU's ways overall.

You're worried about MOTU keeping up? MOTU has been one of the leaders of the DAW revolution since it began, and MIDI before that. There is no company in the business of making DAWs and MIDI sequencers with the longevity and creative span that MOTU has had. All others have either gone out of business, changed hands and/or were shut down, or simply are pups compared to MOTU.

Shooshie

[vbassguy]

I don't think MOTU's software team is very creative in thinking outside of the box.

I still find that I prefer MOTU's ways overall.

There is no company in the business of making DAWs and MIDI sequencers with the longevity and creative span that MOTU has had. All others have either gone out of business, changed hands and/or were shut down, or simply are pups compared to MOTU.

Shooshie

Yup! Absolutely True.....

[Tonio]

Actually I think the controller 64 editing problem is something that has happened in DP5/6 - it was ok in DP4.61 if I recall reading from another post recently.

Have to agree here.

no problem w/ CC 64 in DP4.61 - it defaults to 0
in DP6xx it defaults to 1

Would blowing up (enlarge)the bottom controller window make a difference? I have not tested much in regards to that.

[dpdan]

CC64 defaulting to "1" in the SE window of DP 6.0 and 6.01 was a problem.
I sent a screencapture movie to Dave Roberts and it got fixed in 6.02,
however, it is still broke in the graphic editing window, it should go down to zero,
not 1 as jlaudon has mentoned.

This was not an issue in DP 5xxx
Dan

[Tonio]

Good to know Dan,

hmm, fixed in SE but not ME? I would think ME would be more applicable for MIDI editing?? MIDI editing in SE is a PITA

[dpdan]

Good to know Dan,

hmm, fixed in SE but not ME? I would think ME would be more applicable for MIDI editing?? MIDI editing in SE is a PITA

SE Window is great for alot of things, but the graphic editor is good because you can change different CC's without having to constantly switch between them.

Dan

[tripit@earthlink.net]

#4. when creating or editing MIDI CC# data in the graphic editor, why are we only given like 7 or 8 CC # options to start with? I know that you can type in any MIDI CC # you want, but it's annoying to try and remember all the parameter #'s for all my different hardware. back in SVP you could type up a parameter name list for each hardware instrument you had, assign the MIDI CC # name list to the proper hardware channel, and then any time you opened up the graphic editor for a track on that hardware channel it would display the entire list, all 0-127 according to your own custom written names. (like CC#40 Filter 1, CC# 42 Filter 2 etc..). this was great for my virus rack and my nord rack.(basically offer a full MIDI CC# list in the graphic editor similar to the VI parameter lists in the seq editor, but with custom name lists per hardware channel)

My thoughts exactly. In this day and age, 8 options is not nearly enough. I don't need to see 127 cc's, but I would like to have the option to add more as needed.