brundlefly

I use lane-soloing frequently to 'promote' the best take (or bounced mix) which is often not the last take/bounce. I have not seen any issues with this. This should probabbly be a new thread, but I'm curious what you're seeing.

This is working as designed. Soloing a lane only silences other lanes in the track It doesn't affect the mix at the track/bus level which is what the button in the Mix module is designed to show and control.

This can be done in either the Piano Roll View or the Event List. All 128 MIDI CCs can be entered and edited in CbB. In the PRV controller pane just click the + (Add) button and type the controller number if it;s not in the pick list. In the Event List, just hit Enter to duplicate the current event and double-click fields to change their values, starting with Kind = Controller. See the Ref. Guide for more detail, and post a new thread if you have more specific questions.

MIDI events themselves have an embedded MIDI channel as they are sent from your controller. CbB can re-write that channel on playback by specifying a forced output channel with the widget labeled C n the track header (Set the Track Control Manager to show all widgets) or in the Track Inspector, near the Bank and Patch widgets

Ultimately, I think you'll find life is a lot easier if you just have one track per instrument, record everything as channel 1, and use the forced output channel assignment in the track as necessary to determine which instrument in a multitimbral synth responds to that track. Non-multitimbral synths can all be on channel 1 since they each present a separate virtual MIDI port to the DAW.

when you duplicate a track, one of the options is 'Events'; unchecking that excludes MIDI/Audio and creates an empty track. But you should be able to resolve this issue without creating a new track.

My guess would be you're coming in too early, and the Note Ons are arriving before the punch point so they get ignored. Because MIDI is editable and doesn't need to have precisely matching punch points like audio, I virtually never punch-record MIDI. I either just fix it in the PRV or delete it and record a second take in Sound on Sound mode. Or just grab a copy of the same sequence from another measure if possible.

Is there an audio file in the project folder? Maybe share the project for others to try and investigate.

Cakewalk does not have the ability to assign another track's output as an input. But you can select more than one port and/or channel for Input using input 'Presets'. Yes it does, see the Manage Presets option in the Input selection menu. Cakewalk only allows filtering what is echoed and/or recorded. It does not support transforming events between input and recording. Everything you wrote here is essentially correct. Events can be transformed non-destructively in real time at the output by MIDI FX. MIDI FX can also be destructively 'applied' to a clip/track. Some MIDI fX are shipped with Cakewalk and many others are available from 3rd parties, often free. That's correct. The best and simplest workaround I know of is to use one of the VSTi FX plugins (not MIDI FX) from CodeFN42 (e.g. MIDIChFilter) which appear as Soft Synth targets for the Output of a MIDI track and echo the MIDI (with or without transformation) to a virtual port that can be selected as an Input for other tracks. There are other plugins and 'virtual MIDI cable' solutions available, but they are rother more 'invasive' and/or introduce transmission delays that the CodeFN42 plugins do not. As noted the CodeFN42 plugins can perform various transformations in real time and act as Inputs to other tracks such that the transformed data can be recorded. Otherwise your limited to destructive options like Process >Find/Change and the MIDI Event Inspector in the Control Bar or using MFX on the output.

If the MIDI starts at 1:01:000, set the Now time at downbeat event that should be at 5:01, hit Ctrl+M to open the Set Measure/Beat At Now dialogue, enter measure 5, beat 1, and OK. CbB will adjust the initial tempo to make that note fall on that beat, and adjust start times and duration to preserve the absolute playback timing at the new tempo. You can set additional points as needed to match the timeline more closely to the performance every 4-8 measures as needed to be able to quantize. You can also adjust or completely delete the tempo changes to reduce or completely flatten the tempo variation. If the piece has 'pick-up" notes before the first full measure, you should start by sliding the clip to put the first downbeat on 2:01, and Ctrl+M to set that point. I recommend you do all of this starting with a copy of the project because it can't be undone once you close the session and lose the Undo history.

If clips are completely missing, I think the most likely explanation is they were inadvertently deleted from the project at some point and it was saved in that state. Or the project crashed before saving the session in which the recordings were made. If the project had been closed without saving the recording session, the audio files would not have been preserved. And any corruption of the project or audio files after the fact that could cause loading to fail would almost certainly result in an error of some sort. 20-20 hindsight: using Save As or the built-in File Versioning feature helps avoid this.

I still don't fully understand what the exact symptoms of "not loaded" are. Is it that tracks that formerly contained audio clips are empty or the clips are present but are empty? I did a quick search and found one report of empty clips disassociated from their audio files, but it was never resolved and I don't recall seeing any other reports of this. Is this what you're seeing? If this is it, you should send the project to the Bakers so they might have a chance of finding and fixing the root cause.

What I'm saying is that recording, though one of the most fundamental things, is also one of the most trivial and version-independent things that CbB does, and not likely to contribute to any issue opening old projects. In other words, I think you're 'barking up the wrong tree' as we say over here. When you say, "some files in wav format are not loaded in the open project", is there an error that files aren't found or do you get empty clips with no audio file associated or no clip at all or... something else?

I believe the version reported in File Stats int he browser and CWAF Tool is the version in which a project was originally created (i.e. saved for the first time). This is useful, but not necessarily the same as 'last recorded', obviously. But this seems like a case where the desired feature would be useful in only in this particular circumstance and not often at any other time. To really be helpful in troubleshooting version-related issues CbB would need to record the version under which every significant edit was made to a project - not just recording - and even then, going back to that version might not help. CW is very good about maintaining compatibility across versions in both directions. I've had very few issues opening old projects in newer versions or even opening current projects in the last release of SONAR to confirm suspected regressions. And I've never had a problem opening audio files in any version that I can recall. Given the stability of the .WAV file format, I wouldn't expect otherwise, understanding that all the metadata related to clip editing, Audiosnap, Melodyne, etc is stored in the project, not in the .WAV file, with the exception of looping metadata in a Groove Clip which should follow a standard format.

Cool. Been waiting for this one, even though $19 is already pretty cheap. Tried the HoRNet one because is was dirt cheap on sale, but it pumps badly on dynamic/rhythmic material with no options to adjust the integration time or attack and release.

Yes, my money's on a mastering plugin with a big lookahead buffer. Disabling all FX will confirm it and enabling PDC [Override] will bypass it on input-monitored tracks, but ultimately that plugin should be removed from the project until tracking is done.

That's why I was wondering if dragging up first might fix it; it would be a lot easier if it did.

In this case with only a single lane, does it work to close lanes and adjust clip gain in parent track? Also, since CW seems to think the gain level and change amount is already at minimum does it maybe work to drag up, release, and then drag down?

Over and out. Good luck.

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