David Baay

As rsinger indicated, this fact suggests that the keyboard is sending events with a different MIDI channel than the Korg is set to receive... or you didn't properly connect the OUT of the keyboard to the IN of the Korg when you moved the cables. Also as he suggested, you should work through the setup one step at a time: 1. Keyboard MIDI OUT to Interface MIDI IN, and interface MIDI OUT to Korg MIDI IN. 2. Create a MIDI track in CbB, set the input to the interface MIDI IN - Omni. 3. Arm the MIDI track, hit R to start recording, and play some notes on the keyboard. 4. Stop recording with Spacebar, disarm the track, and confirm notes are recorded in the PRV, and are on MIDI channel 1 (double-click a note to see properties). 5. W to rewind and Spacebar to play the track and and verify you hear sound with headphones plugged into the Korg. 6. Add an audio track to CbB with Input set to the appropriate interface channel and enable Input Echo on it. 7. Start playback and verify you get meter activity on the audio track and hear audio through headphones plugged into the Interface (if there's an echo, disable Direct Monitoring on the interface). 8. Stop playback, enable Input Echo on the MIDI track, play some notes on the keyboard and verify you get meter activity on both tracks and hear audio through the headphones. If all these steps work, recording and playback of MIDI and audio and realtime perfomance with input monitoring will all be working. If any step fails, let us know exactly which one, and we can troubleshoot further.

Don't know why you keep insisting that you have to sign up. Below is a screenshot of the first link that search brings up: http://bandlab.com/membership I get your point about the challenge of getting there from the Sonar page, but making false statements to support your argument isn't helpful.

You need to have an audio track in the project with Input set to the interface channel to which the audio output of the Korg is connected with Input Echo enabled on the the track to echo the signal to the output of the track and on to the Master bus.

No biggie; I almost didn't notice it but am pretty sure K has been the default since advent of clip muting while Q was already reserved for Quantize. I've joked previously that K stands for "Kwiet". ;^)

Yes, looks like the clip is muted, but the default shortcut is K, not Q. If you loop-record in Comping mode, any part of a take that's overlapped by a later take will be muted. Right-click the Record button in the transport to see recordng preferences, and see the Ref. Guide for how it all works.

Not true. Google 'bandlab membership' and any of the first half-dozen or so links will get you to a page that shows the cost. But I agree the 'Bandlab Membership' link on the main Sonar page should take you to http://bandlab.com/membership instead of account log in/sign up.

I recommend getting familiar with the keyboard shortcuts for From = Now, From= Start, Thru = Now, and Thru =End. I've restored the original shortcuts F9, F10, Ctrl+F9 and CTl+F10 for this very frequently used operations. F7 = Go to From and F8 = Go to Thru are also indispensible. I don't know offhand what the new default assignments are.

The 'Interment' (chuckle) has always been flooded with misinformation. You can't blame Cakewalk for this. ;^)

Delete and Cut are actions that will be added to the History list without affecting the Record action. If you want to discard the recording and remove the Record action from history, you need to Undo (Ctrl+Z) the Record action before taking any other action that adds to the History.

When drwing new notes in a track with a single lane of MIDI, the distance at which a new clip is created when drawing a new note in the PRV is anything over 7 beats from the end of the most recent note. It can be avoided either by initially drawing the note within that distance and then dragging it later as necessary or by dragging out the boundary of the clip in the track view to encompass where a new note will be inserted in advance. Having multiple lanes in a MIDI track can complicate this as it's difficult or impossible to control which lanea note will go into when drawing in the PRV. Unless this has changed, I believe it will usually default to the earliest/lowest-numbered lane, but this can be unpredictable based on the recording/editing history of the track, and focusing a particular lane before drawing in the PRV does not guarantee new notes will go into that clip's lane.

The suggestions to use the tempo map are correct for this situation. SMBAN is for aligning the time line with a real-time performance that already has a variable tempo. I suggest setting snap at the smallest note value in the MIDI at that point to draw a tempo change at each note/chord.

When recording a mono source, you need to select only the left or right channel of the stereo input pair as Input to the track. You can bounce the stereo track to Split Mono and discard the silent channel to fix what you’ve got without re-recording.

The last time I looked only Pro Tools and Reaper support this (i.e. defining the value of a beat to be a dotted quarter with three eighths per beat), and it's optional because not all 6/8 and 9/8 compositions have a triplet feel. In CW and every other DAW, a "beat" is always a quarter note and has two 8ths. This also affects how tempo is defined - bpm is always quarters per minute (not the dotted quarters per minute of compound time).

