Jordo

I didn't do nothin'.

Drummer bug test.zipHere it is with every track but the Drummer one removed. Very curious to find out what is going on.

How would I go about doing that here?

Note: When I "convert to MIDI region" and then convert back to Drummer (a tip I found online), the drummer region is now completely blank. This appears to be a bug. One I am in desperate need of a fix for because I need to extend a 10 second rock song into a 90 second rock song today, and I do not have time to program the drums individually. Any help would be greatly appreciated. Creating a new drummer region works but I need to also adjust what I have here. I can't think of a reason why it would stop letting me. Also, I have no idea if this bug will happen again, further messing me up when I need to do adjustments.

See the video. The audio is struggling, glitching, stuttering, which in my view is "crashing" but feel free to use another word. And the error is literally "system overload." That's what it says. I have tried both with similar results. I don't know how to read those. I did this days ago but I don't know where they are now. So after a lot of research, it seems these companies have not become compatible with the Apple silicon processor in all respects. Some plugins, but not all, and my Logic is seeing a mix of them. East West is now a "legacy" plugin so it's not compatible and you have to pay $200 for the update. Kontakt is a blend of compatible and not. Omnisphere no issues. My mac mini is a 100% fresh install with all the latest software.

Another new issue since updating Logic. I created these drummer regions when I started the project. I don't know when this happened, but now when I try to extend or adjust them, the extension looks blank, and Logic is telling me to "select a drummer region" even though it's already selected. I've tried googling this. This never used to happen with my older Logic. Is this a bug or am I misunderstanding something new in the updated Logic? These have not been converted to MIDI, these are still Drummer regions.

Hey everyone. Another post. My 2013 iMac died last month. Everybody told me to replace it with an M2 because they said it was incredible. They said the apple silicon processor is great, and that I wouldn't need much ram to do music, so I got 16gb ram. I was even told 8 would be fine. Well I have been working in Logic all day and wasting hours troubleshooting because it has crashed, given me system overload messages, and the audio is crashing and glitching out (see video I posted on reddit here: My friends who are computer nerds are 100% positive I have more than enough ram to make music, but I can't find any explanation for this. I have a handful of plugins and software going, typical orchestral stuff (EastWest, Omnisphere, Kontakt) everything my 2013 iMac could handle just fine with zero issues. I have done much more huge projects than this on a 2013 and no crashes ever happened. Can anybody help me make sense of this?

Well this sucks and hurts my workflow. It wasn't like that for me. It undid every little change I made. If I wanted the region gain to go back down to +3.2 after making it 3.2 and then +7.5, it did that.

I think 10.4.4, Logic Pro X, as the person above says that's what my old sig here used to say. I basically never updated it until now because my mac was too old. I don't really have that information though. My old computer was wiped and everything is new, so I have no way to check that I know of.

This issue absolutely did not happen in the version of Logic that I have. Changing the gain many times and undoing the gain is something I do constantly, even only a few days ago. So I was quite surprised by this behavior in the update. And yes my sig is out of date, I have not needed to post here in several years. I have now updated it.

I recently got a new computer and upgraded Logic, finally. Though now I am in the dark in a few areas. One of the new confusing things is if I gain change an audio region, then keep adjusting that audio region gain a few more times, when I hit Undo, it undos ALL of the gains I did, not just the last one. So if I turn a gain up +9db, then go maybe that's too loud, and go down to 3db+, then decide actually, 9db was good, and press undo, it all goes back to 0 again. It did not used to do this. How would one fix this problem? This is an extremely frequent thing I am always doing so any help would be appreciated.

So is it not possible then? With all due respect, you're making assumptions about my show that aren't really applicable. I'm not making a newspaper. I'm essentially trying to make a documentary. One sustainable, enjoyable and professional enough to warrant repeat listens (as many of our listeners have told me) and be a significant document that will stick around for a long time. I wasn't looking for advice on how polished or unpolished to make my show, as I already have strong, fairly settled opinions on this subject. "Not many will hear it" is never a good reason not to try your best. Otherwise I would have quit making music 20 years ago. And a good amount of people do listen to my podcast, so I want it to sound great. If someone asked me for advice about audio, I wouldn't really go in the direction of "who cares, nobody's listening." That's not how you learn and improve. I'm aiming for it to be as good as it can be. Also, I use strip silence anyway, because the show is intensely edited. It's not loose or unstructured. So that helps create region chunks to easily discard. Long pauses. Countless "ums." Gross lip noises. Motorcycles driving by. Ramblings that go nowhere and will save us a good minute if cut out. So "don't strip silence" is not an option here. Otherwise every cut, hundreds of them, would be manual. I just want to know if there's a technical way to be more accurate with stripping silence, as it greatly improves the audio quality of my presentation. Thank you

I have been wanting to ask this for years. I record and edit a podcast that me and my friend do. I swear, I spend so much extra time manually editing every single region because stripping silence is so inconsistent. I have tried every setting possible but it always ends up cutting words off, and/or leaving long trails of ambient silence once sentences or words are finished. Even when the silence is very consistent in a file, like a very isolated vocal recording with very very quiet ambience. I feel like I'm missing something about this feature. Is there some better way to do this? I really wish I didn't have to manually adjust every. single. region. Hundreds of them. Here's two screenshots as an example:

Hello. Often when I do automation in logic, the sound I am hearing does not sync up with what I am doing in the automation. For example, I want a reverb to start on the drums in the chorus. I will do the "wet" automation and start it right at that first beat. However what I hear is the reverb starting a few seconds before that. Same for when I end it. It is so frustrating that I generally do not use automation and have to find other ways around it. Why is this happening?

Thanks everyone. I am reluctant to bounce tracks because I am constantly making last minute changes to my mixes and experimenting inside the plugins. Oh well.