brundlefly

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.

In the past, just the presence of Steinberg's Generic Low Latency Driver on the system has been reported to cause problems with SONAR/CbB, and it's usually been recommended to remove it.

As mentioned in your other thread, CbB uses the ASIO buffer as the default "chunk" size for offline rendering and some plugins can be sensitive to it - more often when it's too small than too large. But in general, offline rendering will work just fine even when the buffer is too small to get pop-free plyback in real time. The reason is that there's time pressure to keep the interface driver supplied with a steady stream of buffers when rendering offline. If a particular buffer takes a little longer to process for whatever reason or a some other system demand interrupts it, the CPU can take a l long as it needs to process it and write it to file.

Clips with ARA FX applied can't be split. You'll either need to remove the FX or bounce it into the clip.

Not really, because more and more instantaneous amplitude information is being thrown away as fewer bits are used to represent it at lower and lower levels. Applying gain to a low level signal just gives you a louder representation of a poorly detailed signal. This might not be too egregious for the first 24-30dB of attenuation, but the lower you go, the noisier it will get.

Ouch. I might have to re-read that few times, but it seems to me it would ultimately be simpler to have a separate track per patch with forced output channels and leave both your keyboard and your expression controller on channel 1. When editing in the PRV you can show all the tracks together, and it might even be helpful that the different patches have different track colors. But if you use the staff view, separate tracks would obviously not be ideal. And it's going to drive up the total number of tracks in a template that's probably pretty huge already. I'm thinking a workable variation of your current setup would be to have one "Master MIDI IN" track with its Input set to Omni on which you set whichever forced output channel is needed at the moment. And that track outputs to a plugin that echos the MIDI for all the individual instrument tracks to receive with their respective Input channel restrictions. Possibly your existing "midiChs" could be that plugin but I like using CodeFN42's free MIDIChFilter for this purpose. Some plugins of this type introduce a slight MIDI delay, but MIDIChFilter does not. In this case, it wouldn't be changing the channel, just acting as one-to many MIDI "patch point" for the instrument tracks.

I ran into a similar problem several years ago (2018 per e-mail I sent to the Bakers at the time), but with the Basic template itself. CbB default for new projects was set to 48kHz, but my interface would respond to something in the template and switch to 44.1kHz after a few seconds when starting a new project from it. In playing around with it, I somehow ended up creating a copy of the Basic template that did the opposite, switching the interface back to 48kHz when the first project had switched it to 44.1. I submitted both templates to the Bakers, but they couldn't reproduce it and confirmed templates shouldn't do this. They could only suggest that something was going on between Windows and the MOTU driver, but I never did get to the bottom of it. I only ever used the Basic template to create "clean" bug demo projects for the Bakers so I've just continued using the "Basic (48kHz)" version to do that. And I've never had any issues once audio was recorded a project; CbB would always match whatever rate was set in the audio files. So I just checked, and the issue no longer occurs with that original Basic template file in the current CbB, using all the same hardware and Win10 installation I was running at the time. I have CbB referencing custom file paths for Cakewalk content so updates don't overwrite anything, but that template file's Last Modified date is the same as the currently shipping one written to the "Cakewalk Core" directory: 8/21/2017. All that said, what interface are you using, and are you sure it's responding to CbB's request to change rates? Some interfaces like my Roland Duo-Capture have to be physically switched. If you open one of the audio files in another audio application or just look at the file properties does the bit rate agree with it being 44.1kHz? (706, 1058 or 1411 kbps per channel for 16-bit, 24-bit or 32-bit files)