MOTUnation.com

toodamnhip wrote:I have your darn pattern for you dude...

EVERYdamn upgrade seems to have to go through unstablity..it is just the nature of the beast I suppose...being along the lines that DP users have always been MOTU's guinniea pigs/beta testers....

True, true.


Shooshie

Shooshie wrote:

toodamnhip wrote:I have your darn pattern for you dude...

EVERYdamn upgrade seems to have to go through unstablity..it is just the nature of the beast I suppose...being along the lines that DP users have always been MOTU's guinniea pigs/beta testers....

True, true.


Shooshie

So sure that I sit here in my studio with the DP 5 disks on my desk...wondering whether to oad them or not...have you found it workable to just load DP5 without trashing earlier DP versions? I wonder how clean this is. I bet. like me and others, you still have 4.62 in your computer....
Do you know what MOTU says about this? I seem to recall them saying it is fine to have older verions in the comp and that they should work.. but have you talked to anyone or considered the possibility that this multiple version in same computer operating basis makes for instablity? In the core areas of dp code, I wonder if there are 2-3 sets of deeper motu files that lead to instablity?

I always erase my old versions after installing the new upgrade. Usually, I wait until I know it's going to work. This time, I just optimistically erased DP 4.61 before installing DP5. I haven't regretted that, though it would be nice to compare CPU headroom in the two on identical files. I probably have a backup copy on DVD, but that's not important enough to me to go looking for it and copy it back over. I actually did an "un-install" of DP before I installed DP5, just to be sure that everything was compatible and fresh.

I think DP5 is a little like DP4.0. I'm guessing that it's got some major changes under the hood, and that this is our public beta. version 5.1.1 ought to be the one that makes us finally sigh in relief and say "ahh... this is why I use DP." Well, at least, I hope. I know I sure don't like this sudden quitting stuff. Even though I save often now (and I had gotten lax about that, lulled by the stability of DP 4.xx), it's still a hassle, takes time, and you always lose something. But I've seen it many times before. It's always brief, always gets fixed in another round or two. And this is very intermittent. Very rare. It's nothing at all like version 4.0 which crashed when you clicked on lists, and things like that.

Shooshie

Shooshie wrote:I always erase my old versions after installing the new upgrade. Usually, I wait until I know it's going to work. This time, I just optimistically erased DP 4.61 before installing DP5. I haven't regretted that, though it would be nice to compare CPU headroom in the two on identical files. I probably have a backup copy on DVD, but that's not important enough to me to go looking for it and copy it back over. I actually did an "un-install" of DP before I installed DP5, just to be sure that everything was compatible and fresh.

I think DP5 is a little like DP4.0. I'm guessing that it's got some major changes under the hood, and that this is our public beta. version 5.1.1 ought to be the one that makes us finally sigh in relief and say "ahh... this is why I use DP." Well, at least, I hope. I know I sure don't like this sudden quitting stuff. Even though I save often now (and I had gotten lax about that, lulled by the stability of DP 4.xx), it's still a hassle, takes time, and you always lose something. But I've seen it many times before. It's always brief, always gets fixed in another round or two. And this is very intermittent. Very rare. It's nothing at all like version 4.0 which crashed when you clicked on lists, and things like that.

Shooshie

I gotcha..

I always save all the time and think that I save so much, it is why I always have to re-build larger DP files after version 32 or so...they end up corrupting. Ever had that happened?

I wonder about the thoroughness of DP's un install....

I recall a more thorough way from a tech support email ..
here it is:hope it helps if help is what you even need..lol

Hello,

Follow these instructions to perform a clean install:

1. Go into the "users / (your username) / library / preferences" and
move the "Digital Performer" folder to the trash.

2. Press Command-F to open the finder's find function.

3. Add a Criteria - Visibility. Set Visibility to all (visible and
invisible items).

4. Search everywhere.

5. Select the drive that DP is installed on and type "AUTH" in the
search
field. You should find a file named "AUTH-Digital Performer 4.0". Move
it
to the trash from the File menu, then empty the trash.

6. Insert the DP4 CD into the computer and launch the installer. Select
"Uninstall" from the install dialog and complete the operation.

7. Once uninstall is complete, restart the computer.

8. Go into the "Applications / Utilities" and open Disk Utility.

9. Select your system drive from the list on the left. click on
the First Aid tab.

10. Once inside the First Aid tab, click on Repair Disk Permissions.
This may take a few minutes.

11. Once complete, install DP4 from the CD.

12. Once install is complete, launch DP with the CD in the drive, then
enter a name at least 3 characters in length and the keycode.

13. Once DP has loaded successfully, you may quit it and install any
necessary updates. The "DP4.12 Update Install" as well as "DP 4.12 MAS
and AU support bundle Update."

