Apple Logic Pro /LogicExpress Discussion

hey there. i am having an issue with system overload, system too slow.

is it that i need to assign more memory to logic pro? don't know how and am frustrated. the 
system crashes when it hits only 8 or 9 tracks. i use a 24 bit firepod and have a 23" screen. 
not sure WHAT is affecting it.

i have 1GB DDR SDRAM memory and am BARELY using any elsewhere. I use a PC PowerPC G4. 
What to do!?!?!?!? HELP!!!!

AFAIK, in Os X you can not assign memory as you did in System 9. Its all 
automatic. However, you need to have enough ram. 1 gb is pretty small actually (at 
least today). I would max out ram and consider an upgrade to any of the dual 
core machines - even the mini if necessary if not the pro.

> 
> hey there. i am having an issue with system overload, system too slow.
> 
> is it that i need to assign more memory to logic pro? don't know how and am 
> frustrated. the
> system crashes when it hits only 8 or 9 tracks. i use a 24 bit firepod and 
> have a 23" screen.
> not sure WHAT is affecting it.
> 
> i have 1GB DDR SDRAM memory and am BARELY using any elsewhere. I use a PC 
> PowerPC G4.
> What to do!?!?!?!? HELP!!!!
> 
> 
> 



[Non-text portions of this message have been removed]

Yes, this reminds me of my Logic days with a dual G4 867MHz system
with less and a gig of memory. Either put in more memory and use
freeze a lot, or get a used G5 system, seen 2x2.0GHz systems for just
over $1k, or then get a Mac Pro (or Mac Book Pro as the MPB is
suddenly a very valid studio system if you use FW hard drives in the
studio). --Kent

On 1/2/07, GAmoore@... <GAmoore@...> wrote:
>
>
>
>
>
>
> AFAIK, in Os X you can not assign memory as you did in System 9. Its all
>  automatic. However, you need to have enough ram. 1 gb is pretty small
> actually (at
>  least today). I would max out ram and consider an upgrade to any of the
> dual
>  core machines - even the mini if necessary if not the pro.
>
>  >
>  > hey there. i am having an issue with system overload, system too slow.
>  >
>  > is it that i need to assign more memory to logic pro? don't know how and
> am
>  > frustrated. the
>  > system crashes when it hits only 8 or 9 tracks. i use a 24 bit firepod
> and
>  > have a 23" screen.
>  > not sure WHAT is affecting it.
>  >
>  > i have 1GB DDR SDRAM memory and am BARELY using any elsewhere. I use a PC
>  > PowerPC G4.
>  > What to do!?!?!?!? HELP!!!!
>  >
>  >
>  >
>
>  [Non-text portions of this message have been removed]
>
>

Turn off or disable all background tasks that are running such as dashboard it is a system hog.
Are you using a separate disk drive for your audio applications and if so what kind is it?
The speed of your audio drive makes a big difference.
sincerely

Howard

----- Original Message ----- 
From: 
To: Logic_Cafe@yahoogroups.com
Sent: 1/2/2007 9:48:35 PM 
Subject: Re: [Logic_Cafe] assigning memory


AFAIK, in Os X you can not assign memory as you did in System 9. Its all 
automatic. However, you need to have enough ram. 1 gb is pretty small actually (at 
least today). I would max out ram and consider an upgrade to any of the dual 
core machines - even the mini if necessary if not the pro.

> 
> hey there. i am having an issue with system overload, system too slow.
> 
> is it that i need to assign more memory to logic pro? don't know how and am 
> frustrated. the
> system crashes when it hits only 8 or 9 tracks. i use a 24 bit firepod and 
> have a 23" screen.
> not sure WHAT is affecting it.
> 
> i have 1GB DDR SDRAM memory and am BARELY using any elsewhere. I use a PC 
> PowerPC G4.
> What to do!?!?!?!? HELP!!!!
> 
> 
> 

[Non-text portions of this message have been removed]


 

[Non-text portions of this message have been removed]

How do you get rid of dashboard? It seems to run in the background no matter 
what.

> Turn off or disable all background tasks that are running such as dashboard 
> it is a system hog.
> 



[Non-text portions of this message have been removed]

http://www.macosxhints.com/article.php?story=20050723123302403

Note, however, that all Dashboard does is staying resident in memory,
it's not running, it's just taking a chunk of virtual memory, causing
more VM traffic to happen. Some thinks it's OK to disable it for this
reason, others don't bother doing it, as the pages are paged out and
if you don't switch over to Dashboard they are not loaded, hence
nothing should really happen. Unless there are Dashboard widgets that
of some reason likes to operate in the background, of course.

I have a very vanilla Dashboard setup on this Mac Pro I'm using, and
looking with top it does not even show up with the top 30 processes
running, so I doubt this is either an issue.

--Kent

On 1/4/07, GAmoore@... <GAmoore@...> wrote:
>
>
>
>
>
>
> How do you get rid of dashboard? It seems to run in the background no matter
>  what.
>
>  > Turn off or disable all background tasks that are running such as
> dashboard
>  > it is a system hog.
>  >
>
>  [Non-text portions of this message have been removed]
>
>

Thanks Kent. 

Here is the hint, although some people disagree with the need to do it :

