Page 5 of 19

Posted: Tue Jul 15, 2008 7:07 pm
by Shooshie
toodamnhip wrote:
Shooshie wrote:Frodo, I have a question for MOTU, but don't feel compelled to ask if the circumstance doesn't feel right. One of the biggest advances they could make in the user interface would be to make it 100% Spaces Aware. If it would save windows in the spaces to which they've been assigned, and not have windows reverting back to the main space, and allow windows to actually OPEN to the last space they were assigned, then DP would instantly gain the advantage of having nearly unlimited monitor-screen space in which to work. Even with the trouble it causes -- and DP6 is worse than was DP5.13 -- I still use Spaces as a productivity enhancer. Sometimes I wonder if its worth it. I'll open a plugin from the mixing board (Space 2) and it will open in the primary space (Space 4) I'll visit my VIs in Space 3, and the Consolidated Window will inexplicably follow, leaving behind its shell in Space 4, forcing me to go back to Space 3 to get it and drag it home. I'll click on a track in the track selector of my MIDI Edit Window (full-screen in Space 1), and it will jump back to Space 4, then return to Space 1, leaving me wondering what just happened.

So, if those kinds of anomalies could be corrected, DP would be wonderful in Spaces, and one could literally leave open every single window in the app, if they wanted to. I've wondered if this might slow down the graphics card? So far it doesn't seem to. Not sure about that, though. Maybe Apple only applies CPU energies toward spaces that are currently visible. I do not know.

Anyway, that would be a nice thing to have.

Another thing would be to give us back some of those buttons we'd grown to depend on over the years: the ones in the title bar of windows, etc. There is some disconnect between the help files and what is really there, in that regard.

Also, I'm having trouble in plugin automation. It's been years since I've needed to automate a plugin, so I may be missing something, but I can't make it happen. I setup the plugin automation to include the parameters I' trying to automate. I even can draw in the automation, but the line remains dotted, never solid. And... it never works. I've tried it in Waves plugins and in Altiverb. Nothing. I'm going to ask around and read the manual and see if I'm missing something, but I fear there may be something wrong.

Honestly, I don't see your being able to ask all these questions to that poor rep, and I don't see you getting any responses other than what we typically hear on the phone: "Haven't heard of THAT before!"

Good luck, and thanks for asking for input.

Shooshie
Have you hit the automation play enable green button on the track itself? Have you checked the automation prefs in the prefs window? There is a bug in DP will sometime a bunch of parameters get put into the "all except" window of the automation prefs..make sure that too isnt happening...

Check, check, checkaroo... I'm definitely not getting automation in my AU plugins so far.

Shooshie

Posted: Tue Jul 15, 2008 7:19 pm
by toodamnhip
FMiguelez wrote:
toodamnhip wrote:If I dont make it mysellf..I know the guys at that store, but if I dont make it, please beg them for me..beg them..

One thing:

The ability to click on any effect parameter in a plug in, such as to apple control click, and have that parameter come up in the SE editor....

It is INSANE to scroll through 300 parameters looking for the gain on the 5th plug in down, 6th channel of the plug...

In pro tool,s if you apple control click any knob in a plug in, THAT exact parameter comes up for editing..this is such a no brainer..
BEg BEG BEG

THIS is one of the best ideas/suggestions I've heard so far, along with the spaces thing.

If they implemented what TDH mentioned, I could cut hours of fiddling with endless little menus.

+1000000000000000000000000000000000000000000000

And also, ALL of PCM's suggestions are just TOO awesome. I'm drooling now...
You see, this changes ones work habits big time..

because pain = UN willingness...
Pleasure= willingness...
right now, it is painful to find a parameter to edit in DP.

When it is easy to get to a parameter, one's willingness changes, and suddenly, you're willing to pencil in EQ's, compression ratios..anything...
YOU'RE WILLING TO GO DEEP!!!!!!!!!
Into ANY parameter... i.e. TOTAL CONTROL...

THIS IS NO BS!!!

I am really pissed at MOTU for not implementing this...
I've sent suggestions to the darn box!

It shows they just don't get it...

they haven;t experienced how deeply this can change one's mixing technique..they are ignorant in this regard..truly...because once one experiences this, you'd never want to live without it..really!

I' have to say that MOTU is completely lost on this on, having not experienced the joy of this ability..it's really too too bad..really!

Posted: Tue Jul 15, 2008 8:51 pm
by Lookinnn
i just thought of something i'd like to see ..

In DP you can change just about anything in the mix window that you can change in the tracks window .. EXCEPT .. Track takes ..
I'd like to see the option to hide / show a pull down menu above the mute solo section for "takes"

Once i set up tracks in the tracks window .. i only need it to verify that all tracks are recording .. and changing / adding takes !!! ..

Posted: Tue Jul 15, 2008 9:02 pm
by FMiguelez
.

To that, I would add the ability to select tracks FROM the mixer (unless, of course, this is already possible with newer DP versions...)

