David Baay

That's a reasonable way of thinking about it except that MIDI track meters in CW are always metering the output regardless of the arming state. So anything coming out of the track should register in the meter regardless of the source.

Hmmm, yes, forgot to mention that one. I've never personally encountered it because one of my guiding principles is "Just say no to 3rd-party MIDI". ;^)

Care to share an example project? Might be the easiest way to confirm whether the problem is in the project or your Dim Pro installation has broken.

Yes, there are many instruments out there that work one day and not the next. ;^) But, seriously, I am not aware of any particular issues with Dim Pro and would suggest you stick with it for the things it does well and troubleshoot the problem. The most commons problems I run into with Dim Pro (and other instruments for that matter) are: - No patch loaded. - MIDI volume is zeroed. - Playing outside an instrument's note range. - Playing staccato notes on an instrument with a slow attack. But if the Synth/Instrument track meter is showing output, it's probably not a synth problem.

That's why it hasn't been updated.... not worth the effort for the handful of Neanderthals still using it. ;^) Personally I like the warm fuzzy feeling I get when I am suddenly transported back to 1990 by some long forgotten corner of the UI.

- Snap the Now time to the the start of measure = Current Tempo + 1, - Shift+M to open the Set Measure/Beat At Now dialog. - Enter. Target Tempo + 1 as the Measure, Beat 1, and OK. CbB will change the initial tempo and adjust the start times and durations so the playback timing is unchanged. Note that it will also insert the new tempo at the Measure that you Set which you might want to delete just tp prevent any future confusion if you decide to make other tempo changes later.

This sounds like an SNL ad spoof... "Remember how much you loved that old upright piano you inherited from grandma? It hadn't been tuned since the Wilson administration, the keytops were the color and condition a chain-smoking vagrant' s fingernails, and the sustain pedal sounded like a coffin being opened in a horror movie, but you somehow managed to learn all the Bach Preludes on it! Well, we found that piano abandoned in the alley behind the Mic Stand Bar and Grill in beautiful downtown Huntingdon, TN, drained the water, evicted the rats and spent a full afternoon sampling every 4th key at two velocities in mono using the microphone from a 1971 Realistic cassette recorder to produce this faithful replica of you childhood piano!"

I guess I misconstrued "These Midi Files play fine using any Midi Player" to be suggesting the files were meant to be GM-compatible. But I was wondering how the 'Style' commands would be expected to work with non-Korg instrument - maybe just ignored...? Related to that, and User 905133's comment about Roland Intelligent Arrangers, when I first got my RD-700NX I recall spending some time modifying an INS file to support it's 'Live Sets' implementation of multitimbral instrument assignments. This was mostly a learning exercise, and I didn't ultimately make much use of it, but it did work. I'm still not clear on what's in the MIDI files that's not being handled as expected or what the result of that mishandling is, but it sounds like some customization of the INS file might be needed.

I haven't concerned myself with Cakewalk's handling of GM files for a couple decades, but... what's the specific unexpected/undesired result? Are you using an Instrument Definition with the Korg? If you assign the output of the track(s) to TTS-1 or an onboard 'Wavetable' synth does the project play as expected?

I did the opposite: Rolled back to 22.02 and could not replicate the issue in a new project. I neglected to save the broken project from the EA, but would not be surprised the issue might persist when a broken project is opened in an older release. It seems the state of the last take lane in a MIDI track driving a soft synth is somehow corrupted on creation in the 22.06 EA.

Confirmed there is an issue with lane soloing in the EA. What I'm seeing is that neither the lane Solo or Mute buttons are functioning for the most recent MIDI take lane when the output is assigned to a soft synth. Tracks that output to physical MIDI ports seem to be working okay. I'm surprised I did not notice this in 22.02. I'll have to roll back and check. I'm fairly confident this was working as expected in earlier releases. As for the Staff View, it does not have the Hide Muted Clips option that you can use as a workaround in the PRV to see only one take. I believe this has been requested previously. I have also requested that the feature honor muting take lanes as well as clips which would help a lot.

CbB has no way of knowing that an external audio input is from the same synth that's receiving the MIDI or how MIDI inputs are related to audio outputs within a hardware synth so there's no way for it to know which audio track(s) to mute when a given MIDI track is muted. You can get this behavior by grouping the track mutes, but I generally recommend muting only audio rather than MIDI. That way when you unmute/mute the audio, the output of a MIDI-driven synth comes and goes immediately like a regular audio track without missed note-ons or pedal-ups, etc. because the synth is still rendering the MIDI.

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?