brundlefly

Had been thinking to check out their loudness compensator for a while but am getting no response from the 'Purchase' button at checkout with Paypal option. Do not see that I have missed filling anything in. Curious to hear if anyone else has success.

Mouse cursor is showing the Crossfade/Split Move Tool. Try holding Ctrl to get the Slip-Edit Tool. EDIT: The second issue may also be related to this. Hard to tell exactly what the goal is. I would recommend bringing up one issue per thread unless they are clearly related. It's not clear the new issues are related to tempo changes.

Your description does not completely make sense, but this should help make sense of what you're seeing vs. what you expect: By default, audio does not follow project tempo changes in Cakewalk, but because M:B:T time is the fixed scale in the timeline (and the Now time cursor speeds up or slows down with tempo changes), audio clips will appear to change length when you change the tempo but their absolute playback duration will not change. If you want an audio clip to follow a tempo change, you enable Clip Follows Project in Autostretch mode, and there will be no visible change when changing the project tempo, but the playback tempo of the audio will change with the pitch preserved. If you want to change the playback tempo of the audio without preserving the pitch (i.e. like slowing down a tape) that is not easily accomplished in Cakewalk. There are workarounds but they are awkward and the audio quality of the result will not be great. EDIT: It occurs to me that you may have imported a 'looped' audio file (e.g. REX or Groove Clip) that will automatically follow tempo changes, in which case you can Bounce to Clips to convert it to a normal audio file before changing the tempo.

Go to the View menu in Event List, uncheck 'Notes', scan the remaining events for 'Patch' in the Kind column, and delete as necessary. If necessary, you can use the Event Manager option in the View menu to uncheck everything but Patch Changes.

Going 15 minutes without something making me temporarily annoyed.

I must have a dozen or more purchased reverbs at my disposal but still insert Lexicon Pantheon first.

'cause when you click the Unread Content link, 90% of the posts are on the deals forum, and the remaining 10% about problems with onboard laptop audio and TTS-1 are not interesting. At least, that's my excuse.

I can only repro that the output ports of the drum map get re-routed to the next available virtual synth port (in the order they were added to the project) while the virtual port of the synth being replaced is momentarily missing. This is not entirely surprising. It works okay if the synth being replaced is the last one inserted or the only one in the project. I'm not not seeing the unexpected freezing.

Ah, okay. So it's not really that "selection is cancelled", either; it's that the first lassoed node that goes offscreen is never included in the selection that's created when the mouse button is released.

Not sure why, but I cannot repro that. Can you repro in another project - maybe one without arranger sections?

Yes, this is something you would definitely want to try reproducing in the simplest possible project. If it turns out to be project-specific, it'll be difficult to get to the bottom of it without examining a copy of the project directly.

Yes there are situations that PDC override can't accommodate (e.g. having both recorded audio and live input on the same track or having a routing that takes the live input through the plugin that's adding the delay). But none of that is really applicable to the OP's issue since he's reporting over-compensation of recorded audio and that Manual Offset can't compensate for it neither of which should be affected by PDC override. One thing I'm wondering about is this: Is the headphone amp getting signal from an output on the same Presonus mixer/interface, and is it using ASIO driver mode? If using ASIO drive mode, you can use the CEntrance Latency Tester to measure the actual latency and calculate the exact Manual Offset as CEntrance Measured RTL minus CbB-Reported RTL. https://centrance.com/driverfolder/CE_LTU_37.zip

This quote from the ref, guide suggests that plugin delay is taken into account when compensating a recording and agrees with my experience. I think something else must be going on to cause the overcompensation the OP is describing. If anything, failure to take plugin delay into account would result in a late, under-compensated recording, and a positive manual offset would fix it. But I just double-checked and adding the notorious TS-64 Transient Shaper to a track did not affect the sample-accurate record compensation I have dialed in though the delay was there when not direct-monitoring the live input or engaging PDC override.

Yes, I'm familiar. I just didn't make the connection between "solo" and "mono".

I should have asked what was meant by ''solo" in your original post, but since volume and sustain controllers were reportedly not being chased, either, I thought the issue was more general.

Definitely need to get to the bottom of that. MME is not going to cut it, and WASAPI should work unless the onboard sound hardware is really ancient/atypical. Look for newer drivers as Mark suggested.

Given the OP is having an issue with crackles, I thought it best to recommend Exclusive mode. Troubleshooting 101 - remove variables that could be contributing to the problem and start with the configuration that has the best chance of success for the task at hand.

Yes, tell us what kind of numbers you're seeing. And what is the Performance Meter in Cakewalk and Windows Resource Monitor showing? What's in the project in the way of plugins? If you start disabling things do you find one in particular that's driving the load? What interface and driver mode? If it's onboard audio you should be using WASAPI Exclusive mode.

I verified this is all working as expected for sustain and volume controllers, and Zero controllers does not have any effect on CC7 Volume, anyway, so even if searchback/chase were not working the last volume in effect should persist after stop/start. And if the MIDI volume control in the track is enabled (no parens around it) that level will be sent every time playback starts unless it's overridden by some volume controller in the track.

I'm not familiar with it, but it appears Poise has a MIDI THRU function, and you need to go to the synth properties for Poise and disable MIDI OUT. Or set all other track inputs to something other than MIDI Omni as discussed. This is just how it works.

Hmmm... I'd have to check that. The name was originally "Controller Searchback" and was changed when Note Chase was added to be consistent with terminology commonly used in other DAWs. I have always understood that searchback/chase looks for all controller types and am pretty sure it works for Volume and Sustain.

Check your DPC Latency - a measure of how ready your CPU is to respond to requests from the audio driver to fill its buffer: https://www.resplendence.com/latencymon Common causes of high/spiking DPC latency are Bluetooth and WiFi drivers. If not needed, the hardware should be disabled in BIOS. While you're there, also make sure that CPU-throttling features like Speedstep and C-States are disabled. And make sure your Power Management profile is set to High Power.

It is enabled by default I believe. Preferences > Project > MIDI > Other Options

+1 on being able to lock the duration of a MIDI clip to absolute time, But in case you're not aware, 'Set Measure/Beat At Now' (Shift+M) does what you want - maintains absolute playback timing of MIDI while shifting the timeline around it with tempo changes. And it calculates the required tempo for you. The first track I lay down is almost always recorded without a click. The main reason I'd like to be able to lock a MIDI clip to absolute time is for the occasions when I inadvertently record into a project that already has tempo changes and need to delete them without altering the playback timing.

I had an issue loading some AAS VST3s that was related to their calls to OpenGL to render the GUI that was resolved by updating Nvidia drivers. Have not had a problem with any VST3 before or since.