MOTUnation.com

I hope they add the "Studio Magic" knob featured in the boyband episode of the simpsons. That baby would save me tons of time!

wish list item: I have consolidated windows setup to display current track mixer channel on the left side of all my windows (SE, Trackst...etc...)... problem happens when I switch to mixer view as my main window (to change mixer settings on a few tracks at the same time) and I go back to SE or Tracks, my consolidated window setup is cancelled... and I have to callup my screen set again with the mixer channel on the left side... would be nice if DP recognizes what I am doing and re-enables my consolidated window with the channel on the left side...

anyone else has mixer channel for current track in a consoldiate windows setup and has the same problem? not a biggie but a wish...

r.

Originally posted by Sylver:
Ok, that brings up another question. I just read up on DCPUM and now I want to know why you would want to disable it?

There's no good reason to want to disable it. It just saves you CPU cycles when the plugin would be processing silence - in other words, there's no audible change. I think people who complain about it don't understand what it is.

Has anybody wished for hardware inserts? That would certainly be a great option in the mixing board. Then again that would be more for 4.7

<small>[ July 09, 2005, 07:44 PM: Message edited by: carnac ]</small>

Originally posted by Paradox:

Originally posted by Sylver:
Ok, that brings up another question. I just read up on DCPUM and now I want to know why you would want to disable it?

There's no good reason to want to disable it. It just saves you CPU cycles when the plugin would be processing silence - in other words, there's no audible change. I think people who complain about it don't understand what it is.

Well in my world it's a problem with huge audible changes.....

The problem for me with DCPUM is as follows,
on any track that is using card based plugins (UAD or TC);
DCPUM basically turns off all resources for a track until it sees recorded audio on it. If for instance you have a BKG vox track that was only recorded for 8 bars in a chorus the track will automatically be off until the wiper reaches it and then turn on to play it back thus preserving CPU resources.
With certain plugins this is a problem as the roundtrip time in processing is greater than the DCPUM lookahead. The result is that the first bit of the audio becomes "clipped" in playback.
Another issue is the decay times on inserted verbs in tracks. When the audio file ends the tail off on the verb gets muted as DCPUM sees the track as finished once the file ends and kills resources to the track thus killing the verb or delay or whatever.

woozers! those are really big DCPUM negatives... have they been addressed in 4.6? do they only affect you if you are using external proccessing cards like UAD or also native plugs?

thanks for the explanation of the problems with DCPUM...

r.

Ouch! It this a common problem? You would think that you would be able to at least adjust it.

Does it occur just on playback, or does it happen when you print and bounce too?

How do you get around it? I suppose you have to fill any gaps until you print the track, and then edit the noise out of the printed audio.

I imagine that could be a bit of a pain.

wishlist/Bug: not sure if this is a bug or wishlist item, but it's real workflow pain that has been around since DP2.72 I think...

when you hover over a soundbite in either SE or TO windows, the cursor turns into a finger - all good... here comes the bug... you can never tell what size of soundbite will make the cursor turn into a finger, or the cursors for the edge edit, or the timestrech (depending on vertical zoom).. it's a great pain - especially with DP's slowness to have to keep zooming in just to move a soundbite. from high unzoom values, the only thing you could really be doing is arranging, not editing... why would you need to edge edit or better, how could you edge edit a soundbite at a really high unzoom setting? or better time stretch it...

after a certain Zoom setting I think you should only be able to move a soundbite, and the edge edit/stretch function should only be avaialble when you are zoomed in closer... anyone else been fighting with this annoyance?

r.

--fix smooth audio edits. This would save a lot of time, if they'd fix what they claim it will do. Or at least don't make claims that DP will do something it can't do yet.

-fix smooth audio edits. This would save a lot of time, if they'd fix what they claim it will do. Or at least don't make claims that DP will do something it can't do yet

Just wondering, but what's the problem with it?
I've been able to use it for basic things.

For example, when I've edited multi-track drums and then quantize, there will be some spaces between many of the soundbites. So, I'll select the soundbites and choose smooth audio edits...edge edit only... and only some of the soundbites will actually have the gaps filled in. It seems improved with the one small test I performed but not completely functioning, yet.

Originally posted by salvadorpauli:
--fix smooth audio edits. This would save a lot of time, if they'd fix what they claim it will do. Or at least don't make claims that DP will do something it can't do yet.

According to the 4.6 update notes, they improved this. I haven't tested it though.

Another issue is the decay times on inserted verbs in tracks. When the audio file ends the tail off on the verb gets muted as DCPUM sees the track as finished once the file ends and kills resources to the track thus killing the verb or delay or whatever.

Doesn't happen with Altiverb though. I haven't had any problems with DCPUM.

<small>[ July 11, 2005, 06:48 AM: Message edited by: hammerman ]</small>

This was mentioned a few months back, but I didn't see it in this thread, so...

Control Panel (Play buttons, etc) as an option for one of the panes in the Consolidated Window. I love CW, but I hate giving up screen space just so I can keep the transport controls visible.

I would like to see the option to only have ONE plugin window open at a time. This is how DP used to be, and for a while in v. 3.x, you had to option to choose either. Starting with v. 4.x, the option is gone, and ALL plugin windows stay open until you close them. This is an issue because of graphics redraw. OSX is way better about this that OS9 of course, where multiple open plugin windows could (and would) bring the system to a crawl. It seems an unnecessary wate of cpu resourses to have all these windows stay open. Worth noting, in Pro Tools, only one plugin window stays open. At least, give us a choice.