reginaldStjohn

Yes, I believe that is normal in my experience. You would have to bounce the clip to get it to apply the melodyne changes and remove the region.

You should also check the option for plug-in load balancing and try both on and off https://www.cakewalk.com/Documentation?product=SONAR&language=3&help=NewFeatures.017.html

I don't know what is going on but a few things to try are change the buffer size you are using for recording. Also, if things are working normal and you just hit spacebar (not shift-spacebar) does it do the same thing?

For a reverb bus. 1. Create the bus and assign a reverb to its FX bin. Make sure to set the reverb to 100% wet. no dry signal 2. Make sure the output of your new bus is going to the master bus or your desired set of hardware outputs 2. The track you are using to record the vocal assign a send to the bus and adjust how much "reverb" you want 3. Make sure that the "input echo" button is enabled on the vocal track 4. Talk into the microphone and you should hear some reverb applied. Most interfaces have a direct monitor support where you can hear what you are recording directly through the hardware. You will want to make sure that you are only hearing what is coming from Cakewalk so you don't get a dry signal from your interface and a latent signal coming through the software.

On each track there is an input gain knob. At the top of the console view is where I access it. You can boost the gain up using that. You can also go to the process menu and apply gain to the clip, although that is a destructive operation that will actually change the gain of the clip.

Just for a second opinion. I have never had the "holding the 'n' key" down work for me. It does as you describes and just blasts snap on off settings to the DAW

I don't know why that happens. Try bouncing the clip and see if that makes me menu items show up again.

In melodyne to "zoom" in vertically you grab the end of the scroll bar at the bottom of the screen. The mouse wheel also can zoom in and out. I think this is what you mean by make the "measures" wider.

I don't know about quantizing just the selected transients. However, if there are just a few you want to move you can just select them and move them with your mouse with snap enabled.

I don't know how your trying to apply the cross-fades, with a short cut or menu option? When I have multi edited drums or the like one way that I apply crossfades to all of them is to lasso select all the desired clips a across the tracks and then cntrl-drag the edge of one clip till it auto cross fades with the next clip. This will move all the selected clip's edges the same amount. This doesn't work if the gaps are not all somewhat close to the same length. In that case I do the best i can with this method and then tweak the ones that were too far off. Just something else to try

I looks like your using the built in Realtek audio device. You may have to go into the windows settings or the Realtek driver settings to adjust the buffer if it lets you do that. The built in audio devices are generally not very reliable for audio workstation stuff.

From your screen shot it could be that windows is using your device. ASIO drivers cannot be shared. You will need to go into your windows settings and make sure that windows is using your built in sound device or nothing. Also, make sure that you have downloaded the most recent driver from Mackie.

I Don't think this has been mentioned. Check that you don't have a workspace or screen set selected. A screenset or a Workspace will remember the hidden state of tracks.

Not that I know of.

You say that it is in preferences, does that mean that you see your Q49 as a midi input device and it is checked? If so, then do you hear any sound when you select the VSTi track and play on your keyboard? Do you see any midi activity on the track? On the input of the instrument track make sure that the input to the instrument has your midi controller selected and using the same channel or omni

It depends on what plug-in you are trying to use. I don't have Autotune so I cannot help you with that. If you have Melodyne you can right click your clip and make a Melodyne region effect. If the plug-ins you are using are standard VST's then you insert them in the FX bin in the track view or in the console view. Of course you mentioned you tried MAutoPitch so you must know how to do that. What happened when you used MAutoPitch?

My guess would be no. However, if the ground loop was causing noise in the audio interface enough where it would mess with other signals, like interrupts or power, then I guess it is possible.

You could try this: https://www.microsoft.com/en-us/download/details.aspx?id=21 Although windows 8.1 is not listed as a supported OS on that page.

If that is the only track or you want it to happen to all midi tracks then you could just double the tempo. That would have the effect of playing back the midi track(s) twice as fast and the markers would all be in the right place. Doing it how you have done it you would have to manually move the markers.

Have you pulled up Task Manager (ctrl-shft-esc) to see if there is a program or task taking a lot of CPU or disk? Anti-virus or Windows indexing could cause this kind of behavior.

A shot in the dark but you could try to reset your plug-ins from the Preferences->File->VST Settings and then rescan?

Zo, I have this same problem. I even had a crash that was related to the control surface driver. I contacted support but they didn't really have anything to go on other then my dump file. They never mentioned anything about the weird text even though I brought it up.

All I can suggest is to double check that you have input echo enabled on the track you have selected so that the midi notes are "echoed" through the midi track to the instrument. If you can add midi notes manually to the PRV or Step Sequencer and the instrument is heard then that connection seems to be correct.

When I have seen this it is because there is a clip underneath one of them. It is not obvious but it seems to occur from recording multiple takes and then not selecting/swiping one of them before editing in the track. In the take lanes when you split a clip by swiping it should already create a cross fade with the next active take.

Just my opinion: If a plugin has a vst3 version I install that and not the VST2 versions. It is the current standard for VSTs so as long a a particular plugin works in vst3 mode I use it. However, Some DAWs still don't support vst3 or a particular plugin may not have a vst3 version so in those cases I use the vst2 version.