HELP! (really, bad things happening in Logic) - but now I've fixed

[BevvyB]

**I managed to fix the problems but I post this here just in case anyone else gets any freaky shit with the EXS24 on 6.4.1

EXS24 has decided to hang when I select sampler instruments from my sample drive. What is strange is that songs will load and play fine with all their instruments and everything

Mu sample drive is accessed by having aliases to it in the Logic folder. Never had a problem with it.

1. Tried re-aliasing my aliases
2. Tried re-scanning everything on all drives with project manager
3. Tried ditching autoload
4. Fixed permissions
5. Ran scripts

Running out of ideas here. I'm thinking that as I'm using the new Logic Pro 6.4.1 I may have come across a BUG.

Any ideas?

[DanV]

How did you end up fixing it?

[BevvyB]

OK, more problems

Logic Pro really doesn't seem to like having two songs open at the same time - it will take a hideously long time to open the second song, and then before you get to see its window, switch back to the original songs window. Then switching between the two is slow, and just resulted in logic quitting itself.

As I type this into my browser I can sense that its still trying to do something in the background. Time for a reboot.

[BevvyB]

Even more problems

Logic now doesn't move its automation data along with its patterns/recordings

Even though I have 'ask' set for 'move automation data' you can hit 'yes please move automation along with parts' and then watch...as it doesn't move any of it - the parts all shuffle along and there are your automation curves back in the same place you left them

I am getting Le Hump with 6.4.1

Another thing I forgot to mention was that yesterday for no reason Logic decided I didn't have a midi channel 1 and only several reboots and USB swappings got it back

Also it decided I didn't have an audio driver at one point

**Update: For some reason the automation is now behaving itself

However, Logic has now decided that the B3 softsynth isn't going to play out even though you can see a level on its mixer fader its not getting to the bus. Yawn.

[BevvyB]

I lied.

The automation is PRETENDING to be ok on certain tracks - its being SELECTIVE on what it decides to move

Which is even worse, i can't even rely on it to be wrong across the board and get away with it, it moves some automation with the parts and some it doesnt



OK OK I know this is the point where I should reinstall logic....

[A33]

Damn you are getting the shit end of the stick!
I haven't had these problems. Are you on OS9 or X?

[keyboardman]

A surefire way to move automation data is to open the automation folder. I think the default is option-e...you might have to assign it yourself. Also, sometimes, you have to hit it twice before it opens.

It will open as another arrange window...a really long one at that. Select whatever you need and paste it into your new song's automation folder.

[BevvyB]

OSX 6.4.1 Logic Pro

Thats a cool tip about the automation window that not a lot of people know about

However, I wish there was a kind of 'rebuild automation' kind of button, where it would have a good look at its automation and see if it can see any problems, 'cos at the moment if your automation gets corrupted you're kind of stuck

Here's another thing, which has been happening for AGES and on all version of Logic -

When I have a floating window open above the arrange page which shows whichever track I have selected on the arrange page its very useful (using the link), but sometimes it just decides to stop showing the track i've just selected, which can be very annoying when you start tweaking a channel's plug ins only to realize its the wrong channel...only thing that gets it all back working again is a quick reopening of the page

Anyone else have this? It's really irritating.

[Jam]

Sorry Bevvy it's been as good as gold here
on a 10.2.8 Motu Lucid rig. Post if you find a cause or fix it's always appreciated !

Jam

[smoothmoniker]

beavy

wow that suck. two general thoughts that may not work.

1 - try trashing your preferences (or moving them to the desktop). Logic occasionally corrupts it's preferences file.

2 - trash the preferences for Quicktime. Same thing, but LOGIC references QT for some of the internal MIDI stuff, and a corrupt QT preferences file will cause a world of pain in LOGIC.

-sm

[flexoffset]

My Logic Pro will arbitrarily change it's midi sync settings. Some days it will open correctly, other days it doesn't even know i have a MIDI interface. Other days it will change the ports i have selected.

OS X v10.3.3

I've always had problems keeping two songs open at a time. It's soooo terribly sluggish and sooooo prone to crashing that way.

I've had 'ok' luck, but I wouldn't say it's absolutely been a bed of rose petals, either.

[BevvyB]

ok, I've traced the wierd EXS24 disk thing to webdav

It seems that webdav launches while the EXS24is looking for the relevant samples, perhaps looking to establish a connection to nowhere and thus giving me the spinning beachball of death....

....because if I launch terminal and kill webdav while this is going on the beachball dissapears, the samples load and all is back to normal for the rest of the logic session

Interesting

(For those unfamiliar with this background nonsense, have a go at opening the terminal and typing 'top' which gives you a list of all active processes - typing 'kill' and then the ID number of the process will terminate that process - this is a handy way of working out what is messing things up by elimination - I could tell webdav was up to something as I could see it using up CPS resources using top)