msmcleod

This is expected. CbB only supports a track delay in ticks. Sonar has an additional flag saying whether this delay is in ticks or ms. As the cwp format is both forward and backward compatible, CbB will load the Sonar project but will not recognise the ms flag, so it interprets it as ticks as that's all it knows about.

Not sure if this will help, but I had a ground loop in my live rig at one point that took absolutely ages to track down.... and yes, they were all powered by a single outlet. The issue was I had two rack cases on top of each other, and the rim of the two cases were touching. Because some of the rack's had their own case grounded, it created a ground loop between two or more of the units via the rack ears and the rim of the rack cases. My fix was a bit of tape (well actually a thin self-adhesive foam strip) over the rim of the cases so the rims didn't touch, but equally I could have used insulated rack screws/washers. So TDLR - don't just check connections, check what they're screwed into too! The way to troubleshoot is unscrew everything from the rack (but leave them plugged in/connected) and make sure none of the units are touching - if the noise goes away, that's your issue.

Which stretching algorithm works best is very material dependent. "Radius Mix" is one of the older algorithms, and although it works well on some material, you may find the Elastiqué algorithms work better. There's also the "Groove" algorithm, which works well if you want to stretch both time (to match tempo) and pitch (to match pitch markers). It's worth mentioning however, that any stretch algorithm is going to have limitations and the quality of results will get worse the greater the stretch is. The preferences page sets the default algorithm, however you can set the algorithms used by clip in the clip inspector after selecting the clip: IIRC, the default is Elastiqué Efficient for Online Render (i.e. live playing), and Elastiqué Pro for Offline Render (i.e. bounce). The reason there are two is because high quality stretching is processor intensive, which can make edits annoying as you wait for it to adjust things. So you use the lower-quality-but-quick online method to get timing correct, then bounce using the high-quality-but-slow method when you're finished. If you also want to keep the original clip after bouncing, I suggest duplicating the track and archiving one of them before bouncing. This will allow you to use the higher quality bounced track, but also giving you the option of going back to the original if you need to change anything.

Do you have a dialog open in the background perhaps? Try using CTRL + TAB to see if there are any other windows waiting for input.

Although not officially supported on Windows 7, Cakewalk by BandLab (CbB) works fine on Windows 7 (64 bit only). You'll get a warning message when installing, but beyond that it should work fine. We don't support Windows 7 since Microsoft has stopped support on it. Given that development has essentially stopped on CbB, it's unlikely that CbB will stop working on Windows 7. CbB is a vast improvement over SONAR X1. There are literally thousands of bug fixes and many new features. Don't uninstall SONAR X1 though - you'll want CbB to migrate all of your settings and take advantage of all the shipped 3rd party products you got with SONAR X1.

To do it as you describe: 1. Add a new MIDI track, and arm it 2. Start recording and hit the same note on every down beat throughout the whole piece 3. Select the MIDI clip you've just recorded, then select "Fit Improvisation" from the main Process menu at the top. This will create a tempo map based on the timing of the MIDI notes recorded in step 2.

Actually, "All Inputs" has been there for as long as I can remember. "All External Inputs" was recently added however, which ignores the outputs of any software synths.

The only way I know works is by using WASAPI shared, as this aggregates all the devices. You should be able to use ASIOLink and open the USB mic as a WDM driver. I used to do this with my Focusrite 18i20 & mLAN setup, where ASIOLink would open the 18i20 in ASIO mode, and use WDM for the mLAN audio ports. In all honesty though, it became such a nightmare to configure all the time, I reverted back to using a small analog mixer, where everything went through the analog mixer and came back through the inputs in my main ASIO interface or through my onboard Realtek line input. Given the ASIO limitation in Windows, USB mics are really only good on a Mac. Sometimes it's easier to go old school. I use Thomann's T-Bone version of this:

I suspect the issue is that VB-Audio Matrix is grabbing the ASIO drivers of the other audio devices, preventing Sonar from opening them. Why it crashes is another question... the drivers should either be fully open by VB-Audio Matrix, or not at all. VB-Audio Matrix is probably leaving the ASIO drivers in a state Sonar doesn't expect. FWIW, I didn't have this issue with ASIOLink which also opens other ASIO drivers, so something VB-Audio Matrix is doing is leaving things in a weird state. BTW - you shouldn't need to uninstall / re-install Sonar - deleting or renaming AUD.INI would have sufficed.

The darker plus signs are meant to indicate that it's disabled - and it's disabled because you've not selected an articulation map to add to your project.

FWIW - I'm not seeing any issues with UVI Workstation here.

@Archerdrummer / @Waldemar Pawlik - can you confirm whether this happens in all cases, or only when the PRV is open?

