msmcleod

Once you've installed Acoustica 6 Basic Edition, run the attached reg file. CbB_Acoustica6_BE.reg

This is one of the few MIDI "cables" that will probably be fine - cheaper ones are a waste of money due to the buffer issues I mentioned in an earlier post. However, you will still have issues when using more than one of these: neither you, or Cakewalk will be able to tell which is which, and unless you leave them permanently plugged in to the same USB port on power up every time, they're likely to randomly switch around as Windows decides which order they should be in.

I've no idea what a MIDI hub is? A network hub or USB hub merges data from several ports into one... so I guess a MIDI hub is a MIDI merge device? This isn't a MIDI merge device. This is an 8 in / 8 out MIDI interface. It's USB powered (USB3), although I've had zero issues using it with USB 2. I don't see why it would need to have a separate power supply. USB power is more than enough to power 16 x serial ports (which is all MIDI is). It's not as if it's powering anything external - unlike say, a Scarlett 2i2 which has audio preamps and has +48V phantom power... all over USB 2. The MIDI spec is 31.25K baud over 5 pin DIN connectors. USB Midi connectors running at USB speeds are part of the problem everyone is having. The computer sends data to it at USB speed, but it has to send it out at 31.25K. For it to do this, it needs to "hold on" to the data it receives in a buffer and send it out at a slower speed. Lower quality interfaces have a very small buffer, which gets full way before it has time to send it out. All I can say is, I've used this interface for a number of years now with heavy MIDI traffic, and it's never let me down.

ALT+SHIFT+5 now toggles the Tempo Inspector and the Tempo Track (just underneath the arranger track), both of which have replaced the old tempo view.

I hate it when manufacturers do this. CC 7 is for volume - and there's a good reason for it: When a synth receives a "Reset all controllers" message, it's meant to reset all of the CC's to their default. For everything apart from CC 7 and CC 10, and CC 11, this is zero.... which means CC 1 gets set to zero. For CC 10 (pan) it's 64 which is centre, for CC 7 (volume) it's 96, and for CC 11 (expression) it's 127. If volume is CC1 and it's reset, it gets set to zero which means no volume. Native Instruments are guilty of this too with some of their instruments. I really wish plugin manufacturers would respect and follow the MIDI spec.

Go to the Downloads section of the website, then scroll down to "Old Versions and Discontinued Products" - you can still download Acoustica 6 Basic Edition.

We've no plans at present to introduce an integrated audio editor. However, it's fairly straightforward to add a 3rd party audio editor to the Utilities menu. I use both SoundForge, and Acon's Acoustic 6 Basic Edition (which is free). Once added, you just select the clip then pick the audio editor from the tools menu and it'll load with your waveform ready to edit. Once you save, Cakewalk picks up the edited waveform.

Unless you've specifically changed Cakewalk to run as administrator, it should be running as a non-elevated app. To check if it's elevated, you can right click on the Cakewalk shortcut, select "properties" then go to the Compatibility tab of the properties dialog. If it has "Run this program as administrator" checked, then it'll be started as elevated. It's worth checking Cakewalk.exe itself too. To make it not run as administrator, just uncheck this setting and click "Apply".

One thing to note: Before you bounce, the split clip is a complete copy of the original - it's just trimmed at the start and end. If you bounce however, you will lose everything that is hidden by the trim. If you're lining up individual drums, this may be exactly what you want... but not always, so something to bear in mind. Another thing to bear in mind: When a region effect such as Melodyne is "active", Melodyne has ownership of the clip until you render the region FX. Rendering or bouncing gives ownership back to Cakewalk. As such, you should avoid editing any active region fx clips outside of Melodyne until you've rendered the region fx.

I meant, that the sonitus pluigns themselves are only DX plugins. dxshell and dxishell are wrapper DLL's to wrap up DX plugins. Those wrappers aren't supplied by Cakewalk though.

I'm not really sure what you mean by move part of a clip, but here's an example of two things it could mean:

The No, they're just still dx. dxshell.dll / dxishell.dll are not installed by, or distributed by Cakewalk. These must be have been installed either by yourself or by another application. Some users use these to access Cakewalk DirectX pluigins in other DAW's.

Both VST plugins and DirectX plugins are DLL's. The difference is the API / methods those DLL's expose. 64 bit programs can only load 64 bit DLL's, and 32 bit programs can only load 32 bit DLL's. Although you can use 32 bit plugins in a 64 bit DAW, the DAW isn't actually loading the plugin directly. Instead it uses JBridge or BitBridge (or equivalent). These are 32 bit applications that communicate with the DAW using RPC calls - this is usually via network protocol, even though it doesn't ever pass over an ethernet cable. dxshell.dll and dxishell.dll are indeed DirectX wrappers. They essentially translate between the VST and DirectX API's. For those interested, you can get them here.

