Jump to content

valve

Member
  • Posts

    122
  • Joined

  • Last visited

Personal Information

  • Location
    LA, CA

Recent Profile Visitors

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

valve's Achievements

  1. I have a lot of trouble with the "Set Start" key command. It often shortens my MIDI regions to an arbitrary point not fully to the playhead. Does anyone know what causes this?
  2. I've always been a little confounded by Logic's ruler. The numbers are so erratic & redundant when you try to really zoom in to do precise editing. I made a little video exhibiting a few examples with SMPTE timecode. Of note: ruler numbers don't match the LCD half the time the playhead isn't snapping exactly to each frame (visible if zoomed way in) when zoomed in, a flurry of repeating/redundant ruler numbers bombard you when zoomed in, numbers indicating, e.g. frame 1, are shown earlier than the actual point of frame 1 I wish we could set the grid's minimum visible value, like a clear grid of frames, nothing smaller; or a clear grid of sixteenth notes, no gradations smaller than that in the ruler.
  3. Oh nice, I dig that idea! Although my gut feeling is, I see "notepad" notes serving a separate purpose than color-coded / user stamped "comments." I'm not sure collaboration-based comments would have much use in a saved patch. But I'd love to see more accessible text-formatting features in the notepad. Colors, fonts, and custom font styles are quite clunky & cumbersome to access and manipulate.
  4. Shoot, it looks like both Photo Booth and Quicktime capture live computer audio in mono, not stereo. That explains why you're losing the panning info and some information in the effects. So if you boil this down, the basic question here is just: "on macOS, how do you record webcam video with live computer audio in stereo?" I was curious, so I researched this a bit. It's unfortunate, I don't think there's an especially simple way to do this. You'll definitely need a more involved app. I think the most common way people would do this is recording the video using OBS or a video editing app like Final Cut Pro. Those apps take time to learn to use though. You'd have to watch through some tutorials for the setup. Alternatively, this video suggests you can get Quicktime to capture stereo audio using a custom audio device you create with the app Soundflower. You set that as Logic's output device and Quicktime's audio input device. This might be the easiest solution, but the setup is still slightly hairy.
  5. If you save a patch to the user library, track text notes (in the note pad sidebar) should be included in that patch. Couple of useful examples: Third party instruments: you might write the company name, product name, and individual preset name for future reference when years later it inevitably becomes an old, inaccessible plug-in. External instrument patches: you might write the MIDI CC numbers that correspond to specific knobs on your hardware synth.
  6. Sends are a slightly messier option than I was hoping for, but it does seem like that's the only option. Roger that, thanks. Is your suggestion also to use a Send, from the Aux track, sending to the Print track?
  7. Soloing doesn't seem to work when my tracks are routed this way: Instrument Tracks > Bus 1 > Print Track > Stereo Out The Print Track is an audio track with Input Monitoring on so I can hear my instruments that are routed to it. If you solo an instrument track, you won't hear anything. If you solo-safe the Print Track, then you'll always hear everything, no matter what is solo'd. Does anyone know if there is a way to achieve this audio printing workflow with proper solo support?
  8. I think "Output 1" might be your problem. The output should be "Stereo Out" or Output 1–2. "Output 1" is just the left speaker. As for the audio quality being off: the "Guitar or Bass" option in the New Tracks dialog creates an audio track that includes a bunch of preset plug-ins on its channel strip. Maybe those plug-ins are effecting your sound in a way you aren't used to or don't like. Try just creating a normal Audio track instead, which is the same exact thing but with no FX. Then you can add your own plug-in effects manually to your liking.
  9. For sure, that makes sense. I recently noticed the "Spy on output to destinations" checkbox in Midi Monitor, so I gave that a try, and am seeing some erratic MIDI messages when starting playback and even well after stopping playback. See video here. Also attached are a couple pics of some of the nonsense that show up on the SL88's screen when it freezes. Anyone know what to do in a situation like this?
  10. I feel like a fool. brain lightbulb on, problem solved, thank you kindly fuzzfilth 🥲
  11. Logic tells you the peak dB value of selected audio in this dialog when you click "Search Maximum." It also indicates a percentage value. What could that possibly be a percentage of?
  12. This depends on what audio material you're trying to "apply ADSR" to. Here are a couple options though: Just do normal volume automation, like you kind of said in the first place. Utilize the key command "Create 2 Track Automation Points at Every Region Border" maybe (⌃⌘2). You can draw your own custom ADSR envelopes one at a time. Alternatively, put your audio into Logic's "Sampler" instrument plug-in to play it on a MIDI keyboard as a sample, and use the actual ADSR controls in the "Modulators" section. (By default, Env 1 is the volume envelope and Env 2 is the filter envelope).
  13. Thanks for the help guys. I'm still testing, but here's an update from your suggestions: I experienced the freeze up even after deleting every control surface from my list. This last one happened when I assigned one of the XY sticks to the Cutoff and Resonance parameters on the RetroSynth instrument plug-in and started moving the stick around. It was controlling the parameters fine for a few seconds, then the keyboard froze and stopped functioning. MIDI Monitor readout looks normal from that moment. It was sending CC 71 and CC 74 controller messages, which that XY stick is set to control. (MIDI Monitor lists those CC's as "Brightness" and "Timbre/Harmonic Intensity") I power toggled the keyboard, performed the same steps, and I'm not able to reproduce the freeze-up, it just works now. I also just realized you mentioned to toggle the "Bypass all Control Surfaces" setting. Just turned it on, so we'll see how that fares. However, it looks like this means I won't be able to map a knob (or an X/Y stick) to any controls, huh?
  14. The SL doesn't integrate with Logic as a control surface, it's simply a MIDI controller. It does have an optional, M1-compatible macOS app called SLEditor which just gives you a computer-interface of the controller's screen controls. I've seen the problem both with and without using the SLEditor app. When I do have the app connected and the freeze-up eventually happens, the app loses its connection to the keyboard. The controller's firmware is up to date.
  15. Logic regularly causes my Studiologic SL88 Grand MIDI controller to freeze up. I.e., it stops sending MIDI data, and the screen on the controller will suddenly show a random patch and stop responding to the screen controls. (This controller has a patch system that lets you switch between various internal configurations). I've had this problem for over a year and haven't been able to figure out what's causing it. I think it's a Logic issue, because I regularly use both Pro Tools and Ableton and never experience this in those DAW's. Has anyone experienced this before? Does anyone have a hunch as to what might be causing this? I can't seem to manually trigger the issue. It happens just inconsistently enough that I more or less get by but can't really figure out what caused it when it happens.
×
×
  • Create New...