Multiple malfunctions in Logic X

[sansharbour]

Sometimes I close logic with pod farm still open. If I do this the main screen won't open automatically because it always defaults to what was last open.
Im not sure if this is your problem but I have to go to Window/ Open Main window. This usually does the trick and the big screen opens and this time I make sure I have closed everything first then saved the project and close Logic. Next time I open it's back to normal

So basically close everything first then Logic last.

This may not be your problem.....
good luck solving the mystery There is always a solution

[orest]

I've experienced that problem as well. It was when I updated (not a clean install) the OS to a newer version.
I'll never make that mistake again.

Hey Orest, how do you do a clean install when the new operating systems are only available from the app store? Or are they?

This is the way (see link below). It could also be something corrupt with your preference files (logic pref files). You can try to delete them and reboot, but, if you have done any user configurations in Logic (like adding your own short commands) you will have to redo them again, but that's pretty easy.

http://www.macworld.co.uk/how-to/mac-so ... x-3637409/

[elser]

This pesky issue has popped up again on a different song. It's definitely a bug and the main reason I'm posting here about it is to raise awareness and hopefully it'll get back to Apple. On top of the other behaviors I've listed I've also found that the meters in the mixer don't work. I'm also reporting it on Apple Discussions and Logic Pro Help.

[orest]

I never use templates, when I did they tended to get buggy after a while.
Sometimes when I have recorded a song with only VI's (no audio) I have used that song as a template for another song. I never do that either nowadays.

The reason is that Logic somehow records CC data and other strange things in the background that won't be deleted when you save as... name your new song and delete all the files you've done in your current song to begin your new session. Say that I'm recording the piano for that new song, the deleted piano file still have some CC (like ghost CC) that will follow along. I have especially noticed this regarding the sustain pedal and the mod wheel (for say, strings and brass).

This never happens to me if I start a completely new track with new VI channels. It's a bit more time consuming not being able to load already done templates, but, it's more frustrating to get those bugs all the time.

[Len911]

I noticed you can save projects either as a "package", which is all one file, or as a "folder". It shouldn't really make a difference, although if you save as a "package" you know a folder within the project hasn't been inadvertently moved or deleted.

I'm wondering if you save as a "folder", assets in subfolders, that if another project uses the same subfolder and makes changes, if it doesn't somehow affect the first project that shares the same asset file?? When saved as a "folder" project. Perhaps a "package" project makes a new folder within the package and doesn't share folders?? I don't know because I haven't found anything that specific. Obviously if you are saving your projects as a package, that's not the cause of your problem, it does seem that the trend is to save as a folder project. I would try saving them as a package project if you are presently saving as a folder project.

[orest]

I noticed you can save projects either as a "package", which is all one file, or as a "folder". It shouldn't really make a difference, although if you save as a "package" you know a folder within the project hasn't been inadvertently moved or deleted.

I'm wondering if you save as a "folder", assets in subfolders, that if another project uses the same subfolder and makes changes, if it doesn't somehow affect the first project that shares the same asset file?? When saved as a "folder" project. Perhaps a "package" project makes a new folder within the package and doesn't share folders?? I don't know because I haven't found anything that specific. Obviously if you are saving your projects as a package, that's not the cause of your problem, it does seem that the trend is to save as a folder project. I would try saving them as a package project if you are presently saving as a folder project.

I've never thought about that! I will try that! Thanks for the tip!