Logic Pro 8 Issues

Im still using logic 8 right now, and I have had it for about two years now,but I am now getting this weird "System Overload Message" and also when I load it up, I have also gotten this weird message about my "DAE Folder" is missing. Does any one know how to fix these issues.
Thanks for your help....

Most of the NI Instruments don't run on Leopard because NI hasn't updated the drivers for them (check the NI website fort info, they say the update is due in Decembre...). The same counts for other 3rd party plugs so either you revert to 10.4.11 or wait for the new drivers.

Similar Messages

Logic Pro issues with input putout

LP 9 Issues . Recently installed snow leopard . Now I'm finding LP9 will not input/output as it shouted .. I get input/output on one session after booting up the computer. When I close that session and open another I get no input/output. So far I've tried trashing the preference and also reseting the computer, neither did not help. Any help.

I get input/output on one session after booting up the computer. When I close that session and open another I get no input/output.
What audio interface are you using? When this problem happens, do you see the interface still selected in Preferences > Audio?
Instead of relaunching Logic, you could try this. Open Preferences > Audio and uncheck "Enabled" (under "Core Audio"). Press the button Apply Changes. Then check Enabled, and Apply Changes again. Does that fix it?
reseting the computer
What does that mean?

Logic Pro Issues with iSight Camera

I have been working a problem for two months that I thought was a Firewire problem. It started having the problem after installing my new TC Electronic ProwerCore Firewire. I look at everything including LaCie Hard Drives to my RME Firewire 800 IO. Then I stumble on the problem. It was my isight camera. Just plugged in was causing problems.
Problems apeared as IO comunication errors in many different forms and different errors depending on the plugin have the issue.

Impressive hardware collection, DavidSimmons!
We rarely hear about such high-end production equipment here, but Firewire connected and AV devices are always conflict candidates.
Your hardware conflict with iSight make my scanner conflict seem really mundane.
Thanks for sharing your example.
Cheers,
Jim
Note: also posted at http://discussions.apple.com/message.jspa?messageID=4995086 and
http://discussions.apple.com/message.jspa?messageID=4995084

Snow Leopard and Help menus (particularly Logic Pro)

Not sure if this is snow leopard or Logic Pro issue. Logic 9 using snow leopard, when I go to the help menu I get -" The Help Library requires JavaScript. If JavaScript is not enabled, you will not be able to view all the content."
However, the help menu in every other "Apple" app (pages, numbers, keynote, Garageband, etc) works just fine - as does Bento..... etc..
Can't find a "javascript" preference in Logic Pro - enabled in ALL browsers!
Help!

Someone had sent me a terminal command that brought the help windows back and it worked great - but it seems that the solution was pulled from this discussion - and I don't know why - and don't remember what I typed into the terminal - sorry!
But it did work!!!

Logic Pro Corrupt Files? Begging for Help!

Hello all,
I am having a real problem here. Every new file I create in logic pro eventually turns corrupt, including the backup projects automatically generated in the project folder. When I go to open the project file I've been working on, a prompt pops up either saying that the file is unreadable, damaged, unrecognized or even sometimes it says my audio files are in an unreadable 8 bit format () So it seems to be corrupting the audio files as well... Some serious problem is going on. I am running all latest versions of all my software and hardware. Leopard 10.5.5, Logic 8.02 and my MOTU Interface has the latest firmware.
I have tried dumping my preferences in the library, and I even did a full reinstall of Logic, and the problem continues. Is it a hardrive issue? I have verified and repaired disk permissions several times with no problems. I tried to call phone support and was surprised to be treated indifferently and would not be helped unless I consented to an expensive user agreement. I thought my $3,000 computer and $500 software purchase would be adequate enough. I guess not.
Sorry for the rant, this has been most troubling seeing as I have lost a project due to this crazy glitch. So I turn to you, online community! Am I alone is this problem? From online investigation it seems no one has had much of a problem with this. Does anyone have advice for me? Anything will be GREATLY appreciated!!!!!!
BTW, DP projects and Garageband projects seem unaffected, which makes me wonder if it's a Logic Pro issue after all. Oh and I'm running the same Logic Pro software on an older Powerbook G4 w/ Tiger and everything runs fine.

