Jump to content

deadline tomorrow - and logic appears to be totally f*cked


wilx

Recommended Posts

apologies in advance for rambling or incoherency, but it's just gone midnight and I have a deadline tomorrow (technically, it's later today) - and Logic has just gone completely mental on me.

 

I'm working on a short film score.

 

I did nothing obvious to mess things up - no extra instances of plugins, no adding effects, all I did was add a couple more bars with instruments that were already in the project.

 

I did a bounce of the project, but logic got a quarter of the way through and crashed.

 

When I tried to load the song again, Logic froze and I had to 'force quit'. Twelve times.

 

I then loaded the song with coreaudio disabled, and could find nothing obviously wrong. When I re-enabled coreaudio, logic froze and I had to force quit.

 

So I loaded the most recent revision before the one that was causing problems.

When I re-enabled core-audio, logic didn't freeze, but instead gave me:

 

sampler

Not enough memory to load all samples of instrument

White Sister.exs

 

then

 

Not enough memory to open plugin - repeatedly, presumably for every plugin in the project.

 

Next time I loaded logic, the 'recent projects' had disappeared.

The next time after that, I got a strange message:

key or key combination reserved

Key or key combination (shift+something) has been removed from command...etc

 

Beyond re-installing Logic, or my operating system, or seeing if there's a Logic update I'm in the dark here. I've got a deadline hours away, and Logic (not for the first time) is in danger of seriously compromising my work & reputation. I'm not a happy bunny. I love Logic to bits when it works, but technology (especially anything computer-related) seems to have a knack for completely f*cking up at the worst possible moment.

 

If anyone can help here I'd be very grateful!

Link to comment
Share on other sites

I've been there. I might be able to help a bit.

 

First important question:

 

Are you using EXS-24's at all in your song/cue? If so, how many instances, and, were you running it with Virtual Memory switched on?

 

If the answers to these are "yes", then read on...

 

You need to re-launch Logic (no song, just the program), open an instance of EXS-24 (no instrument loaded), toggle Virtual Memory off and then on (using the Apply button as necessary). Do the same to the disk speed prefs too, hitting Apply as necessary.

 

Quit Logic, restart Logic, and the load your song. You should now be able to load it. If you can't then there's some other kind of song corruption at work, but first things first...

Link to comment
Share on other sites

Just read your post a little more closely. I see you're using EXS-24. Sounds to me like your preferences got trashed and that's why your EXS-24 samples aren't loading. Might not be a bad idea to move your existing prefs to the desktop (Logic shouldn't be running when you do this). Then re-launch Logic; this will establish a fresh set of preference files. Re-load your previous key commands from the old pref file (now on the desktop).

 

At this point your EXS-24 virtual memory prefs are going to have been reset, but probably not a bad idea to toggle them as I described in my previous post.

 

One last note... once your recent items list is gone, it's gone forever afaia. So don't bother trying to get that back.

Link to comment
Share on other sites

trashing prefs didn't work. I can now get into the project two revisions before the current one. I'm going to have to copy the tempo map, midi & automation & place them, bit-by-bit, into the older project - and I +really+ hope that works.

 

I did the EXS stuff, but that had no effect. And my system drive is 300GB with 99GB free. My sample drive is 300GB with 35GB free.

 

I still can't think what's gone wrong. Do other sequencers go wrong like this in such a catastrophic way?

Link to comment
Share on other sites

I feel for you. Deadline pressure is not nice when you need to troubleshoot. Can you get an extension on delivery? If the clients know you they might be willing to help. Get a breathing space if possible. Take a walk, maybe.

 

You *will* get things running again.

 

Do you have friend whose Logic you could open the project on?

 

Good luck

 

RR

Link to comment
Share on other sites

trashing prefs didn't work. I can now get into the project two revisions before the current one. I'm going to have to copy the tempo map, midi & automation & place them, bit-by-bit, into the older project - and I +really+ hope that works.

 

I did the EXS stuff, but that had no effect. And my system drive is 300GB with 99GB free. My sample drive is 300GB with 35GB free.

 

I still can't think what's gone wrong. Do other sequencers go wrong like this in such a catastrophic way?

 

Is the sample drive formated to Mac Os Extended?

 

Have you tried moving the samples to the systemdrive desktop and then disconnect the sample drive and let logic find the samples on your systemdrive?

 

Is Spotlight enabled?

Link to comment
Share on other sites

I feel for you. Deadline pressure is not nice when you need to troubleshoot. Can you get an extension on delivery? If the clients know you they might be willing to help. Get a breathing space if possible. Take a walk, maybe.

 

You *will* get things running again.

 

Do you have friend whose Logic you could open the project on?

 

Good luck

 

RR

 

I'm getting there - I'm almost back where I started having recreated what I lost with the most recent backup. The memory issue seems to be fairly fragile, so I'll check to see if my RAM is corrupt.

 

As for that walk, most of england is now covered in thick snow, so I'm going to go and get some fresh air and take in the scenery :)

 

Thanks for everyone's help with this - I might not have solved the original problem, but I've more or less managed through a workaround.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...