Jump to content

polanoid

Member
 View Profile  See their activity

  • Posts

    3,803

  • Joined

  • Last visited

  • Days Won

    51

polanoid last won the day on April 10

polanoid had the most liked content!

1 Follower

Recent Profile Visitors

3,642 profile views

polanoid's Achievements

Grand Master

Grand Master (14/14)

  • Great Support Rare
  • Great Support Rare
  • Great Support Rare
  • Superstar Rare
  • Problem Solver Rare

Recent Badges

1.7k

Reputation

201

Community Answers

  1. polanoid
    Well, if you insist on using a Shift-modifier KC for this, this is probably a good solution 😉
  2. polanoid started following Automation lane or point via shortcut , Midi Velocity issue , Logic keeps crashing when I adjust volume automation... and 5 others
  3. polanoid
    Looks like Logic sends a reset message (Modulation -> 0) at playback stop, so could you try disabling this setting (Settings->MIDI->Reset Messages->External MIDI) ? Also, you could of course try and change your keyboard's settings so that modulation doesn't affect output volume (which is a bit unusual anyway because usually you would use Expression CC#11 or MIDI Volume CC#7 for that)
  4. polanoid
    Well that would use DKD, no? Drummer tracks are assigned to DKD channel strips per default.
  5. polanoid
    If I may chime in here - "Animal" is the code name of Logic's Drummer (geddit? 😉 ) - AFAIR this has been mentioned on the forum somewhere - so the crash looks like it might be in Drum Kit Designer (AnimalSampler suggests something like that) - was that used in your crashing project? What leads you to that conclusion? I'm seeing a simple error related to memory allocation...
  6. polanoid
    That you can avoid by enabling this General->Editing setting so you will only be able to either drag horizontally or vertically, but never both
  7. polanoid
    Also, are there any audio tracks with active Input Monitoring ?
  8. polanoid
    Are you using any unauthorized/trial version plug-ins?
  9. polanoid
    Those two I guess but they will copy and paste all regions between locators as well, so you would have to manually delete those regions after using the Insert command
  10. polanoid
    Except that Cursor Down (or more exactly, the Select Next Event key command) doesn't seem to stop at the end of the event list, but wraps around and starts at the beginning when the last event is selected. This is a weird one.
  11. polanoid
    I was not able to reproduce anything unusual when "Close Window" is assigned to "2" (or any other numeric key for that matter) though.
  12. polanoid
    It's not that weird when one takes into consideration that the Shift modifier indeed ensures that all plug-in windows are closed (just try out by clicking on one plug-in window's close button while holding Shift). So the bug really is that, if the key command is a combination of only the Shift modifier and one other key, Logic will not ignore that modifier later on when it executes the key command.
  13. polanoid
    The only difference (though I'm pretty sure that it's not a benefit) will be that you can play your whole orchestra unisono by simply focusing the main summing track - that won't be possible with Folder Stacks.
  14. polanoid
    Nope, works just fine here, even with the highly unusual KC assignments you chose
  15. polanoid
    That would be the step width in time, which doesn't apply to value changes of course. AFAICT the step width is fixed to 1/100 of the parameter range for the Nudge Automation Up/Down commands
  16. polanoid
    There's actually people on this forum who want to help other Logic users ("worshippers" or not) with their problems. That's why it's called logicprohelp, I guess.
×
×
  • Create New...