Sir Hannes

Hi, in the key command menu, there is shortcut "Transpose region/ event by +1 half-tone or automation by +1 step" (or similar). My Synth-Lane is on +5% and I want to replace this mouse fiddlings to get it to zero, it changes the sound still and this behavior I experience a lot. I searched for key commands to decrease "steps" and set it to 1/64 and later to a sample. But this doesn't change the behavior. Neither 1/64 nor sample brings mir close to zero, they all stay within +/- 2 increments. Is the labelling "step" misleading here? Note: In the German version they use Schritt and Schrittweite, I translate this to Step and Stepwidth, but may vary in the english version. 🙂

As I just read about this feature and @des99 gave me the ultimate hint, I will report it now. Thanks for confirming!

Looking at the waveform it could be a voice, then true, no workaround. If it is a atmo, and thinking on surround/ ambisonics, these are often atmos, then it might be a workaround. 🙂

First I clarify, I am not searching for help, my intention posting this was to share with @Frankenhaus that there are many issues going on, and he and others might get too. I hope that he/ they then feels not alone with maybe anger about Logic. Screenshot is from yesterday, upper lane shows the actual number. A video would show, that the 17% is the value where the playhead is. If it comes closer to a ramp all 17% numbers changes parallel/ together. Also look at the first automation point: it should be a 0, right? 2nd lane the same: the automation point at the ramp should be 0, right? Hope I could translate it now better. 🙂

Ah see, ok. for the 2nd: I do not mean overlapping audio. I mean "cut out some of the meat which might causes the audio engine to produce that bug" - Then bring them together. Then do the crossfade.

Yes for big projects and yes for smaller as well. I get 150-250 tracks work well but then inserting any plugin confuses the automation, very bad. Right now I am in a small project, 15 tracks, and a PlugIn Alliance plugin gets the honor to let the Logic automation counting the automation values. This looks like a live number counting up or down, so where the playhead is I get the accurate number of a parameter. I can't tell you which parameter, I have 3 parameters of that plugin automating. And all automation lanes counting parallel the same number. And I can't switch this off (nor even on). I feel helpless. Attached picture is another bug, also with small projects but with big I really shout out loud. Under any circumstances Logic changes all (!) automation lanes into random parameters. This is so terrible as while mixing I rely on these. Top priority parameters are always on top first. Parameters I have to re-work are open too. Now look at the picture: Tempo? Formant? Drive? Why! 😄 A solution sometimes works: Before quitting LogicPro always switch of the display of automation. I am grateful btw. to this forum that I can share this pain in my stomach with other people. 🙂

Indeed! The video cutters used tape more longer. I watched them sometimes cutting on these tables. Not looking back-friendly. 😄

Hi Landmeter, try to delete the crossfade plus the curve numbers. Then do it again. I work a lot with crossfades and this happens many times without a reason I know. But this little workaround helps. If not, cut the end and the beginning of each file and bring them together. At least here this works then.

I try it: all playback shortcuts I use won't work anymore if Chase for Notes is activated. 😞 Start playback from begin of region/ note, from last locator etc. do nothing now. Unfortunately I can't set in hundreds of regions the midi notes a few ticks away.

Chase for notes I was searching for, thank you @des99 🙂 I activated it. But now there is more ongoing: If my region is followed by a region with the same note (C-0), it will no longer be played. It only plays if I jump inside of the region. That doesn't make any sense - I want to be able to play from the start of any midi region in my session. I can only fix this if I change the note of the following midi region, i.e. from C-0 to any like C#-0 or B-1. Is this a mistake or is it supposed to be like this? @oscwilde Freezing/ bouncing even on a M1Pro take a while for 64 bars, I need 12-30 steps of BIP till I am done, plus deleting the created all *.wav-files afterwards. Freeze doesn't allow me re-adjusting VI parameters. 🙂

Got an advice to try out Shure AONIC 50 Gen2 BK. https://www.thomann.de/de/shure_aonic_50_gen2_bk.htm

Nice description for the standard process everyone should now. Reminds me on cutting tape. 😄 As soon as your hand starts hurting due so many mouse actions you might want prefer sth like a 3rd party plugin from iZotope or anything else. 🙂

Discipline, better audio station system, learning your technic. The last one is the longest yet best one: you realize you don't need so many plugins, you can create your sound more efficient. Back in the days every track in my session had a compressor. Today only on these tracks they really need. Saves 20 instances of various compressor plugins. See? 😄

Hi! Imagine you have a 64 bar note for an ultra evolving VI sound with lots of automation, you work your way forward bar by bar, but each time you have to play from bar 1. Does a new function solve the problem of extremely long midi notes (i.e. atmospheres/pads that build up extremely slowly) so that you no longer have to play them from the beginning in order for the midi on command to be triggered? Maybe it was a dream I had, but thought there was a feature in one of the latest updates?

If I understand you correctly, you get clicks and dropouts using bypass, right? That's normal in Logic, annoying, and either it is the job of the developer of the plugins or of Logic Team. I would appreciate a de-clicker or a "volume ramp" as Steinberg Wavelab has it.