dsermon wrote:
As far as other hardware, it's only the ultralite and a oxygen 61 keyboard
Yes these corrupt files work ok on G4 unless the audio has already been corrupted by my macbook pro
*I will definitely try out all of your suggestions* and see where it leads me. I'm glad other people are experiencing this problem. Well, not glad, but you know what I mean... Just thought I was going crazy.
Elith- does your exported audio come back as garbled audio sometimes? Mine either make a TERRIBLE hiss, garbled, or are not readable at all. Really sad stuff....
Are you connected to the internet via wireless or ethernet cable?
If so disable and see if it makes a difference.
pancenter

Performance issues with Logic Pro 9

Hi,
I'm experiencing quite big performance issues with Logic Pro 9:
bad midi timing and sync, user interface is kinda slowing and less reactive, ...
Mac Pro 2x2.26 Ghz Quad, 4Gb ram, early 2009, shipped with 10.5.6 now upgraded to 10.5.8
Should I upgrade to 10.6.2?
Thanx

Hi,
I'm using the same machine ...
I never get any performance issues
I bought my mac in March 2009 and I was ben ready to work in less that 3 days without issue...
so more details about your setup are required to answare!
4GB ram???
I suggest to check your ram!!!
Ram must be compatible with Xeon Nehalem Try specification!
if you add 1GB of ram from nor clear manufactor.. i suggest to disconnect the addition 1GB RAM
G

Latency issue Logic pro 9.1.3.

Hey,
At the same time as upgrading to Logic from Garageband
I bought a Cakewalk Roland UA25EX ext usb soundcard because i was told
i'd have latency issues if i used the caps lock keyboard for midi
or direct input thru the input jack of
my MacBookPro
(5,3 Intel Core 2 Duo 2.8 GHz)
Sometimes i use the caps lock keyboard to sketch in midi ideas and mostly it's ok.
Other times it's delayed and there's no smile on my face.
When recording with guitars/303/generators DI thru the soundcard
I have latency issues that don't seem to be very regular.
Sometimes it's worse than others.
I make sure i have nothing else running on the computer,
just Logic Pro 9.1.3, so it's not like i'm overloading macbrains.
I have tried all the rebooting, i/o buffer size changing (down to 256), headfones from the mac output/headfones from the soundcard/ etc
but still no luck.
I can record with the low latency button on
and it's kind of better, nearly, but that means i don't get to record with the effects on the channel strip
that affects the recording/playing quite a lot, as i'm used to recording with effects/guitar amps if i go DI.
This was the selling point - that i could record DI wthout disturbing Thee Neighbours.
It seems to have gotten worse recently.
I wonder if it's been corrupted somehow because it also has been acting funny when i bounce down -
the play head is set to 1111 and i save - then in the bounce window
the start position says a silly random number and it takes a few attempts of fiddly changes to get it to stay at 1111...frustration!
Is there something i can do or is this normal? -
it seems weird that a Pro app that cost me so much £s wouldn't work in a simple recording/bounce down set up?
or has anyone else had this problem and fixed it?
If i wipe Logic and install again would i have to go from my Logic Express and then up to my Logic Pro upgrade/extension again?
Any pointers would be greatly appreciated.
Thanks in advance

Hey Fox,
Thanks for that info -well umm, yes i installed the correct drivers.
I use just the AU plugins or the basic logic ones on the channel strip
but even when i was going in dry there was still a delay.
I had experimented with the buffer size, as mentioned, but not gone down that low cus
last time i tried that i had other strange things happen!
But i will try again.
Sample rate was at zero, btw. Always says zero.
But today, when i just opened logic, the sample rate had changed. Strange. I need to understand this side of things so i'm gonna read up.
Also, if plugins are involved, i installed some novation bass station and some freeware TAL bass synth
stuff recently but don't have them up when i'm recording.
Maybe they sit there quietly and interfere just by their facial expressions or sumthing!!
I booted Mr MBP just now and i pulled out the USB and he's shining me a big ole red optical light
out of his output jack!!
In SysPrefs it has only optical digital as an output option.
In the last few days as i was playing around trying to correct the latency issue i noticed that the output options had changed to the UA25 and the 'digital optical' options - rather than the UA25 and 'line out'.
I'm off to go and read up on how to get my line out back, and try this buffer thing again.
Thanks again
Gravity

"Mouse Over" issues in Logic Pro - Mountain Lion

