David Baay

Where do you get that people have something against using a mouse? The OP actually 'Liked' your post. Just because people continue to discuss other options, that doesn't mean they're discounting your suggestion. I answered the OP's question as asked, though I might use the PRV velocity pane myself in many cases. It would depend on where I was in the UI when I decided to change the velocity and whether I needed it to change proportionally; if you're in the Track or Console views, Event Inspector is convenient. Dragging in the PRV can't change by percentage, and changing by a small amount like 5 levels can be a bit fiddly to pull off with precision, especially if you happen to be on a laptop and using a glidepoint pad. No big deal, either way. It's always good to know different ways to skin the cat.

Uncheck 'Use Paste Special Options on Paste' under Preferences > Editing.

See this thread on the old forum for a possible solution: http://forum.cakewalk.com/lost-breverb-presets-m2883066.aspx

A longstanding issue that apparently never got fixed: http://forum.cakewalk.com/Do-external-inserts-go-quite-when-soloing-an-Aux-track-or-Bus-with-an-external-insert-m3475781.aspx

Just to beat the dead horse some more... ;^) To me the easiest approach is to put the part on its own track and use the MIDI Gain (Velocity Offset) control on the track. This is a fixed offset, not percentage, but if you're just tweaking up and down by 10-20 levels, there's very little effective difference between a fixed offset and a percentage change. Or, better yet, get the audio output of that kit piece going through its own track (or synth mixer channel), and tweak the audio level. The best approach for a given situation depends on how the synth is responding to velocity, and what you're going for in terms of tone. And, of course, I always have to advocate... just record the dang part in real time from a MIDI keyboard! Much more fun, and the more you do it the better you'll get, and the more natural and 'grooving' your MIDI parts will sound. It's easier to do a little quantizing and tweak a few hits here and there than to place and adjust every event with a mouse and PC keyboard.

What about dragging MIDI clips from other tracks instead of from the browser?

Also noting Max tick is 479. If clock is not 480PPQ, you might need to click All, then None, then check RPN. That said, I reported an issue to the Bakers a while ago that empty lanes for controller types that had been completely deleted were perisisting in the PRV, and couldn't be permanently eliminated.

Two things: - To reduce by a percentage, subtract that from 100 - i.e. 80% to reduce by 20%. 75% would be subtracting 25%. - Remember that the inverse of a multiplication factor, x, is 1/x. So the percentage that reverses a 20% increase is not 80%, but 1 / 1.2 = .833 = 83.3%.

I second the motion. Leave your onboard sound enabled and set as the default audio device for Windows, browsers and other generic multimedia apps, reserving your Focusrite interface for Cakewalk and other ASIO-optimised apps. If you need to hear multimedia audio through your studio monitors, use an external mixer.

If it requires a reboot to fix, I would be more inclined to suspect some issue with the mouse driver. Is it wired, and using a generic Windows driver?

I can't repro that. I would guess some corruption has occurred in RAM, and close/re-open (or save/close/re-open if necessary) will fix it. If not, you might need to recreate one or more tracks to fix internal indexing.

Hi Vidhi. Welcome to the Cakewalk forum. The video tutorial thread linked below is a good place ot start. If that doesn't get you going, let us know at what point you're getting stuck.

The track lane is for Writing (or drawing) an automation envelope that generates controller messages on playback. To record actual MIDI controller messaages, set the record mode to Sound on Sound, arm the MIDI track for recording, start recording, and 'perform' on the mod wheel in real time.

Just for the record, the Patch Point/Aux Track funcitonality that made this possible was introduced in October, 2015: http://static.cakewalk.com.s3.amazonaws.com/cakewalk/news-archive/Welcome-to-the-October-2015-SONAR-update.pdf

I'm not sure what this means. You should be able to hear the audio metronome when enabled for playback; it will just be out of sync with the music if the project tempo isn't matching the recording. Fit Improvisation is requires a MIDI click track as a guide. The best 'automatic' solution for audio is to drag-drop the audio on the timeline to have Melodyne extract tempos. If you don't already have some flavor of Melodyne installed, you can install the trial of Melodyne Essentials using the 'Install Add-ons' option on the Apps tab of Bandlab Assistant. The trial expires, but the drag-to-timeline function will continue to work indefinitely. Depending on the material, Melodyne can do a good job, but the Essentials version will sometimes mis-detect the tempos by a factor of 2, and doesn't allow for any correction. Also, it interpolates tempos at 8th-note resolution which I find to be excessive, and potentially problematic, expecially when the tempo is essentially fixed with just a bit of rushing/dragging drift over time. Personally, I prefer to do tempo extraction manually using Set Measure/Beat At Now. You can find a summary of the process here:

Pretty faint. If you Google 'Focusrite analog bleed problem', you'll get a some hits. Not sure how common or noticeable this problem is with different interfaces, but I do recall it coming up in reference to Focusrite in the past.

I meant no input signal - either nothing connected or a silent audio source like a keyboard synth, tape/CD/MP3 player, etc.

Yes, input gain on the interface.

Make sure you have each track;s Input set to only your keyboard's MIDI port, not Omni - All Inputs. If the problem persists, right-click Instrument tracks, choose Split Instrument Track, and check the routing of the MIDI track outputs. I haven't seen a problem, but a number of people have mentioned soft synth routing getting crossed up recently - usually in connection with connecting/disconnecting hardware MIDI devices with a project open.

That's gotta be bleed between the analog output and input sections of the interface. Sounds like the input sensitivity is cranked, which is exacerbating the issue. Try recording a flatline on a track with no input, and a drum track or something with loud transients playing back with no metronome. If you hear that playback track in your recording, it's an analog isolation problem.

I would htink almost any workstation could output a MIDI click on a specified channel Even if that channel also had a musical part on it, assigning a suitable note number/pitch to the click would make it easy to extract to a separate track. And when all else fails, Set Measure/Beat At Now is your best freind. I record a lot of improvisations without a click, and set the timeline to the MIDI after the fact using SM/BAN, both with fixed and deliberately variable tempos.

Yes, SMPTE sync may yield better MIDI timing precision, but it's not going to help with the tempo issue. And I suspect there are few hardware workstations that output SMPTE.

Though it's most common to use one MIDI track per channel with mult-timbral synths, it is possible to put some or all of the 16 parts on separate channels in a single track a la Type 0 MIDI files. And, of course, drum synths are often driven by a single MIDI track, using separate audio ouputs to allow processing the kit pieces independently.

Recording with MIDI sync, and reading MIDI files are two different things. If a MIDI file is opened in Cakewalk, any tempo changes in the file will be read into the project. Also, when you say "We want to capture what we are playing live and not re-do tempo after the fact", that's a different situation. If the MIDI was originally recorded into a sequencer running at a constant tempo, the sequence will play back correctly from SONAR when recorded at the same fixed tempo, but aligning the timeline to the variable tempo with tempo changes is never going to happen fully automatically. There are may ways to extract tempo from MIDI and audio, but none will yield perfect results without some work. But in the case that the hardware sequencer was providing a click (or acting as a drum machine) for the band at varying tempos, the quickest way to get those tempos into Cakewalk would be to record the sequence in an app that does derive tempos from MIDI sync, and then export/import that to Cakewalk via MIDI file.

The problem is that tempo changes aren't diescrete MIDI 'events' per se. The ability to capture the sync signal and convert it to tempo changes after recording is compete could most certanly be implemented, but it's not simply a matter of capturing bpm numbers sent from the the source with time stamps. I would think some sequencer/DAW app out there has this capability already, but have never looked into it.