msmcleod

Some videos on the Loop Construction View - some cover general groove clip stuff, but soon get into the Loop Construction View. SWA Complete Sonar X2 (35/50) SONAR X2: Get Started - Loop Construction View Groove Clips and Looping-Cakewalk by BandLab Tutorial

I think he's mixing up native ASIO drivers with ASIO4ALL.

IIRC, the tempo map is only loaded / saved when you do an Open or Save / Save As. Import / Export doesn't include tempo information.

NRPN is a 14 bit controller, where CC# 98/99 are the MSB/LSB of a 14 bit pair. CbB is showing both messages as one entry (i.e. CC98 = 0 / CC99 = 111) , because they're meant to be interpreted as a single 14 bit message.

The key information would be in the Range panel - I suspect the ranges are different for some reason (probably automation or tempo envelopes after the project end).

I've got a couple of these, and also a couple of ADA8200's. The ADA8000 is fine for line levels, and the outputs are pristine, but I found the mic-pre's a bit harsh/brittle sounding. The ADA8200's are much better in this respect with it's "Midas designed" mic pres.

This is the one I use now. The great thing is I can use my 18i20 for one of the inputs/outputs, which has my bread & butter gear (keyboard rack / guitar fx processor / vocal processor) permanently connected. It also lets me easily swap back to the 18i20 if I'm taking the RME elsewhere. The other I/O's are connected to three Fostex VC-8's - two of them fed from the direct outs of my A&H MixWizard WZ3 16:2, and one from my preamp "collection". The best thing about the RME Digiface is that you can upgrade the pre's / converters as and when you need. The VC8's aren't exactly the top of the range, but they suit my purpose for now until I feel the need to upgrade... and I can do so without changing my interface.

I can almost guarantee this is the cause. Cakewalk will automatically refresh activation if it's logged in and it detects you're close to needing an activation refresh.

Is your project empty? The most common reason for this is having "Stop at Project End" checked ( bottom of Track View "Options" menu).

No, it's not mandatory. Quite often programs like TONEX (NI Massive is another) have an internal library database of all their presets, libraries etc - in TONEX's case it's all of its amp models. When this is run from inside a DAW while the plugin is first being loaded, it can cause the DAW to think it's being unresponsive and something has gone wrong. Massive used to take literally minutes to update its patch library. Other things that can happen after updating is checking the your authentication is up to date. By running the plugin in standalone mode, it allows it to update its internal database in its own time, meaning that when the DAW loads it as a plugin, it responds instantly. Yes - just do a normal scan without a full reset. If the plugin parameters have changed for whatever reason, it will allow Cakewalk to pick this up.

Are you definitely running the very latest version of Cakewalk by BandLab? The back-end servers were changed earlier this year to support the new Sonar, and earlier versions of Cakewalk will be trying to connect to servers that don't exist any more. The latest version (as of this post) is 2024.02 build 98 (29.09.098).

From what I could see, it was TONEX that was crashing Cakewalk - not the other way around.

What I normally do with these: 1. Create a new project based on the Basic template 2. Navigate to your old project folder in the browser 3. Drag the project from the browser to a blank space in the track view 4. Delete the two tracks (Audio / Midi) that were created as part of the template. This ensures all imported audio tracks are created with a Pro Channel.

So Tonex 1.6 was installed, I updated to 1.7.1 and it crashed Sonar... so I did my usual with VSTi's that are also stand-alone: 1. Run Tonex standalone... let it sort itself out, then exit the app 2. Run Sonar 3. Run VST scan from Preferences 4. Drag Tonex into an FX bin - success! I recommend following these steps for all VSTi's that have a stand-alone version.

The buses are matched by name - are you sure the Master bus has exactly the same name as the one in your template?

