Jump to content

dmuckala

Member
  • Posts

    94
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

dmuckala's Achievements

Rookie

Rookie (2/14)

  • Conversation Starter Rare
  • First Post Rare
  • Collaborator Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

7

Reputation

  1. re: stereo vs mono, make sure 'include volume and pan automation' is unticked
  2. Ahh, and there it is. When they reversed the click vs. option-click behavior, it seems they didn't mirror it in this behavior as well.
  3. Thanks for all the replies. Hmm. This is an older session but not ancient. Was probably created under 10.7.9 initially. I just tested again by 1. disabled a track within a stack including unload (should we call this fully disable?) 2. disabled the stack 3. re-enabled the stack result: all tracks within the stack are now enabled.
  4. As of 10.8.1 disabling and unloading plugins in a track (or tracks within a stack) is now just a click, instead of option-click like before. This is obviously an improvement, but now if you have a stack of tracks with varying states of enabled/disabled within it, turning the stack on enables all the tracks within it. Before the prior state of the tracks within the stack were remembered.
  5. try focusing the 'main' window before you save and not the plugin window and see if it still happens. For me, that gets rid of the beachball.
  6. Glad this fixed worked for you as well. But yes, its a pain to have to go into the dreaded environment. Apple needs to remove VI output from the 'sum' input and then give us a midi fx that taps into the VI output port so we can optionally record midi from there only when we want to https://www.apple.com/feedback/logic-pro/
  7. Ok, I found a workaround for now I think. Go into environment>click & ports layer. in the box 'physical input', click on the cable coming from the 'sum' port and delete it. Then cable from whatever inputs correspond to your controller to 'Input Notes'. That should at least get you up and running until they fix. note: to get to environment, hold option and click on 'window' menu and you should see 'open midi environment' above 'Open Transport Float' menu
  8. Someone that recently updated Logic reported no double notes, although I believe they had already been on latest OS. It must have something to do with a preference file getting corrupted and a Mac OS update. I was on Monterey, and too updated (although I went to Sonoma) when I updated Logic. I also noticed when i went to settings/midi/inputs I am unable to delete inputs like I used to. Plus when i uncheck an input, a duplicate/ghost input is automatically created. so something is definitely screwy
  9. i'm also dealing with this at this very moment. Trying to delete logic preferences, and audiomidi preferences but so far no luck.
  10. I submitted this as a bug report, but here's my workaround for now. for me it happens primarily (probably only) with flexed regions. it seems to be related with tempo information in the clip either getting corrupted or read wrong. I've made lots of attempts at correcting tempo info on files, erasing tempo info on files, etc etc but these not only dont reliably work, but its very time consuming. So for now, the only way to reliably work around this is to put a flex marker where i want to make the cut, and then make the cut. I never used to have to do this before 10.7 came out.
  11. So very glad I found this topic. This has been ruining my imports at least going back to 10.7. Thankyou!
  12. I have been dealing with this issue as well for several versions. I was really hoping this would be addressed in 10.7.5 since i seem to recall references to it in the release notes. But sadly, it's still just as bad. Just simply recording a part, quantizing it (with flex) and then splitting it up to make other edits causes regions to shift, ends of regions to get larger or smaller, and various other chaos that makes editing in this way a real creativity killer, constantly having to clean things up instead of focusing on the music.
  13. thankyou, thankyou thankyou both. I have been TORTURED by this for months and months. Trying these fixes and will report.
  14. this is maddening. For the last several versions, i'm having to click and move around constantly to get midi region contents to be properly framed and centered in piano roll window below. This never used to happen and is totally annoying to workflow.
  15. I've been using this for a while...try this applescript. It bumps region gain up 1db. For -1db just change 'increment' to 'decrement'. I have this bound to a key command in Keyboard Maestro tell application "System Events" tell process "Logic Pro X" increment slider 1 of row 8 of outline 1 of scroll area 1 of group 1 of list 1 of group 2 of (first window whose value of attribute "AXMain" is true) end tell end tell
×
×
  • Create New...