David Baay

Cool. I thought it might just be glitch due to the high volume of downloads during the GB. I did the Syner-V installation shortly after the problem was mentioned and just the first part was missed. Downloading and installing manually fixed it.

I know there are a lot of posts about soft synth port assignments changing when hardware ports go missing (arguably user error) or, similarly, when soft synths change the number of ports they present to the host (not ideal). But that problem will resolve itself when the missing ports are restored so long as you don't save the project in the bad state. Other than that, I am not aware of any confirmed issues with CbB's handling of MIDI ports that aren't 'just how it works', like inputs getting assigned to Omni when you have Always Echo enabled and don't deliberately assign a specific port and channel. But, enough hijacking of this thread. If you have a recipe that's even somewhat repeatable - and not synth-specific - you should post it to the Feedback forum.

Yes, I was making that mistake - cleared up a few posts later.

Maybe not user error, but not universally experienced, either, so won't get fixed until you can find a recipe and share it with the Bakers. Not likely the OPs' issue in any case.

I have seen that happen previously with a Syntronik 1 synth. I ended up just manually copying the missing folders from the extracted installation files to the samples directory. Worked fine. EDIT: on re-reading I see the issue is not just that the files weren't installed, but that they weren't even downloaded. In that case you can download the missing parts from the IK website, extract them, and run the installer.

8 Freebies!

I'm not sure what that's referring to...? I was suggesting a possible misconfiguration by the user not some inherent problem with CbB.

Set a loop to start at the first marker and encompass the whole piece, then W will take you to the first marker. I use this whenever I want to repeatedly return to the same non-zero starting point. Hitting W repeatedly will alternate between 1:01 and the start of the loop.

I have always presumed they do this so that bass parts are playable on smaller controller keyboards without transposing. But, yes, you would expect a given vendor's products/patches to be consistent.

Do track and bus meters show signal from the start? Almost certainly an interface/driver issue. What is it? Possibly failing pre-amp section if you've had it for a long time. Try the headphone out if it's an external interface.

Was going to suggest ye golden olde problem: Punch region is set further out in the timeline. But if audio recording is working in the same region where MIDI recording is failing, that would not be it. Cannot think of any other config issue that would have MIDI being echoed but not recorded unless possibly another track is doing the echoing and the armed track has the wrong Input port/channel assignment...?

Indeed. I was mistakenly thinking the limit was 1/3 rather than 30%. Tune in next week for another episode of Stoopid User Tricks. ;^)

It seems likely this is project-specific or CbB has gotten into a bad state in RAM. If it's reproducible in a new project after restarting CbB, it would help to know the exact sequence of splits and moves. I'm not able to reproduce it in general.

Are you trying to switch projects with the transport running? If so, that seems like asking for trouble. In my experience, the audio engine will enable automatically in the newly focused project within a second of switching when playback is stopped, but there may be some dependency on the audio driver (MOTU in my case). Too avoid any glitches I've gotten in the habit of disabling the engine (by a keybinding) in the currently active project before switching but I sometimes don't bother and have not had any trouble recently. Having more than just the main program window open may complicate things depending on how you're switching projects (i.e. choosing from the Window menu or by Ctrl+Tab or by clicking a visible part of the track view for the other project).

Click the Audio tab at the bottom of the Inspector to show audio controls of the Instrument track.

Looks like the GB is well on it's way to 10 freebies needed to get all 11 new instruments so I'm in now for the princely sum of $35 plus 15 JamPoints. Should have been able to use 16 but for some reason it only allowed 15. I demand to speak with the manager of this corrupt enterprise immediately if not sooner!!!

Shift+T to expand lanes on the track. Definitely appears you have some earlier muted takes from recording in Comp mode. You can just delete the un-needed lanes if you're happy with the whole of the latest take.

Show the Tracks pane via the View menu or dragging the splitter from the right side of the PRV and select the track you want to edit. If you drag across multiple track numbers, the first one you click will be focused and the others will show as gray. There are more options for managing multiple tracks. Definitely an area you will want to review the documentation: https://www.cakewalk.com/Documentation?product=Cakewalk&language=4&help=EditingMIDI.03.html

Unlike MIDI Input selection, output port and channel are separate widgets. Channel is just labeled C. Here's a link to an image that won't insert inline for some reason: http://static.cakewalk.com/documentation/Cakewalk/EN/images/Playback.24.1.png

Cakewalk is not detecting that the driver for the keyboard (if USB MIDI) or MIDI interface (if the keyboard is connected by a DIN cable) is loaded. Reseat the cable and power-cycle your keyboard/Interface or reboot with it powered up and make sure it's available and selected in MIDI Devices.

Yes that's possible. it's not clear from the tightly cropped screenshot with only the M:B:T ruler how extreme the zoom level is.

I don't understand what you mean by "previous project" here. All I know is that locking a screenset with the VSTi GUI open will cause the behavior you're describing, and I'm not sure what else would. I don't use Workspaces, and my description of how screensets work is based on that. There is interaction between Workspaces and Screensets that can get confusing. Possibly that is contributing to your dilemma. FWIW here's a discussion that covers some of that:

I can't replicate either the audio lines left hanging outside the clip or bounce failing to honor the new boundary. Was that flatline audio created by slip-editing a clip longer in the first place?

It's a little odd that SI Bass is programmed that way, but I would say in general it's a best practice not to overlap notes on the same note number. I've encountered a number of synths over the years that don't handle that well - usually when playing third-party MIDI files as my own are always recorded from a keyboard in real time and a keyboard will never generate overlapping notes on the same note number.

That would be standard operating procedure to avoid receiving input from unintended ports, either physical or virtual (e.g. output from a MIDI-generating drum VSTi). This is not a problem if Input Echo is disabled, but if you have Always Echo Current MIDI Track enabled in preferences, every MIDI/Instrument track needs to have an appropriate port/channel selected for Input.