I am new to Mac and Logic, and I can't understand why sometimes my MacBook Air's trackpad is registering Force Touch even though I am clicking only once. This is mostly happening when I solo a track and try to zoom individual tracks.
Why does this happen? Is it normal? I don't think it's a trackpad issue as it's only happening in a few cases in Logic. My MacBook Air is running macOS 26.7.1 and Logic Pro 12.4.
Hi Y'all, made this tune on a whim, was wondering if anyone had some feedback or ideas what to do to improve. Mix is not really where I want it so mainly want to make some of the sounds fit better.
If anyone has good ideas on things to add/change let me know!
I've been trying to learn music production along with music theory for a few months now.
I listen to a wide range of music so it's difficult for me to know what I want to make yet. I feel like a cow trying to find its moo.
I have installed Rave Generator on Logic and it works but is about the most unrefined plugin I have.
Instagram has picked up on my new musical arc and I keep getting recommended plugins. They're all fairly cheap (less than £40) but I worry about how well known they are.
This one called RAV3 by "TheProducerSchool" keeps getting recommended. It looks pretty good, like a full successor of RaveGenerator, however I'm afraid it's not very well known. The video demo and the graphics, to me, feel like they're a bit AI generated.
I understand everyone is at different points with AI (I'm an engineer) but I doubt I'll ever be happy to support AI imagery. Music is a creative thing, that includes the visual side of it.
So I guess I'm just asking if this plugin is any good? Or if this company is well known.
I could be overthinking it and I could be wrong. It's just some of the images of it are inconsistent, like "REVERB" showing as "REVERS" at certain points. Plus it has that piss tinge AI images used to have.
My dad's a composer and for now he's just saying to avoid buying tons of plugins, but I feel this one could be really helpful for me.
I'm experimenting with using the M-Vave FM-1 as a portable midi controller. I used to use an Arturia Minilab 3 but turns out I didn't really use it a lot since I'm not really a keyboard player, I wanted to use it mainly as a control surface and if I need to input some midi notes. My desk also doesn't have too much space so it's usually out of my desk. I like that the FM-1 can sit on the left on my keyboard so I can use it more.
I'm currently using the CTL-1 custom firmware which turns this into a full midi controller: 4 knobs, 4 banks, 16 switchable channels, and the keys. The sound still works on its own. I just turn off the volume if I don't want to hear the built in sound.
CONS: the knobs are stepped. The bare knobs (just bare potentiometers actually) are a pain to use so I had to put these knob caps which greatly improved its usability. I wish they weren't stepped but they work fine.
Still my main problem with Logic is it will always control the first instance of the plugin if it's used multiple times in the same track. I really wish there's an option to just control only the active/open plugin window, to prevent accidentally adjusting a different plugin which is a mess.
I've been really interested in using a control surface but the well known brands that work great with Logic are very expensive for me and they're not available in my country.
I'm assuming there's a setting I'm missing. I have an audio file with analyzed chords which I can put into the chord track, but it doesn't show under the audio region. When I copy and paste it into a new project, it shows there.
Am I indeed overlooking a setting? LogicPro help and web search turned up nothing.
I’ve built a series of Quick Actions for audio, including one specifically for Logic.
When you save a session in which you’ve created a Sampler instrument, you’ll obviously check “Sampler audio data” in the save dialog, and that’s fine. The problem is that if you also loaded your favorite piano, strings or organ from your Logic library in that same session, the project will save those samples too. You can quickly end up with ten copies of the same samples scattered across your computer.
Worse, sometimes you open an old session and Logic can’t find the original library where it expects it. It then asks you where you want to load those samples from and lists every location where they exist…
So I made a Quick Action to fix this. You scan one session, ten sessions, or your entire hard drive. “Clean Logic Sample” finds every Logic session (including Logic 6, 7, 8 and 9), analyzes its Samples folder and checks whether those samples exist in your library. If they match the library samples byte for byte, it lists them and lets you delete them. Once that’s done, Logic won’t find the samples in the session’s Samples folder and will load them straight from your library by default. I personally got rid of 68 GB of duplicate samples on my computer. The problem mostly comes from older versions of Logic, since file handling has been a bit “better” since Logic 11.
The other Quick Actions aren’t specific to Logic but are more general audio tools. Feel free to take a look; it’s my personal toolbox. (Find Mono, Find Key, Analyse Loudness, Normalize Peak etc..)
For those who don’t know what a Quick Action is: it’s a feature that plugs into macOS and lets you run an action with a simple right-click.
Installation is pretty simple: download the Quick Action you’re interested in, double-click the .workflow file, and you’re good to go.
Work on Mac Intel & Silicon with macOs 13 ventura or later
