xchrisxtopher

@Alan Shields @David Nahmani - thank you both for so kindly mentioning my website WLPR! I also whole-heartedly recommend David’s books. The lessons are straight-to-the-point and immediately rewarding, launching the reader directly into the fun of crafting music in Logic Pro. I continue to pick up copies and follow along with the lessons 🙂

I’ve been digging in deep with Flex a lot lately and have learned that Quantize-Locked editing is not what many of us had thought it to be. Quantize-locked audio ensures that the transient markers of Q-reference tracks are applied at the same location across a group of tracks. In the case of drums, the transient marker for a snare selected as the Q reference is applied to the kick, overheads, etc for locked editing and quantizing. While this works well for Slicing and okay for some other modes, unfortunately this falls apart with Polyphonic mode. Sure, Quantize-Locking ensures transient markers of Q references are applied across a Polyphonic group. But as I’ve found, it doesn’t mean edits will result in perfect phase coherence. Just try hard panning your stereo guitar tracks, group the tracks together, and then quantize with Flex. I bet you’ll hear the sound of the guitar shift around. Throw Voxengo’s free Correlometer on the Stereo Output and watch the signal go in and out of phase at different frequencies. An unfortunate bummer! The workaround I’ve found is to bounce multimic signals together into a new file/region, then edit the new region with Flex. I hope this helps!

If it helps, I’ve replaced some of the screenset key commands to load the Pointer Tool and Gain Tool. For example, “1” now loads the pointer tool, and “2” loads the Gain Tool. I’m hoping for a Gain Tool click zone in the future. But until then I find it easy enough to swap the Screenset keys as I never use them.

Hey there, just wanted to say this really helped me out with laggy UI issues with both Logic Pro and Logic Remote meters. Thanks to this thread I deleted my 3 novation controllers from the Control Surfaces Setup window, and then the laggy UI problem was solved! Thanks so much.

No, it was never possible to preview pads by clicking the instrument icon in the step sequencer (just to make sure I tried it in 10.7.1 and indeed that does not work). On the other hand if you open Drum Machine Designer and hover a pad with your mouse, the icon is replaced by a speaker icon, and you can click the speaker to preview the pad. Perhaps that's what you're remembering? Over here clicking on the pads while the Step Sequencer is idle does indeed result in the playback of individual sounds. But does not appear to work during playback. Sometimes I have to click on the icons a couple of times to "wake" Logic Pro up to play the individual sounds. Edit: A row has to be selected first in the Step Sequencer before playback of a sound will commence. Still only while playback is not occurring.

If it helps, I'm using an HP VH240a monitor that I'm very pleased with. No glare, plenty big enough, 23.8 inches for $170 USD.

Hi Drew, Thanks! And again, I recommend demoing first. Who knows? What works for me might not be applicable to your situation. I only offer the idea in hopes that it saves you gobs of time and energy.

David's advice is brilliant and a great suggestion for developing deep intuition for this kind of work. I did want to offer that Melda Productions has an amazing plugin called MAutoVolume. Which is a plugin that adjusts the level of audio over time. Think Automation, but in a real-time format. Certainly no automated process works 100% of the time. But MAutoVolume might be worth at least demoing if it can save you many hours and streamline your workflow: https://www.meldaproduction.com/MAutoVolume Also - I'm not affiliated with Melda at all. MAutoVolume is a permanent fixture in my Projects for both music and VOs.

For anyone else (though this question is unrelated to the original thread) - the Symphony Desktop from Apogee works with i5 processors. I used to use mine with an i5 iMac before upgrading to an M1 Mac mini. And I just tested it with an i5 Macbook. Works as expected.

Hi FabJoe, this issue occurred for me as well on both an M1 Mac and Intel iMac with 10.6.3. The way I solved the issue of Waves plug-ins not showing up in Logic Pro was to follow this support doc from Waves. Specifically step #3: https://www.waves.com/support/how-to-find-your-plugins-in-logic-pro-x

Another one: Logic Pro should analyze the available space on a disk before exporting video. Not so much a problem for me anymore. But I do remember the juggling act of trying to make space on external hard drives for exporting movie files. The movie would take forever to export. And after waiting 10 minutes or so for an export, Logic aborts the export process because of a lack of hard drive space. Ideally Logic Pro would estimate the resulting file and "see" if the destination had the appropriate space before attempting an export.

Happy to help! Reading over my original post, I make it sound like adjusting the X-Over is a time-sensitive workaround. It’s not. You can adjust the slider any time to correct this glitchy behavior. I do it as a matter of fact now whenever I load Space Designer. And definitely worth submitting a support ticket! I’ve done the same

Hi Cinningbao, I've experienced this glitch as well with Space Designer. What has worked for me is to adjust the X-Over as soon as you hear the glitching occur. Manipulating the X-Over seems to stop Space Designer from freaking out. This workaround has worked for me on 3 Mac systems (Macbook Pro, iMac, and M1 Mac Mini). I hope this helps!

Oh, I got a good one. Bring back the language in Bounce, Export, and other dialogues that key command Command and . (period) can cancel these processes. Or! Add a "Cancel" button to those dialogues

Hey Dan, thanks for your reply. Yes, I am aware of the Groove Tracks. And that's an interesting suggestion, as I've never considered using it for aligning multiple vocal tracks. Definitely have to give it a try!