Posted: Tue Jul 15, 2008 9:16 pm
by Frodo
Just chiming in to say all Q's have been documented.
FMiguelez wrote:.

To that, I would add the ability to select tracks FROM the mixer (unless, of course, this is already possible with newer DP versions...)
FM- can you expound on this? DP5 has a track list from which one can choose tracks to appear in the mixer (and other edit windows). Is that what you mean? Just curious.

DP6 allegedly uses a single track selector list for all edit windows, but maybe someone with DP6 can explain the current pros and cons for you.

Posted: Tue Jul 15, 2008 9:28 pm
by blue
FMiguelez wrote:.

To that, I would add the ability to select tracks FROM the mixer (unless, of course, this is already possible with newer DP versions...)
Double click on the track's title in the mix window.

Posted: Tue Jul 15, 2008 11:10 pm
by Eleventh Hour Sound
Shooshie wrote:
toodamnhip wrote:
Shooshie wrote:Frodo, I have a question for MOTU, but don't feel compelled to ask if the circumstance doesn't feel right. One of the biggest advances they could make in the user interface would be to make it 100% Spaces Aware. If it would save windows in the spaces to which they've been assigned, and not have windows reverting back to the main space, and allow windows to actually OPEN to the last space they were assigned, then DP would instantly gain the advantage of having nearly unlimited monitor-screen space in which to work. Even with the trouble it causes -- and DP6 is worse than was DP5.13 -- I still use Spaces as a productivity enhancer. Sometimes I wonder if its worth it. I'll open a plugin from the mixing board (Space 2) and it will open in the primary space (Space 4) I'll visit my VIs in Space 3, and the Consolidated Window will inexplicably follow, leaving behind its shell in Space 4, forcing me to go back to Space 3 to get it and drag it home. I'll click on a track in the track selector of my MIDI Edit Window (full-screen in Space 1), and it will jump back to Space 4, then return to Space 1, leaving me wondering what just happened.

So, if those kinds of anomalies could be corrected, DP would be wonderful in Spaces, and one could literally leave open every single window in the app, if they wanted to. I've wondered if this might slow down the graphics card? So far it doesn't seem to. Not sure about that, though. Maybe Apple only applies CPU energies toward spaces that are currently visible. I do not know.

Anyway, that would be a nice thing to have.

Another thing would be to give us back some of those buttons we'd grown to depend on over the years: the ones in the title bar of windows, etc. There is some disconnect between the help files and what is really there, in that regard.

Also, I'm having trouble in plugin automation. It's been years since I've needed to automate a plugin, so I may be missing something, but I can't make it happen. I setup the plugin automation to include the parameters I' trying to automate. I even can draw in the automation, but the line remains dotted, never solid. And... it never works. I've tried it in Waves plugins and in Altiverb. Nothing. I'm going to ask around and read the manual and see if I'm missing something, but I fear there may be something wrong.

Honestly, I don't see your being able to ask all these questions to that poor rep, and I don't see you getting any responses other than what we typically hear on the phone: "Haven't heard of THAT before!"

Good luck, and thanks for asking for input.

Shooshie
Have you hit the automation play enable green button on the track itself? Have you checked the automation prefs in the prefs window? There is a bug in DP will sometime a bunch of parameters get put into the "all except" window of the automation prefs..make sure that too isnt happening...

Check, check, checkaroo... I'm definitely not getting automation in my AU plugins so far.

Shooshie
I was able to automate the ProVerb and IKMultimedia's CSR Reverb just now...

Interesting... In the Automation Setup there's the global stuff, then there's the track stuff, but at the bottom it says: Apply to Selected Audio Tracks, or Save as default for audio tracks. Does the last option mean it applies it to all audio tracks?



(Someday I need someone to splain to me about the differences between overwrite and touch etc) I use a control surface and when I use anything but latch, sometimes the fader fight me.

Posted: Tue Jul 15, 2008 11:12 pm
by Eleventh Hour Sound
Frodo wrote:Just chiming in to say all Q's have been documented.
I hope the cue for the Q's hasn't been closed yet, it's only Tuesday.

You know I was thinking today, it would be nice if you could meet with him over coffee or dinner before or after since those events are often focused on sales and sometimes newbies.

Posted: Tue Jul 15, 2008 11:35 pm
by Frodo
RecordingArts wrote:
Frodo wrote:Just chiming in to say all Q's have been documented.
I hope the cue for the Q's hasn't been closed yet, it's only Tuesday.

You know I was thinking today, it would be nice if you could meet with him over coffee or dinner before or after since those events are often focused on sales and sometimes newbies.
Hey, RA.

No, I'm still documenting but will probably close the polls by dinner time Thursday night.

If I could get enough of these questions answered, I'd sell 100 copies of DP *for* him on the spot, if he only knew.

Trust me-- I don't plan to just saunter down there to compete with noobs wanting to know if DP6 will help them write music. I've got a "plan"... :wink:

