msmcleod

Also if you've not got Sonar set to do an automatic background scan, make sure you kick off a manual plugin scan every time you update your plugins.

There are two things in question here: 1. The speed of the drive (e.g. HDD vs SSD) 2. The speed of the interface ( SATA vs SCSI vs NVME ) Depending on the generation of SCSI, SCSI can be faster than SATA (150MB/sec) & SATA 2 (300MB/s), but slower than NVME ( 3,000MB/s to 7,500MB/s ) There are several generations of SCSI, the latest being: Utra320 SCSI : 320MB/s Utra640 SCSI : 640MB/s By contrast SATA 3 is 600MB/s. Obviously these speeds will be limited by the access speed of the drive itself. So I guess the question is, what generation of SCSI is being used and what is the access speed of the physical drive? You may find whoever installed it just picked the fastest interface that the PC could support - if it only had SATA/SATA 2 ports on it, then that explains the decision to pick SCSI. In saying that, the speed of the drive has a HUGE impact here... for me a fairly large Omnisphere patch takes 45 seconds to fully load from a SATA 2 7200 RPM HDD drive, vs 2 seconds from an SSD on the same SATA 2 port.

The biggest plus for me for the Sonitus plugins is their CPU usage. They were originally released back in 1998, when a typical PC was a Pentium running at 200Mhz. The DSP code had to be efficient to run on those machines... but on modern machines they hardly make a dent on CPU.

Have you made sure your Visual C++ Redistributables are up to date? Some plugins force an install of earlier versions, which can be problematic. A link to the latest redists install can be found in this post:

The GPT / MBR is basically the disk's index of what partitions are contained within the disk, so you format the new disk as GPT. I used Clonezilla to backup/restore the old OS partition, not the entire disk.

Converting from MBT to GPT for an upgrade is a major PITA. I had this issue when changing from an MBT formatted 2TB drive to a 4TB drive (which needs GPT to access all 4TB). The way I did it... 1. Use Clonezilla to backup my original OS partition on the 2TB drive as an image to a backup HDD 2. Format the 4TB drive, and install a clean Windows OS - and don't activate it 3. Use PartitionWizard to partition the 4TB drive, reducing my new OS partition to around 64GB, a new partition large enough for restoring the old OS partition, and another partition for data. 4. Use Clonezilla to restore the old OS image to the new partition on the 4TB drive. 5. Boot up the 4TB drive - this boots into the new OS on the 64GB partition 6. Set up a dual boot, so I can boot either partition 7. Boot into the old OS, and set it as the default boot. 8. Remove the dual boot leaving only my original OS as the default boot 9. Finally, erase the 64GB partition - I think I added it to the data partition in the end using PartitionWizard. Steps 6,7 & 8 are the trickiest. You need to use command line tools... so read the MS documentation carefully.

When CbB/Sonar is bouncing audio it's writing to the disk... if anything tries to hijack that file( e.g. AV / cloud sync services), then it can cause a crash as CbB/Sonar is expecting exclusive access to the file. I had exactly this issue when I had my Mega cloud sync service watching/syncing from my projects directory. I've also had it happen with OneDrive in the past. What I do now: Make sure Cakewalk directories - especially project directories are excluded from anti-virus / cloud sync apps. I now have a batch file to do an incremental copy of my projects directory to a HDD backup drive, and its from this drive the cloud sync is done from.

You could delay just the kick & snare this using articulation maps, e.g: The above is using the GM mapping of note 36 for Kick and note 38 for Snare, but you can define as appropriate for whatever drum VSTi you're using.

@Creative Sauce did a video on exactly this scenario.... the title is a slight misnomer, it's actually recording while listening to effects, but it's recording the dry signal - not recording the effects as well.

There's the middle ground compromise that I use... stick in another drive and have a dual boot - same PC hardware, two installs of Windows. I've got one boot that is only for DAW use and another for more general use.

From the help: Magnetic snap. Cakewalk’s snap grid has an option called magnetic snap. This means that when you’re dragging the boundary of an object, you can move the boundary freely until the boundary gets within a certain number of ticks from the snap target. The closer the object gets to the snap target, the more strongly the object is pulled to the target. You can set the strength of magnetic snap to low, medium, high, or off. Note that if you are zoomed out a certain amount, the time boundary around the snap target will appear to be quite small, and you might think that the snap grid is not functioning. If this is the case, zoom in closer to enhance your editing experience. If you’re dragging a whole clip, magnetic snap is not in effect.

It's worth noting that unlike CbB, Sonar is DPI aware. I'm running Sonar with my CPU's integrated graphics, however my two displays are 1080P @ 100%. If you've got a 4K display, Sonar will be drawing 4 x the amount of graphics. In this scenario, having a dedicated GPU may make sense - especially if you've got multiple 4K displays. Not to say that your integrated graphics won't be able to cope - it may be fine... but if you are running 4K displays, bear this in mind.

The Event Module in the control bar allows you do to the same in Sonar/CbB.

If I'm doing MIDI only recording/playback - and by that I mean hardware only MIDI, i.e. no software synths, I always insert a blank audio track in the project. This allows Sonar/CbB's clock sync to work correctly using Audio as the source, which is often far more reliable than Internal. You can always hide the audio track if it bothers you being there.

