FuzzBub

I'll be very interested in this if I can do audio track comping (like on the full Logic Pro). I tend to doubt it will have that capability, at least at the start. But if somehow it dos, it'll be hard for me to resist.

I used to have this problem with traditional spinning external drives, but haven't ever since I transitioned to SSD external drives (with, as des99 says, a USB3 interface).

That was indeed it! Thanks, fuzzfilth!

Crashes or general auto-save certainly makes more sense than me doing it by accident; I'm just glad, whatever it is, that fuzzfilth had a quick answer for me (still have to confirm later tonight, but his analysis sounds very reasonable to me).

Thanks! That makes sense - I don't remember doing so, but I certainly may have accidentally at some point, maybe while in some kind of button-mashing frenzy. I'll check when I get back to my music computer later tonight!

This is a decidedly minor issue that doesn't seem to be affecting anything else, but I just noticed that every time I start a new project, it opens as "Untitled 4" instead of just "Untitled." Again, it doesn't seem to be affecting anything else, and it goes away when I first save the project under a proper name, so it doesn't really matter, but it is vaguely annoying for some reason. Any idea why it's doing this or what could be causing it? (I could try deleting preferences, but then I'd have to set everything else up again too, and it just doesn't seem worth it for such a minor issue unless I'm positive it will work. I was just wondering if anyone else had also experienced this peculiarity.)

For whatever reason, the first time I launched 10.5.1 after installation, it took a really long time doing the standard “updating AU plugins” check; I’m talking 5+ minutes, to the point I was considering force quitting. But it finally progressed to the project screen. After that I tried quitting and restarting several times (including a reboot) to see if the problem would continue, but each subsequent launch has been as smooth and quick (a couple seconds) as usual, so I’m hoping it did whatever strange updating it had to do the first time and I’m now in the clear.

Logic 10.5 requires OSX 10.14.6 (Mojave). According to your signature, you’re on 10.13.6. So it is incompatible with your current setup; you’ll have to update your operating system to run it.

It's an unfortunate (and fairly inexplicable) limit of Logic's MidiFx implementation. But when I don't feel like using Midi FX Freeze, I use Plogue's Bidule (which I have found invaluable in many ways in terms of midi routing, among other uses). Specifically, as Dewdman42 suggests, I open Bidule as a standalone, load up the MidiFX I want to use in Bidule, go into Logic's environment to route the IAC output from Bidule into Logic (and disconnect the keyboard midi routing from Logic), and then, when I record, I get the "processed" MidiFX notes from Bidule recorded in Logic's piano roll. I've never noticed a particular timing lag (although I'm sure a minuscule one exists), but as for me this is all studio-bound (and not live), I can quantize as needed. The disadvantage, of course, is that the Bidule project (with the MidiFX plugin) is not part of the Logic project, so if I want to come back and make changes on another occasion, I have to have saved and reload the Bidule project separately (or set it up again) and redo the Logic routing in my next session. But it's a pretty quick process and, I suppose, one of the (few, for me) downsides of working in Logic.

I know a couple of months ago, there was a thread on this forum complaining that the Arturia V Collection (version 5) was crashing Logic: viewtopic.php?t=128345 Anyone have any subsequent experiences? Or, more particularly, has anyone taken the plunge yet with the new version 6 who can confirm it's working OK? I know I could demo myself, and will in order to test the sounds if the crashes have been resolved, but if it's not going to work anyway, I'd prefer to avoid installing yet another copy protection scheme (the Arturia service center) on my computer, as one never knows which installation will lead to an overall meltdown.

I have found Izotope's RX De-Plosive works fabulously well (and, as an aside, the Mouth De-Clicker is an invaluable resource for me), Of course, going the Izotope Rx route can be a rather expensive solution, especially if one doesn't have use for the other plugins in the suite!

This happened to me the other day. Thought I was going crazy or something. "Happy" to see it's a glitch other are experiencing, which I hope means it gets fixed at some point.

I've found the "guitar strummer" script in the built-in Scripter MidiFX to be pretty good (or good enough for my purposes).

Thanks for these posts -- it's interesting reading. I've also found that some plugins (for example, Izotope's Nectar when extreme effects are applied) tend to slip tempo or otherwise glitch when I do offline rather than realtime bounce, but I've never really systemically tested it and can't prove it, so it's good to read someone who is taking a more rigorous approach!

I'm also not sure why you'd go to Yosemite rather than El Capitan. Like you, I stuck with Mavericks for the last two years because change is scary when everything's working fine (like it was for me). But just two weeks ago, due in part to wanting to get the latest Logic and Final Cut (among other programs), I took the plunge into El Capitan. Indeed, I specifically chose to do it now, with El Capitan about as "final" as it's ever going to get (and hopefully most of the bugs are ironed out), and before the craziness starts anew with Sierra. And while everyone's experience can obviously be different, I'm pleased to report that, for me at least, I've not encountered any problems under the update with Logic (or anything else) thus far.