I suggest you uncheck Use ASIO Reported Latency, leave the Manual Offset at 0, and try recording the metronome output via the loopback setup suggested by reginaldStjohn. The recorded click should be laid down approximately that 262 samples late (usually a little more due to unreported hardware/firmware latencies). If it's still early, execute Reset Configuration File and try again. If you can get the metronome recording late without compensation as expected, then you can re-enable automatic latency compensation plus or minus a Manual Offset to dial it in to the sample and then move on to recording your DI guitar. If you continue to see the metronome recorded early without any compensation applied, then I would have to think there's something on your system like ASIO4ALL or Steinberg's Generic Low Latency ASIO Driver interfering with Cakewalk's using the Focusrite driver exclusively.

Your setup should be working as expected if channels and ports are correctly assigned. If you record MIDI, do you see CC64 messages in the PRV controller lane and/or Event List, and they're on the same channel as the Note events? If so, try playing back that recorded MIDI to EZ Keys. If not, double-check that the track Input is including the Icon controller port with no channel restriction (Omni) and the Arturia and Icon are both set to transmit on channel 1, and retry recording.

I had not updated to V15 yet so I had a go just now. I got installation errors until I executed Clear Cache in Settings as suggested above (and also by the Waves support page for "Installation failed – Please check your internet connection"). All seems fine with existing projects after updating and re-activating licenses.

Because the underlying code that determines what should be drawn in any given situation hasn't changed, only the way it's drawn. I've previously reported a number of crossfade-related display issues that have been fixed. What are the specific scenarios/steps where you're seeing problems?

Go to HKEY_LOCAL_MACHINE\SOFTWARE\ASIO in the registry and remove the 'Generic Low Latency ASIO Driver' key. Cubase installs this and it's notorious for causing issues with Cakewalk. It's not needed for using WASAPI with onboard audio or for an external audio interface with its own ASIO driver.

Go to the Cakewalk application folder in Program Files, and rename AUD.INI. Cakewalk will replace it on launch with one that defaults to WASAPI. Not sure why this happened with WDM; likely some issue with the response of the device driver to initialization. EDIT: It'll be in Cakewalk\Cakewalk Core for Cakewalk by Bandlab.

That's not likely an inherent issue with Instrument tracks but some error in the conversion process causing the track to be associated with the wrong synth in the first place. Because inserting synths in FX bins is such an old implementation, I wouldn't be too surprised if there are issues with audio/MIDI port enumeration changes when deleting the ones in the FX bins. The right sequence of conversion steps should avoid that. I would recomment the following approach to avoid having ports crossed up or having to recreate the MIDI and synth audio tracks, preserving the existing FX and track settings: - Save a copy of the project, save presets for any synths that aren't using a default, and then delete all the synths from FX bins and re-save it. - Using the original project as a reference, insert the first missing synth by Insert > Soft Synth, and don't have Sonar create any tracks for it. - Assign the input of the audio track to that previously hosted the synth in its FX bin to the newly inserted instance, click the icon to open the synth UI and assign the relevant preset. - Assign the ouput of the relevant MIDI track to the synth in the rack. - Select the MIDI and Audio tracks, right-click and choose Make Instrument. - Test playback. - Repeat the insert, I/O assignment, Make Instrument and test playback for each synth.

Enable Ripple Edit Selection, select the region from the cutoff point up to the controllers that you want to keep (PRV or Event List will probably be easiest for this) and delete. Ripple edit will close the hole created by the delete, bringing the controllers back to the end of what you're keeping.

LPF in Gloss EQ or LP-64 EQ or built into the plugin or somewhere else? Does it matter how low the cutoff is? Any particular instrument plugin or you can reproduce it with several?

There are still situations where MIDI timing can drift progressively out of sync by a few samples per iteration when looping at random points at certain tempos but it's usually avoided by looping exactly on bars/beats. I believe Jamstix uses song position so I might try experimenting with that later.

Alt+Ctrl+C gets you Copy Special and Alt+Ctrl+V gets you Paste Special with the option to include Tempo Changes.

Glad to help. Separate Synth Audio and MIDI tracks should be okay as well, you just need to get the audio into synth track via the Input from the Synth Rack rather than the FX bin.