msmcleod

Time signatures are entered in the Meter/Key view. Go to View->Meter/Key and add a time signature / key entries at the bars the meter or key changes. The staff view will automatically add a time signature/key signature change at those points.

I find the easiest way to achieve this is: 1. Expand the take lanes before you start recording. 2. After clicking stop, just solo the take you want to "favourite" Don't forget, there's always the notes area to the right of the MSR you can add to as well.

The Rode NT1 is a great mic, and has a much flatter response than the equally good but brighter sounding NT1A. Other great mics... Aston Sprit / Origin, any of the Lewitt LDC range or the Warm Audio range. If you like the sound of the SM58/57, check out the Shure SM7B - not an LDC, but a great vocal mic nonetheless and a step up in quality from the SM58/57. If this is for your own vocals however, I'd strongly recommend trying a few before you buy as you can't guarantee the mic will necessarily suit your voice. With a budget of $1000 however, you could also consider the Slate VMS system which would give you a huge choice of mic emulations.

Be aware that 16 bit and 24 bit are integer based formats, whereas 32 bit / 64 bit are floating point based formats. The jump to 32 bit is not the same as the jump from 16 to 24 bit, as being different formats they're not really comparable in the same way. Generally speaking, exports should always be 16bit or 24bit unless you're going to be doing additional processing to the exported file.

Try increasing your ASIO buffer size: If the slider is greyed out, click the ASIO Panel button and change the buffer size from the dialog that pops up.

@dogufo - here's a video showing you what you need to do in CbB: PART 1 - Importing the SY77 instrument definitions - this only needs to be done once. 1. Go to Preferences->Instruments 2. Click the Define button 3. Click the Import button 4. Navigate to C:\Cakewalk Content\Cakewalk Core\Instruments 5. Click on Yamaha.ins and click Open 6. Click on all of the SY77 definitions and click OK 7. Click Close to get back to preferences 8. Click on the Channel 1 of the MIDI device connected to the SY77, then hold down SHIFT and click on Channel 16 of the MIDI device connected to the SY77 9. Cick on "Yamaha SY77" 10. Click on Channel 10 of the MIDI device connected to the SY77 11. Click on "Yamaha SY77 Drum 1" 12. Click Apply, then Close PART 2 - Assigning MIDI Ports on a track 1. Insert your MIDI track 2. Choose the MIDI Output Channel 3. Choose which SY77 bank you're using 4. Choose the patch

Ælleden - please send us a crash dump. This should help us to determine the cause of the issue. Also, if you have a project that can reproduce the issue please PM me a copy.

Linked clips shouldn't affect external controller behaviour - they only affect editing operations on the clip event data. @Dana Elston - are you using CC messages for external control? It might be that one or more of your softsynths have their MIDI output enabled, and are echoing the CC messages to other tracks. Unchecking the "Enable MIDI Output" on these synths might solve the issue: You may also want to uncheck Enable MIDI Output on your default synth options:

The view state of almost everything is saved with the project. The key thing with workspaces is the "Apply Workspace on Project Load" - if this is checked, then the workspace will be applied to the project, regardless of what was saved in the project. If this is unchecked, then the project view will remain unchanged by the workspace - i.e. features hidden by the workspace will stay hidden, but the project's UI state will be largely retained.

The Track View splitter.

