Matthew Carr

A difference in behaviour from CbB, which seems like a bug - apologies if this is not new to 2025.06, this is the first time I've really used new Sonar 1. Click and hold on the timeline to begin a selection 2. Hold and drag mouse pointer off the far right of screen In Cbb, this would advance the selection end, and the waveforms displayed in the track view would scroll in sync with the end of the selection In Sonar, the selection end is advanced, but the waveforms only refresh their display once either a) the mouse is released or b) the mouse pointer is moved back to the left to be on screen. This makes it very difficult to fluently select ranges longer than what is currently displayed on screen as you can't see the waveforms for the current end selection point.

That sounds like the reason - I didn't migrate, and probably had CbB open, which although the driver is multi client, may have meant Sonar then defaulted to WASAPI.

Could the membership icon be moved up a line, so it doesn't take a whole line of screen real estate? e.g.

RESOLVED: Default Driver mode was set to WASAPI on new install, instead of ASIO ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Just looking to move over to the new Sonar, ahead of losing activation of CbB Audio outputs look completely different in Sonar compared to CbB, and I'm totally lost! I'm using a Behringer XR18 as my audio interface in CbB: In Sonar 2025.06 Have I missed something here? When I go to select an output for a track, I should have 18 tracks to select from In CbB - makes sense, 18 Mono tracks, 9 Stereo tracks In Sonar, how would I know how to select channel 17 as the input (or any input >8)

Yes, can record (and playback) on all 18 channels - with pretty good latency as well. Not sure what problems you're having with ASIO, but i'd suggest getting rid of ASIO4All as it's just adding something you don't need and may well be causing problems. Once gone, install the latest XR18 ASIO driver from the Behringer site and you should be good to go.

Anyone seen this before? Seems like an edge case bug Occurred when trying to save changes to an existing project No problems when saving the same project file usually.. just when trying to save changes after this session of edits, I started getting the error when saving: One change from normal was that I disconnected / reconnected an audio interface not being used in the project whilst it was open. (UMC ASIO Driver in the list below) Resolved the error by de-selecting all the audio input / output devices being used in the project (X-AIR ASIO Driver [X] in list below) After doing that, the save worked ok without the error dialog. Cheers, Matt Windows 11, latest CbB

Using a modern laptop can be a minefield - there is a tendency from manufacturers to add BIOS level code that hampers performance in order to manage the thermals. No 1 check would be that the laptop you are interested in passes a latencyMon test. Generally that means finding someone on a music forum who has the same laptop and has run the test successfully, or sourcing the laptop from somewhere where it can be sent back without any quibbles - so you can test it yourself when it arrives. No idea about cakewalk running on an ARM laptop, but that would involve a lot of emulation, which given how finely tuned Cakewalk is for x86 I can't think that would be a good idea. This guide is good for optimising a PC for music production: https://gigperformer.com/docs/ultimate-guide-to-optimize-windows-for-stage/index.html

Absolutely! As a software dev myself I would really not want this task - tons and tons of effort to produce something that will undoubtedly come in for criticism along the lines of either 'it's not exactly the same as before!' or 'it's basically the same, why have you not spent all that time on adding features!' ? Haven't had a play yet myself, but from what I see it's looking good and the inevitable snags are being picked up and being resolved quickly - let's not forget this is still an 'early access' build to get feedback, so there will be improvements to come. Bitmaps can add eye candy, but for many reasons are not how modern UIs are composed . This update is essential to support Sonar going forward. Nice work Bakers!

Hmm.. Restarted CbB, now don't get the API error - back to being saved in Bandlab with the CbB project name rather than the name given in the upload dialog

The whole export to Bandlab seems a bit underdeveloped - or I am being a bit dim!! ? I try and do the same operation as above and now I get the dialog I suspect this is because: 1. The selection I am uploading as a 'Test' is always being uploaded with the CbB project name (DX7 Master Set List.cwp), not the name 'Test' as given in the upload dialog 2. The upload is being considered as a revision to the CbB Project name, rather than a New Project - despite the 'Upload as New Project' option being checked 3. The API Call can't find the project to revise as I deleted it from within the bandlab app. So now, I'm stuck - I can't export any sections of this file to Bandlab... ? Can only imagine this is because I am trying to export sections of a CbB project rather than the whole project - If this was the case for whole projects then surely these issues would've been picked up by now...

Been playing around with the export to Bandlab feature, as thinking of using it more Hit a few issues though, anybody had the same or have a solution? When exporting a section to Bandlab, I use the dialog options as shown below, however: The new project is always created in Bandlab with the name of the CbB project, not the name entered in the upload project dialog box! If I only include an audio patch point in the selection to be uploaded, then the upload complains that uploaded Bandlab projects cannot be empty (despite the empty tracks option being selected). If I export the same selection as an audio file to disk, the audio for the patch point is exported If I include a track with audio / midi data as well as the patch point in the selection, then both tracks are exported to Bandlab and the patch point track includes the rendered audio. I guess it can be hard to work out if a patch point has audio, so maybe the easiest option would be to change the dialog above to 'The export may not have audio data, do you want to continue?' rather than a 'Computer Says No' dialog... or just don't show it at all if the include 'empty tracks' option is set Bandlab Upload Dialog:

Seems unlikely, but this is what I get when I visit the site to download the control center in order to install the plugin. Think I'll err on the side of caution... how many plugins (and install managers) do I actually need, lol!

Thanks for the responses, and sorry for the late follow up - have slowly been changing things around and believe the issue came down to a dodgy USB cable, Gah!!...? The new build is working well now, so I'm a happy chappy!

I had something similar. I went to the menu option 'Help' \ 'Sign in to Bandlab' and after signing in, cakewalk authorised. I've just signed out, and no issues with auth

I'm using a Behringer XR18 as my audio interface... might be worth trying it on some other USB ports though, so thanks for the idea!