Hi,
Since I upgraded to Mountain Lion, I spotted an issue with Logic Pro (Logic 9).
In the Arrange window, when pointing the mouse at the end of a region, the pointer icon doesn't change to the looping (upper right corner of the region) or resize (lower right corner) icon.
As a result, those functionalities (looping and resizing regions) are gone.
Anyone having the same issue?
Is there a way to solve this or do we need to wait for a Logic Pro update to get these back?
Thanks in advance,
A nice day everyone,
Vince

Vlvl wrote:
As it's the only problem I have noticed since the upgrade, and as I mentioned in my last post, looking like a minor problem to me, I will keep Mountain Lion.
But anyway, thanks for the advice, Ivan.
Vince
No problem, as a professional musician using Logic I learned that lesson the hard way first time around. Hard as it was to not have the toys I soon learned that stability ruled the day....

Logic Pro X and Yosemite issues

It seems I have some very basic issues with Logic Pro X 10.0.7 after upgrading to Yosemite OS on my MacBook Air:
1. Zooming the main window by swiping two fingers apart or together on the mouse pad does not work anymore.
2. Adjusting the length of audio regions in the main window does not work anymore. It works as usual on midi tracks, but when I hover the end of an audio region the brackets just do not appear. I have now used automation to silence the bit that I wanted to shorten, but that is more of a hassle.
I have tried restarting Logic Pro X, restarting the MacBook and looked for any settings that may have been changed, but to no avail.
Do these issues sound familiar to anyone? Any thought on how to fix?

1) Zooming
the zooming with the swipe gesture was always problematic, but it is now only happening in the Audio FIles Editor and to some extend in the Score Editor. All the other windows work fine on my machine.
2) Resize Tool
Works fine without a problem in the Main Window and the Editor windows. Of course, you can resize in the Audio FIles Editor.
Hope that helps
Edgar Rothermich
http://DingDingMusic.com/Manuals/
'I may receive some form of compensation, financial or otherwise, from my recommendation or link.'

Logic Pro 9.1.1 AU third-party plug-ins ongoing issue for many

Where is the Logic development team on this? Nearly all third-party AU plug-ins produce random pops and clicks at the beginning of playback and on occasion randomly during playback but before audio regions in tracks with these plug-ins installed. These pops and clicks are even visible in the track's meter. http://www.gearslutz.com/board/music-computers/482381-logic-3rd-party-plugs-pop- click-nightmare-how-does-rest-world-do.html How many people need to complain? Is Logic Pro considered production software?

I can't imagine a more textbook and apple-friendly environment than what I have. 32-bit is not the problem. I don't believe logic runs at 64 until you're on os 10.6 and I'm still on 10.5.8. My entire rig is what you'd see in an apple store logic demo. I've tried nearly everything:
1) All standard optimization tips including but not limited to no date/time updates, no airport/wi-fi, no bluetooth
2) I have a ultra high-quality external fw drive by G-drive
3) Standard issue ensemble with updated firmware
4) Moving AU component files from system library to user library
If you look at the number of people commenting on the GS thread as well as other forums – the problem is common and needs to be fixed. I'm not the only logic user plagued by this issue:
http://www.logicprohelp.com/viewtopic.php?t=43306
http://www.logicprohelp.com/viewtopic.php?t=50030
I really believe it has something to do with how many third-party plug-ins handle AU's reset or initialize callbacks; somewhere in between. This bug is clearly affecting many users and I'm coming close to starting a petition and devoting some serious time to making a big dorky stink about it on youtube.
Either the AU spec needs to be updated to clarify some tricks (or hacks) specific to Logic's on-demand DSP usage or the logic team needs to publish a notice to all "Logic" AU developers. Optionally, if Logic had a preference to turn OFF on-demand AU DSP (so that plug-ins are always-on like in every other DAW or...ugh...outboard gear). Logic's on-demand AU DSP handling is outdated considering the processing power available in ANY apple computer made within the last 3 years. My CPU meter in Logic barely even lights up. On-demand DSP is overkill and antiquated and the least Logic can do is provide production or mission-critical users the ability to opt-out if they have the CPU power to do so.
Having said all that; I hope I'm wrong about something and can come back here to eat my words and feel very embarrassed about my rant. I'm going to keep digging for solutions – hopefully, I'll find out the secret to whatever it is the few of you are doing to keep your third-party AU plugs quiet before an audio region starts.
Also; Scott at Stillwell Audio has graciously begun trying to track down this very issue and is one of the few DSPers who has taken interest in helping Logic folk.

