msmcleod

That's the official site, so it'll be the best place.

Whether it shows sharps or flats seems to depend on the current key (ALT + SHIFT + 6).

Are you using your onboard sound device? These are known to be noisy. Quite often if its on a laptop, running it on batteries solves it (but obviously causes issues with performance etc). If you've not got a separate audio interface, consider getting one - something like a Focusrite Scarlett 2i2 would be ideal as a starter interface.

I use a ground loop isolator like this, between my audio interface and my monitors: They're around $9 / £6 from Amazon.

The Bank No. / Program No. must be being reported back from the VSTi. I've got a few VSTi's that I know respond to bank select (like Yamaha's old XG softsynth), but don't report a patch list. If I host the XG VSTi in Cantable, and route from Cakewalk via a hardware MIDI interface it will receive the Bank Select, but hosted in Cakewalk, it never gets it. Same with SysEx.

In general, if you've got a MIDI interface then any MIDI compatible keyboard controller will work with Cakewalk. Most keyboard controllers are USB nowadays (the good ones are both USB & MIDI), but again, most will work with Cakewalk. I'm unaware of any that don't. As far as recommendations, it's a bit difficult to answer this without knowing a bit more about what you're wanting to use it for. There's basically four types of keyboards: 88 Note weighted keyboards (basically like a piano). 25, 37, 49, 61, 76 note full size keyboards - these can be semi-weighted or not. So basically your standard organ or synth type. 25, 37, 49 & 61 "Minikey" keyboards - like the old Yamaha portasounds. 25, 32 & 37 note nano keys - really small keyboards, usually used for non keyboard players, portability (i.e. will fit in a laptop bag), or for triggering keyswitches on some VSTi's. All of them may or may not come with the following: Velocity Sensitive - the harder you play, the louder the sound. Most have this, but check just the same - IMHO it's really a must. Aftertouch (Pressure sensitive) - this is rarer nowadays, but basically it can alter the sound by "pushing" the key with more pressure whilst you have the key held down. I quite often use this for vibrato. Pitch Bend Wheel - for doing pitch "bends" ( a bit like bending a string on a guitar, or using the whammy bar) Modulation Wheel - usually used for introducing vibrato, but can be assigned to most things like filter cut-off, or a leslie speaker effect. DAW Controls (such as faders, transport controls), extra knobs & sliders to alter your synth sounds Obviously that's a lot of features to take in, and there's dozens of keyboards out there depending on what you want. I'd take a think about what you're going to use it for, then shop around. If you've found something you like feel free to ask for opinions here. [Edit] Ones I'd personally recommend: 88 note: Studiologic SL88 Studio Full size: Too many to mention, but Alesis & Native Instruments do good ones, as do M-Audio. Cheaper options are Samson & Behringer. MiniKeys: The Korg microKey range NanoKeys: M-Audio Keystation mini32, Korg nanoKey

If you did record audio, and you didn't check the "Copy all audio with project" setting when you saved it, e.g.: Then your audio will be saved in your global audio folder, as specified in your preferences: To find out what the actual audio files are, select Project->Audio Files from the menu: This will bring up a dialog, showing all the audio files used by your project:

All your RAM sticks need to be the same. So just remove the smaller one, or replace it with one EXACTLY the same as the other one.

The TTS-1 that comes with CbB is 64 bit, but I was thinking that because you had Sonar 6 installed it may have been trying to load the 32 bit version. It sounds like you've got things working of a fashion... Have you tried running Cakewalk as Administrator? As far as the transport is concerned, to automatically rewind, set this option in the track options:

Nah, I cheated... it was a 1TB SSD ?

Yeah, I noticed that. It could well be the issue. All RAM sticks should be exactly the same capacity and speed. RAM issues can be a nightmare to track down because they're so intermittent, but this seems an obvious one. I'd recommend ditching the 1GB stick.

FWIW, for giggles, I made 100 pure audio tracks in Cakewalk on my 2.6Ghz i7-6700HQ laptop. Every track had the pro-channel engaged (compressor. EQ and console emulator), and a Scheps 73 EQ. They all had to have their faders turned down considerably as it was LOUD with all tracks going at once. But not once did it complain.

I would contact support over your password issue: https://help.cakewalk.com/hc/en-us/requests/new

Are you using any look-ahead plugins ? Linear Phase plugins can introduce latency of 1 to 2 secs, depending on how far ahead they need to look. If you are using them, you can turn off the PDC if you need to do any tracking. But any plugins that have to look ahead aren't really designed whilst your still tracking - they're for mixing only.

I wonder if it's trying to load the 32bit version of TTS-1. Is there more than one entry for TTS-1 ? As for your other synths/effects, you need to make sure that their location is included in your VST scan path. Also, note that whilst BitBridge can load 32 bit VST's/VSTi's in Cakewalk, 32 bit DirectX plugins (such as the TTS-1 that came with Sonar 6) will not work and will likely crash.

I wonder if updates to the plugins affects this. In other words, if the VSTi parameter list changes, it could affect Cakewalk's ability to restore the patch. The only thing that goes against this theory is that the normal workaround to stop this happening is to save your VST patch as a Cakewalk-style patch. I'd have thought the mechanism of reloading was the same for both, but maybe not.

I've tried them on Windows 10. They work fine.

Unfortunately not. Instrument files don't work on soft synths. Cakewalk also doesn't send Bank Select messages (Ctrl 0, Ctrl 32) or SysEx to soft synths. I really wish it did. Cakewalk retrieves the patch list from the VSTi itself. VSTi's have a list of parameters. Cakewalk saves the values of these parameters along with your project, so they're recalled the next time you open it.

I've not found that myself. All the key shortcuts work for me. The only thing I noticed was a fairly long delay before it played, like about 1.5 to 2 secs, but it did play and worked as expected. I actually prefer the workaround I suggested though, as it displays the time-frame at the top which I find useful.

+1 for CCleaner.

Personally, I don't see anything wrong with using take lanes as a way of building up a more complex part made up of all the takes. This is exactly what sound-on-sound mode is all about. If you want comping, use comp mode, otherwise use sound-on-sound. I don't find overwrite mode particularly useful. I'd rather use sound-on-sound with mute-previous-takes enabled - at least then I can go back to previous takes if necessary.

MTransientMB is actually a really useful tool. Being able to affect the transients of only a certain frequency range whilst leaving the rest alone can really help. It makes a normal transient shaper seem like a sledgehammer, whilst this one is a craft chisel.

Full screen is working fine for me. The only thing I can suggest as a workaround is to make a separate screenset with the multidock taking up the whole of the track area, and the track inspector minimised. You want to set the video stretch options to "Stretch to Window". You can then press "C" to hide the control bar (press "C" again to show it). This will show the video on most of the screen, e.g.: The advantage of this approach is, that if for example, you set this to be screenset 2, with your normal tracking in screenset 1, you just press "2" to view it "almost full screen" and press "1" to go back to normal tracking view.

Behringer used to provide their own official ASIO drivers for this, before they decided to force you to use ASIO4ALL. They still work on Windows 10, and perform much better than ASIO4ALL. Behringer have since removed them from their website, but you can download them here: http://www.123dj.com/audio/mp3s/uca222.html

Having been badly burned using my Amiga live in the 80's, I've steered away from using computers live. At first I used an Alesis DataDisk when things were all MIDI (it was also great for sending custom patches via sysex and setting up my patch list for the next song). Then I moved on to the SMPro V-Machine (a poor man's, very under-powered version of a Muse Receptor), mainly using it to play sf2 versions of my plugins/hardware sounds, although it can cope with some CPU friendly VSTi's: Of course nowadays, laptops are built to be portable and should be fine on the road... not sure I'll get over the scars though!