David Baay

It's not a bug; it's a missing feature. A bug is a feature that does not work as documented. It is not documented anywhere that one MIDI track can drive more than one instrument in CbB. The MIDIChFilter option is a workaround for the missing feature that was proposed by another user, and not verified or endorsed by any CbB developer. That said, I did a quick test and had no problem driving four instruments from two MIDI tracks outputting to two instances of MIDIChFilter. You'll need to give exact sequence of steps to reproduce your problem with it.

This could definitely be the root of the problem. Inserting instuments in the FX bins is supported for backward compatibility with legacy projects that used this configuration, but is definitely not the preferred routing and has some longstanding issues with stuck meters and stuck notes.

My guess is you're seeing the difference between CWP projects that were created before or after Mix Recall was implemented. Newer projects will have been created with the MixScenes folder already in place when they were first saved so there won't be any changes to the project folder when they're re-opened. I can almost guarantee a fresh install of CbB is not going to behave any differently.

This is not new to CbB or any particular Windows version. Long before SONAR became CbB, it would create a "MixScenes" subfolder to support the Mix Recall feature on opening a WRK file that would cause the parent's Last Modified date to change. This continues to be the case. Even if you don't re-save the project and the MixScenes folder is discarded/deleted on closing the project, the parent folder's Modified Date will already have been permanently updated - first by creation of the subfolder and again when it's deleted. I long ago copied all my old WRK projects to a "Old Files" directory that I use whan I want to resurrect one of them and archived the original directory in a different location specifically for this reason to preserve the Modified Dates. As I convert them to use modern templates, plugins and routing. I move the copied WRK folders/files to a "Converted" subdirectory with a shortcut link to the new project location. I have actually done this a number of times as some projects have been repeatedly updated to work with different MIDI and audio interface and routing configurations over 30+ years. It's worth taking some time to work out a process and directory structure to reflect your evolving project setup conventions, PC configurations and studio layout, and rebuild old projects using current templates rather than just updating them and resaving in the current release which won't capture all your preferred default project preferences.

You should let @Noel Borthwick take a look at the project that's still misbehaving with all plugins removed.

Same here. It's pretty common that the velocity and/or timing needs to be offset or I only want doubling on the chorus or the instruments need different values for some MIDI controlle. But I do have a couple common setups where I've tweaked two patches to work together with identical MIDI input and it would be convenient to use a single MIDI source.

To a great extent this is constrained by tempo scale zoom level and mouse/screen resolution. There is no way you are going to be able to draw tempos with decimal values when the scale is at the default 100bpm range and less than a 1000 pixels high. At maximum zoom and minimum height the range is only 5bpm wide, and I can draw in increments of 0.1 bpm. But the minute you go outside that range, the tempo track will automatically re-scale to be 100bpm wide. It seems to me what's really needed is more positive control over the range and centering of the scale with the ability to disable auto-scaling. The old Tempo View wasn't perfect but was more manageable in this respect.

Notes in the PRV will show the same velocity adjustment tool cursor when you hover of the upper edge of the note near the center.

Can you (or someone) please explain this? I don't quite understand. Thanks, Bob Bone I'm not seeing a problem saving a track template that uses a drum map. My guess is the drum map had not been saved or was not available in the expected path when the template was reloaded.

It does sound like that, but OP said it was a VST which will almost certainly have a stereo output. So then the question is: how is the synth being inserted? As a simple Instrument track or separate MIDI and Synth audio tracks? I sould suggest trying something more mainstream in freeware synths than CT-WS1 or one of the bundled synths in CbB to get started.

