David Baay

I gather you mean VST instruments and probably polyphonic ones like keys/pianos as opposed to FX; is that right? Are any of them using physical modeling (e.g. Pianoteq) or disk streaming (e.g. Ivory). Both of those types would tend to give smoother playback from recorded MIDI that allows buffering up audio in advance vs. responding to live MIDI input.

Uncheck: Preferences > Audio > Playback and Recording > Disable Input Monitoring During Playback

Utilities > CWAF Tool (Cakewalk Audio Finder) will show you which files are referenced by which project(s) and where they're located, among many other things.

Upsampling has to be enabled per-Plugin by clicking the icon at the left end of the plugin UI's title bar. The 2X button in the Mix Module then enables/disables upsampling globally, but only for plugins that have it enabled individually.

Just be sure to check the box to Copy all Audio with Project in the Save dialog, and the initial recordings done before saving shoud be copied to the project audio folder.

Sounds like CPU throttling is lowering performance until the load hits a certain threshold. You'll want to make sure that Speedstep, C-States and other CPU throttling functions are disabled in BIOS and Windows power management is set to High Performance.

All you really need to do in this situation is manually reassign the output of the replaced instrument that defaulted to output 1 to output 3. But the better approach would be to simply load a new instrument into the existing instument slot in the rack rather than deleting it in the first place.

If you record MIDI are sustain pedal message recorded, and do they show as CC64 in the Controller pane of the Piano Roll view or in the Event List view? the value should be 0 for pedal up and 127 for pedal down. If there are no messages recorded or they are something other than CC64, it's a problem or configuration issue with the Alesis. The pedal is just an on/off switch; It's up to the controller to generate the message. Views > Event List (Alt+8) should show you something like this:

No, you can change forced MIDI channels as needed after the fact, and you should be able to delete an instrument in Kontakt without ill effects. What Mark was saying is that changing forced MIDI Channel assignments might interefere with creating more Instrument/Output tracks for the same synth instance later. I'm not sure exactly how that manifests as I've not tried it, but I don't think it's relevant to the issue you encountered. I'd have to see your project before and after deleting the instrument to understand what might have happened to cause the soloing issues. All that should have happened is that the track that was using that instrument would go silent, but it might depend on how instruments were assigned to outputs in Kontakt. Before doing anything I would recommend going into Kontakt 7's Outputs view and changing the default configuration to 16x stereo outputs so that when you insert it in a project with the Instrument per Output option, the instrument tracks are named like Kontakt 7 1 Out 1, Out 2, Out 3, ... Out 16 for clarity.

Sounds like a Clip Gain Envelope: https://gaga.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.061.html

Lighted buttons means automation Read is enabled. If the global Read button in the mix module is not lit, all the Read buttons in individual tracks will be disabled. Clicking them will just additionally disable them individually. You need to leave them individually enabled, and also enable the global Read button in the mix module.

The next place to check would the MIDI Activity indicator that CbB places in the System Tray section of the Windows Taskbar when enabled in Preferences > Customization > Display. If that isn't showing flashes on the Input (left) side, then something's not right with the driver and CbB won't be receiving any input. Are you able to set the Input of the track to a channel of the Tascam IN port , specifically?

You should start your own thread to investigate this. If you read the whole thing, you should know this was for a specific case that has been resolved. Do you get corresponding spikes in the Performance Meter with the crackles? What ASIO buffer size? If 128 samples or more, try enabling/disabling Plugin Load Balancing in Preferences > Audio > Playback and Recording - sometimes having it enabled costs more than it benefits. In general, I can't replicate your issue; sidechaining an instance of Sonitus compressor costs almost nothing.

I am for the most part also; I'm always buying one or two tiers down from top-of-the-line, and used or refurbished stuff. I was originally looking at a cheaper, refurbished wireless Logitech combo using the M720 mouse that I use with my laptop (and like very much). But the keyboard had a fixed, non-removable palm rest which wasn't ideal for my situation. And I'm often willing to shell out a little more for something I will be using many hours per day for years.

