MOTUnation.com

Frodo wrote:
Du nimmst mir den verstand, aber ich brauche die beide meines am zu klavier zu spielen.

Unter anderem

Tim wrote:

Frodo wrote:
Du nimmst mir den verstand, aber ich brauche die beide meines am zu klavier zu spielen.

Unter anderem

pervertito!

MIDI Life Crisis wrote:[pervertito!

Now now, Magilla; remember - where the mind goes, the man (or ape) follows.

Oh, that's right; you're already there.

Okay--

Other important questions:

Is anyone getting a crash or a spinnng beachball when:

1. Opening a second or third (etc) project without first quitting DP?

2. When switching from one sequence to another within the same project?

3. When activating or deactivating V-Racks?

Is anyone getting a crash or a spinnng beachball when:

1. Opening a second or third (etc) project without first quitting DP?
No.

2. When switching from one sequence to another within the same project?
No

3. When activating or deactivating V-Racks?
Don't use it.

Phil

Frodo wrote:Okay--

Other important questions:

Is anyone getting a crash or a spinnng beachball when:

1. Opening a second or third (etc) project without first quitting DP?

2. When switching from one sequence to another within the same project?

3. When activating or deactivating V-Racks?

1- No
2- No
3- Sometimes

1. No.
2. No.
3. Don't use V-Racks.

Kind regards.

Phil O wrote:
No.
No.
Don't use it.

MidiLifeCrisis wrote: 1- No
2- No
3- Sometimes

Thanks, guys. I really appreciate it.

I've gotten a "sometimes" for V-Racks from quite a few others off the forum, so this really helps distinguish between those memory management issues that are the result of faulty hardware vs those issues which are still in some way caused by the way DP might be handling memory.

I'm also starting to parse issues which are unique to the G5 and MacPro along with those issues that are symptomatic of DP on both platforms.

There have been debates about whether DP really does release resources under certain circumstances. Part of this may be a remnant of the old DP crash-on-quit issue. Some of it may be due to the way OSX and UNIX hang onto old file references well after they're needed.

PPC or Intel, for some of these issues it seems that quitting DP, logging out and back in again, or even restarting the computer are the only ways to really clear things out.

I'm not sure what to do about V-Racks since that has to be instantiated with DP running. V-Racks acts up occasionally on all my computers regardless of CPU type.

Looks like I picked the wrong day to quit drinking!

I quit using vracks in my last project as I couldn't find a simple way to freeze them. I'm struggling a bit with a DVD a producer gave me that will not mount on my G5, but will mount on the Mini and DVD players. ARRRRGH!

Glad you're hanging in there Froders...

Frodo wrote:Looks like I picked the wrong day to quit drinking!

Let me know when you've figured out the right day.

MIDI Life Crisis wrote:I quit using vracks in my last project as I couldn't find a simple way to freeze them. I'm struggling a bit with a DVD a producer gave me that will not mount on my G5, but will mount on the Mini and DVD players. ARRRRGH!

Glad you're hanging in there Froders...

Thanks, MLC.

I'm trying my uttmost best not to let this get the best of me. I just want to be prepared when my MacPro comes back with a new logic board or if I get a new computer-- and some of these issues are still happening.

What I'm afraid of (where all three questions deal with similar problems) is that my MacPro may just be less toleratant of bad code in the same way OS9 was not as particular about certain types of RAM that were installed until OSX came along. I recall Mac Universe (in Encino) put some odd RAM in my Lombard bronze-keyboard G3 PB which Apple didn't recommend. It was really fine until I went to OSX and the additional RAM was no longer recognized.

I know that I'm pulling at straws here, but it's not to avoid buying a new computer or having my MacPro fixed. I just cringe at the notion that DP will continue to misbehave no matter how much time and money I throw at it, even if that means throwing money at a new computer.

I just wish I could be more certain about what problems are *truly* hardware related where so many glitches have so much in common on different computers. I mean, I'm willing to do what's necessary-- but until MOTU fixes more of DP's weaknesses there's no way to be sure that anything I do will be truly necessary.

Okay, so I braved a couple of minor experiments this evening.

I loaded up a project in DP, then quit. I checked the Activity Monitor and found 1.8 GB still wired with no other applications running.

So, I rebooted the computer and checked AM again with no apps running and it shows 660MB wired.

Wuzzup widdat crizzle?

I'm now wondering if DP should be giving a cue to OSX to let go, or should OSX simply let go once an appliction has been quit...

I thought I had heard somewhere that once you open an app, some of its allocated RAM remains engaged by the OS after you quit. I have noticed that apps that have been quit will open faster the next time around if you dont reboot, which seems to bear that theory out. Still, 1.8 GB seems like a lot.

blue wrote:I thought I had heard somewhere that once you open an app, some of its allocated RAM remains engaged by the OS after you quit. I have noticed that apps that have been quit will open faster the next time around if you dont reboot, which seems to bear that theory out. Still, 1.8 GB seems like a lot.

Yeah--- for example, once you start VSL and it goes through the "delay" of authorizing itself, the "VSL daemon" keeps running and it skips the slow authorization the next time you open it as long as you don't shut down.

But as I understad it, VSL was specifically designed this way later on. It didn't always do this-- and the amount of gunk that stays wired on my G5 is way less than 1.8GB. Hmm.

blue wrote:

Frodo wrote: Looks like I picked the wrong day to quit drinking!

Let me know when you've figured out the right day.

I most certainly will, blue! LOL!

But I may have to crack open a bottle of champers first!

OK, I found where I had read about the memory thing. It was a post from Magic Dave, no less. Here's what he says:

• The way the Mac OS works is that virtual memory is always on. A great deal of what the computer does gets stored in RAM memory. If you launch an app then quit it, portions of that app are kept in RAM. This means the next time you launch the app, it will launch much faster.
  For a Powerbook user like me, this is a big deal because I rarely restart my computer. That means over time, RAM useage becomes less and less efficient. There may be utilities that clear out or optimize RAM. I haven't checked. I do know that a restart refreshes the RAM.

And here's the thread:

http://www.motunation.com/forum/viewtop ... ram#142562