Not exclusively. They send out CC 93 ( Which is defined in the MIDI spec as Chorus or Effects #3 Depth ) and CC 91 ( External effects, or Effects #1 depth in the MIDI spec ). I guess it depends on the synth. If they're respond to CC 91 / 93 for effects control, then yes, otherwise no. If they don't respond to CC 91/93, you can use assignable controls instead. First check "Show Assignable Controls": You then have 4 slider controls to re-assign/play with:

It's likely the file location of the Garritan Steinway was different in your older projects.

When a keyboard supports Mackie Mode, it should show two sets of MIDI ports: one for the keyboard part, and another for the DAW control part. It sounds like you've picked the keyboard MIDI ports rather than the DAW control ports. Also, unless your keyboard has a specific SONAR or Cakewalk mode, you'll need to check the "Disable Handshake" checkbox within the Mackie Control dialog under the Utilities menu.

I'm forever putting my back out, and I've got an old shoulder injury I sustained while playing squash which plays up every now and then when putting PA speakers up. My usual go-to is my tens machine, which works wonders. On my shoulder, the pain is gone again for around 6 months... for my back, it takes away enough pain to allow me to move around normally while it sorts itself out over the next couple of days.

Aha - there is a two-click solution.... only just noticed it. Click on the right hand corner of the clip header, and you'll see a popup menu. You can select Render Region FX from there:

I was about to suggest that, but realised if you've got clip gain (or pan) automation, or any clip fx, they'll also get bounced. If you've not got any of those, then yes, it's the same.

FWIW I record everything on MIDI channel 1. The track MIDI channel overrides the MIDI channel before it gets to the synth (whether hardware or software). In any case, if you're exporting as audio to give to an engineer, MIDI doesn't come into it. I wouldn't worry about it.

Up-sampling on Render is when freezing, bouncing or exporting audio, whereas up-sampling on Playback is just when playing the audio in real time. Up-sampling will almost double your CPU usage, so you may want it only for rendering. Your audio interface doesn't really come into it. The way it works is, that audio is read from the track, then up-sampled to double the rate as it's passed through the plugins. It's then down-sampled back to your project sample rate before being sent out to your audio interface. Up-sampling can help reduce additional artefacts introduced at audible frequencies, when a plugin tries to add harmonics above the nyquist frequency (which is half your project sampling frequency). This is generally only applicable to plugins that generate saturation or distortion, and the artefacts although visible on an analyser, aren't (IMO) usually that audible. The down-sampling at the end won't introduce any additional artefacts as this is a simple process. It's worth mentioning though that: - Many modern plugins do internal oversampling, which can negate any benefit of up-sampling. - Not all plugins will work at an up-sampled frequency - some may even crash, especially your project is at 44.1K (88.2K is not a common sample rate). - Many plugins will sound exactly the same after you up-sample them, but will take up twice the CPU usage. So my advice would be, check each plugin first to see if it works, and if it makes an audible difference - if it doesn't, don't bother.

You can also bind a keyboard shortcut to open the synth on the active track:

The Realtek ASIO driver is the problem. It doesn't even pass the most basic ASIO tests using the test application in Steinberg's ASIO development kit. If you're using a Realtek device, use WASAPI Shared if you want to share the device with other apps, or WASAPI Exclusive for low latency.

I guess it all depends on what gear you have, but having gigged with various instruments, I would say from my experience: Easiest: Sax then.. Guitar ( 2 guitars, 2 stands, VG88, Laney Amp ) Keys - ( 2 or 3 keyboards with stands, 8U rack with sound modules, outboard mixer, keyboard amp ) Nowadays my Keys rig is cut-down. I can get away with one stand, a Studio Logic SL880, Korg X5D, SMPro V-Machine, a passive mixer and a keyboard amp.

Glad it worked out for you. If possible, could you capture a crash dump and send it to us with the plugin flushing set to 20? It would be useful to know which plugin is causing the issue.

It's not confusing when you read the paragraph afterwards: This statement is incorrect. As I said in the last paragraph of my original reply: If you set an output channel for the track, it will send all MIDI events out on that MIDI channel, regardless of what channel the MIDI events are. If the track output channel is set to "None", only then will it send MIDI out on the channels they were recorded at.

Plugin flushing sends silence to the plugin for a period of time, or until a quietness threshold is met. When set to 20, it's the equivalent of 20 seconds of silence. This is to ensure that things like reverb tails are cleared before moving on to the next export. Some plugins get upset with the plugin flushing, so setting it to 0 essentially disables it.