If the exe is the full installer (~500Mb) , then yes - if it's an update installer (~50Mb), then no... maybe @Jonathan Sasor can send you an installer for the previous build to check whether it is indeed a 2025.02 problem. Given that both myself and others are not having a problem however, my gut feel is that it's not the 2025.02 release. It's more likely a Windows update or installing something else has upset things. If this is the case then rolling back probably won't make a difference. I'd advise: 1. Use the Windows system file checker to verify that your Windows installation is ok: run sfc /scannow in an admin power-shell ( Windows Key + X, then press A). 2. Ensure the latest VC++ redists are installed. There's a link to a bundle of the latest MS VC++ redists here:

Good find... I had this problem a few years back... random freezes, blue screens etc... took months to find out it was a bad memory stick. You're lucky you spotted it.

Not seeing any issues here with BFD3 using those steps.

Have you tried the link to HyperCanvas above? It's almost identical to TTS-1.

There have been discussions but nothing concrete. FWIW the removal of TTS-1 was by request of Roland - it's their IP.

IIRC Groove3 has tutorials on both MixControl and Focusrite Control. I'm not sure how good the Focusrite Control tutorial is, but I'm using 1st gen Scarletts, and the MixControl tutorial was invaluable. In general when dealing with audio interfaces, you have the following: 1. Hardware Inputs/Outputs 2. Inputs/Outputs as seen by your DAW 3. A mapping between 1 & 2. Most people assume that 1 & 2 are the same thing - and by default they're probably set up to look that way. They're not the same though, and once you start messing with things you can get unstuck pretty quickly. I made this assumption too at first, but the tutorial corrected that for me. Having not seen the Focusrite Control video, I can't really go ahead and recommend that specific one (and there are probably free tutorials on YouTube in any case), but it is well worth watching one or two tutorials just to help get your head around how the routing works before it even reaches your DAW.

FWIW I'm using Windows 10 still and not seeing any issues. I've got two Windows 10 boots on this machine: one is my dev boot, which has a bunch of random stuff on it, the other is my DAW boot which is relatively clean. Neither have any issues with text/fonts.

There isn't one. Cakewalk will only automatically insert TTS-1 when opening a MIDI file if: 1. You have TTS-1 installed, and 2. You have no hardware MIDI outputs defined. The way to do this is: 1. Copy the TTS-1 folder from your old machine into the new one (into the same directory, i.e. C:\Program Files\Cakewalk\Shared DXi\ ) 2. Launch Power Shell as administrator (Press Windows Key + X, then press A) and enter the following: regsvr32 "C:\Program Files\Cakewalk\Shared DXi\TTS-1\TTS-1.dll" [EDIT] - Just tried out the Hyper Canvas @cakerun suggested. This works pretty well and is almost identical to TTS-1. I'm running it JBridged, although BitBridge also worked fine. The advantage here being that it'll not crash CbB/Sonar - the worst that will happen is JBridge/BitBridge will crash should there be a problem. [EDIT 2] - Turns out JBridge is problematic - CbB/Sonar hangs when trying to re-open the Hyper Canvas UI. BitBridge works fine.

All MCU buttons send Note On messages when pressing the button down, and Note Off messages ( or Note On with velocity = 0 ) for releasing the button. Scrub is note value 101 decimal ( 0x65 hex ). Bank Down/Up are 46 / 47 decimal ( 0x2E / 0x2F hex) Alternatively, you could just send the correct note value for switching to tracks / buses: Switch to Tracks: 76 decimal ( 0x4C hex ) Switch to Buses: 80 decimal ( 0x50 hex )

For really old projects (Sonar 1 to Sonar 8.5) and old .wrk files (Pro Audio 9 and earlier) I always use this method: 1. Create a new project using the Basic template. 2. Browse to your old project in the browser 3. Drag the project from the browser to an empty space in the track view. 4. Delete any unwanted tracks This ensures: 1. The master/preview/metronome buses are present 2. All audio tracks have a valid Pro Channel configuration.

Get a rack blanking plate - the mesh ones look better IMO:

Get a rack blanking plate - the mesh ones look better IMO:

Just to clarify: The offset is in the transforms section, not the triggers (i.e. key switches) section. It applies the offset to all notes that fit the specified criteria for the duration of the articulation, so the actual notes will be played earlier (for negative offsets) or later (for positive offsets) than they show on the grid. For the time being, there is no offset for triggers/key switches. You can however set the articulation to start slightly earlier which will have the same effect. What I would do here is have a single track per instrument, but use multiple articulations on the track. In other words, you'd have a Cello Legato articulation and a Cello Staccato articulation. Both articulations would contain the key switches necessary to switch to that sound, but also optionally a negative note timing offset to make up for a slow attack for any notes playing while that articulation is active. As mentioned earlier though - note timing offsets are only available in Sonar, not CbB.