Will.

There's a reason why its called "rogue peaks." That is why I say, it can be anything. If it's an audio clip and happens at the beginning, then someone abruptly trimmed/cropped it down to where there was information on. If it happens exactly when the clip starts where there's nothing - even when it seems there might not be something (there's always something/noise in an audio clip) a fade in will definitely fix it. If it's randomly as you say, two frequencies might be fighting with each other for space. The ear then hear these buildup at random times withing the mix. Buildups dont occur only in the low end area, but throughout the mix and might be masking the actual culprit. Try giving the audio clip in discussion a slower attack from the clips its competing against - even when you have a fade in on. It can be a ping pong delay whose feedback is too long and loud that clashes/feeds into a certain track. It can be another track that's not aligning up with the loop when its enabled. It might be how it was recorded, so when ever you feed it through some time processing effects it shows its face at "random." I something spend 30mins searching for it going through each track. Trying to fix such problem with SOLO or MUTE wont give you what you're looking for. You have to locate it while the track play. You said it yourself, that it happens on the same place, but at random times.

Agree. The Antivirus might be blocking it. Avast and Windows Defender are two most annoying AV software causes, but highly recommended for me.

This depends on if its an audio or midi file you're using. It also sounds more like rogue peaks. So you might want to tame those peaks and dynamics. It might need a cut in eq instead of a boost in the frequency range. You can also try to split the clip and do crossfades by ticks value with the region zoomed in until you see the tick grid lines (I like to work in value of 2 ticks - more surgical with my workflow.) If its audio and between phrases, you can always add in silence in between. It can be clipping inside the plugin. Its hard to say from the information you gave on top. It can be a lot of things - even just a spike from your CPU.

? Weird! Double message? ?

Yet, its still the same thing - it reverts back to ZERO. Cakewalk is a safer step. It prevents accidental reverts on crucial editing, by placing the second tab on a different key. I'm well equipped in every shortcut key in CbB and all its menus. So there's no need to explain the Ctrl+Spacebar or any other shortcut. Point is: Every DAW has its own language and its reasons.

Activate it by Ctrl+W and when ever you want to RTZ (if it's already activated) just press "W."

Love both VOLT 276 and Volt 2, but ultimately went with the Apollo twin as it came with full pack bundle and thousands of other stuff with the MAC at the time. Volt 2 comes with Melodyne Essential if I remember correctly.

It brings a constant level to all your vocal and guitar recordings that I guarantee you. Vocals and acoustic guitars you can at -6dB every time. Honestly: I haven't tried out the M4 yet, but from reading a few reviews and pictures - no one mention it it has a scale. So what the use of having meters, but you're still blind. A linear scale meter would've been a nice touch.

Oh flipfops! I was suppose to make a video. As soon as i'm done with these clients.

It'll walk and run.

Lol. No problem. Then again, there's always the case of you can never have too many ins or outs. They always come in handy every day even in the most innocent setups. You might want to look at this one for its LEDs meter.

Hey Olaf. With comp trimming, I think you have stretch on, thats why the information in side the clip is moving. It's trying to adjust to the tempo its stretched too. I might be wrong. I will take a look at the project as soon as I get free time (if its still available.) I'm not paying full attention to this thread, right. Doing my yearly check up. Dentist after this ?

Instead of buying a new interface, why not adding a 16 channel mixer with LEDs to your setup and connect your Presonus to it? Plus, you'll have more ins and outs too. How do you like that sauce?

Appreciate your suggestion. I just think that's more unnecessary work that will bring/introduce problems. Sticking to dragging the end and start out then groove clip loop would be a thousand times better and safer.

Could not care less what you say here. So lets agree to disagree.

Lol. You just wanted me to make a video scook. Revert.mp4

Isn't that what the OP asked? I'm aware of this double tab in another daw and it basically does the samething, just named differently. Cakewalk just makes it easier for the user.

Yes. Press Ctrl+W to activate the jump to start/beginning option.

Maybe its a setting already available, but for years I had been looking and can't find it. Can we have Cakewalk to obey Midi clip lengths when bouncing a clip to not crop/trimming the start and end empty spaces when draaged out to fill the measure/bar as seen in the video attached. I know when we groove the clip for loop, it obey's the command, but as soon when doing edits - it does that trim/crop again. Comping.mp4

No, you can't. Why is it bothering you, if i may ask?

Don't know why I made the old room black, but that's the issue I have. Guess a 4K ultrawide screen doesn't help either.

Yeah. It is a great little limiter especially for a plugin that is free. I often send an e-mail there to keep the developer interested to consider redesigning its UI. I agree. This is really interesting to know. I do have the Youlean. Now you've just made me curious and eager to test this. This is a must when I get home. Normally when I encounter this, I know theres something i didn't EQ right in the low end.

This makes me excited. The Concrete Limiter sounds great.

There's literally thousands of information about this on the WWW. Buffer size is the number of samples (which corresponds to the amount of time) it takes for your computer to process any incoming audio signal. A higher buffer size will result in greater latency (delay) and the higher it is set (larger number), the more noticeable it will become. That means that if you set the buffer size lower (smaller number), then the processing will take less time and the latency (delay that you hear) will be decreased, making it less noticeable. However, reducing the buffer size will require your computer to use more resources to process the data. So, this is a balancing act: the smallest-number buffer size will be better, but it may tax your computer’s processing power, resulting in errors. If you have a less powerful computer, you’ll likely need to increase your buffer size, both while recording and mixing, to keep from encountering errors. Typically, you’ll want to use the smallest buffer size your computer will tolerate without getting errors (glitches/distortion/cracks/gibberish what ever we call them.) The more plugins you use, the more CPU resources you eat up.

A fundme account would be great to get money for the licencing of the Concrete limiter. ?