Actually it does. As soon as you open ASIO4ALL, it opens the WDM driver for your audio interface and sets its sample rate/bit depth to what ASIO4ALL wants. Even when the DAW closes the ASIO4ALL driver, ASIO4ALL stays active in the system tray with the WDM driver still open. Most audio interfaces will refuse to operate in different sample rates/bit depths in WDM / ASIO mode, so ASIO4ALL and the native ASIO driver will be fighting each other. Some audio interfaces won't even allow WDM and ASIO to be used at the same time. Obviously YMMV depending on what audio interface you're using, but the above highlights the main issue with using ASIO4ALL. TLDR: If you're using Realtek, use WASAPI. For anything else, use native ASIO driver for your audio interface. DO NOT use ASIO4ALL unless you absolutely need to, and you fully understand what it's doing.

Project templates and track templates are very different beasts...

Although this is technically true, it's worth putting things in perspective. In any system you're going to have a bottleneck somewhere. In a DAW, you've got disk access speed, memory access speed and CPU speed. If you're using plugins, by far the biggest bottleneck is the CPU. Memory comes in next if you've got 100's of tracks (especially with samples). Disk speed only becomes an issue when you're using a large amount of sample libraries that are streaming from disk, or a VERY high track/clip count streaming from disk. Streaming 32 tracks of recorded audio data with a handful of clips per track isn't going to be an issue for any disk drive. I was doing that on a P166 with IDE drives back in the 90's, and modern portastudios are streaming 24+ tracks from SD cards which are way slower than any hard-disk drive, never mind SSD's. FWIW I'm currently using SSD drives via SATA 2 and have zero issues. A large Omnisphere patch takes around 30-45 seconds to load on a 5400rpm hard-disk drive - on my SSD drives it's around 2 seconds. Would NVMe be quicker still? Absolutely. But does it warrant the extra cost? That's for the OP to decide.

It could be a MIDI message that is bound to a keyboard shortcut. Take a look at your keyboard shortcut settings, and see if you've got MIDI checked... if you have, uncheck it:

I think there's a general misunderstanding here regarding headroom. Regardless of how loud or quiet the waveform is, ALL audio within Sonar/CbB is converted to 32 bit float (or 64 bit float if using the 64 bit engine) as soon as its read from the file on disk. This effectively gives you unlimited headroom during the mixing process (it can literally go to 1000's of db or 1/1000ths of a db). It's only when it reaches your mains out that its then converted back to 24 bit integer, where at this point it could clip, or be too quiet. That being said, the volume fader on a track/bus only has a finite range. This is where normalize can be useful, as it can make a quiet sound louder or a loud sound quieter, meaning that the fader can be used on a more useful range. Yes, there's offset mode - but again, it's still limited in its range. Normalize will not change the existing dynamic range of a clip. All it does is make it louder or quieter. The most common use for normalize is to make quiet audio louder. If the audio is too quiet, then once you've pushed the track fader up to +6db, it can't go any louder. Normalizing the audio will make the whole clip louder, allowing the fader level to be reduced, and allowing you to move it up or down. As for the OP's original question... normalize will NOT smooth out the levels of audio. All it does is turn it up or down. To smooth out the dynamic range, use a compressor plugin.

In your first example, where you'd deleted the section and wanted to copy the other section in its place... use CTRL + ALT instead. By default, the arranger automatically shifts things along as you go. If you don't want this, use the ALT modifier when moving, or ALT + CTRL when copying. The CTRL + C / CTRL + V - the issue here was due to the active track not being the first track. Paste always starts at the active track, regardless of where you copied from.

Is your external controller set up as a control surface? The latest Sonar should be excluding any Control Surface from Zero Controllers When Play Stops.

Your Kontakt library instance is listening on MIDI Channel 1, but you've set your drum map to transmit on channel 10.

The easiest way is to just save your project as a Standard MIDI File. The positions of all of your MIDI clips will be retained within that. Alternatively, you could add a text event at time zero in each MIDI clip. You could then drag/drop the clips to a folder.

The offset can be applied to any MIDI track, including the MIDI track portion of a simple instrument track. Use the MIDI tab at the bottom right of the Inspector to access the MIDI page for instrument tracks. It's impossible to apply a negative offset to live input. You're asking CbB/Sonar to play the note before you have! There are three methods to workaround this: 1. Use a different instrument for recording that doesn't require a delay, then swap to the instrument you want after recording; OR 2. Positively delay all other tracks, leaving the track that requires a delay without a delay; OR 3. Record your part normally, then nudge the clip by the required amount once you stop recording. You can set 3 custom nudge amounts in preferences. Cakewalk by BandLab and SONAR Professional/Platinum only allow Time+ in ticks. The new Sonar allows Time+ in either ticks or ms. If you're using CbB/SONAR Professional: If the tempo of your project is the same throughout, then you can calculate the ticks equivalent in milliseconds for a given tempo and set it accordingly. If the tempo of your project changes, you'll need to create a separate track for each tempo change and do that calculation for each track. To convert milliseconds into ticks: 1 beat is 960 ticks. Say the tempo is 120bpm. 120 beats per minute is ( 120 / 60 seconds ) = 2 beats per second. That means there are 960 * 2 ticks in every second at 120bpm. 960 * 2 = 1920 ticks per second. There are 1000 milliseconds in a second, so 1 millisecond ( 1920 / 1000 ) = 1.920 ticks So the formula is: ticks = ( ( 960 * ( tempo_bpm / 60 ) ) / 1000 ) * milliseconds This is probably more easily done in a spreadsheet (e.g. Excel, LibreOffice/OpenOffice calc):