10.8.4 Logic Pro Hard Drive (Disk I/O) issue

Hey,
since yesterday my Logic Pro (9.1.8) has a big problem. After I installed the Update 10.8.4 the Hard Drive (Disk I/O) Display overloads everytime, when i start to play my vocals/tracks. Even older projects (i never had problems) with just 20 tracks and without third party plugins the HD Display goes up and with the latest project (49 Tracks) i cannot even create a new track anymore. It says "not enough memory" and then it crashes.
I bought my Imac some months ago. Just some informations about my Imac.
- Late 2012, 21,5"
- 16 GB Ram
- 2.7 GHz Intel Core I5
- Hard Disk 5400 revolutions per minute, Sata (still 900 GB free)
Basically I bought my Imac to create music and to use logic pro - its very frustrating .. i cannot work anymore.
I tried everything - change the settings, change the buffer size, not to use my interface, 32bit to 64bit, to delete Autotune (my only third party plugin) from the AU-Manager. I even had a call with the Apple Support (2 hours long) and they couldnt find a solution ..
If they cannot find a solution, i think its even harder to find someone here, who can help me. So my question is just, is there someone else who has a similiar problem with the update?? .. I'd say a problem shared is a problem halved :-)
thank you & nice greetings from Austria :-)

Hello Stefan,
Bootup holding CMD+r, or the Option/alt key to boot from the Restore partition & use Disk Utility from there to Repair the Disk, then Repair Permissions.
See if the Disk is issuing any S.M.A.R.T errors in Disk Utility...
http://support.apple.com/kb/PH7029
Open Console in Utilities & see if there are any clues or repeating messages when this happens.

HI. ... Anyone know of any issues with using Logic Pro music software with Mountain lion OS.. I have heard rumours in the past is that all sorted now?

HI. ...
Anyone know of any issues with using Logic Pro music software with Mountain lion OS..
I have heard rumours in the past is that all sorted now?

At least Logic Pro 9 and Logic Pro X work correctly in Mountain Lion. Furthermore, Logic Pro X requires the latest OS X Mountain Lion version

Logic Pro X Import Audio Issue

I justed upgraded to Logic Pro X and whenever I import any sort of audio the 1st small bit of music always gets messed up. Please let me know how to fix this. I have had issues importing mp3's as well as converting mp4's to audio files. Its like there is a little hiccup in the conversion proccess for the 1st half second of music every time.
**THE AUDIO IS FINE PRIOR TO BEING IMPORTED INTO LOGIC PRO X***
Please help ASAP!!!@!@!! I am trying hard to stick with Logic Pro X instead of 9 but find it hard when my audio is getting botched on the import proccess
Thanks!

I have this problem too.
im running Mavericks 10.9.2 and Logic X 10.0.6.
I dont enable my time machine.
I'll try converting the file to other formats before importing to logic and see what happens

What's the best Mac to run Logic Pro 9 and above with no issues

What's the best Mac to run Logic Pro 9 and above with no issues?

Any Mac that can happily run OS X Snow Leopard 10.6.8 and Logic Pro 9.1.5.....
Note: Newer Macs cannot run Snow Leopard because SL doesn't provide hardware support for the newer hardware found in these newer Macs....
Next best combo for newer Macs is Mavericks 10.9.5 and Logic Pro 9.1.8... but it is nowhere near as efficient a combo as the previous one mentioned...

Logic Pro 8 Issues, Error Messages

Hi all.
I've been having a variety of problems with my home recording studio, which i have neglected to post about until now- from what i've read it seems no-one knows how to fix them. I'm turning to the MacTalk community to resolve my woes... First things first, here's the gear:
 MacBook Pro (mid-2008), 2.4GHz C2D, 4GB RAM, OS X 10.5.6.
 I use Logic Pro 8 primarily, and this is where all the errors are popping up. I record to WAV, 24-bit, 48KHz (for the sake of diagnosing errors, I have tried 16-bit, 44.1KHz and noticed no difference).
 All audio-related work is handled on a WD MyStudio External FW800 HDD.
 My audio interfaces are an Apogee Duet, and an M-Audio ProFire 2626 (both running latest drivers).
