msmcleod

While Creative Sauce's tutorials are good, they don't go anywhere near as deep as the Groove3 tutorials. He does however cover areas that the Groove 3 tutorials don't (e.g. Arranger, Articulation Maps, multi-output instruments etc), and also offers some very useful tips, so I would definitely recommend watching them. All of the Groove 3 tutorials (both SONAR and CbB) are still very relevant. Obviously there are a few things that have been updated in CbB that will be different in SONAR (e.g. the Export Audio dialog), but 99% of the content is still relevant. Streamworks Audio's SWA Complete SONAR X2 and SWA Cakewalk Sonar X3 - New Features videos although older, are free and just as deep as the Groove 3 ones, and are still more than 90% relevant.

No - it doesn't work like that. The config preset is a separate file on disk that contains a backup of any configs in your registry settings, and the contents of several .ini /.dat files. Essentially it's a backup of your global settings. What it doesn't contain: Any user specific details (e.g. user name, serial number etc) Plugin inventory Project specific settings Restoring a preset re-applies these settings to the registry and .ini/.dat files. Once it's applied, it becomes the current config. Any project specific settings will of course be in your Project Template. The main uses of the feature are: Saving a backup of a working config so it can be easily restored either to the same machine or a different machine Allowing users with several different hardware profiles an easy way to switch between them (e.g. different MIDI devices, or different audio interfaces) An easy way for Cakewalk support to replicate your current configuration in order to reproduce any issues

Make sure this is checked: Preferences->Display->Display all times as SMPTE

You'll need to convert each of the tracks to split mono tracks to do this: 1. Select the Track you want to split 2. Select "Bounce to Track(s)" from the Track View's "Tracks Menu" 3. When the dialog pops up, ensure the destination is set to "New Track" and select "Split Mono" from the Channel Format drop-down 4. Click OK. 5. Do this for both the orange and green tracks. 6. Delete the tracks you don't want and pan the remaining tracks - the orange one hard left, and the green one hard right You've not got two mono tracks you can edit independently. If you need to make them a single stereo track: 7. Select both tracks 8. Select "Bounce to Track(s)" from the Track View's "Track Menu" 9. When the dialog pops up, ensure the destination is set to "New Track" and select "Stereo" from the Channel Format drop-down 10. Click OK. 11. Delete the original mono tracks

Yes. It includes pretty much everything - audio & midi device config, control surfaces, all of your options preferences and any global options throughout the app. You can save/load presets either within preferences, or alternatively specify a config preset as a command line option (so you can have different shortcuts on your desktop that launch Sonar with different configs).

The way I've done it in the past is as follows: 1. When the routing is correct, close Cakewalk and copy AUD.INI from %APPDATA%\Cakewalk\Cakewalk Core to a backup location. 2. If the problem occurs again, close Cakewalk and copy your backup back to %APPDATA%\Cakewalk\Cakewalk Core 3. If the problem is still there, reboot, copy your backup back over again, then start Cakewalk. The new Sonar will have configuration presets, which will make this far easier.

TouchDAW for Android, or TouchOSC (for iOS & Android) are good alternatives.

I think this is probably the likely cause. Whenever I've had similar issues (though, normally this is with MIDI devices rather than audio), it's been a power-on order thing. General advice: 1. Always use the same USB ports for your audio devices. Swapping them around causes Windows to see them as a different device. 2. Switch on your audio devices before you switch on your PC 3. Once you've switched on your PC, give it time for the L20 to initialize before you start Cakewalk. Opening the L20 ASIO panel before you start Cakewalk will show you if it's fully ready to go or not. 4. Make sure you've NOT got any aggregate ASIO drivers installed - i.e. ASIO4ALL, or the Steinberg, FL Studio or Magix equivalents. The way these drivers work is by wrapping your real device's WDM drivers up as ASIO drivers, which can cause the real ASIO driver to be blocked when Cakewalk tries to open it.

A couple of things that may be different from my setup: 1. I don't use the Korg USB drivers, as they keep breaking with Windows 10 updates. It works fine as a class compliant device. 2. Set your MIDI mode to MME rather UWP within Cakewalk.

SONAR Platinum was rent-to-own. If you paid 12 consecutive monthly payments, you'd own the version of the product at the point of your 12th payment. If you paid 12 months up front, you'd own the version of the product exactly a year after your payment. Once you owned the product, that version would continue to work regardless of whether you continued to pay or not. This is different from a subscription, which disables the product (either partially or fully) when you stop paying.

