David Baay

You've got that backwards. Insert FX are inherently pre-fader because the FX bin is ahead of the Volume control. It's not possible to have them post-fader

The above seem to be in conflict with this: How are you expecting to move "everything" downstream of the insert point without affecting clips that cross the insert point? There are many ways to selectively move content later, but not by Insert Time/Measures. This function is designed to insert an empty gap in all tracks.

Once the project tempo is well-aligned to the audio, you should set the Follow Option to Auto Stretch before enabling Clip Follows Project and making manual changes to the tempos. Other modes will try to re-align transient markers to the timeline again which may result in some immediate stretching, especially if the mode is different from that used to Set the Project from the clip. Autostretch mode won't stretch any audio until you make tempo changes, and then will just uniformlyl stretch the clip between tempo changes without regard to transient markers which will tend to be more transparent.

That's true because the Record meter is ahead of the input to the track, but the hardware input connects to the track after the Gain control. See this signal flow diagram: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Mixing.07.html The diagram doesn't show it, but the "take off" point to write the signal to disk is essentially at the same point as the Record meter. But on playback, the signal from the file/clip comes in ahead of the Gain control. So if you alter the Gain, you will hear the difference on playback but not while recording.

In John's defense I will note that you ommitted "and installed it" from your quote, which is key to understanding which application that poster was referring to. Having been accused recently of not reading carefully enough when I am, in fact, a very careful reader in general, I can sympathize. Sometimes you just miss stuff. And John's reponse seemed more of an "explanation" than a "deflection" to me.

Are you seeing this in all projects? Snap Intensity is saved per-project and the intensity of the most-recently opened project will pertain to all open projects, but you should be able to change it in any one of them unless possibly a particular project has become corrupted somehow. Workspaces should not have a bearing but you might try setting Workspaces to None and re-trying. Otherwise... I dunno.

Strange. File import/conversion is an offline process that should not care what hardware (physical or virtual) drivers are in place. Seems more like one of those drivers was not allowing the .WAV file to be written to the drive as opposed to interferring with the conversion process, although I suppose there could be some contention for a CODEC. In any case this might be something you want to take up with the virtual audio cable developer to get a full solution.

Nether the track's Gain (input) level or Volume (output) controls alter the recorded level of a hardware input. That is solely determined by the input level/sensitivity control on the interface. So you can freely change track's Gain to get the desired level into any FX plugins you might be using and Volume to get the desired listening level.

Is this happening with a new project started from the Basic template? Can you record the note into a MIDI track regardless of whether you're hearing anything?

Just to clarify, what needs to be changed is the Edit Filter. This would be my guess also.

You can't record/import the backing tracks into CbB first...?

The whole point of Clean Audio Folder is to find all un-referenced audio anywhere in the subdirectories of the project folder. It just isn't designed to accomodate storing audio files that it doesn't recognize as part of the project. I don't think that's likely to change. Workarounds that come to mind are: - Change the file extensions to something other than .WAV or maybe convert them to .FLAC. - ZIP the Files directory.

Enable 'Select Controllers Along with Notes' in the Controllers tab of the PRV.

Yes, click the minus button and choose 'Remove HMSF'; I'm not not sure whether it's ever worked to remove a ruler by unchecking it in the context menu, but it's reasonable expectation that it would.

I learned recently, myself, that it's working as designed that offline bounces of Aux tracks are silent unless the source tracks are also selected which happens implicitly when bouncing through a bus or a hardware out. From Ref. Guide: "To bounce/export a project containing patch points, select all tracks that contribute to the mix. For example, if the project contains three audio tracks that send to an Aux track, you must include the Aux track as well as all contributing tracks prior to performing the bounce/export." https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Mixing.13.html Selecting the source track(s) along with the Aux and then unchecking the source track in the bounce dialog will achieve the desired result.

Share the project?

+1 I have 30 years of old projects, and all of them open fine in the current release. But I'll also suggest you copy the track content into a new project started from a current template (or a custom template created from one of the included templates) as old project files can be missing values or have non-ideal default settings for various parameters/features that didn't yet exist at the time or have been re-engineered.

Another advantage of linked clips is that you can unlink one of them at any time to introduce a small variation without affecting the linkage of the others.

I believe we're talking about the Input Echo button. If you have Always Echo Current MIDI Track enabled in Preferences > MIDI > Playback and Recording, the currently focused track (track name highlighted) will always be echoing input from your keyboard as indicated by the 'A' (for Automatic) in the icon; you can force it to be always on, but you can only turn it off by changing focus to a different track. The issue with NI is likely due to it being multitimbral and needing to have a specific Channel assigned to each instrument and track. See the documentation on Intrument Track per Audio Ouput: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.16.html#

That was Linux... er, um, I mean Linus.

Disable "Set Now Time with Full Restart" under Track View Options. https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Views.03.html "Set Now Time with Full Restart. When you change the Now Time during playback, the Transport comes to a full stop, and then restarts playback. This stops the sound for a brief moment, but makes synchronization (especially with video) more robust." It's not mentioned, but toggling Looping also forces a restart when this option is enabled.

Likewise, I'm not suggesting there isn't a bug; just trying to get a handle on the steps that manifest the problem so it can be reported if necessary. My main issue with moving between CCs and envelopes is that conversion of CCs to envelopes uses linear segments instead of jumps by default and doesn't give you an option. The segment types can only be changed one at a time, and converting back will create new CC events with interpolated values.

Glad to help. We were all noobs at some point. I had the advantage that the CW manual was about 30 pages at the time. ;^) Good on you for sticking around to see the answer and respond. Welcome to the forum!

Been meaning to click on this for a while, but haven't until now because, as a long-time fusion fan and fusion-musician impersonator, I inevitably end up feeling both envious and lazy after listening to one of Hidden Symmetry's productions. Hurts so good. ;^)

To write/re-write automation after the fact you need to enable Write automation on the track in the desired mode and write the new data during playback: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Automation.04.html 1. Different instruments/patches/parameters may respond badly when receiving new CC data that conflict with exisisting values. Using Overwrite mode or deleting the automation in advance should avoid this. 2. What are the steps that reproduce "cannot move the [envelope] data back to CCs"? 3. Existing envelopes should automatically move to lanes when you show automation lanes - this will need detailed steps to reproduce as well.