DavidAndersson

That's a bummer. Well, I suspected it was a long shot anyway, but let's hope they add this as a feature in the future. Yeah, I've been using logic for 5 years so I don't think I'll stop doing this mistake anytime soon

Hi everyone! Have you ever clicked a few pixels to far to the left of a plugin in the inspector, and inadvertently hit the small arrow? It opens the Library, and it's pretty annoying when that's not what you intended. I do it from time to time, and now my hatred for this little arrow has grown so big I would like to banish it from this earth. That's probably not gonna work, so the next best thing is to at least remove it from my Logic. Does anyone know how? Kill my arrow. Pleeeaase. P.S Here's a stupid picture of the stupid arrow.

I'm still experiencing this in 10.3.1. When changing the buffer size, and hence reloading the Audio Core, Filter Pro Q2 on two guitar tracks got copies from another guitar track. I wonder what else changed.... This is terrible for a professional software

I'm not sure what you mean. I did it a lot yesterday (using "flatten and merge" on quick-swipped comp takes) and it worked flawlessly (as usual). When I click "flatten and merge" nothing happens, so I have to do it over and over again I try having different stuff selected when doing the command but nothing seem to matter. Oh well then, not too annoying.

Anyone else having problems when trying to flatten a take folder? I have a success rate at something like 10%, have to try it over and over again. Pretty weird. Hate the new "recent plugin"-thing too, so confusing since everything just jumps around there. Why do they implement such a feature with no way to turn it off? Other than that I think this version is quite nice. I get the feeling that it responds more quickly. Had to get the Gold Theme mod and do some tweaking to it though. The new look made my eyes sad

Yeah I know, but most of the time I'm not playing MIDI. I would like to choose if the selected track is supposed to be record enabled upon playback (like in Pro Tools). It's so annoying to have the CPU hit the roof unless I select a audio track. Guess I'll have to keep on waiting.. Antiphones, I'm on OSX 10.11.6 and Logic 10.3.0, updated my signature now. I've read that all processing for a single track have to occur on a single core, so if you have one extremely heavy track it will kill you project. In that case a solution might be to route the output to an aux and move some of the plugins there. Right now my CPU is ok at spreading out the processing, as long as I don't have a Instrument Track selected

Thanks for you answer triplets. Yeah, I started to avoid having software instrument tracks selected when starting playback and it made a huge difference. It's quite annoying but at least I'm able to work with heavier projects now. Would be really nice if it was possible to turn off automatic record-enable...

Hi! I don't think Logic is using all the potential in my CPU. The Activity Monitor says that around 60%-70% of the CPU is Idle when logics CPU monitor is full. I've tried messing around with the settings Processing Threads and Process Buffer Range without any direct changes. By the looks of it it should be able to go harder but there are pops and clicks when I play. According to the Apple Hardware Test nothing is wrong with my mac and Geekbench got the CPU to peak at 95% or something like that. Anyone seen something similar or know what's up?

I just had my first (At least what I'v noticed) change in a Instrument plugin, similar to what Arnaud described. I lowered my buffer size and afterwards my Addictive Keys was reset to default. It was pretty obvious cause it went from Rhodes to the default Studio Grand. Only had one project open at the time.

Nice! Thanks Flatliners. I kind of doubt it's the only thing causing the bug though, just my gut feeling, but at least there's something to try out and see if it helps. Anyone know if this has ben fixed in 2.3 / 2.4 ? Just found this line in the 2.4 release notes: Duplicating a track now reliably duplicates all plug-in parameter values. Sounds like a lot of things can be causing this bug. I'm thinking of updating to 2.4 just to see if these two "fixes" might be the end of it.

Yup. It just happened again on the same track. This time I'm certain that it was when changing buffer size and the Core Audio loaded. Made a save before changing it to 1024, applied the settings, same thing except this time only the Pitch Correction changed. Reverted to my save, did the same thing again but this time all plugins stayed normal. Yeah, xchrisxtopher. Definitely sounds like somethings wrong with Logic's memory or save files.

Thank's for your input! Even though I hate to hear that you're experiencing the same thing, it's great for the discussion so we might come up with a solution. I'm pretty certain i'm not causing it by being clumsy. Just now the Pitch Correction (Insert #1) got reset to the default setting, meaning 0 ms response time and chromatic scale, which I naturally wasn't using on any of my tracks. At the same time, the Channel EQ (#2) and the RDeEsser (#3) was reset, while CLA-2A (#4) and REDD37-51 (#5) was NOT. EDIT: Doesn't seem like the RDeEsser changed after all. Had a closer look on that one now and the settings were correct. Might just be Logic's plugins that are affected. When I noticed, I had been recording new vocals on that track, hence turning off and on plugins and setting the the Buffer Size to 32 which of course reinitializes the Core Audio. This is definitely the shortest time between having a working track until noticing it's "broken", but i might have done a couple of more operations before recording. What I DO Know is that i didn't have any single default PitchCorr or flat EQs in my project. Sometimes I get the feeling that Freezing/Unfreezing tracks and Undo/Redo heavy operations might be the cause but I haven't gotten to see the bug as a direct effect of it yet, so I can't be sure.

Sounds like there might be something weird going on with the DSP on your interface? Maybe Logic can't account for that latency. Do you get the same problem if using plugins that are processed on the computer?

Hi! I'm having a catastrophic problem. From time to time, probably only when running heavy projects, a insert plug-in might all of the sudden have disappeared or have settings from another channel. When I've noticed the problem I haven't even been working with that specific track! Most of the time I just check out a track setting because something sounds weird or have lost energy in the mix, and there it is, either gone or changed settings. I can't trust Logic when it's behaving like this. I have no clue what might be causing this craziness. I sometimes drag-copy plugins but I haven't seen any direct correlation with the problem when doing so. So, have anyone had experiences like this or any clue what might be the cause?