DP6 : Hobbit Meets With MOTU

Phil O · Post by **Phil O** » Mon Jul 21, 2008 8:18 pm

grimepoch wrote:I could understand if I was playing back something at this high zoom, but I was not. I was just trying to edit the end point of a region, or shift something over and it was SOO SLOW!!!! This is on a MacPro 4x2.66Ghz and 7 Gig of RAM.

They really need to address this in the future as doing REALLY fine edits is painfully SLOW.

Hmm. I'm not seeing this at all. I'm on a MacPro too. Don't know what could be different.

Phil

dbl · Post by **dbl** » Mon Jul 21, 2008 8:25 pm

Phil O wrote:
grimepoch wrote:I could understand if I was playing back something at this high zoom, but I was not. I was just trying to edit the end point of a region, or shift something over and it was SOO SLOW!!!! This is on a MacPro 4x2.66Ghz and 7 Gig of RAM.

They really need to address this in the future as doing REALLY fine edits is painfully SLOW.
Hmm. I'm not seeing this at all. I'm on a MacPro too. Don't know what could be different.

Phil

FWIW, grimepoch appears to be running the (usually) dreaded OS X 10.5.2.

Phil O · Post by **Phil O** » Mon Jul 21, 2008 8:36 pm

Dreaded OS X 10.5.2? What problems do you know of? I've had great luck with 10.5.4. So much so that I'll be hesitant to update to 10.5.5 if it comes out.

Phil

dbl · Post by **dbl** » Mon Jul 21, 2008 8:49 pm

Disclosure: I don't run Leopard (nor have I worked with DP since 4.61 was relatively current).

But I do trouble shoot for a limited circle, most of whom are running 10.5 on Intel boxen. The shakedown criuise lasted till 10.5.3, at which point everyone got pretty much happy.

Ergo, I thought it useful to highlight as a data point the different versions you and grimepoch were using. Not saying either is a cuplrit, but rather possible grounds for further discussion or research.

Eleventh Hour Sound · Post by **Eleventh Hour Sound** » Mon Jul 21, 2008 8:53 pm

Frodo wrote:
RecordingArts wrote: So there's a DP5 uninstall? Hmmm
Yep. Put in your DP5 installer disc and go through all the steps as though you were going to do an install. But, once you see the EASY INSTALL sticky menu appear in the upper middle of that window, click there and choose UNINSTALL.

Cool. I'll be sure to save the Mas.AudioUnit deal first

grimepoch · Post by **grimepoch** » Tue Jul 22, 2008 12:31 am

I'm actually running 10.5.4 but haven't updated my sig yet

Timeline · Post by **Timeline** » Tue Jul 22, 2008 12:50 am

What a list wow! Love the alt pan idea to. Too tired to ask questions. Later...

chaim · Post by **chaim** » Tue Jul 22, 2008 7:07 am

18. cosine fader algorithm

fascinating suggestion-- was taken to heart with deep interest

Can some one explain please what this means?

Thanks.

willheim · Post by **willheim** » Tue Jul 22, 2008 7:49 am

reat to read all this stuff, but gads it wears me out. One thing I will comment on - Grimepoch, I have had the same problems with audio as you -

I have learned (like a wounded dog workaround) in previous versions to keep the soundbite window closed when running my sequence and only opening it when i edit - i am not suggesting o do this i know it is a royal pain in the ass.

and i have had the same slow downs and crashes - this used to be better for me in previous versions 4.13 and maybe earlier and on earlier macs - i would hammer away without these crashes

i have had that digital distortion as well, it is always when I paste an identical soundbite around - drives me nuts - never used to do that. it is usually when it is the same soundbite being pasted around, and i noticed you were doing the same thing.

makes me seriously consider a different audio system - but the deil you know...

gearboy · Post by **gearboy** » Tue Jul 22, 2008 8:59 am

Frodo, thanks so much for taking the time to do all of this!

Jeff

Shooshie · Post by **Shooshie** » Tue Jul 22, 2008 9:03 am

I, too, would like to know about cosine fader automation. Google searches have provided me with much interesting material about Fast Fourier Transforms, but not about fader automation.

Shooshie

Frodo · Post by **Frodo** » Tue Jul 22, 2008 12:48 pm

chaim wrote:
18. cosine fader algorithm

fascinating suggestion-- was taken to heart with deep interest

Can some one explain please what this means?

Thanks.

Shooshie wrote:I, too, would like to know about cosine fader automation. Google searches have provided me with much interesting material about Fast Fourier Transforms, but not about fader automation.

The suggestion came from tomeaton:

tomeaton wrote:A default cosine fade in the fade editor?

There are very flexible features where creating fades are concerned, and there is even a feature to "create new fades". But there's no way to save specific user curves as defaults even though they can be edited. Given that a proper "cosine" is just a sine that has been displaced by 25%, more specifics on the practical use of the cosine in particular will have to come from Tomeaton.

However, being able to save user defaults as "corresponding-sine" fade curves made a lot of sense to me. As it stands, the edited fade curve remains until a DP default curve is chosen and edited, but can't be saved. This would spare the user from a bit of clicking where the edited curve and its corresponding default are both available at a glance.

Again, Tom might have more insights to offer which speak to his own intentions for this feature.

toodamnhip · Post by **toodamnhip** » Tue Jul 22, 2008 5:49 pm

kinnylandrum wrote:I might add that I called MOTU this morning about my problem with the one file that played MIDI notes that weren't there. Ronan suggested I try loading the 5.13 chunk rather than opening it in 6. I thought I'd open the file first and see if it still exhibited the same problem, and by damn the problem has gone away! It plays back fine, no matter how much I stop it and rewind. I can't explain it, but it works fine even with "always play in real-time" on or off. So I didn't even try loading, maybe everything's OK. Oh well, I swear it really did happen, but I just thought I'd report.

That means by loading DP 6, you got a fresh architecture-d file and that something about DP 5 files screws up the file framework of DP 6 files..

toodamnhip · Post by **toodamnhip** » Tue Jul 22, 2008 5:52 pm

dannygold wrote:
toodamnhip wrote:
It used to be that you could adjust the "Q", see and hear the result..now, you can't. You have to guess/adjust and when you let go, the Q jumps and then adjusts...it doesnt work well in realtime..and it is really hard to grab the side width of the EQ graphic t manually adjust Q...
Sounds like maybe a prebuffering issue... try choosing "always run in realtime" in the plugin mini menu.

Thanks..nice advice..I hadn't thought of that!!
I already make waves run in realtime for freezing issues..I guess now DP EQ's may need it too..

So all of this pre buffering in DP is looking like a bit of a mess isn't it?
If one has to check that option on tons of plugs to make DP work correcty, it becomes a time eater instead of an efficiency helper..

zed · Post by **zed** » Tue Jul 22, 2008 6:49 pm

toodamnhip wrote:So all of this pre buffering in DP is looking like a bit of a mess isn't it?
If one has to check that option on tons of plugs to make DP work correcty, it becomes a time eater instead of an efficiency helper..

Yeah, but hopefully 6.01 will resolve some of these issues. And hopefully MOTU will include an option to automatically force all plugins and VIs to run in realtime, in effect disabling the pre-rendering function, allowing you to disable the "run in realtime" as you see fit. For the time being, perhaps they should just make "run in realtime" the default, until changed by the user on a plug-in to plug-in basis.