David Baay

Missed opportunity; a little paint could have made it BORG.

Man, you are really begging for a snarky response, if not an all out flame war, but I will refrain. No, that's the Split Move tool (a.k.a .Crop Abutted Clips) The one I pasted is the regular Crop tool. Here they are together; note the differences: The Split Move tool can be used to crop a single clip edge as you showed, but it's designed to move all clip edges on the same timestamp across all lanes as you also showed. The behavior you got is expected. If you only want to move a single edge, you should use the tool for that purpose. When CW is defaulting to the Split Move tool, holding Shift will get you the normal Crop tool.

No it's not. This is the cursor for that: As for the rest of it... have it your way. Just trying to help you have a better chance of getting your issues addressed whether due to defects or misuse.

From a development standpoint, they each have to be docuented and investigated individually; if they are found to have a common cause and solution, great, but that's for the Bakers to determine. From a forum standpoint, multi-issue posts are not as sensible as you might think; they tend to just become a confusing mess of random responses. Videos can be helpful but they only show the actual result, not the expected result which is required to have a full understanding of the issue, (and to confirm whether there is even an issue or whether the expectation was faulty) and requires a verbal description. The problem with this is that you're relying on users to correctly determine whether their issue is actually a bug and whether it's the same bug as someone else reported. I can't tell you how many times someone has posted "I have the same issue", and it's not the same at all. Sometimes the same symptom, but a different cause (at least as often a config or training issue as an actual defect), and sometimes not related at all. I guarantee almost none of that will be reproducible by other users or the Bakers without a detailed description of the steps and much if it will turn out to he hardware/plugin/project-dependent. Personally, I have never encountered any of that or recall it being reported by anyone else in so many words with the possible exception of "worse performance at higher buffer settings" which can happen when your audio and disk buffers are not well-matched among other things. Bottom line: if you seriously want to see anything 'fixed", it needs a separate post with reproducible steps and a copy of the project in case it's not readily reproducible in a new project started from the Basic template. I believe your expectation of what should happen in the last two cases is mistaken, but I can't make sense of what you're trying to accomplish or why you're talking about 'slip-resizing" a clip and expecting other clips not to be affected when you're using the split move tool instead of the single-clip crop tool. I was mistaken BTW; It's Shift that changes this tool. not Ctrl.

Turns out you have to check the box to "allow HoRNet Plugins to use my personal data as stated in the privacy policy".

This can happen If you have certain Visual Effects disabled in the Performance section of Advanced System Settings in Windows. I recommend setting this to 'Best Appearance'. EDIT: On re-reading, I may have misunderstood. If you're referring to the mouse cursor rather than the Now time cursor, hit X on your keyboard to toggle Aim Assist on/off

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.