Jump to content

Henry Plawthiccens Jr.

Member
  • Posts

    52
  • Joined

Henry Plawthiccens Jr.'s Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. Hi, I've been running into (what I assume are) a couple of really frustrating bugs for a while and I'm wondering if anyone else has experienced this or has a solution. It's getting to the point where I'm considering jumping ship and learning a new DAW, which is not something I really want to do. First bug: -Sometimes I will discover (usually 10 minutes later after I'm finished with what I'm doing) that Logic has dragged a bunch of regions to the wrong tracks. I suspect this has something to do with a combination of duplicating a track, undoing and then redoing some things, and then dragging a region down as I have noticed that Logic will select multiple tracks when going back in the undo history. However this seems to be happening to tracks that I haven't touched in some time, and the regions it moves from the track seem to be random, i.e it's not moving every single region on the track but rather just a handful of them. This happens with both audio and MIDI tracks. I'm running into this very frequently but I can't seem to intentionally recreate the sequence of events that causes it. It's possible I'm just doing something wrong here but I've been using Logic for years and don't recall having this problem until pretty recently - probably the 10.4.x updates. Second bug: -Sometimes when switching flex time modes on a track, it will change every track in the session (even tracks that have flex time turned off) to that flex mode. This seems to happen most frequently when I switch to the "Speed (FX)" mode. Unfortunately this isn't undoable, so I have to be extremely diligent about saving before I change the flex mode. I'm guessing not a lot of people use that mode, maybe that's why I haven't found anything about this bug... I don't think my signature is updated, but I'm on macOS 10.12.6 and Logic 10.4.1 currently. Thank you!
  2. Hi all, this might actually be a FCP issue rather than a Logic issue, but I figured I'd ask here... I'm trying to import a Final Cut Pro XML into Logic Pro X. Everything APPEARS to work fine, except that nothing shows up in the timeline, like it's missing all the metadata or something. I've tried exporting it from FCP with various different settings but nothing seems to work. Just for the hell of it, I tried an older version of Logic I had backed up (10.1.1), and it gave me this error: "No Projects or Compound Clips were found in the selected XML file, so nothing was imported." Am I missing something simple here? Thanks, Jamie
  3. I could have sworn you used to be able to option-click the track header to do this... However that doesn't seem to work for me. Perhaps it's just a bug? Maybe it will work for you.
  4. I have never had this problem, and I've never used the "displays have separate spaces" option in mission control, so my guess is that would be the culprit.
  5. Does it show up in the audio unit manager? If so, perhaps you could try assigning it to a custom section in the plugin menu. Also, maybe look under AU MIDI-controlled effects instead of AU instruments?
  6. Wouldn't you multiprocessor support enabled? If it's spiking on one core running Kontakt on one core would make it worse afaik. It's worth trying though I suppose. A few of suggestions: -Make sure Kontakt and Massive aren't record enabled or selected if you're not recording them, and create a "dummy" audio track to leave selected when you're just playing back/mixing. -You can also adjust the process buffer range in Logic, which should have a similar effect to increasing the buffer size. -As stated above, try Kontakt with mp support on and off. I forget which one is default. -If none of those things help, you can try running Kontakt and/or Massive in standalone mode and use JACK or Soundflower+IAC bus to send MIDI and audio in and out of Logic.
  7. As far as I know you still have to symlink it manually. It works fine though.
  8. Holy crap. What an update! I like that automation alignment guides are now in the snap menu, it makes much more sense that way. I just took the LPX exam today and while I was studying I noticed that they were in the functions menu or something and thought that was weird. I thought this one was just a problem on my end: "It is now possible to adjust sliders in the Mixer when controlling Logic via screen sharing, Apple Remote Desktop, or other VNC clients." Good to know that that's fixed. Downloading it now.
  9. Based off my personal experience with this, it will probably drift a little bit and you will have some latency, but it should be usable as long as you are planning on bringing it together into one DAW eventually.
  10. You should be able to do it on an iPad 1 just fine. try Air Display. That being said, with a resolution and screen as small as the iPad 1, compared to your Retina's enormous resolution, the only way it would actually be useful would be for putting a plugin window on the iPad. And yes, the framerate is pretty sluggish but it's usable. The cool thing about it is that you it also responds to touch when using it as a secondary display.
  11. I found the JbridgeM icon really ugly, so I made one that looks like the Logic 9 AU Bridge except with the Logic X icon. 32 Lives looks interesting. I don't know if it's $69 interesting though. jBridgeM.icns.zip
  12. Am I the only one that is annoyed that I can't make the mixer full screen? It's like okay, I know it doesn't need to take up the whole screen, but I want it to. I hate seeing my wallpaper behind my mixer when I'm trying to work. Basically what I did is make one track, add a bunch of plugins until it filled the screen, then deleted it and saved the project as a template. I'm also annoyed that I can't resize how big the comments section of the mixer is, because I can't see all my notes unless I double click on the track.
  13. Honestly, I don't think this suggestion will work in your situation, but the first thing I would try is to get rid of the preferences (the preferences file is com.apple.logicpro.plist and com.apple.logicpro.lockfile and they are in ~/Library/Preferences. Temporarily move them to the desktop or something. Also, you could try clearing the audio unit cache, which should be in ~/Library/Caches. I believe it's called com.apple.audiounits.cache. Look in Console for error messages when you try to start up, and look at the crash report too. Look through them and see if there's anything that looks unusual that you can Google for. There's also a key you can hold when the splash screen comes up to keep coreaudio from starting, that might be something to try as well. I forget what key it is. Also, try temporarily moving all your audio units out of your /Library/Audio/Plug Ins/Components folder temporarily, if it starts after that it will make it easier to narrow down the issue. Do you have a time machine backup or a clone? Something is obviously corrupted, and if you can figure out what it is, you can restore it from your backup.
  14. Typically Apple expires certification a few months after a new upgrade is available. Meaning since Logic Pro X was available since July 16th 2013, chances are that Apple will expire Logic 9 certifications for example January 16th 2014. Meaning after that date, you can no longer say that you are Apple Certified unless you re-certify for Logic Pro X. I hope that answered your question? Thank you, that answers my question. If I want to re-certify, do I have to take the logic 101 and 201 classes again or can I just study up and take the master pro exam?
  15. Hey David, how much does it matter which version of logic I have my master pro cert in? I got mine less than a year ago, should I worry about getting the next one when it's available?
×
×
  • Create New...