David Baay

@Roger W If you choose to show 'All" controls in the Track Control Manager above the tracks pane or go to the MIDI tab at the bottom of the Track Inspector, you will see controls labeled C, B and P for Channel, Bank, and Patch. The Channel control sets the forced output channel; this is what needs to match the Kontakt channel.

You don't have to change you're keyboard's output channel; you can leave it at 1 and leave the track's Input set to 1. The forced output Channel setting on each track will re-channelize both incoming and existing recorded messages dynamically on playback as they are sent to the output to match the channel assigned in the Kontakt. This sounds like you've created some multi-channel presets at some point.

Just to be clear, the audio is saved per project, and you moved the whole project folder? Even if you somehow separated the audio from the project, you should just get a "missing audio "notification, not a hang. Otherwise it shouldn't be a problem but if that's that last thing that changed before it quit working, you should definitely try moving it back.

Solo the track(s), export with Source = Buses, Ctrl+Shift+click one bus to deselect all, then select only the vocal bus.

Yeah, I almost quit playing the piano because of all the stuff I had to learn. ;^)

One and done method, but does not keep the timeline/metronome in sync with the slower audio: - Hold Ctrl+Shift and drag the end of the clip later to slip stretch it. Distinctly non-clunky, two-step method that keeps the timeline in sync, but doesn't offer flexibility in choosing stretching algorithms: - Ctrl+L to enable Groove Clip Looping on the audio clip. - Change the project tempo. Not very clunky method that keeps the timline in sync AND gives you the option of selecting different stretching algorithms to get the best audio quality: - Expand the Audiosnap section of Clip Properties tab in the Track Inspector. - Click the Enable box. - Change Follow Options to 'Auto stretch'. - Check the Follow Proj Tempo box. - Change the project tempo. Very clunky method: - I dont know this one; you'll have to ask John. ;^)

I coincidentally just corrected a typoed project folder name this morning and had no issue opening the project from the Existing Project browser after doing that. And I've done this many times in that past. I've also migrated 30 years worth of projects across many PCs (and different drives in the same PC) without issue. In general, CbB will always look in the local Audio folder at the same level as the .cwp file within the project folder unless the project was saved referencing audio from the Global Audio Folder specified in Preferences > File > Audio Data. I have only seen issues arise with absolute paths including drive letters when saving/opening projects to/from a network directory that was not set up as a mapped drive.

It's been a while since I had a controller set up to use ACT, but I think you need to remove this. IIRC, when ACT has control of ports, they can't be used for regular "musical" MIDI I/O by another device.

Just posted in another thread this morning:

CbB has the same Elastique Pro stretching algorithms available in Reaper plus some others. The difference is that stretching is not enabled by default. To enable it: - Ctrl+A to select everything. - Expand the Audiosnap section on the Clip Properties tab of the Track Inspector. - Check the Enable box. - Change Follow Options to Auto stretch. - Check the Follow Proj Tempo box. - Change the tempo; if the tempo is not constant, use the Tempo Offset function in the context menu of the Tempo Track. - You can change Online/Offline Render algorithms if desired; different ones can be specified per clip/track by selecting individual clips/tracks.

You need to send in a formal report to support@cakewalk.com with a copy of the project. If you share a copy of the .cwp without audio as azslow3 suggested we can check if it's reproducible on other systems.

Miło, że mogłem pomóc.

Over the years, I've found the various algorithms can produce various anomalies on various parts of a track. I've also seen cases where it sounds good in real time but gets worse when rendered, even using the same realtime algorithm. In that case, you can do a realtime bounce to another track. I've always attributed these isses to the algotithms themselves, but it's hard to know. One other issue I've encountered with audio stretching is that it can interact badly (distortion/buzzing/clipping) with the 64-bit Double Precision Engine (possibly in combination with certain plugins) so you might try disabling that. I've ocassionally encountered hangs/crashes over the years while editing with Audiosnap tools - mostly in clip mapping as opposed to transient editing - but never on rendering that I can recall. If you can get even a semi-consistent repro, you should send it to the Bakers.

They lost me forever when they expired the discounted upgrade from SD2 to SD3. Dumbest marketing decision I've ever seen in the music software industry. And that's saying a lot, coming from a life-long user of Cakewalk. ?

Clips with ARA FX applied can't be split. You must first render the FX by bouncing to clip or make you splits before applying the FX. I believe this is an ARA limitation, but have not tried it in another DAW.

Yes, but you need to be on the latest release and the activation server it uses will eventually be shut down after an unknown - but likely pretty generous - period, so it will quit working when your activation expires. The price of the paid replacement, Sonar (no longer all caps), has been promised to be "very reasonable" (or similar language). If you like CbB, have used it for a long time, and music is important to you, you should just plan on shelling out when the time comes. All the discussion about this reminds me of the answer that's commonly given on motorcycle forums when someone asks how much they should spend on a helmet... "How much is your head worth?"

The right tool to use and how to use it depends on whether you want values between 110 and 127 to be raised proportionally. One key thing that's often overlooked about using Find/Change is that it needs an initial selection on which to operate, so you need to start by selecting the clip or part of it either in the track view or the PRV. To just bring the velocities below 110 up to 110, Enter Min and Max of 0 and 110 in the Find dialog, and 110 for both Min and Max in the Change dialog. To compress everything upward proportionally, you need to know what the lowest velocity is; if it's not known and not easily found, LoVel.CAL can find it for you. Then enter that as the Min in the Find dialog with 127 Max, and enter Min/Max of 110/127 in the Change dialog.

Bounce to Track(s).

Yes, I see that. If you want to snap to clip landmarks, the Landmarks button needs to be activated.

Did you get mobo/chipset drivers installed?

Clearly it's got issues. Have you tried running any other apps on it? How custom is it? Have you done general checks of system health?

Plugins either require delay compensation or they don't; a powerful CPU will make no difference in this case. And when plugin load gets too high for a given CPU and buffer size. the result is not increased latency, it's Rice Crispies. Plugin Delay Compensation can be temporarily overridden while recording Input-monitored tracks (including Synth/Instrument tracks) by the PDC [override] button in the Mix module, but only if the PDC-inducing plugin isn't in the path of that track to the output.

Define "can't use". What are the exact symptoms? What type of drive is D:, and what else is on it?

Mute the clips and enable Hide Muted Clips in the PRV.