Will.

Then you're doing it wrong yes. ☺ What you want to do is: Create a New Bus or Aux Track and insert Vocal Rider on it. Next you want to route the OUTPUT of the vocal to the Bus or Aux track itself. Finally send the instrumental file as a SEND to the plugin Input. It should read something like (if my memory serves me well) "Vocal Rider Mono/Stereo (Input 2) Bus/Aux." This will activate once you press play. Sorry I can't send you a video right now to demonstrate this - i'm not at my home studio. Out with the little one.

Heres the thing with Windows computers I don't understand. I have an intel i7-6th Gen Cpu. Just added another 8GB of Ram a week ago, so I sit with 24GB of Ram (need one more 8gb to make that 32gb official.) A fellow producer has an i5 - 9th gen cpu and 32gb ram and performs better than my system.

Try it - your picture will come to life.

Heres the pudding again. Weird.mp4

The studio Instruments Suite: Are they strictly 32bit? And why do they appear in the Audio FX category? I've downloaded them over a week ago when I did my entire system over. Didn't bother to install them until now, cause I needed the String Plugin. Going crazy looking for them, just to discover their in the FX category. Is this correct?

Works fine here. Latest build 058. Infact you don't have to click on the track header. I click directly on the track view to where I wana paste. The only time i do drop the f-bomb - its when the loop is on and I do a paste.

Lol! Language please.

Thanks. Although: 😣 Let's not take what was said out of context by reading too much into it. After all, I did say whatever the ingredients will be without giving themselves a headache when doing this (or something like that.)

☺ 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.

Yet, another complaint from me with the 058 build (and I've doing this a lot with this build.) I believe it's the 4th time cakewalk just cuts out a Vsti. This is not the typical cutout during playback where it resumes after a quick double TAP on stop and play with the spacebar. You have to re-insert the Instrument and shift the midi file on the newly created insert for it to play again. This workaround isn't a big deal, but after a few times - frustration starts to kick in.

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.

Another bug in this builld. Previously: when I've set my LinkPFsendMute to "True" I couldn't hear the effects on a bus, if you mute or solo the routed/group Aux track - which have always been my preferred setting. In this build, it does not obey the selection on Mute with an Aux track. It obey's the selection on solo only. Meaning: When I solo the Group-Aux track - no effects are heard. When I mute the Group-Aux track you hear them.