David Baay

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/

The only time I have seen that is with audio rendered from a Bitbridged 32-bit synth plugin in x64 Cakewalk. This was due to a bug in Bitbridge. Otherwise it should not happen.

Latency is strictly a realtime phenomenon; it's not applicable to non-realtime "offline" rendering to file by bounce or export.

The extent of a Lasso selection is defined by the start and end times of included notes so there shouldn't be any difference between that and Ctrl+ or Shift+clicking to extend a selection. And I don't see right offhand how copying from linked clips would have any bearing on that...? In any case, I can't replicate a problem. Might need to see a before and after screenshot to understand the scenario exactly. Do you have Drag and Drop mode set to "Blend"?

As the dropdown header indicates, it's milliseconds, though it should technically be "(ms)" instead of "(MS)". Since latency doesn't matter, offline rendering allows using much larger buffer sizes which may be more efficient, and thus faster, for some types of processing. I've had my default at 20 for a long time just to avoid issues that some plugins have when rendering offline at very low buffer sizes. The only caveat is that larger buffer sizes use more RAM which could be an issue in a project with tons of plugins and tracks (e.g. orchestral scores) at 200ms, but probably not so much anymore with most serious DAWs having upwards of 32GB these days.

Not completely clear what that means.

I have Shift+Right/Left Arrow bound to Fast Forward/Rewind for quick moves of less or more than a measure that don't require precision. If I need to get to a specific note/transient, I use Tab/Shift Tab from there. In the past I've used this old CAL-based workaround to 'nudge' the Now cursor by specific small increments; see posts #18 and #23 in the following thread: http://forum.cakewalk.com/quotnudgingquot-the-quotcursorquot-now-time-m1339533.aspx

If you used the procedure I outlined to enable Audiosnap Follow Project Tempo in Autostretch mode and offset the tempos by a percentage, what exactly was unsuccessful about the result?

But still the better choice in many cases as it avoids having to click and drag with precision or inadvertently changing focus as in this scenario if you leave Auto focus enabled

I checked that before I posted just to be sure. I didn't expect it to make any difference, and it didn't. Auto focus has no effect unless you click on a note of a track that isn't already in focus, which you shouldn't need to be doing in this scenario if you select by lasso or already have the selection defined before you change focus to the target track.

You need to start by ensuring both tracks are enabled for editing in the PRV by swiping or Ctrl+clicking their track numbers in the PRV tracks pane . The first track you click will get focus (track name and number highlighted white) and be the target of a paste. You can change the focus by clicking a different track's name in the PRV tracks pane but you need to leave the track nmbers selected so both source and target tracks are showing. I'm not sure about the full-length clip; that may be related to the state of the Non-Destructive MIDI Editing option, but I can't say I've ever run into that. All that said, I generally prefer to do track-to-track or lane-to-lane moves in the Track View because it's easier to control and confirm exactly what you're getting.

@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: