Apple Logic Pro /LogicExpress Discussion group photo

Yahoo Groups archive

Apple Logic Pro /LogicExpress Discussion

Index last updated: 2026-04-28 23:06 UTC

Thread

I don't know. It is most likely attributable to human error.

I don't know. It is most likely attributable to human error.

2005-04-17 by Tao

These phrases are hung above the door to my office so I have the best 
answewrs ready for folks who drop by with questions.  99.9% of the time 
one or both will work quite well.

As for GAmoore and suggestions here ya go - presented on no particular 
order 'cept how it comes off the top of my head.

Get rid of AOL - unnecessary additional interface and configuration 
tools.  At least keep it off your production box and use the iBook to 
download updates.  I know it is convenient to have WWW service on your 
production machine but AOL does not play nice.

Start from scratch and work slowly.  This will take a sec.  but will 
reward you in the end.  Back up your system.  Use CCC from Bombich if 
you do not have a current incremental System like Retrospect 
(recommended) inplemented yet.  Start from the install CD, Erase and 
format the SATA 0 device to 1 partition Mac OS extended journaled.  Run 
OS installer and at the options page select only the required system 
software for install.  No X11 or BSD or additional fonts or language 
translations.  Restart.  Create "Apple Admin "(apple) admin user.  
Log-in.  Enable root with /Applications/Utilities/Directory Access.  
Create a local user account for yourself - do not enable admin access 
on this account.  Turn on fast-user switching & Set the auto-log to 
your local account in /Applications/System Preferences/  Repair 
permissions with /Applications/Utilities/Disk Utility & ReStart  Switch 
to your local account and install Logic.  Repair permissions as above & 
restart.  Install only required drivers for Audio and MIDI interfaces.  
Repair Permissions  Restart.
Run /Applications/Utilities/Audio MIDI setup and configure.  Restart.

Start Logic and run setup assistant.  For evaluiation and testing i 
have a little 4 track four-bar groove ("Autoload Groove") with some FX 
on busses nothing too extreme that I use to benchmark and evaluate 
system performance.  Make something for yourself like this.  Run the 
loop and get a look at Logic Pro/ Audio/System Performance.  How it it 
running?  Do you need to increase the value of Logic Pro/Audio/Audio 
Hardware and Drivers/I/O Buffer Size to optimize the performance of 
your sound card? Get this rig working do not install anything else 
until you do, then add slowly - one AU at a time and test with the 
Autoload Groove each time.  NI have never worked well for me (Horrible 
ugly bloatware unusable interface and no real additional functionality 
to Logic) and Arturia's stuff takes alot of processor cycles. Add one 
at a time installing from your local user account and repairing 
permiossions before using.  My test sequence plays an external MIDI 
Instrument to adjust  Logic Pro/Preferences/MIDI/Sync/All MIDI Output/ 
Delay.  And generates MIDI Beat clock to adjust the /previous path/MIDI 
Sync Song Settings Transmit MIDI Clock  if you use these functions be 
sure to incluse them in the test jam.  Good Luck!

That's just the point, some people have to work hard to afford the
expensive software, leaving little time to sit for hours and figure out
what the software companies forgot to do. If the consumer allows
substandard products in the marketplace, the manufacturers will surely
agree.

"Substandard"  hardly - it hasn't killed anyone that I know of yet and 
I think you would have a hard time indentifying any substandard portion 
of the source code.  The results of an individual's use of an 
application however are subject to interpretation - see messsage 
heading.

Yeah, sometimes. There ARE such things as bugs, ya know! And, often, the
only so-called solution seems to be to avoid them. I'd hardly call that
"resolving" them.

A guy goes to his doctor and says "Hey doc, I hurts when I do this" and 
the doc looks at him and says "Well don't do that".  Bugs, sure but 
there are so many other factors involved once code is compiled and the 
app distributed that few true "bugs" are really identified - there are 
a combination of factors that lead to system instability and all of 
them have the user configuration as a major component, since this 
factor is unknown at the test phase it is impossible to account for.

I wish I could but that's the problem. Accepting the high cost for such
low level efficiency is the same as the black slave saying it's ok that
he's a slave. These products aren't new anymore, they've been around a
long time. It's time for all the companies making these products to
start integrating a bit of integrity into the equation for once. Maybe
then the forum can be used as a brainstorming environment, discussing
different ideas for usage and not a how to make it work discussion.
I don't believe that's asking too much.

OK but the trade-off is innovation.  Computing would be stuck in UNIVAX 
if the goal was OS integrity.  I want hot new tools and an ever 
expanding selection of services available to me.  Computer Users should 
be accustomed to this by now, these products are not new and have been 
around a long time.

Whew!

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.