rpacker

Thanks for your feedback. I think what all of these plugins have in common (except PSP) is they are the latest versions of software that has since been revisioned or in the case of Altiverb, is about to be upgraded. It is just strange, because there are no error messages from Ableton Live or Digital Performer or Final Cut Pro, etc., just Logic. So it seems the auvaltool is the problem, because again the plugins do work.

The following plugins have crashed the au validation: Altiverb 6.3.7 Melodyne Plugin 1.04 Melodyne Bridge 3.2 PSP 608 Multidelay 1.1.2' I somehow have the impression the auvaltool is corrupted, but I'm not sure. Again, these plugins do work, even though they say "failed" or "crashed" validation in the AU manager.

Since I upgraded to Lion, the auvaltool tool is crashing with some of my 32 bit plugins. They actually still work, but there are listed in the plugins menu in an "incompatible" category. Has anyone experienced this problem? I am using the latest version of Logic in 32 bit mode.

Thanks David for jumping in. I have considered MainStage, however there are two issues: (1) it doesn't have surround capability and that is critical to my work. And (2), I would have to somehow transfer the track setup to logic for subsequent mixing and editing. (maybe this is easy?) Essentially what I do is bounce down the tracks on two other computers running Ableton and Machine (the audio that Logic is monitoring live), and bring the stems into Logic, into the same tracks that have been used for monitoring. At that stage, I turn the input monitoring off and begin mixing with all my plug-ins and levels in place. Logic's transport is not used until after the stems are brought in, mixed and edited. This process works really well until I discovered I lost 75% of my CPU while in live mode.

thanks for keeping this thread going, it's somehow therapeutic given I am going to have bury Logic in the graveyard of useless software (for me anyway...) I need to move quickly from live performance, to recording, to mixing/editing, to finished piece and keep all my tracks, levels, plug-ins, etc. consistent. I have a system that involves three computers, one of them (Logic) is dedicated to the mixing and finishing task, the others I am running Ableton and Machine. It's taken me months to figure this system out and I thought it was complete until I discovered the crazy core allocation in Logic. Show stopper! Oh well, I can hear taps playing now...

I have a rather specialized need: I want to use the same DAW for both live mixing and multi-track editing, so that all the effects and plug-ins are consistent from the initial recording to the final mix. It's true that Ableton is great for live work, but rather limited for mixing and editing. I am thinking of switching to Digital Performer or Pro Tools, but I have been using Logic for nearly 15 years, and I hesitate to purchase and learn new software. I wonder if this method of core allocation might change in the next version of Logic?

I have found that Logic works great for live mixing, except for this one problem, it only uses one core while in live mode. Do you know why Logic is limited to one core while in live mode?

Has anyone resolved this incredibly frustrating problem of only one core being usable in Logic when one or more audio tracks are set to input monitoring. This is referred to as "live mode" and Apple has acknowledged this. I am using Logic as a live mixer and I discovered recently that I am limited to only one of my four cores. I am using Plogue Bidule to farm out my most intensive AU plug-ins, but really, this seems like a major fault in the software. I am curious to know if anyone has found a good workaround or is using another DAW that accesses all the cores while in this so called "live mode." I haven't tried Mainstage because I need surround. Thanks!

With the recent Logic 9.1.1 update, I was disappointed to see that you still can't play video in external mode while in 64bit. Is there any hope for this capability on the horizon?

Automation moves properly in a snip/cut action in a small test file, but it seems when the project gets larger that it does not work consistently. I think this is the problem. It would be nice to know what causes this.

Please let us know the result of this fix as I have having the same problem with the @context showing up in the MIDI library associated with multi-instruments.

I think we are talking about different problems. I am concerned specifically with the @context items that appear in the library as shown in your third screen shot (above). They are messing up my midi assignments for multi-instruments.

There is another thread addressing this problem, but I thought I would start a new one due to the seriousness of the issue. Multi-instrument are breeding "junk" midi assignments called @ (=Context Name). They populate the library and seem to rob the multi-instruments of their correct midi assignments. The tracks only play when inputting midi from an external controller and the track is armed record. All other efforts to play fail. This makes it virtually impossible to use the Logic project. I hope this issue can resolved! Thank you.

I don't believe it effects audio tracks, the problem seems to be confined to midi tracks that are associated with multi-instruments. These strange @context files seem to multiply and rob the midi instruments of their correct output assignments. In fact, I noticed the midi out was working when the track was armed to record and you played midi from a keyboard, but not when the track was actually playing. Very strange.

I am using Vienna Ensemble Pro as a host for Omnisphere and Kontakt. All of these multis seem to be effected. Does anyone know what is causing this?