If the tempo of the 110 project can't be changed because it already has audio, I would enable Audiosnap in Autostretch mode on the clip in the 150bpm project, temporarily change the tmepo of that project to 110, and export the audio. Then close the 150bpm project without saving changes, and import the stretched audio file. If the 110bpm project doesn't yet have audio (i.e. it's all MIDI and soft synths), I would temporarily raise it's tempo to match the 150bpm, import the audio, and do the change to 110bpm with Audiosnap in the new project. Two things to keep in mind, though: You'll want to try different rendering algorithms for the export to get the best result, and lowering the tempo generally produces more artifacts than raising it.

The primary use for offline/real-time rendering is to include audio from external hardware FX or synths while bouncing. In line with what Mark said, I have encountered very few issues with fast bouncing of VSTs and they were never subtle. Some could be resolved by raising the buffer size or setting a non-zero value for BounceBufSizeMsec in the Config File to override the real-time value which is the default for offline rendering. I've had this set to 20 (milliseconds) for years, and have not had a problem rendering Iris 2, but I've only used it in a couple projects. https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=INI_Files.6.html Also, since you mention automation, there is a setting for how fine a resolution is used to process parameter automation that may have bearing: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.033.html

What's the pitch reference? If it's an audio file and all your VSTs are in tune with each other, it's probably playback of that file that's off. And are you sure about the interval? Sample rate mismatch (either between CbB and the audio interface or between the audio file metadata and the actual audio data) is the most likely cause, but the difference between 48kHz and 44.1kHz is more than a half step.

Without getting into the weeds about what it would take to do this or how to do it manually, the bottom line answer is no, CbB cannot do anything like that to automatically sync multiple audio streams, and I don't know any DAW that can. I suspect a program like Syncalia is using metadata from the video editor that just isn't available in audio files. MusicXML is a standard for encoding music notation in a universal way that different notation programs can read and write; it doesn't have anything to do with actual audio data.

Laptop or Desktop? Power management on laptops can really mess with DAW performance. Even if you're on a Desktop, you need to make sure all the CPU throttling mechanisms are disabled in BIOS and the Windows power profile is High Performance. And check for WiFi, Bluetooth or other hardware drivers causing spikes in Deferred Procedure Call (DPC) latency: https://www.resplendence.com/latencymon I haven't really found that Win11 is any more troublesome than Win10 in this respect, but access to 'advanced power management' settings has been further obscured in Win11. IIRC, I had to go through the old Control Panel UI to get to them.

MIDI Groove Clips: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Looping.14.html Select by Filter: https://www.cakewalk.com/Documentation?product=Cakewalk&language=4&help=Dialogs1.43.html Event Inspector; https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=ControlBar.15.html

That seems in agreement with my hypothesis that it's about defining the clip properties - the container for the event data. If the object already exists, Step Recorder can successfully add data to it, but it can't properly create the object from scratch. I'd be interested to see what happens when you try to Step Record data starting more than a measure past where the existing clip ends which would create a new clip object in the PRV.

Did you roll out the 100 bars from a two-bar Groove Clip? If so, you would need to roll it back, and re-roll for all the iterations to take on the change to original Groove Clip. Personally, I would probably use a combination of Select by Filter (Notes on Tick 0) and the Event Inspector module (Time = -5) to acheive this goal.

Step Record mode probably hasn't had a developer's attention since the GUI was created for it at the dawn of the Windows era. I wouldn't be at all surprised to find that it has some bugs related to generating all the necessary properties of a MIDI clip object as it is now defined for it to be displayed correctly.

The Track Control Manager drop down is at the top of the Track Pane in the Track View. If you don't see it, you might need to change your Workspace (upper right corner) from Basic to Advanced (or None which is my preference). You may find it easier to just go to the Track Inspector (shortcut I) rather than adjusting the Track Control Manager and track header size to be able to see all the controls. Here's documentation on track controls for all track types; very basic and essential stuff you should get to know: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Playback.20.html

Just to be clear, the channel you choose along with the Input port determines whther the track records and echoes live MIDI input. The forced MIDI output Channel control determines what channel is embedded in the events sent to the instrument, whether live input from a keyboard or playback of a MIDI clip. I understand what you're saying, but there is no such dependency between the clip and the track on which it was recorded. There are, however, many things in the clip content, instrument/patch programming and track setup that could make an instrument fail to generate sound from a MIDI clip (or be heard in the monitors) other than routing issues or channel mismatch; these include but are not limited to: - The note numbers/pitches are outside the range of the instrument; typically happens with bass instruments having a non-standard octave assignment or brass/woodwinds with limited range. - The notes are short and the instrument has such a slow attack that you don't hear anything before the note ends. - The notes have extremely low velocity and a velocity offset (a.k.a. MIDI Gain) in the source track was compensating. - Some controller in the track or the Zero Controllers on Stop option in Preferences is silencing the instrument; typically happens with instruments/patches that depend on non-zero Modulation (CC1) or Expression (CC11) controller values. - The clip is muted. - The MIDI track is muted or the volume control is zeroed. - The track is Archived. - Some other track is soloed. - Input Echo is not enabled on the audio track that's receiving audio back from the hardware synth. But I would still put my money on this being either a channel mismatch or audio routing/monitoring issue. If you set the silent track's input to your keyboard/controller's port and channel and enable Input Echo on the MIDI track, do you see activity in the MIDI meter when you play the keyboard and get a response from the synth's headphone output? Or, better, yet, plug the keyboard's DIN MIDI OUT into the synth's IN with no other hardware or software involved and see if you can get sound out of it. Beyond that, you really need to tell us what keyboard, synths, project routing and hardware interfaces are involved.

Each synth on a dedicated MIDI port or daisy chained and using different receive channels? And are they single-patch synths or multi-timbral? If each synth is on its own physical MIDI port (either DIN or USB) and not multitimbral, channels shouldn't matter, but the "C" (channel) widget in the track can be used if necessary to force a different output channel than is embedded in the MIDI clip's events (probably channel 1). The MIDI track Input should be assigned the specific port and channel your keyboard/controller is on rather than OMNI, regardless of how the output ports and channels are assigned. The synths should have MIDI activity indicators to teel you if MISI is being received. If channel assignments are correct and MIDI is being received but you're not hearing the output, it may be an audio routing issue. If you're input monitroing the synths through audio tracks in CdB, you will need to have Input Echo enabled on those tracks. If something in the aboove does not help resolve the issue, we'll need a thorough description of the MIDI and audio routing, including a screenshot of the Track View.

See this thread and linked CAL script: http://forum.cakewalk.com/CAL-Script-CleanTrackcal-a-combined-duplicate-and-overlap-remover-m3782351.aspx

Referencing a copy of the same file with a different name in a different location worked fine for me. There is no need to Search; just change to the directory where the desired file resides, select it, and okay the warning that the name is different. Then Save As, being sure to uncheck the "Copy All Audio" option in the Save dialog. You can save over the exisistng project name, but I generally recommend to add a filename suffix when making changes like this just to keep everything straight, and allow going back to the original project if anything goes wrong.

The best way to replace one file with another would be to rename the currently referenced file and copy the desired file into the project audio folder, giving it the name of the original file. That said, renaming/removing the file and telling CbB to reference a file with a different name from a different location should work so long as that file is identical to the first in format and length, and you re-save the project with the new references. I'll have to do a quick test to confirm success or failure.