In the Plugin Browser, plugins (both synths and effects), can live in more than one category. You could add a category of _Favourites (note the underscore at the start so it's always at the top), and add all your favourite synths in there. Then simply drag the synths from there into your project.

I saw a similar article last week. It's worth pointing out that oldest CPU supporting the SSE4.2 instruction set is the Sandy Bridge Intel i7's, which were 2nd gen i7's ( released in 2011, discontinued in 2013). My DAW PC is running Ivy Bridge (i7 3770), which is 3rd gen i7 (released 2012, discontinued 2015). I tried an upgrade to Win 11 on Friday using a Windows 11 iso downloaded direct from Microsoft, and Rufus to transfer it to a bootable USB stick while also removing the TPM / minimum processor requirements. I also checked the options for Rufus to remove the need for a Microsoft account to log in. The upgrade worked fine, and most of my software worked without issue - the ones that didn't were due to them needing re-authed for the new OS.

Sounds like you've got some lookahead plugins. Mastering/Linear Phase plugins will cause this. They're designed to be used at mixing/mastering time and should be avoided at tracking time.

Just a FYI - when you start randomly getting dropouts you didn't get before, check the date... it could be Windows downloading updates in the background. Small updates don't really make much of a difference, but the feature updates can definitely slow the machine down significantly. I've been caught out by this more times than I'm prepared to admit, wasting hours troubleshooting only to find it automatically "fixes itself" later.

FYI - regarding latency with automation... for VST2 plugins, the automation resolution is restricted by the current buffer size. So for a buffer size of 1024, you may experience up to a 1 second lag in picking up automation (unless your automation happens to land exactly on the buffer boundary). Reducing your buffer size will help to mitigate this. VST3 doesn't have this limitation.

PerfectSpace is 32 bit, which is probably the issue. Sonar's BitBridge was originally included to ease the migration to 64 bit while the majority of plugins were still 32 bit. It's very naïve in its implementation, being (a) based on Windows XP technology and (b) only doing a simple pass-through of the VST commands. I use the JBridge wrapper for pretty much all of my 32 bit plugins to avoid these sorts of issue. If you've got JBridge installed, just check "Load using jBridge wrapper" in the plugin properties. For plugins that are already using BitBridge, the properties can be accessed via "Cakewalk Plugin Manager" in the Utilities menu.

<spelling nag> Actually French Kiss is exactly what "Buss" means... quite different from the "Bus" you send audio to.... </spelling nag>

You could take a look at ReaStream - it's a VST plugin that comes with Reaper. IIRC, you put ReaStream on a bus, then send your audio to it. ReaStream then sends the audio stream out to a configured IP address/port. On the other machine, you have ReaStream on another bus that is receiving the input audio via the network. I think it's original design was for use over a LAN, so I've no idea how well it'll work over a WAN - it should work, but expect some significant latency.

I'm not seeing any change in behaviour with the notes edit box. When clicking to edit notes, the cursor appears at the top left, which is the same as it is in CbB. If you want to add notes to the bottom, either click again in a blank space, or press CTRL + END, and the cursor will move to the bottom.

MIDI latency was an issue that gave me grief for years, until I worked out what was going on. In Preferences->Project->Clock, you can choose your clock source. It defaults to Audio, which is by far the most accurate and reliable. The only issue is, you need the audio engine to be running for this to work. If you've a MIDI only project (like I used when I used racks of MIDI synth modules), then this isn't going to work unless you have audio or a soft-synth in your project. If you don't, then the timer essentially isn't running, and MIDI timing is all over the place. If you're recording only MIDI, you could set the clock to "Internal" - this will work for MIDI only projects, but its accuracy can then depend on whether the high-resolution timer is enabled both on your motherboard and in Windows, and how well they play together. Sometimes enabling the high-resolution timer can make things better, sometimes worse, and in many cases can cause a whole bunch of other system instabilities/blue screens if its set wrong.... best not to play with it. Really. Feel free to try the "Internal" clock setting - if it works right away, great - but don't mess around with high-res-timer stuff unless you really know what you're doing and know how to revert it. By far the easiest solution is to leave it set to Audio, then insert a soft synth or an audio track with a silent clip, and do this before you start recording any MIDI.