Jump to content

kotrl

Member
  • Posts

    35
  • Joined

  • Last visited

Personal Information

  • Mac
    M1

Recent Profile Visitors

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

kotrl's Achievements

Explorer

Explorer (4/14)

  • Reacting Well Rare
  • Collaborator Rare
  • Dedicated Rare
  • First Post Rare
  • Conversation Starter Rare

Recent Badges

11

Reputation

  1. What's the relationship between these three things? - Quantize settings in the region inspector - Quantize settings in the piano roll - Quantizing an individual note by pressing 'Q' Some related (but less important) questions might be: Which has priority? Can a region be quantized to one setting, then notes individually quantized to another? Does Logic always remember the note's unquantized position?
  2. I possibly had this on Ventura too (now on Sonoma), at least it was recent enough that it must've been. But I haven't had the issue in quite a while. Latest version of Plugsearch and Logic now
  3. Ah… I’ve been making hazardous Keyboard Maestro macros today and it must’ve selected that
  4. Earlier I dragged a box over some notes in the piano roll and something I wasn't expecting happened. The box I drew stayed there, and two handlebars appeared on either side (like the ones you see when you select text on iOS). Dragging the handlebars resulted in all the notes getting longer or shorter, like if you were to select the notes from the edge. I definitely didn't imagine this, but after starting Logic to take a screenshot, I can't make it happen again.
  5. I use both PlugSearch and Keyboard Maestro and had exactly the issue you describe: immediate crash when clicking the traffic light. Haven't encountered it recently though, maybe it was related to a particular macro…
  6. There's a trick when drawing automation (I think with the marquee tool) that lets you automatically create ramps, but I can never remember what it is. I think it's a modifier, and then you drag inwards.
  7. Thanks very much! I'll try that on my next project.
  8. I am, of course, sending to two different buses?
  9. Supposing I want a short delay in the verse and a long one in the chorus, what's the least fiddly, simplest way? I thought the secret to an automation-free life was to put the different sections of my vocals (verse, chorus) on different tracks, apply my different send settings there, and then send the tracks to the vocal bus. But the downside here seems to be that effects like reverb and delay are sent before the processing on the bus channel. So that takes me back to doing it on the bus channel, fading one send down, and fading another up, on each section with automation, which I can make a bit more efficient with the marquee tool and aliases of region automation. Might it possible to switch between Send A and Send B with a single lane of automation? Or is there a better way of splitting them out to different tracks?
  10. Oh you're right! It seems after flattening the take folder all the regions work like that. I just didn't know the click zone existed, so thank you!
  11. Thank you David! I wish it was possible with crossfading regions. After flattening my comp folders I usually go through and refine the crossfade point, which I've sped up a bit with a macro but seems a bit slow. Maybe I need to do things the other way around.
  12. 😯 How do you change the start and end point of two regions at the same time like that? I'm using a fade tool but the cursor never changes to that icon
  13. That is very helpful. The plug-ins I found to be causing the issue are in my template, but disabled in most projects. RAUM came up several times, although not in reference to JUCE Timer
  14. To my memory the trials are only limited by outputting silence every 60 seconds 😯
×
×
  • Create New...