msmcleod

The only way I know to get a clip into that state is using the Mute tool. There maybe some combination of options that would cause a clip to be blended with a longer one, and therefore a time region has been muted rather than the entire clip. It could be down to your loop region being different to your punch in/out region. To unmute however, use the Mute Tool and drag at the top half of the clip:

This looks normal to me. When you're using Comping Mode, the other takes are muted. You can then use the comping tool to decide which take (or parts of which takes) to use. You can override this by unmuting the clip ( the K key is the clip mute/unmute shortcut).

Thanks for the example projects guys - it's now fixed for the next update.

Ok, a couple of us here have tried to repro this with no joy. We've tried with different display scales, first open of a project / subsequent loads of project, clicking notes, altering velocity, before/after horizontal zoom etc. The PRV notes pane is totally collapsed for all tests. Tried with arranger pane expanded and collapsed. Still can't repro. We're gonna need a more detailed recipe... maybe a full screen video too in case there's anything else on screen that could give us more of a clue. If you could PM me a project, that may help.... also can you repro with a new project made in 2024.12, or is it only older projects?

@Sailor55 / @HOOK can you confirm exactly what version of 2024.12 you're using? I'm not seeing this on build 004 or build 006.

This notification typically appears when a MIDI device is no longer available - reasons include: 1. The interface/device is switched off 2. USB sleep mode has kicked in and turned it off 3. Some other program has the MIDI device open 4. Bad USB cable 5. Dirty USB connections You can check in preferences to see if the device is there or not... if it's not, the best thing to do is close CbB/Sonar, ensure the device is switched on and plugged in, then restart CbB/Sonar. In this scenario, it'll recover. If you go into preferences and change the Control Surfaces config, you'll have lost its previous configuration... in which case it might be easier to remove/add the control surface again. Remember you also need to re-load any preset you'd been using within the control surface's dialog.

By default in both CbB & Sonar, CTRL+Shift+T adds a MIDI Track; CTRL+Shift+B minimises / maximises the tab view My suspicion is you're either using a Workspace that is stopping those functions being available, or something else is stopping the .kbn file from being imported. Before you import the .kbn file, make sure your workspace is set to "None" and you've got a project loaded (use something like the "Basic" template). You mentioned this in another thread. You need to send us your project for us to investigate. Upload it to a file sharing service (e.g. OneDrive, Dropbox etc) and PM me the link. As @David Baay says, uncheck Preferences -> File -> Advanced -> Allow Only One Open Project at a Time.

You don't need to keep every arrangement, and I suspect you're not going to try every single possible combination of sections. What I'm suggesting: 1. Duplicate the existing arrangement 2. Delete the section(s) you want to mute At this point you could Undo to get the section(s) back, and remove another section... or you could delete the arrangement and duplicate your original again. It might be worth you posting a video of what your existing workflow is here...

What display resolution / scaling are you using? IIRC CbB has a minimum screen resolution requirement, so if your resolution is too small on some view the data won't fit into the cells.

Check this setting... you probably want to set it to 0:

Next has a tempo track, and internally has a tempo map. Adding a MIDI file to a blank project will import the tempo map from the MIDI file.

