David Baay

Set the metronome to MIDI, and then you should be able to set the Clock to 'Internal' (system clock).

Make sure Polyphonic Velocity Auditon is enabled in Preferences > Editing. Then lasso-select all the notes in the chord before clicking one of them.

Also, if you set a loop region, reWind will stop there first, and jump forward to there if already at zero. Very handy. Incidentally, I navigate by measures/markers so often that I have PgUp/Dn with no modifier bound to Previous/Next measure, and Ctrl+PgUp/Dn bound to Prev/Next Marker.

When you wrote Shift+Drag, I assume you mean Click and Drag since Shift isn't needed to move a crossfade. I don't work with crossfades enough to have run into that, and can't reproduce it now. If you have a semi-reproducible case, you should report it to the Bakers with a copy of the project.

Hmmm... I can confirm the MIDI track solo button doesn't light, but it does continue to be heard in my case. Not sure when this changed, but in the past users have actually complained that it wasn't intuitive that all MIDI tracks driving a multitimbral synth would be soloed when you soloed any output even though it's neessary because Cakewalk can't know how channels relate to outputs within the synth.

Respectfully, I typically recommend the opposite: leave onboard audio enabled and designated as the default playback and recording device for use by Windows, browsers, games and other generic multimedia apps so that they keep their mitts off your dedicated "pro audio" interface, reserving it for applications specifically configured to use it (preferably via the manufacturer's own ASIO driver). If you want to hear multimedia audio through your monitoring system, use an outboard mixer to merge it.

Can you record MIDI, even though you might not hear the synth respond?

Right, so enable (check) the Behringer IN and OUT ports, select the Behringer IN as the input to your MIDI track, and it should work.

If the keyboard is plugged into the Behringer, it's not the Yamaha that you'll see in MIDI Devices, it's the Behringer's MIDI IN/OUT. Do you see that in MIDI Devices? If not, check Windows Device Manager to make sure it's seeing the Behringer's MIDI ports, and ensure Driver Mode under Preferences > MIDI > Playback and Recording in Cakewalk is MME.

Not sure what could make it go that wrong. If you want to share either the guitar track or the click track somewhere I'll see if I get a different result.

That can probably be done just as easily within Cakewalk. Noises in between words and phrases can be attenuated or silenced with a Volume automation envelope, and gaps/silences and can be closed up by deleting sections with Ripple Edit enabled. And plugins like an Expander can often be used to automate some of the noise reduction.

If you want to get more specific than MIDI Omni (i.e. all channels of all ports), which can be problematic if you have MIDI-generating VSTs in the project, choose Manage Presets from the Input pick list, and define a preset for only those specific MIDI ports and channels that you want to record: http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x203D5

I'm in. Love playing in real time with multitap delays, and this one sounds doubly (pun intended) inspiring. Hmmm... 2009. I think I'm overdue to post another one: The Power of Two

Are those transients supposed to be a quarter-note click track? Is Melodyne inserting incorrect tempo changes, or just not running at all? I've never tried Melodyne with just a click track, but it should work. EDIT: I did a quick test using a click track with a steadily increasing tempo. Melodyne Editor made some mistakes, but got pretty close.

When you say 'preroll' you mean the section ahead of the punch region? What's the audio source, and what are you're record settings?

Malcom, you can click the Reset Configuration button under Preferences > Audio > Configuration File to get back to default configuration that should work... if audio configuration is the issue. I specifically suggested it for the OP since he said his X3 config was working, and Platinum should be able to use that same config. But it may not be right for you, depending on the driver mode you're running. If you haven't already, you should start a dedicated thread for your particular case, and let us know what hardware you're running with what audio settings.

Almost suggested checking channels, but most synths will respond to any channel. But a multitimbral synth might need to have a patch explicitly loaded for each channel used.

Back up CbB's AUD.INI, and copy X3's over it. If it solves the problem, compare the files.

What interface are you using for output? The onboard audio is showing muted in the system tray. Also the notes in the PRV are so light, they look like they might be muted (not the clip, but the individual notes). If so, select all, and click a note in the PRV with the mute tool to unmute. Other possibilities: Shift+T to show lanes, and make sure the lane isn't muted, and show the controller pane in the PRV and make sure the velocities are up.

Looks like the clip has some 'dead air' on the front end, and setting the tempo at 2:01 should not have been necessary. Try clip-editing the start of the clip to the first transient, drag it back to 1:01:000 and then drag it to the timeline. If you need it to start at 2:01, you can insert a measure with Ripple Edit All enabled to push the clip and the tempo changes out with it.

What about WASAPI Exclusive? I can't vouch for Cakewalk's performance in WASAPI Shared mode in an otherwise ideally configured environment because I've never used it that way. When I wanted to see what WASAPI was capable of at low buffer sizes, I ran it in Exclusive mode. In fact, IIRC, the lowest buffer settings aren't even available in Shared mode...?

I can repro that. Same happens in the last release of Platinum, but it's probably using share utilities that have been updated by CbB.

For my part, there is no rushing to judgement. I'm just suggesting logical troubleshooting steps, including making changes to the Cakewalk configuration. The current release is working too well for too many users to conclude that the update has an inherent issue that's independent of the environment it's running in or the configuration of Cakewalk or project files. Of course the ultimate troubleshooting step would be to roll back the update, but that isn't possible with the current installation model unless you've prepared in advance by backing up or using scook's utility for managing versions. I believe there were some changes to WASAPI driver mode related to sharing drivers, but the OP is using ASIO. I do see more dropouts on my laptop, but I attribute that to using WASAPI shared mode on a low-spec machine with years of accumulated software bloat (dual-core company Lenovo). And it's no worse in this release than it's ever been. It's fine if I only use it for playback with the buffer at 10-20ms, but down at 3ms where you would want it for real-time performance of soft synths or input monitoring , it's dropout city. But I can see the DPC spikes and CPU hits from other processes that cause it, and if I go out of my way to do a clean boot ith WIFI and Bluetooth disabled, and switch to WASAPI Exclusive mode, it's quite stable at 3ms. This reminds me... there was a problem with WASAPI driver mode at 44.1 kHz in a release late last year that I never encountered because I run at 48kHz. There's no indication that anything like that has resurfaced, but it might be worth changing sample rates (in a project with no recorded audio) as another general troubleshooting step, regardless of what driver mode you use.

How 'suitable'? IIRC, Latencymon labels anything under 1000-1500us (1-1.5ms) as 'suitable', though that's not ideal for a DAW that's running a buffer on the same order of magnitude. That said, moderately-high-but-stable (say 400-500) is better than usually-low-but-spiking (150 with spikes to 1000). And you need to let it run for a while to see if anything is causing spikes. Did you try the Config File reset?

The Octopre is a standalone pre-amp with no direct connection to the DAW, right? In that case you can only set Timing Masters to channels of the slaved 18i20. That's how I run my interface when slaving to an Alesis QSR (because the Alesis didn't like being a slave) . Works fine. The only limitation is that Cakewalk can't force a clock rate change when you load a project that includes audio recorded at a different clock rate.