PJH

Hi everyone,

I have a problem where CBBL doesn't recognise my MOTU 16A in ASIO mode anymore but SONAR does. If I go to devices in preferences in CBBL the MOTU is greyed out.

Anyone have any ideas what could have happened and how to fix this? I am using the latest drivers etc.

Thanks!

On 1/11/2025 at 4:55 PM, jack c. said:

real nice.jack c

Thanks Jack!

On 1/6/2025 at 10:22 PM, AndyB01 said:

Happy New Year Peter.

Beautiful vocal and great guitar work. Mix sounds really well-balanced to me and works very well. Love the build at the end of the bridge and the sax solo - very retro.

Great stuff.

Andy

Thanks for the comments, Andy! 

Cheers!

Hi Mark, I really like this! I agree that you should concentrate on the melody at the beginning. 

Definitely worth developing! Well done!

On 1/6/2025 at 5:18 PM, equality said:

Nice and easy listening. Very well performed and a enjoyable video as well. Sometimes lots of reverb can be disturbing but the athmospheric mood of the song suits it well. Perhaps the sax a tad up in volume would be the only suggestion from me. 

Thanks for the comments! There's actually not a huge amount of reverb on anything. I did apply the exact same reverb settings on everything though and it seemed to make the whole mix come together nicely.

Cheers!

Happy 2025 to everyone!

I've been busy revisiting an album from 2001. It was originally released on cd and I recently found the original multitracks so I decided to remix and remaster the album using the latest version of Sonar.

It was essentially a duo (myself and a singer by the name of Sherry Wilde) The name of the album is Nowhere Land and we called ourselves Age of Innocence. It also features Clint Zerf (piano) and Phil Holder (sax).

I think that the original version was recorded using Cakewalk Pro Audio 8 or 9.

I've put together a video of the first track (Dreams) off the album.

Hope you enjoy.

Just now, Noel Borthwick said:

I like to fix a bug for Christmas - glad it’s sorted. Merry Christmas
Since nobody was able to reproduce it I suspect it’s something within your project. I’ve seen some bizarre issues in the past where certain plugin copy protection schemes were locking project files intermittently. Not impossible that your issue was similar.
Auto save is now deferred by a few seconds after the change is detected.

Brilliant! As I mentioned, your prompt response is really appreciated!

Once again Noel has stepped up and solved the error.