To turn Dashboard off:
 defaults write com.apple.dashboard mcx-disabled -boolean YES 
To turn Dashboard on:
 defaults write com.apple.dashboard mcx-disabled -boolean NO 
You have to restart the Dock after making either change for it to take 
effect:
 killall Dock 
[robg adds: I'm thinking this might be a pretty popular hint :). I tested the 
commands, and they definitely work. When I ran ps ax | grep Dash with 
Dashboard active, my three open widgets showed up in the process list. After changing 
the defaults, F12 no longer worked, and the same ps command didn't find any 
matches for Dashboard (OK, technically, if found the grep, but that's because 
I'm too lazy to add it as an ignored match). When I re-enabled Dashboard, I was 
somewhat surprised to find that my three open widgets were indeed still 
open.]


[Non-text portions of this message have been removed]

On Jan 4, 2007, at 12:15 PM, GAmoore@... wrote:

> Thanks Kent.
>
> Here is the hint, although some people disagree with the need to do  
> it :
>
> To turn Dashboard off:
>  defaults write com.apple.dashboard mcx-disabled -boolean YES
> To turn Dashboard on:
>  defaults write com.apple.dashboard mcx-disabled -boolean NO
> You have to restart the Dock after making either change for it to take
> effect:
>  killall Dock



Haha now I can use my F12 key in World of Warcraft again!!
Oh wait Logic yeah... None of that time wasting game stuff hehe..
:D
---
Chris
www.monotrematamusic.com
www.descentrecords.com

I'm a little confused:  does it look like that consensus is that dashboard can cause a problem if you're running a lot of programs or not?  If it is, I think I'll disable mine, too, since I never use it

  ----- Original Message ----- 
  From: GAmoore@... 
  To: Logic_Cafe@yahoogroups.com 
  Sent: Thursday, January 04, 2007 12:15 PM
  Subject: Re: [Logic_Cafe] assigning memory


  Thanks Kent. 

  Here is the hint, although some people disagree with the need to do it :

  To turn Dashboard off:
  defaults write com.apple.dashboard mcx-disabled -boolean YES 
  To turn Dashboard on:
  defaults write com.apple.dashboard mcx-disabled -boolean NO 
  You have to restart the Dock after making either change for it to take 
  effect:
  killall Dock 
  [robg adds: I'm thinking this might be a pretty popular hint :). I tested the 
  commands, and they definitely work. When I ran ps ax | grep Dash with 
  Dashboard active, my three open widgets showed up in the process list. After changing 
  the defaults, F12 no longer worked, and the same ps command didn't find any 
  matches for Dashboard (OK, technically, if found the grep, but that's because 
  I'm too lazy to add it as an ignored match). When I re-enabled Dashboard, I was 
  somewhat surprised to find that my three open widgets were indeed still 
  open.]

  [Non-text portions of this message have been removed]



   

[Non-text portions of this message have been removed]

On 1/4/07, Tim McLane <timmclane@...> wrote:

> I'm a little confused: does it look like that consensus is that dashboard
> can cause a problem if you're running a lot of programs or not? If it is, I
> think I'll disable mine, too, since I never use it

Few studio computers disable it. You could disable Dashboard if you
think you will never need it, it does not hurt either way. Maybe you
save 100-200 ms in the startup time. --Kent

Now, to *really* save CPU and memory cycles. Don't run Safari/Firefox,
Mail and similar apps that poll something out there on the network
from time to time... --Kent

On 1/4/07, Kent Sandvik <sandvik@...> wrote:
> On 1/4/07, Tim McLane <timmclane@...> wrote:
>
> > I'm a little confused: does it look like that consensus is that dashboard
> > can cause a problem if you're running a lot of programs or not? If it is, I
> > think I'll disable mine, too, since I never use it
>
> Few studio computers disable it. You could disable Dashboard if you
> think you will never need it, it does not hurt either way. Maybe you
> save 100-200 ms in the startup time. --Kent
>

On Jan 4, 2007, at 1:43 PM, Kent Sandvik wrote:

> On 1/4/07, Tim McLane <timmclane@...> wrote:
>
>> I'm a little confused: does it look like that consensus is that  
>> dashboard
>> can cause a problem if you're running a lot of programs or not? If  
>> it is, I
>> think I'll disable mine, too, since I never use it
>
> Few studio computers disable it. You could disable Dashboard if you
> think you will never need it, it does not hurt either way. Maybe you
> save 100-200 ms in the startup time. --Kent
>

Its the memory space it takes up really. If you just hit F12 once and  
show the Dashboard, it remains in memory until you reboot and hit F12  
again. Its really only trouble if you have a hundred widgets open at  
once on it and you dont reboot your computer. Now if I could figure  
out how to kill Expose hehe...

---
Chris
www.monotrematamusic.com
www.descentrecords.com

There are a bunch of command keys that Apple uses for system activities. For 
example F14 makes the screen brighter, and control shift command 8 makes the 
screen reverse color. It makes it harder to assign key commands in Logic.


> Haha now I can use my F12 key in World of Warcraft again!!
> Oh wait Logic yeah... None of that time wasting game stuff hehe..
> :D
> 



[Non-text portions of this message have been removed]