Nomad76

Has any discovered a solution to this problem. It is really slows down the work flow. Sigh... I've been drawing them in for years.

You’re Welcome!

Just had this problem. After reading the thread, I tried right clicking on Logic Pro on the Dock and selecting "Options". Then I assigned Logic Pro X to "None". This fixed it for me. I'm using Logic Pro Ver 10.4.8 and OS 10.13.6

This has been one of the most useful threads I have come across. There is so much here. I've downloaded presets, I've followed the advice of others and got Keyboard Maestro, and I make my own presets now. Adding the presets to the logic browser has made my work flow faster, and it has opened up sounds that I didn't realize that I had. So Thank you to all that contributed!!!!

So far with initial test, fixed in 10.0.7 for me too! I was able to create stack track, add plugging, set smart controls, save as a patch, then recall the patch with the same settings. I was then able to tweak the parameters, and save and recall ok.I also was able to save the session and recall with the same settings. I used 3rd party VI's and Pluggins. So far, all was fine.

Yeah, I would love to be able to even setup patch templates so that I can load up a patch that is already tweaked and ready to go. But like you said, my trust is gone. Hey, do you know if there is a way to get the same function using a plugin or the environment? I'm seriously considering any alternatives that will keep all my work inside of logic (vs another DAW). Thanks.

I have spent days trying to get that feature to work right. I even called apple, and used the feedback form. This sucks. I like the ideal of stack tracks, but if that part doesn't work, it makes it useless. Who wants to spend hours tweaking a project, but not be able to recall the tweaks the next week. If anybody has a solution, I'm all ears. I would rather use logic than live.

I had a similar problem, and a similar frustration. My session would not open. But if I persistently tried to open it, it would open on maybe the 4th try, and crash soon after. I even tried the core audio fix, and I tried making session copies. Because of my stack tracks and such, import into a new session was messy and everything did not copy right. However, here is what worked for me, and solved my problem: It seemed that the session had got too big. I closed every program, and startup item that I could close except Logic X to maximize memory. I then got the session to open after repeated tries. As soon as this happened I did a "Save a Copy As". Now this Saved Copy had the same issues as the original, but this time when I finally got it to open, I went to "Project Management / Clean Up..". I deleted the files. I then deleted any unnecessary tracks. I also went to the Project Browser and deleted any unused files. Basically I did what ever I could to make the session smaller. I then saved this session, and my problem went away, and never came back! I hope that can help you, because it saved my life.

Thanks for the response, David. Some sample based VI's are very CPU intensive this will free up resources....but really, it might just be an old habit leftover from the analog world of tracking all my instruments first. So in your opinion, it is fine to just leave them as VI's and mix? I might try this. It would make for a smaller session file and save disk space.

Hi! My production is complete. I want to convert my virtual instruments into audio files for mixing. Logic allows you to Bounce In Place. If I do just that, the levels are sometimes at the bottom of the fader. I was taught to record between -6 dBFS and -3 dBFS. So now I have two choices: 1. Adjust the output of the VI - This messes up my mix, and adds extra time to the process. 2. Or use the Normalize function - Seems like this would greatly speed up the process. But after all my forum reading, this seems to be super taboo. Adjusting the output of the VI is the way I would normally do this; if it was hardware. But in the DAW, it also messes up my mix, and makes for a more messy session. When I just BIP. Its done. Also for some VI's, like my Native Instrument stuff, the levels are always low. Is there a better way or workflow? The Normalize just seems so, um convenient.