Jump to content

Antiphones

Member
  • Posts

    270
  • Joined

  • Last visited

Antiphones's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Yes it crashed with and without plugins on the master bus. Always when it's been idle for a few mintues, never when I'm actually using it. It also crashes a when I open a session. But once it's up and running, as long as I keep using it, it's very stable.
  2. I almost never use Logic's plugins so I'm guessing the answer is yes. Relabl told me that plugins can sometimes "bump into each other" in Logic and that I should try to figure out if there are certain plugins which are incompatible with each other (which might be fine in another combination). The problem with this theory is that I have plugins from several manufactures crashing logic. It basically always crashes if I leave it idle for 10 minutes. The crash report always says it crashed due to a particular plugin, but it can be any one of a half a dozen plugins from the major vendors which it names. I've been using logic for over a decade and I've never had this problem until I upgraded to 10.6
  3. Hi, thanks. Yes many times. This problem has been going on daily for weeks.
  4. I upgraded to the latest version of Logic and it's crashing all the time. Each time a plugin is named in the crash report. But it's a different plugin every time. All the big vendors, Slate, Relab, Waves, Plugin Alliance etc... take their turn in the crash report. The crashes always happen when Logic is idle for a few minutes, never when I'm actually using it. This happens on any song I load in logic, so a huge range of different configurations and plugins and projects. I'm really having trouble seeing any common denominator. Any help would be hugely appreciated.
  5. Let's say that Logic's bug list has 2,791 bugs. Out of those 2,791 bugs, only 3% are deemed critical and urgent to fix by quite a few Logic users. That's 84 bugs that should be fixed urgently. Out of those 84 bugs, the Logic teams can fix only 21. Yes I'm sure you're right about this. I'm also a Pro Tools user and unlike Logic, it's automation is very accurate, what you see is what you hear. But Pro Tools has it's own set of bugs which are just a annoying. For example in Pro Tools at random, delay compensation sometimes just breaks and tracks go out of time with each other. Sometimes it's subtle enough that you just get phasing or flamming on the snare, you hit stop and play and it lines up again. That undermines your trust in the whole Pro Tools engine, because you never know when that might be happening on some small level without you noticing. It's arguably a worse bug than Logic's out of time automation. But given Apple's vast fortune, I wish they'd don't give the Logic team more resources.
  6. Thanks for letting me know. I'm having problems getting my head around how the Logic dev team could not have fixed this.
  7. I remember having this problem with early versions of Logic, but it seems to have returned recently (Logic 10.4.4) I will write some automation on an audio track and it does not match up with the audio. So I'll automate the volume of a plugin to match exactly with the change in section on a song, but when I play it back, the volume goes up a beat before the change. Can anyone think what I might be doing wrong here? Delay compensation is set to All and software monitoring is off. Thanks for any help.
  8. I'm not sure of anything in particular. But I think I'll now keep an eye on what I've just added when I notice the playback behavior. Thanks for the help.
  9. Thanks I'll see if reducing the history helps.
  10. Thanks for the thought. If this isn't a problem other people are having then I guess there must be something in common between my two machines. I'm not working from the same template so that can't be it. It doesn't happen on a new recording. It starts to happen as I add more and more plugins. Or at least that seems to be the pattern. What I can say is that I never have the problem when I have a new recording with only a few plugins loaded. But it's very common once I'm near the end of a mix (with lots of plugins) and someone asks wants some extra edits.
  11. I save them in various locations. Sometimes on my internal HD (solid state) and sometimes on internal or external drives. At the moment the mix I'm working on (which is having this issue) is on an internal drive (not my system drive). The problem seems to be more related to the number of plugins I have loaded. I'm not sure about that. But it does seem to get worse the further on I get in a mix, if I need to do some unexpected editing after I've already got lots of plugins loaded.
  12. Logic often refuses to play back when I hit play (spacebar) the first time. On the second attempt it plays. But this behavior is random. Half the time it does play on the first press. This make editing very difficult because I'm hit space bar constantly to play and stop and play. Since it sometimes does play with one press, but there's a delay (of random length), I'll press twice thinking it didn't play the first time, but then because it was going to play, it then stops. It's a nightmare to edit. I'm on Logic 10.4.4, but I've had this problem for at least a couple of years now and it happens on two different machines. If anyone has a fix for this I'd be hugely appreciative.
  13. I am having a problem where, once my MS setups get over a certian size, the on screen knobs start moving eratically in responce to my hardware controllers. The actual controls on plugins and the mixer (like faders an sends) move smoothly as expected. But the MainStage knobs move very eratically and often continue to move even after I've stopped moving a controller. I am also findin that MS sometimes forgets my controller assignments during a performance. I can still see midi coming in to MS (in the bar at the top) but I have to re-assign the controller to get it working again. Does anyone know why this might be happening? Thanks for any help.
  14. I'll have a think about new plugins. Thanks for your help.
  15. Not in front of Logic at the moment but the message was the usual can't process audio and midi fast enough that you get when the CPU meter spikes. I think you might be right about the cached files thing. After relaunching Logic and the session four times the problem disappeared. Having said that, I could not fix some other projects with exactly the same issue with multiple reboots. So that's strange that it worked on this one session but not others. The strange thing is that I never had this problem until recently, and now I'm getting it on almost every project I work on.
×
×
  • Create New...