The MT-32 was my first proper synth (I don't count my Casio HT700). I later replaced it with a CM-64 (which is basically an MT-32 and a U-110 in the same box with no display). I wrote an MT-32 editor on the Amiga - amazing how good and how deep the synth engine was for the day. None of the "real instruments" sounded any good at all on it, except may. It was a synth, not a sample player. The samples it did have were essentially attack transients. The TTS-1 is completely sample based.

Looks like this one has been there for around at least a year. It's fixed for the next update.

Just to clarify: Sonar/CbB supports multiple audio outputs from VSTi' (i.e. soft synths) that have them. Sonar/CbB doesn't support multiple audio outs from VST effects at present - just a single mono or stereo output. This limitation also applies to VSTi synths you add to an effects bin (as opposed to creating an instrument track).

The way Sonar/CbB handles RPN / NRPN is to interpret them as per the MIDI spec - i.e. as 14 bit controllers. There are some hardware devices (and even more VST/VSTi's) that ignore the MIDI spec and just treat RPN/NRPN as standard 8 bit CC messages. You can tell Sonar to bypass the special RPN/NRPN handling by adding the following to TTSSEQ.INI: TranslateRPN=0 This will cause Sonar/CbB to treat RPN/NRPN messages as standard CC's. It doesn't stop you using RPN/NRPN as such, but you'll have to handle the MSB/LSB yourself as separate CC messages: CC 98 - NRPN LSB CC 99 - NRPN MSB CC 100 - RPN LSB CC 101 - RPN MSB NOTE: I've no idea what the consequences would be if you had a project with RPN/NRPN's in it, then you re-open and try to use that project after adding this to TTSSEQ.INI.... so beware.

Actually having re-read this, the way you can do this is using "Fit to Improvisation" What you do is: 1. Create a MIDI track, and arm it 2. Start recording from the beginning and play a single note for each beat of your project 3. Stop recording 4. Select the clip you've just recorded 5. From the main Process menu, select "Fit to Improvisation" This will extract the tempo from what you've played and populate the tempo track. If you simply want to adjust the tempo of what you've already recorded, all you need to do is alter the tempo envelope on the tempo track. MIDI tracks will automatically follow the tempo. Audio tracks can follow the tempo, if you set the clips to follow tempo within the clip inspector.

Templates you can just copy over from C:\Cakewalk Content\Cakewalk Core to C:\Cakewalk Content\Sonar (assuming you're using the default folders). Themes are not supported in Sonar.

Just to clarify: The "4ALL" in ASIO4ALL is what causes the problems. ASIO4ALL opens all WDM drivers and combines/presents them through an ASIO interface. When the Apollo WDM driver is in use by ASIO4ALL, it causes issues trying to open it separately using its own ASIO driver, as the physical Apollo hardware is already in use. ASIO4ALL does pass the Steinberg ASIO tests - it's the Realtek ASIO driver that doesn't. Sonar/CbB enumerates all available ASIO drivers on start up. When it enumerates ASIO4ALL, ASIO4ALL grabs the Apollo device and remains open in the system tray causing Sonar/CbB to be unable to fully access the real ASIO driver. There's nothing wrong per-se with ASIO4ALL - it serves a specific purpose and can be useful in a two scenarios: 1. Where there are no suitable ASIO drivers available for a particular device, and for some reason WASAPI isn't suitable 2. You need to combine several audio interfaces - note there are additional word-clock syncing requirements in this scenario. Most users however are unaware of how it works and the consequences of using it - the issue in this topic being the most typical outcome. So in summary: With the exception of Realtek, you should always use the manufacturer provided ASIO driver. If you're using the onboard Realtek device, use WASAPI. Don't install ASIO4ALL unless you know exactly how to configure it (which will probably need to be re-done every time its opened), and you fully understand what it's doing... if this isn't the case uninstall ASIO4ALL.

You can create as many arrangements as you want. Just create an arrangement without the section you don't want played, then play that arrangement.

AFAIK this is the case. Any MIDI will have been lost, however any audio that was recorded will be in your Global Audio Folder - by default this is C:\Cakewalk Projects\Audio Data, but it'll be in whatever path is set under Preferences->File->Audio Data.

Main File Menu -> Export -> Publish to BandLab Alternatively, use the Export module:

For years I used a Remo practice kit, modded with piezo sensors glued to soup tin lids inside them. I cut the foam inserts in half and wedged the tin in the middle, and put a 3.5mm jack socket at the bottom (in retrospect, the side would have been better... they fall out too easily otherwise, so I had to tape them). These then got plugged into an Alesis DM5, which allowed me to tweak the sensitivity. I had 11 pads in total: kick, snare, 3 x toms, hihat (with a standard sustain pedal as my hi-hat pedal), ride, splash, china and two crash symbols. In fact even now, although I use an Alesis Nitro as my main kit, I still use three of those pads as extra symbols via the DM5. Both the Alesis DM5 or D4 have trigger inputs, so either will work for this kind of setup. The D4 sounds are similar to the SR16; the DM5 has more sounds of better quality.

Given that the crash was in mfc140u.dll, I'd recommend reinstalling the C++ redists:

Two things mainly: - Improve the Fader resolution / responsiveness in HUI mode - Fix send controls when using LaunchKey MK4 in HUI mode

Time+ has always been applied when exporting as MIDI - all we've done is allow you to specify in milliseconds as well as ticks. MIDI Export / Save As is effectively a bounce operation, so the result is "what you hear". Even if we offered an option to bypass the Time+, we'd get users that complain that they needed the delay on one track but not another. By far the easiest way to get around this is to: 1. "Save As" myproject-nodelay 2. Open that project and set all the Time+ to zero 3. Export your MIDI from that project.