In my experience, the Korg nanoKONTROL 2 / nanoKONTROL Studio are by far the easiest to integrate with Cakewalk - as long as you're using it in Mackie/SONAR mode that is. It's pretty simple to set up... just follow the steps in the nanoKONTROL 2 manual: SONAR 1. While pressing and holding down the SET MARKER and REC buttons, connect the USB cable from your computer to the nanoKONTROL2. 2. Open the “MIDI device” window in SONAR, then select nanoKONTROL2 for “Input” and “Output.” 3. Open the “Controllers/Surfaces” window, then select “Mackie Control” for “Control Surface.” 4. Select nanoKONTROL2 for the MIDI In/Out ports used. If you're using it as a generic ACT controller, your mileage may differ however. Swapping between nanoKONTROL 2 "modes" can be a PITA ( i.e. using it in Mackie/SONAR mode, then changing it to CC mode) so I'd avoid doing it unless you want to go through the setup steps every time you swap. Better to get an additional (and different) controller so you have one for each mode. But to answer the original question of the post... "How many users does CbB have?"... go here: https://bandlabtechnologies.com/brands/cakewalk/

Ah yes, this makes sense - the selection has a time extent which in this case is dictated by the clip extent. So it will only select nodes that are under the clips that are selected.

I suspect this is down to how you are selecting things. Select All selects all tracks, which subtly different from selecting clips - and it's the clip selection that triggers selecting the associated track envelopes. For some operations, there is a notion of "implied" selection, where tracks are selected because all their clips are (and vice-versa), but not everything checks for this. Also synth automation, although shown on the track, isn't actually "owned" by the track the envelope is shown on - instead it's owned by a hidden automation track ( this is also why changing the shown automation track is such a simple operation - it only affects display, not who owns it). So this is why volume envelope is selected in this situation, but the synth envelopes aren't. I'm not 100% sure what is going on here, but it could be that the misbehaving envelopes are absolute time based perhaps?

There's a reason why, within Insert Soft Synth Options, "Display Automation On" defaults to "First MIDI Source Track" - it's so both your clips and envelopes can reside on this track and be selected together. This would be my first recommendation. The second would be to ensure you're using either Simple Instrument or Per-Output Instrument tracks. That way, you also get the audio track's volume automation showing. If you're using split instrument tracks, there are workarounds however: 1. If you want the audio track's volume automation to be selected along with the MIDI clip, the simplest way is to use CTRL + left click to also select the audio track. If you're using Copy + Paste (as opposed to CTRL + drag), remember to give the correct track focus when pasting. Alternatively, select the MIDI & Audio track and temporarily "Make Instrument Track". You can then do your operation, then split afterwards. 2. Within the Synth rack, the dropdown in the header allows you to change which track you want the automation for the selected synth to be shown on. This can actually be ANY track you want (even unrelated ones), and you can change it as many times as you want. So you can move your synth automation to the track who's clips your moving prior to doing your operation.

Also check that the following directory is not compressed: C:\Program Files\Cakewalk\Shared Utilities\Internal

@Jim Stamper - we've identified the issue and a fix will be available in the next CbB drop.

Modern cars certainly do have bugs, for example: - I drive through a spot that has a lot of tree cover, so my headlights switch on... it thinks it's dark, even though the dashboard clock clearly shows its the middle of the day. It takes up to 5 minutes to work out that it's not still dark and turn the headlights off. - The automatic wipers come on with a single drop of water, but then don't when it's raining lots of fine drops.

For any of these services, check the fine print... there are so many gotchas there it's not funny. I've heard stories of people getting copyright strikes on YouTube from their own material, just because they've used a distribution service in the past. Whatever you do, don't base your decision on price alone.

Although the Add Track button does have some options that will override those in the dialog, for the most part the options from the Insert Synth Options dialog will always be respected (and remembered for next time).

The TTS-1 uses exactly the same samples as used in all of the Roland Sound Canvas modules - in fact it's actually a software emulation of the Sound Canvas. The D110 predates the Sound Canvas by quite a few years, and is a totally different beast being based on LA synthesis. AFAIK there are no piano samples in the D110 to speak of (except maybe the shortest piano attack you could imagine). I've got a D110, and the piano sounds are awful... but pianos aren't what you'd use this synth for. The U110 / U220, which were around at the same time have piano samples and aren't that bad for the time, but are to my ears inferior to the Sound Canvas (and therefore the TTS-1 too). I've got both the D110 and the U220 (as well as the MT-32 and CM-64)... they have their uses, but nowadays not so much! The D550 is the only one that still has charm for me.

@FaithD0ntFall - check your Templates folder within Preferences->File->Folder Locations. The default setting is: C:\Cakewalk Content\Cakewalk Core\Project Templates - this is where the installer puts the stock project templates. If you've got it set to a different folder, make sure there are actually project templates in there.

FWIW, the new Sonar will have Project Start /Project End markers.

Living in a Box - Living in a Box:

Compare the size of the files on both computers. Cakewalk can store multiple waveforms in a single file (the .wav file format supports this), but some file transfer programs try to get clever and try to re-interpret the file. This was a common issue with Cakewalk bundle files. If the file sizes are different, try zipping up the files into a single zip file and transfer that.