Until a few months ago, I could have said I'd never had either go bad. Then my 8-year-old Dell keyboard went from slightly flaky to dead as a doornail over a period of several weeks. I took the opportunity to go wireless and treated myself to this combo: https://www.logitech.com/en-us/products/combos/mx-keys-s-combo.920-012274.html Decidedly spendy, but super-solid and worth it in the grand scheme of DAW costs if I can amortize it over the next 8 years.

See Track VIew Options > Click Behavior > Double Click > Audio Clips The default used to be Loop Construction, but is now Clip Properties in the Track Inspector, and can also be "Nothing". I didn't fully understand your last post. Maybe share a copy of the raw 4-beat audio clip here and we can check it out.

Open AUD.INI in a text editor and delete the entries under [AliasInput] and [AliasOutput]. CbB will restore the default <drivername>=<drivername> entries on the next launch. As always, it's a good idea to save a copy of the existing file before making changes. %Appdata%\Cakewalk\Cakewalk Core\AUD.INI

Sounds like the clip was not selected. Opening clip properties by double-clicking will do that automatically, but if you navigate to clip properties with nothing explicitly selected, it will be blank.

Yes, you should make sure the Audiosnap markes are at the very beginning of the transient before moving the transient. Otherwise the attack may get unevenly stretched and sound like a flam or otherwise distorted. Does the Yamaha not have a "brain" module that you can drive with MIDI to use it in real time or at least record your audio clip using quantized MIDI so you don't have to quantize the audio?

As rsinger said, you need to manually correct the "Beats in Clip" value in the Groove Clip section of Clip Properties tab in the Track Inspector. But this may not recover the "discarded" audio; you might need to start over and make sure the clip boundaries are precisely on measure boundaries before you enable Groove-Clip Looping.

This thread is a blast from the past for me. I haven't listened to April Wine since the hard-rocking (and smoking and drinking and tripping) days of my late teens. I have Harder ... Faster on vinyl.

As in years past the upgrade from two or more years older product is only $10-20 more than upgrading from the previous release, depending on the version. As a result, I've gotten in the habit of upgrading every other year at the most. There are some useful enhancements this year, but for $85/year instead of $150/year, I will wait til 2025 to upgrade my Ultrapak. I mostly only play around with it, anyway; it's not a regular part of my creative process, and I've never "published" anything I've done with it. Like others, I sure do wish they would bring the UI into the 21st centry. The year they do that, I will definitely upgrade.

Try toggling the audio engine off by the button in the transport module. If the problem persists, it's not load-related. With all the other tracks frozen, it shouldn't be RAM-related, either. I would sooner suspect some issue with the interoperability of the CW with your video driver. Have you added/updated any hardware/software/firmware/drivers around the time this happened? If it's only this one project, try to identify anything unusual about it, and maybe start stripping down a copy of it.

I'm pretty sure GUI Throttle Mode (a.k.a. CPU Conservation Mode) activated by Pause is not the issue here. It's only active during playback, reducing UI updates (mainly meters, Now counter and Now cursor motion) to approximately once per second. If you were to try moving notes in the PRV during playback (which I'm guessing is not the case here), there would be that slight delay in the UI update but not "many seconds of the screen slowly flashing and re-adjusting itself trying to get to it's goal" as described.

I don't have much to offer other than to suggest you have another go at finding an affordable x64 substitute for VSampler. If the issue is related to Bitbridge, you might try the inexpensive 3rd-party Jbridge if you're not already running it. Bitbridge has an issue that it adds and empty buffer of audio to bounces/exports; Jbridge doesn't have this issue. It also solves the problem that having a 32-bit UI focused unavoidably grabs all your keystrokes so, for example, you can't start/stop the transport with Spacebar while working in the UI. It's cheap, but you can demo it first: https://jstuff.wordpress.com/jbridge/