MacMusic.org  |  PcMusic.org  |  440Software  |  440Forums.com  |  440Tv  |  Zicos.com  |  AudioLexic.org
Loading... visitors connected
Welcome Guest
> memory allocation for vision dsp
post Thu 22 Nov 2001, 19:32
Post #1





Group:
Posts: 0
Joined: --
Member No.: 0




I'm hopping that someone can help me with this on going problem I've been having running
Vision on an iMac 350mhz.

The problem being that it's always stopping (not freezing) in mid operation ,(midi only. No
audio) and the cpu performance window pops up. I've tried setting and re-setting the
minimum and preferred sizes in the memory allocation window within the suggested ranges
all to no avail. I've got 128 megs of ram which should be more than enough,as well as all
extraneous extensions turned off.

Any suggestions to resolve this problem as well as simply improve overall performance
would be greatly appreciated.

Thanks in advance,

Gep
Go to the top of the page
 
+Quote Post
 
Start new topic
Replies (1 - 4)
kaboombahchuck
post Fri 23 Nov 2001, 11:57
Post #2


Advanced Member
*****

Group: Members
Posts: 495
Joined: 12-Oct 01
From: Chandler - US
Member No.: 2,003




Well, I wa gonna go for upping the ram, but you don't think that's it so.........


--------------------
kaboombahchuck
-------------------------------------------------------------------------------
Go to the top of the page
 
+Quote Post
abbie
post Mon 26 Nov 2001, 18:30
Post #3


Member
**

Group: Members
Posts: 74
Joined: 01-Mar 01
From: Orleans - CA
Member No.: 322




I am running Vision on a lesser configuration with no problems except Vision sometimes crashes when I use the note display feature for midi. There have been issues related to OS 9 with Vision that you might find info on in these forums. Doubt if this will help but I once had the same CPU-type problem as you when I installed an extension that allowed sound manager output to be captured to a disk file. I got this extension from this web site. Even with the extension turned off, I still had the CPU problem until I deleted the extension completely off my computer. I also had a similar situation once when I had a corrupt plug-in in my plug-in folder (even though I wasn't using any plug-ins).


--------------------
Abbie
Go to the top of the page
 
+Quote Post
post Wed 28 Nov 2001, 15:00
Post #4





Group:
Posts: 0
Joined: --
Member No.: 0




kaboombahchuck,

Thanks for your prompt reply.

Opcode say that my problem is not a lack of ram but rather of memory allocation to vision that is at issue.

Regardless, I'm going to bump up my ram from 128 mb to 512 mb and see what happens.

Abbie,

Thanks for the feedback though I must say I get a headache just thinking of going back into my extensions manager. Though I think your right about conflicts with extensions, I find it utterly confusing trying to sort it all out.
Go to the top of the page
 
+Quote Post
abbie
post Thu 29 Nov 2001, 13:00
Post #5


Member
**

Group: Members
Posts: 74
Joined: 01-Mar 01
From: Orleans - CA
Member No.: 322




Dear Gep, I wan`t really suggesting that you sort through all of your extensions (I agree - yuk). This sound manager extension that I mentioned is something that you would have had to conciously install, otherwise, it won`t be there. I hope that assigning more memory solves your problem. I was using an iMac 333 with 96M and gave 40M to Vision and never had problems with CPU until I started going crazy with EQ`s and plug-ins. Any how I hope the memory solution works for you.


--------------------
Abbie
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:

 

Lo-Fi Version - Fri 13 Dec 2024, 23:21
- © MacMusic 1997-2008