Posted: Wed Jul 16, 2008 12:00 am
by pcm
toodamnhip wrote:
FMiguelez wrote:
toodamnhip wrote:If I dont make it mysellf..I know the guys at that store, but if I dont make it, please beg them for me..beg them..

One thing:

The ability to click on any effect parameter in a plug in, such as to apple control click, and have that parameter come up in the SE editor....

It is INSANE to scroll through 300 parameters looking for the gain on the 5th plug in down, 6th channel of the plug...

In pro tool,s if you apple control click any knob in a plug in, THAT exact parameter comes up for editing..this is such a no brainer..
BEg BEG BEG

THIS is one of the best ideas/suggestions I've heard so far, along with the spaces thing.

If they implemented what TDH mentioned, I could cut hours of fiddling with endless little menus.

+1000000000000000000000000000000000000000000000

And also, ALL of PCM's suggestions are just TOO awesome. I'm drooling now...
You see, this changes ones work habits big time..

because pain = UN willingness...
Pleasure= willingness...
right now, it is painful to find a parameter to edit in DP.

When it is easy to get to a parameter, one's willingness changes, and suddenly, you're willing to pencil in EQ's, compression ratios..anything...
YOU'RE WILLING TO GO DEEP!!!!!!!!!
Into ANY parameter... i.e. TOTAL CONTROL...

THIS IS NO BS!!!

I am really pissed at MOTU for not implementing this...
I've sent suggestions to the darn box!

It shows they just don't get it...

they haven;t experienced how deeply this can change one's mixing technique..they are ignorant in this regard..truly...because once one experiences this, you'd never want to live without it..really!

I' have to say that MOTU is completely lost on this on, having not experienced the joy of this ability..it's really too too bad..really!
What he said.

All of the motu people who are actually versed in engineering should all be force to spend a week with a PTHD system, with an experienced PT engineer by their side. I think they would be shocked. I certainly was.

Posted: Wed Jul 16, 2008 12:16 am
by toodamnhip
Imagine this scenario...a common one...

Your working on a vocal..many takes equalling a comp.
One line has harsh highs...
In Pro TOOLS, you control/apple click the gain on a waves plug in and immediately, your penciling a bit of a gain dip in the 7k region on that line...and voila! you move on...

In DP?

You think, "hell with it"..it will mean scrolling through 300 parameters to find the damn waves gain on band 4"...so what happens?
You leave the vocal artifact unless absolutely necessary because you hate having to go dig it out of DP's morass....

This is big stuff here..

Posted: Wed Jul 16, 2008 1:42 am
by Matcher
Good questions everyone.

- Is MOTU planning to present a list of things that have been fixed in DP, with the updates?

Posted: Wed Jul 16, 2008 6:09 am
by chaim
toodamnhip wrote:Imagine this scenario...a common one...

Your working on a vocal..many takes equalling a comp.
One line has harsh highs...
In Pro TOOLS, you control/apple click the gain on a waves plug in and immediately, your penciling a bit of a gain dip in the 7k region on that line...and voila! you move on...

In DP?

You think, "hell with it"..it will mean scrolling through 300 parameters to find the damn waves gain on band 4"...so what happens?
You leave the vocal artifact unless absolutely necessary because you hate having to go dig it out of DP's morass....

This is big stuff here..
No. What you do is, you put an eq on that track let's say the MW EQ, put the track in automation write, click once on the gain/freq/Q knobs of a band on the EQ (while DP is playing) this 'writes' the automation line in that track, now head over to the SE and you'll see those lines and names in that track and at left in the regular drop down menu - under soundbites/volume/pan etc... those layers.

The PT way is faster but this is OK and not so complicated as it looks in text.

Posted: Wed Jul 16, 2008 6:32 am
by tomeaton
Can you ask them to display and make editable soundbite volume up where soundbite start and end times are displayed in the sequence editor?

A default cosine fade in the fade editor?

Multiple marker tracks?

Realtime fades?

Those are the biggies for me...

-tom

Posted: Wed Jul 16, 2008 11:47 am
by Frodo
Just a note:

A lot of the questions will be submitted as feature requests. This is because we know these features and functions are not currently available. More difficult would be those workflow questions that *do* work but might feel more cumbersome or a less frugal use of time.

I may have to limit actual questions to those pertaining to DP6 which will likely generate a response other than "not at this time" or "maybe in a future up date".

Rest assured that all questions in this thread will be documented and submitted in one way or another.
Matcher wrote:- Is MOTU planning to present a list of things that have been fixed in DP, with the updates?
This alone would answer a HOST of questions that would not otherwise need to be asked. It also speaks to the bigger issue of customer relations where info in general on known bugs and bug fixes remain a longstanding user request. One would think that publishing bug fixes would also serve to ease the traffic on their tech links, but one can only conclude that MOTU has its own reasons for not making such info known.