When you load a MIDI file into Cakewalk, the first volume, pan and bank/program change for each track is transferred to the track properties. As they've been transferred to the track properties, you won't see them in the event list, but you can edit them via the track inspector. Any further pan/volume/bank select/program changes in the track will appear in the event list. When you export/save as a MIDI file, the volume/pan/bank select/program changes that were transferred to the tracks will be added as MIDI events at the beginning of the MIDI file. The most common workflow for users is to start with a MIDI file, then continue as a Cakewalk (CWP) project, so it makes more sense to reflect these in the track properties rather than having to edit MIDI events in the event list. For more details, refer to the Reference Guide PDF (page 1455).

To record in mono, set your track input to either the L or R, depending on which input you're plugged into - i.e. "L" for odd numbered inputs, "R" for even numbered inputs: To record in stereo, pick the stereo (S) input:

You can adjust existing envelope shelves by holding down CTRL and moving the shelf:

I really wouldn't use those MIDI -> USB cables for a couple of reasons: 1. The internal buffer is tiny, and are liable to stuck/missing MIDI notes especially during heavy MIDI traffic (i.e. when using pitch bend, modulation etc). 2. If you use more than one of them, they're impossible for both you or Cakewalk to tell them apart, as they'll all show up as the same device.

Select the clip, then select Process->Apply Effect->Normalize from the main menu. Pick a sensible db level, such as -3db, the click OK. In future you should try to record at a higher level - although 24 bit audio has a huge dynamic range, having to normalize very quiet signals will also bring up the volume of any background noise.

CAL scripts can be bound to keys (or MIDI notes) in Key Bindings - so the easiest thing is to bind the key first, then get stream deck to invoke it.

Freezing is really just a short-cut to a bounce, so you can always bounce the buses to new tracks using "Bounce to Track(s)" Alternatively, as @gustabo has mentioned, Neutron can be very CPU hungry. Bypass each "family" of FX individually to see if you can narrow down the one that is causing the most CPU hit, and consider putting in an intermediate bus between your existing buses and the master bus, putting a single instance of the problem plugin on that bus. Other things to try: 1. Make sure your Cakewalk projects directory and global audio directory are excluded from any virus scanner or cloud sync app. 2. Try disabling your network interface - this may not actually be an issue, but I've been caught out 3 times wasting hours trying to troubleshoot performance issues only to find Microsoft was downloading an update in the background. 3. Double check your audio settings, and systematically try different configurations - by systematically, I mean: a) Write down your current settings b) Either change the settings one at a time and compare, or write out a table of the various settings going through the combinations. The settings to try: Audio->Playback & Recording: Plug-In Load Balancing on/off Use MMCSS / Enable MMCSS for ASIO Driver (try all three combinations) Audio->Configuration File: ThreadSchedulingModel - try models 1,2 and 3 (click "Reload Config Settings" after changing this) There are 12 different combinations of the above - you could try each one, and see which one performs best:

FWIW I used to use the MIDIMan interfaces, but the drivers do not play nicely with Windows 10 any more. I'm using two MIDITech MIDIFACE 8x8 (one in the studio, one in my office) - they also do a 4x4 version. It's class compliant, but has no issues with heavy MIDI traffic.

Check your MIDI driver mode in preferences ( MIDI -> Playback and Recording). If it's set to UWP, change it to MME (or vice versa), then restart Cakewalk and try again. Note that you can't change MIDI driver mode while there's a project loaded.

If it's Windows 7 64 bit, then CbB should work fine. It's not officially supported any more so you'll get a warning on setup. In the future there will come a time when we're forced to use Windows 10 API calls to support newer features, but for now Windows 7 is working fine.

FWIW - I can run SONAR Platinum on a Dell Vostro 1700 laptop (Intel Core Duo at 2.2Ghz with 4GB Ram) on Windows 7 32 bit, and CbB on Windows 10 64 bit on the same machine (it's a dual boot). I have zero problems recording 16 simultaneous tracks, while playing back 32 tracks. Obviously there's a limit to how many VST's I can use, but I've found the ProChannel and Sonitus FX to be very light on CPU - and in any case, the Sonitus FX are exactly the same as they were in Sonar 8.5. I've not seen any noticeable performance difference between Sonar 8.5 and CbB - in fact, in anything, there have been optimizations since 8.5 which make it slightly more efficient. I've also had no issues loading Sonar 8.5 projects into CbB - although to be fair, I did convert most of them at the time of SONAR X3.