reginaldStjohn

solicitações de recursos vão para o fórum "Feedback Loop" https://discuss.cakewalk.com/index.php?/forum/8-feedback-loop/

I have not seen this. I have done this many times. Can you reproduce it with a brand new blank project? If it works in a new (not from template) project then it could be a correct project?

Is the track you recorded a stereo track or a mono track? Does it show two waveforms or one? Try toggling the stereo interleave button on the track to see if the mono mode makes it appear on both sides.

Just a thought for you. Your issue may be a timing issue where when your projects load up normally something is not ready, licensing or something else? So you could still try to debug wich VST is causing a problem by removing them one at a time, saving, closing, re-opening. Sounds like a pain but it might tell you which plugin is having a problem.

Or, if you don't want to mess with your master bus, for whatever reason, create a sub-bus to do the same thing. A bit redundant but some people like to leave their master bus alone.

Umm, So you just don't want it to make a cut in the previous take(s)? Maybe you can disable takes? If I loop record it always cuts the previous audio and then adds a take lane. "Sound-on-sound" should not mute the previous take(s). I suppose you could try to "lock" the clip over which you are recording and see if that prevents the cut?

If quick grouping doesn't work then I am not aware of another way to do it other than click on each control individually.

If you want to hear the audio of the same track on which you are recording you need to change the record mode to "sound-on-sound". Right click on the big record button in the transport bar and change the recording mode.

I successfully use MODO bass in Cakewalk. Haven't noticed any issues personally. I use the vst3 version. Just a for another point of reference.

Yes, what I meant is to un-select your device, shut down Cakewalk and then restart and then re-select. However, if you have un-installed and re-installed the driver then you have probably already done that step. Sometimes windows gets too many midi ports installed and you have to clean them up. You can try the following utility to see if it helps. I don't know what your issue is but just suggesting things that I have tried. https://support.korguser.net/hc/en-us/articles/115004269166-Windows-is-unable-to-recognize-a-USB-MIDI-device-

Have you tried to delete and then re-add your midi devices in Cakewalk? From what you have said it seems that the projects have something in them that is confusing the midi connections in Cakewalk.

Doesn't sound like an effect but maybe crackling or audio streaming issues. You would have to give us more information about your audio interface and settings to know for sure.

No, but contacting their support, as the pop up mentions, sounds like the quickest way to find out?

Can't say that I have but then again my default is linear so I probably would not have noticed. If you can reliably reproduce it you could submit a help ticket? Good luck

p. 244 of the Cakewalk Reference Guide says the following about "none" None. This option actually sets the Input field to Omni. With this setting the track will respond to any MIDI input coming in on any port (MIDI interface input driver) on any channel. I don't know why.

The Cakewalk Reference Guide mentions the "Cakewalk Core" folder locations on p 1854. It uses by default: "C:\ProgramData\Cakewalk\Cakewalk Core" for some files and "C:\Cakewalk Content\Cakewalk Core" for others On p. 1958 It mentions the following directory for Windows Media video profiles. \Documents and Settings\All Users\Application Data\Cakewalk\Cakewalk Core\WMV Profiles On p. 74 It mentions the following folder for custom toast messages %APPDATA%\Cakewalk\Cakewalk Core In addition there is a cakewalk core at C:\Program Files\Cakewalk for the executables

Usually that is caused by using direct monitoring with your audio interface and having the input echo on. If you disabled the input echo button in Cakewalk do you still hear what you are trying to record. If you do then it is likely that you have another audio path that is monitoring the same signal.

I don't know of any such command. Also, Cakewalk doesn't have "macros" normally understood as a play back of sequential commands. Some 3rd party software might be available that would let you automate this but I am not aware of any.

It will if you set a loop region around the area you are comping. This is just to try to debug issue.

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