msmcleod

Have you manually moved any of the files from their original locations? The control surfaces are COM objects that are registered at the time of installation - they can't be moved, else you'll get exactly what you're seeing.

+1 to what @scook has said. Your total round trip is 18.3 ms... you want to aim for less than 10ms if not less for recording in real time. Try reducing your buffer size to 128 or even 64 ( personally, I can't tolerate playing with anything above 64 ). Bypass any effects you don't actually need while recording - you can always enable them afterwards and/or turn up your buffer for mixing. Alternatively, freeze the other tracks with the effects on them if you really require them to be heard as is when recording, then unfeeze afterwards. It's quite normal to have a low buffer size of say 64 for recording (with minimal effects), and then jump to 512 or 1024 for mixing later.

Even if TrueIron was TWICE the price it currently is... it's still worth jumping on It's probably my most used plugin.

Ever since my early days of using sequencers back in the 80's, I've always been acutely aware of how the sustain controller works. I remember watching a friend cutting and pasting my piano parts in Pro 24 and grimacing thinking "you can't just do that - what about the sustain pedal events!!!" For the most part, the sustain controller is just a switch. Unless you've got reset all controllers set as default, if you stop playback when the switch is on, it'll stay on until the synth / piano receives an off switch. Similarly, if you crop a clip so it hides the sustain off event, the sustain will continue to the next part. Like it or not, this is just how MIDI works. I got into the habit a long time ago of inserting a CC#64 : 0 (sustain off) at the beginning of every clip in piano parts to minimise unwanted sustains. IMHO you should treat your CC sustain events as being as important as the notes, and be aware of where they are.

I actually prefer to do the JBridging all within CbB rather than use JBridger. There's only a handful of 32 bit plugins that work better with BitBridge (and if IIRC, they're the old Cakewalk ones), so nearly all my 32 bit plugins are JBridged by setting the "Use JBridge Wrapper" flag within plugin properties. There's one advantage in doing this... when using JBridger, it assigns a new unique plugin DLL and a new Id for the wrapper, which is different from the original plugin id. If you use the built in JBridge wrapper in CbB, the old plugin id retained. That way, if you swap back to BitBridge, or even manage to get a 64 bit version of the plugin at a later date, CbB will recognise it as being the same plugin and load it normally whether it's BitBridged, JBridged or 64 bit native.

Ok - other things that can cause this: 1. Cheap USB MIDI "cables" can cause this because their internal buffer size is tiny. 2. Check your MIDI settings within cakewalk ( MIDI Playback & Recording) Make sure "controller" is checked Make sure your MIDI Prepare Buffers aren't set to some crazy value - the default of 200 should be fine for the vast majority of projects. If your project is particularly large (e.g. 75+ MIDI tracks, maybe try 250 or 300 ) Some older MIDI interfaces have problems with UWP - try MME (you need to have no projects loaded to change this)

I think you have to check the MIDI radio box first with the Enabled checked , then save, disable the checkbox then change it back to Computer.

Select your clip(s), uncheck "Use Track Colors" in the clip properties and set the Foreground (waveform) and Background colors: e.g.: [Edit] If you want your colors to default to more "vibrant" ones all the time, change the colors within Preferences:

Check your keyboard shortcuts to see you've not got MIDI Controller 64 mapped as SHIFT:

You need to change the clip Time Base to "absolute" then lock the clip position.

You need to change the clip Time Base to "absolute" then lock the clip position.

This is exactly how I work too. I've got well over 200 unfinished songs now - mostly 8 to 32 bar sections. What I've started doing is every time I save a project, I export it as an MP3 giving it the same name as my project. I copy the MP3 to a PREVIEWS folder, which I've added to the media browser. I don't bother with individual stems - just the whole export: When I'm stuck for a chorus for my verse (or vice versa), I go to the media browser and click through them so see if any might work. If they might, I'll drag the mp3 on to an audio track, cut it up / speed it up etc... if it sounds good, I'll open up the original project and copy the tracks over. For MIDI, it's easy enough to work with... audio I'll re-record if the key is wrong.

When a split is across lanes, they always move together when they line up. The way I get around this: 1. Select the whole lane 2. Nudge it to the right 3. Move the split well out of the way 4. Nudge it back to the left 5. Adjust my split in the one lane

And it's here....

FYI - the early access is now out with a keybinding to toggle between clip gain automation / clips:

The way I've got around this in the past, is to: 1. Create a new Cakewalk project based on the "Basic" template 2. Navigate to your .wrk file via Cakewalk's media browser 3. Drag the .wrk file to the clips view from the media browser. Save your new project.

If you're using a Realtek device, switch to WASAPI shared.

@Jim Fogle - when you same multi-channel outputs, do you mean audio outputs? The video I posted earlier in this thread shows how to do this for Omnisphere. Unfortunately the process is different for every VSTi, so you'll need to refer to the user guide for each VSTi. I'm sure I did a similar one for Kontakt at some point... I'll try to dig it out.

Cakewalk only does load balancing on VST effects... not on VSTi synths.

Omnisphere is 8 channel multi-timbral. The setup part in the Multi tab is to route each channel to a separate audio out, so each instrument track is (a) on it's own MIDI separate channel and (b) on its own separate audio track... but yeah, they're all going to the same omnisphere instance. Omnisphere (which the OP was querying about) is actually pretty good with cores... so one instance works well vs multiple instances.... Kontakt is the same, if it's set up properly. But as you say, you do lose the ability to individually freeze each track - it's none or all of them.

I'm guessing your workspace is set to "Basic" ? (see top right hand corner ) The Basic workspace hide's a lot of the more complex functionality. Set your workspace to "None" and you'll see everything... including the Event View.

The easiest way to do it is like this:

It could be, but it could also be your USB sleep settings. Make sure USB sleep is disabled for all your Audio & MIDI devices. It may be easier just to disable USB sleep altogether in your Windows power config.

I think we're getting our wires crossed here... So if your filter is currently set to CLIPS, you can use CTRL + drag to adjust the overall clip gain envelope if your mouse is on the lower part of the clip. If your filter is set to Clip Gain Automation, CTRL + click will work anywhere in the clip to adjust the overall gain. If your filter is set to Clip Gain Automation, you can make a selection by left click dragging along the bottom of the clip and drag from the very top of the clip (without any keyboard modifiers) to adjust only that selection.

CTRL + drag should work, but you need to be dragging from the lower half of the clip. The next release will have a key bindable shortcut for toggling between clip gain & clips, so watch out for the early access.... shouldn't be too much longer now.