Now, there are 3 (possibly related) problems i'm having with my setup.
✖ Problem #1
I receive an error message indicating a 'System Overload' at random times during playback and occasionally recording.
It halts the audio, and I need to click play or record again. Sometimes it happens again and again, other times it’s just a one-off. This problem can occur with either the Duet or ProFire interface. Apparently the number of tracks I’m recording or playing is irrelevant, as it happens under many different circumstances.
✖ Problem # 2
I receive an error message telling me that the “Drive is too slow, error -10004”, and this happens only in recording (I think; oh and it looks like the previous dialogue box). As mentioned above, I use a FW800 external HDD, so it shouldn’t be a hardware requirements issue – it SHOULD be fine as far as I know. It was particularly bad when I was recording 5 channels of audio into the ProFire 2626. Like the previous issue, it halts the recording, and sometimes recurs. It may not happen with the Duet.
I may be imagining things, but I think it records fine indefinitely when I’m recording near-silence, i.e. not playing my drums. It almost seems as though the problem is triggered when I get particularly loud. Perhaps it’s clipping, I’ll have to check. Still, it shouldn’t cause an error that halts recording should it?
✖ Problem #3
This one only occurs with the ProFire. I get minor crackles and little bits of distortion and ugly tearing sounds in some channels occasionally. They each only last a fraction of a second, and usually aren’t particularly loud, but they spoil takes. Can occur during silent passages OR loud parts.
For the record, I typically record to WAV, 24-bit, 48KHz, with a 128 or 256 sample buffer, Medium Process Buffer Range, and Software Monitoring enabled. However, I have tried up to 1024 sample buffer, Large Process Buffer Range, 16-bit, 44.1KHz WAV, and turned off Software Monitoring – none of this made a difference.
So, if anyone thinks they can help me out here, please do so! I’ll greatly appreciate any input ☺
Cheers,
Chris

1. http://support.apple.com/kb/TA24535?viewlocale=en_USy
This problem points to a buffer that is set too low. Make it one step bigger, but leave the I/O safety buffer OFF.
also: you can disable the warning message.
2.
CAN also be buffer-related, but it may be the disk. Is it a 5400 or 7200 RPM disk?
It may also be that memory is too full. I would recommend installing Menumeters (freeware) http://www.pure-mac.com/diag.html#menumeters
You can monitor CPU-use, disk activity, memory use, paging activity and network activity with it.
Another thing to consider is to Freeze all Software Instrument tracks before recording. Also freeze heavily 'insert-pluginned' audio tracks. This may free up a lot of CPU power.
3. This problem might benefit from the above tips as well, but I think you can win the most by NOT using software monitoring when recording (for all three issues); it brings extra latency and puts much more strain on the CPU. Through which plugs do you monitor? And why?
I'ld recommend using the direct monitoring capabilities of both your interfaces, and avoid Software Monitoring when recording. Also being aware of what is going on (by using both Menumeters AND Logics' own CPU-meters) can be crucial - especially Paging (when active RAM is written to or read from disk) can disturb Logic, as well as background OS X applications that kick in during a session.
I also recommend turning off Journaling before a recording session. To do that, open *Disk Utility*, select the recording disk from its' list, hold down the ⌥ key and choose the menu *File>Disable Journaling*.
To turn it back on after recording, same actions, only now the menu item will say *Enable Journaling*.
regards, Erik.

Pro Tools/Logic bouncing issue URGENT

I have an urgent Logic/Pro Tools question. I've asked several people and searched online but I can't find the problem. For some reason, my bounced Logic files come out as 5 mono tracks in Pro Tools.. but they're bounced as interleaved in Logic. I'm not sure what the issue is.. I have a deadline for this track (Jan 5th) help is REALLY appreciated. Thanks in advance

Quality shouldn't differ between interleaved and separate right/left mono files.
If you want Logic to work like Protools and be more compatible with PT, go into Preferences/Audio and uncheck "Universal Track Mode". Now Logic will use separate files for left/right.
Most DAWs can import interleaved files because they also use them as the main recording option, ProTools has always stuch with single right/left files.
pancenter-

Logic Pro 8 Issues

Similar Messages

Maybe you are looking for