Just before Christmas he sent me a new build to check out (which wasn't successful) and then he sent another new build this morning to test which seems to have sorted the problem.

Noel, thanks so much! Your support has been amazing!

Much appreciated!

4 hours ago, Noel Borthwick said:

I sent you a build to evaluate.

Thanks Noel! I'm going to test shortly and get back to you!

1 hour ago, Noel Borthwick said:

It would appear that somehow autosave is trying to sneak in and save before the bounce fully completed. What are your autosave settings?
I can't say with certainty since I cannot reproduce this, but I've made some changes that may prevent this from happening. 
Also made some improvements to auto save for next version.

Thanks Noel, it definitely seems to be linked to autosave. 

Look forward to the next release. 

2 minutes ago, bitflipper said:

I have not seen this, but I'm willing to try and reproduce it. Could you provide more detail about your bounce process, e.g. are you combining tracks, embedding fx, creating a new track vs. bouncing in place?

You might get additional information by enabling more detailed error reporting. Here's how you do that:

Just bouncing two clips into one.

16 minutes ago, Bristol_Jonesey said:

That clip looks as though it isn't selected

Yes, as I said, the clips bounce perfectly.  It's just the error message that's a bit disconcerting. 

I get this error everytime I bounce to clips. The task is performed perfectly but I get this error as well.

Does anyone else get this?

45 minutes ago, 57Gregy said:

Considering all the work that went into helping you (and others) with this issue, you might consider changing the title of the thread? Maybe add 'Solved' to it?

Good point! Done!

23 hours ago, Noel Borthwick said:

Is it ok now?

Unfortunately still very difficult to see unless the theme is changed to a light colour. Only problem with the light colours is that the overall look is very harsh.

30 minutes ago, DeeringAmps said:

@PJHthe latest version dropped 15 hours ago. Did it fix your issue?

t

Yep, definitely fixed!

Thanks to Noel!

I spent the entire day working in Sonar - not a single hiccup!

55 minutes ago, John Faughey said:

fantastic!!! i hope this will be addressed in a future update!

I've just heard from Noel that they are making some improvements for this next imminent release and that they are considering further colour improvements in the future.

5 hours ago, Starship Krupa said:

This, along with smaller font sizes for text in multiple places, is my number one gripe about Sonar. Close behind is the invisibility of the Aim Assist line in PRV in the light schemes.

I like the new look, now when I open Cakewalk by BandLab, even with one of my own custom themes, it looks clunky by comparison. I spent many hours creating Cakewalk themes and I'm fine with no longer being able to use them. Sonar just looks so much slicker.

But those damn measure and beat lines! It was great when we had control over them via the custom colors preference. Mine were very contrast-y, red on a dark background. Now I can barely distinguish them, I have to use the Aim Assist line and the ruler to try to line things up, and sometimes I miss by whatever the smallest snap size is and don't realize it until playback reveals that it's not in time. So trying to line it up visually has failed in that case and I have to rely on another sense.

I've asked, begged even. I don't understand why the feature was removed and I don't understand why it still hasn't been restored. I don't recall that people ever got into trouble due to changing the color of their grid lines.

Thanks for speaking up about it.

I'm communicating with Noel about this at the moment. He requested a screenshot. so I've sent him a screen shot of the grid lines in the track view with the grid lines in front of the clips.

7 hours ago, Noel Borthwick said:

Yes this is indeed a Sonar bug but related to persistence. It will be fixed in the next update.

In the meantime, before saving your project, make sure that the Loop Construction View window is closed. This also fixes the problem.

36 minutes ago, sjoens said:

 For me it's better to import the clips and settings into a brand new project each time I switch DAW versions.  Each time I migrate a project thru several versions of Cakewalk the more crashes and other weird things happen.  This is why I keep all versions back to 32 bit Sonar 8 installed on each system I've run.

Not so easy on newer systems tho.  I just installed the initial version of X1 Producer and ProChannel did not work.  Once I had all the updates thru X1d Expanded up and running, it works fine.  Only issue so far is when moving the Plugin Manager window across the screen it leaves remnants of itself.

Windows animation is off.

 

The interesting this is that this wasn't an old project migrated from CBL. It was a new project which was created in Sonar. 

The only reason that I went back to CBL was that it started crashing in Sonar.

33 minutes ago, Bass Guitar said:

Why do I bother, the last 3 answers I gave on this stupid forum resulted this sort of reply. Signing off. 
 

Yeah, I'd like to apologise for my outburst BG. I went against my better judgement and decided to take out an annual subscription (which I normally wouldn't do as I prefer "owning the software"). I was annoyed with myself for doing this and I took it out on you. Not acceptable so I do apologise.

I've corresponded with Noel and he's given me a few options to try. I'm going to test tomorrow and get back to him.

It's a strange problem. The project will load (the dialog box at yhe bottom right states "loaded successfully " and then I think it's loading the GUI and all of a sudden I'm back to the desktop.

If I open the project in safe mode and I allow all the plugins in the project to load one by one, the project then opens perfectly. If I then save it under a new name it opens fine.

If I then go back and try and open the previous version it kicks me back to the desktop.

Anyway, I do appreciate the suggestions and will post any fixes if we find any.

21 minutes ago, Bass Guitar said:

This!  Do it.  Noel offered his help and you sort of ignored him.  He takes these things seriously and they need the report as it is what in the end makes Sonar stable. We all benefit from users cooperating with this. 

And if you go into the crash dump you will be able to possibly see what caused the crash. But there's always more to it that is best those who can decipher have the info. 

Windows Debugger, also known as WinDbg, is a tool made by Microsoft to help troubleshoot bluescreen minidumps. Windows Debugger is a tool that helps you read the minidump file. 

 

Find out the facts before blurting out stuff that you are completely unaware of. 

Noel and I have been communicating regarding the issue.

It seems that I was a bit hasty. After removing the plugin I was able to carry on working in Sonar but after saving and re opening the next day, same thing. Sonar states "project successfully loaded" and then the program disappears and I'm back to the desktop. No message, no dialog box.

Once again though, it opens perfectly in CBL.

I reloaded the project in safe mode and it looks like it was the Fabfilter Pro R reverb plugin.

As I mentioned before the same plugin doesn't crash CBL.

Regarding the vertical grid lines, has there been any mention that the issue is being addressed?

I've started to regret my decision to upgrade already. The first thing I've come across are the difficult to see vertical grid lines which cannot be altered if using the Tungsten theme.

The second problem is more serious. I have a VST synth loaded in a multitrack that consists of about 24 wave tracks and everything was working perfectly until I had to save and close. On re opening the file Sonar shuts down immediately. 

The interesting thing is that I'm able to open it perfectly in CBL. No problems.

Not a great start.