Will.

☺ I don't think it would be a major re-write. Like you said: We can do this already, so no re-write needed - just an add-on perhaps? Copy those codes over to the Smart Tool, add the commands of Ctrl+Alt | Ctrl+Shift or Shift+Alt to activate the feature (Whatever the ingredients would be to cook this up ?) without sitting with a massive headache when doing it. Like this response. Yes, it would be a speedy editing edition during production. I'll be keeping my fingers cross that this gets noticed by the developers.

Lol, Hi @chimkin2 Thanks, I'm aware of that. I use it it from time-to-time when I do compression with custom shortcut keys. = SHIFT+"PLUS symbol." I believe the default shortcut key of "C" is for the control panel - hence the letter "C." No, my request is on the workflow as seen in the video without toggling between the clip view and automation view. What I forgot to mention is to say this to be with the smart tool. I better fix that right now. This is not a huge request. I was just thinking "Smart Tool" while editing, so why not ask for a request and see who like this quick workflow suggestion without that extra steps?

The current workflow to this, works 100% flawless. It's one of those second nature editing process in production. BUT . . . What if we can do our gain reduction with the smart tool in clip view, without having to do cuts to the waveform | or | by going into the automation view? Having the crossfades automatically built-in (or with NO visible crossfades) without slicing the clips on the selected region? Gain Auto.mp4

To use: Tick the FL Studio Asio Drivers. Its way better than Voicemeter or any other Non-Interface Asio Drivers.

And also the ability to remove it from the track strips in Track Control Manager.

I believe he is talking about his computer. I could be wrong. I own the surface studio 2 with no issues in this department. Is your windows up-to-date? What's your default playback device within windows? I've downloaded the Free Waves Studio Grid and it messed with my Audio Device in Windows changing it from my interface drives to that of the waves grid drivers. There's also some video apps doing this and some audio conversation applications. Try looking at these to make sure you're on the windows default drivers. Another thing: My Surface Studio only came with USB3.0 ports. So I had to buy an extra compatible USB 3.0 Cable for my interface and Midi Keyboard. Some of these devices comes with a cable that works in both 2.0 and 3.0 ports. For some reason my Focusrite and 49 Keystation as a bundle did not (This was of course 6 years ago.)

This is one I cant get my head around.

I was trying to make a joke. ?

But - Isn't asking questions the basic research? ? We first ask questions, before doing research. Soliloquy: Darnit! What is 1+1 again (asking the question) Let me check my text book (doing the research.) ??

The irony with this is: Only realizing now that, right after giving you advice - the samething happened to me. Definitely some Voodoo things going on here. ? Probably a bug.

This is going to be tedious on another level. Delete your plugins one-by-one and save the project to check for any compatibilities issue with any third party Vst or VSTi. If it doesn't solve your dropouts, you can always attach a mini dump file here for management to check.

?? I had those too before. Had to delete that entire project. Fix something and then another problem occurs somewhere. I'm dealing with an issue at the moment. Not a big issue though. It comes and goes.

But then it would be triggered to play the entire measure of the problematic region. I'm not saying it isn't so - but, it would play the same melody as is through the other Vsti too and not just a "D" note. I run into this from time-to-time too. That's easily detectable and an easy fix.

Experience with this is telling me there's an underlying "D" underneath the original clip. Exit the PRV and locate the section where you hear the "D" note and zoom in on the clip in the track view state. Highlight the focused clip and temporarily delete it to check if the "D" note reveals itself. If there's nothing: Try to record that piece over on a new instance on a separate track and delete the old track. Do not copy and paste things over to this newly created track.

I agree with Gswitz.

When this happens again. Just enter the Task Manager from the Taskbar or by pressing Ctrl+Alt+Delete and close it there. I'm not gona go too deep in yo why this happen - just know it's commonly due to some third party plugins | OR | Cpu and Ram overloads and drivers not closing/releasing in-time upon closing the program. This will happen from time-to-time, so you need to make a mental note of this.

Glad I could help. Yeah. It needs some refine work. Though, once you're use to it - it works well. I normally bounce to dry by removing everything that is selected and just flip between MONO or Stereo. Another useful method for you might be to freeze the midi track. Just hit the Snow Flake button on the track in track view. If you don't like the extra empty tail it gives you - you can always right click on the track and go to "freeze option" and tweak according to your taste.

If it's still in a midi state - it's in Midi. To bounce the Midi to an AUDIO Waveform you need to go up to the "Track TAB" and click on "Bounce to track"

Plenty of times! Same result. An interface has absolutely NOTHING to do with your export - that's the work of your DAW's render[ing] encoder.

What I normally do is - I load SPAN into the reverb buss and a gain plugin crack that up all the way to listen to how long the tail is after I put in my levels on the reverb. I hear what you say - but even with the KRKs at a steady calibrated level - some tails can't be heard without crancking the Reverb buss. Heres something to try: Render every track as stems and play it back in Windows. When you hear one locate the same track in CbB, with both effects bypassed on and off.

It does not. The only job of an audio interface is to let you get audio signals into the computer and out to your speakers or headphones. Whatever happens in mixing is entirely in the DAW. Perhaps a long tail from a reverb? I've uploaded a video on a bug where the groove clip feature does not cut of the notes by rounding the clip out - check that too. Oh-boy! I'm trying to think of possible causes - what about clips that has been bounced to a track | Or |freeze track fade out? Could be something thay is tailing into the silent part that gets cut of? Headache.

I always try to keep things as how it was send unless the client agree with me. People don't normally like it when you make changes to their work. This is why communication between you and the client need to be on point - really important. Like @pwalpwal said: Contact the client again and ask if it wont be an issue for him to resend every stem "clean" to you? The fact that he already said others dont normally find an issue with this - that's a barrier of causion if he was my client. It's easy to lose clients with this. I'm lucky enough not to ran into this issue. As I stated: I'm only there to clean/polish up the stems not to alter their work - unless it really is a problem in the mix itself. Though most of the time pushing it back or bringing to to the front by isolating it works everytime and maybe just widening it more, but i don't mess with their panning. Just my 2cents.

Question: Are you doing this on an Audio Clip or Midi Clip. On midi clips - this is pretty much a no-zone. Also you need to have the "Smart tool" selected.

Can't seem to get this video smaller than the required upload size for videos on the forum - so I'm gona have to send screenshots. Edit: @Noel Borthwick @jsg Download the video here: https://file.re/2021/08/07/test-2/ Or you can edit your Track Control Order first, then custom save your workspace and select "APPLY TO PROJECT LOAD" and re-save your project | OR | saving it as a custom default template - like how it is in my case in the video.

It's working I'm already shortening the video.