Peter
MOTU Tech

Dave, thanks for posting Peter's guide to un-installing. I didn't know about the "Auth" file. That's good info to have. I wonder if that file could become corrupted and cause the crash-on-startup that some people have had? Actually, only one person at the moment that I can think of.

Shooshie

Shooshie wrote:Dave, thanks for posting Peter's guide to un-installing. I didn't know about the "Auth" file. That's good info to have. I wonder if that file could become corrupted and cause the crash-on-startup that some people have had? Actually, only one person at the moment that I can think of.

Shooshie

well dude..you're the man so spread the wrod and keep up the good work....

Do me a favor, bitch at motu with me to get them to put un-dos and trims in their effects......lol...

I was mastering the other day in Ozone and man was it obvious how crippled I am without undo's..it's really retarded to not be able to touch a plug in freely and undo's give one that ability..it's alomost the difference between usable and UN usable....
Dave

A DIY undo work around for plugs you could use (maybe already do use) is to copy the plug into an adjacent track insert (via a project clipping) and then mute the original. Then after tweaking the new one you can even A/B using mute/unmute and always go back to your starting point (the original plug)....then just keep the one you like best.

Having two plugs open (one muted) per track or at least an adjacent insert free to put one is perhaps not the most ideal method and only offers one limited kind of undo but it does the job.

Personally I would like to see an A/B workspace in the major DP plugs (ie MW EQ) as much as an undo feature.

Spikey Horse wrote:A DIY undo work around for plugs you could use (maybe already do use) is to copy the plug into an adjacent track insert (via a project clipping) and then mute the original. Then after tweaking the new one you can even A/B using mute/unmute and always go back to your starting point (the original plug)....then just keep the one you like best.

Having two plugs open (one muted) per track or at least an adjacent insert free to put one is perhaps not the most ideal method and only offers one limited kind of undo but it does the job.

Personally I would like to see an A/B workspace in the major DP plugs (ie MW EQ) as much as an undo feature.

I could give you ten more work arounds..lol..

all a pain in the butt due to retarded oversight and all too slow when one is a pro, focused on his art and not wishing to be bothered with such stupidity...

I never throw away older versions of DP. I installed DP5 and it works great!

As far as wanting an undo for plugins,

make your changes,
"SAVE" then listen,
if you dont like it "command X".

Simple

Dan

I never did understand the point of having an uninstaller if you still have to manually uninstall items like preferences and authorization files. What else is left, besides the application and the MAS folders in the Library folders?

blue wrote:I never did understand the point of having an uninstaller if you still have to manually uninstall items like preferences and authorization files. What else is left, besides the application and the MAS folders in the Library folders?

That's why some logical thinking folks have designed AppZapper! I haven't tried it yet because I only just found out about it a couple of days ago. Reading this thread, though, gives me good reason to take AppZapper for a ride. Maybe it doesn't get rid of everything but it probably helps save time.

bone.china wrote:

blue wrote:I never did understand the point of having an uninstaller if you still have to manually uninstall items like preferences and authorization files. What else is left, besides the application and the MAS folders in the Library folders?

That's why some logical thinking folks have designed AppZapper! I haven't tried it yet because I only just found out about it a couple of days ago. Reading this thread, though, gives me good reason to take AppZapper for a ride. Maybe it doesn't get rid of everything but it probably helps save time.

App Zapper doesn't (yet) work on everything.
X-11 Apps being an example.
I have tried it on rather large apps and it appears to clean out
most, (if not all) of the application and its' associated files.

Can somebody tell me how to turn on and off this rendering function? I have been looking for it since Friday when I recieved 5.0.

In the pulldown menu in your plug in window, just select always realtime. and the pre rendering will be off. (For that plugin...)

Personally I think it's a great feature. I am fiddling with DP5 on my ibook G4 till I get to the studio and install it on my G5.

I am sure it will make my mixing much more efficient and give me a reason to not upgrade for a while.

Using Waves SSL on my 2.0, soon as I hit 18 plugins, my G5 starts crying, the pre-rendering, I believe, should make that a dead issue, ass I dont keep 50 plugin windows open at once anyway. Maybe 5 at a time. as I am working on diff sections of a track.

So far on my Ibook, with 1 250GB Firewires and 1 250GB USB 2.0 Drive attached, no worries.

Does somebody use an Alesis Multimix FireWire with the new DP 5 ?

I have a G5 (2GHZ + 1.5 GO) with Tiger, no extra plug in and I have big problems with the 4.6.1 : any sound signal through the Alesis ends up becoming crackles.
It is fine with GarageBand, Cubase LE and Logic Pro 6.
So I suppose it's a problem with DP.
Thanks••¦