Jump to content

Scardy

Member
  • Posts

    15
  • Joined

  • Last visited

Scardy's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hey David, Yes better late than never thanks for your reply. Just looked up info on deleting automation. While it refers to the eraser under "Delete single point", it does actually say you can drag over automation points to delete. So I think it should still function as I'm expecting when I drag over points. And I can even drag over multiple points sometimes to erase them. It just usually never deletes ALL points properly and seems to always have this bug, even when trying to delete one single point. I can't imagine no one else has this bug? It's so prevalent for me that it's surprising no one else has reported it. Thanks for your help though. Best, Jason
  2. Anyone else having this issue? I drag the eraser over nodes in automation and it does nothing a lot of the time and even looks to be trying to erase in completely different areas than where my cursor is. See video. Happens almost every time to some degree. Link to video example: https://app.box.com/s/09g6uwbcrt361orxv32m22njqxtgjjc0
  3. I am also having this problem. Logic is full of incredibly annoying bugs. I have NO idea why they make you have to uncheck so many things in the main window and piano roll window to turn off catch playhead. It's astounding. One tip I do have is that if you hit "Ctrl" click (on Mac) on the catch playhead button it brings up a few selections that you have to uncheck. But I've also already done that and it automatically turns back on whenever I close the piano roll and re-open.
  4. Hi, Every time I start up my computer (15" 2018 model MacBook Pro w/ Touchbar - Catalina 10.15.3) Logic automatically loads. I have definitely checked the two main areas that have settings for this 1. system preferences/users/login items and 2. the Logic options which are accessed by right clicking on the dock icon (see attachments). Incredibly frustrating that neither of these settings have worked for this. If anyone has any other solutions please let me know. It's almost less the annoyance of the app starting up as it is the options to turn this off not actually working.
  5. There is no default quantization on. I only quantize in the piano roll after recording.
  6. Thanks Atlas007 for the reply. I never use the quantization in the Region inspector. Just in the Piano Roll.
  7. Hi, I've had an awful problem with Logic's quantization for some time. It's making the function very hard to use. It mostly works fine but sometimes, I think usually when I try to apply swing, the quantization freaks out and moves the MIDI notes to the wrong beat or division. It also only occurs when I select all the MIDI notes in a region. When I go and select the note individually the quantization applies correctly. This is not because of the region start/end either. My regions are always right on the grid usually on the downbeat. I've attached images to show the original notes and then the quantization applied. Also sometimes getting different behavior from pressing Q as opposed to clicking the Q button in the piano roll. I am always quantizing in the piano roll after MIDI recording. Thanks for help
  8. Thanks David, actually tried that one too and same result. I just figured out a work around where I can create 5 software tracks - one of them is the bug duplicate and the rest are completely new blank tracks. Don't know if that leads to any more ideas but at least it works.
  9. Oh and one more little tidbit - it doesn't matter what track I select, if I DUPLICATE a track, it will automatically create the same track that is created when I create NEW track. In other words: Say I have 10 software tracks in my project all named Track 1, Track 2, Track 3, so on. Tracks have different instruments, plugins, auxes, etc. The bug starts occurring, and when I "Create New Track" it automatically creates Track 3. Now even if I go select Track 1 and hit "Duplicate Track" it still creates Track 3.
  10. Hello, I've had this problem many times before but there's easy work arounds so I don't get too flustered. However, it really frustrates me so I'd like to find a solution. When I'm in the midst of a project (i.e. have lots of channels and regions - audio and MIDI), I go to create a NEW software track, and instead of creating a new, blank track, it duplicates an existing software track. I don't know how Logic is selecting which track to duplicate. It will duplicate the same track no matter which track I have currently selected. I don't have the "Open Library" checkbox selected in the new track dialogue. Also, if I reset the duplicate track I've just created, it will reset the original track as well, which is extremely annoying as I've lost channel settings this way before, and not realized it. Any help is greatly appreciated. Thanks! Jason
  11. Just a heads up I fixed the issue. I had to uninstall and re-install Maschine. I think some of their new updates or something must have been messing with the core audio in the existing projects. Thanks
  12. Thanks for the reply angelo. I don't believe it's the plug-ins because once I turn core-audio off and open an existing project, then turn core audio back on everything is fine again even with a ton of plug-ins in the project. Also when I start new projects and add plugins it works fine.
  13. Also forgot to mention I have an Mbox 2 that I run monitors through as well. It was working today and then stopped turning on when plugged in. I updated the driver today but still nothing.
  14. Hi all, Thanks for the help. First timer here. So today I sat down and opened logic with an existing project and I got the spinning wheel immediately once the project is loaded. I had the same issue with all existing projects, but not with new projects. New projects work fine. I did come on the board and saw a post about disabling core audio and checking the 3rd party plugins, which I proceeded to do. As a control, however, I opened a new project, disabled core audio, and opened an existing project. With core audio disabled, the project opened fine. I then immediately re-enabled core audio, and everything still works fine so it doesn't seem to be any plugins but something about Logic and core audio upon loading up. Any thoughts on this? A couple notes: - Running Logic Pro X 10.1.0 (Just updated today upon running into this issue) - Macbook Pro from mid 2014 OSX 10.10.2 Yosemite (Just updated earlier this week) - Processor: 2.2 GHz Intel Core i7 - Memory: 16 GB 1600 MHz DDR3 - Just updated a bunch of Maschine drivers in the past couple days as well Any help would be GREATLY appreciated! Thanks, Jason
×
×
  • Create New...