John T

I've been banging this drum for a while myself. I don't exactly miss the old days or anything, and my objections are also not aesthetic ones. I think it's just inarguable that functionally, the new design is less at-a-glance readable *and* less internally consistent than CbB / old Sonar in many areas. I understand that it's a small team, and what they achieve regularly is impressive. But if there isn't time / money / whatever for a solid UX designer to take a pass at it, we really could do with more customisation.

Ah! I always assumed Global contained everything, but I see what it means now.

As the title says. Would be really handy to have key bindings for both "on / off" and "all / selection".

Got a strange behaviour which I think is new to the latest build. Every time I load a new project, then save and close it, the Quick Start menu grows vertically. I don't mean it adds new items to the list, that's expected. I mean the actual window itself. It's now too tall for the screen, and I can't access the X to close button. It resets itself after restarting the program.

Really great to see all these frequent updates and fixes lately.

Sure, but it would be way nicer to elimate that step entirely.

I remember talking about this on a thread a few years back, as a thing we might get one day. I do a *lot* of splitting out a section of audio to edit in an external editor, via the Utilities menu. This clip is then sent back to Sonar when the editor is closed. The current behaviour is that the entire wave file is sent to the external editor. The only way to only send the section that's been split out along is to right click it and select "Apply trimming" before sending to the external editor. Can't speak for anyone else, but I *never* (not rarely, but never) want the default behaviour. So I'm going right click > apply trimming, I dunno, hundreds or thousands of times a month. Would be great if this could be streamlined. Make it an optional switch if needs be.

In CbB's start screen, I used to click in "existing projects" to browse the drive. And this would remember what the previously used folder was. In the new Sonar version, the nearest equivalent seems to be selecting the browse icon in "local projects". This doesn't remember the previously used folder. The use case for me for this is multiple projects in a single folder (for spoken word / audiobook / podcast stuff), going back and forth between different projects quite a bit. It has become very un-quick :) Is this something I can change with a setting?

Hmm. This seems to have stopped happening. Not sure what I was doing, but I now think it must have been some kind of user error on my part.

Subscribed.

Yes, that's the version number.

In the latest build, my control bar is resetting to defaults every time I open a project. Is that a new behaviour? I've only just switched from CbB, where this didn't happen.

I feel like you've not read the very bit of my post you've quoted. What you propose *is* "picking away at it piecemeal". I'm saying that's not a good approach.

The UI stuff is the one thing that stopped me moving over to Sonar sooner, and to be honest, still would if CbB wasn't being retired. It's not that I'm stuck in the past. The new Sonar seems really good, but honestly, this kind of thing is really letting it down. I'm not fussed about theme editors or anything like that, and it's not a question of style or attractiveness or whatever. This is just baseline UI readability stuff. I know it's a small team, and I'm sure there's not time or resources available for someone to full time specialise in UI. But I think it sorely needs a thorough design pass, from someone with a solid grounding in UX stuff (not just visual design) rather than picking away at piecemeal. There are many issues with readability throughout the application.

This is a great feature, but what would be really handy would be if it could be set to show on all EQs whether switched on or off. Would be handy for just getting a quick overview without having to switch them all on. Would also gives a really quick pre/post EQ view by switching an individual module on and off.

I've also got this problem.

I can... that'd be great if you could take a look. Where do I send it to?

Hmm. Still laggy with a new project.

Ah, that's an interesting point, yes. I'll try creating a project from scratch rather than just testing an existing one.

Ah, thanks, that's useful data. I do think (and hope!) that it's a config problem.

Display scaling is 100%, so presumably native.

No, and not really doing anything much display wise. The waveform is zoomed in vertically, and that's it really.

That's not the issue. With them on or off, the difference between CbB and the new Sonar is still there. I tried making a video, but it doesn't really look like anything; you kind of have to feel it.

With respect, I'm not asking how to do this. I've worked with thousands of hours of narrative content, and have been doing what I describe successfully in Cakewalk for nearly a decade. The track is not compressed; as I mentioned, it's very zoomed in.

So... among my audio jobs is audiobook and podcast editing. It's probably about a third of how I make a living. One of the things I do (in Cakewalk bB) is scan along a *very* zoomed in waveform looking for bumps and other messy sounds *before* even listening to the thing. This is many orders of magnitude faster than just doing it by ear, starting and stopping for every fix. Of course, you still have to do a full listen, but the amount of stuff you can knock off in better than real time with a method like this is enormous. Looks like this: In that view, I'm using CTRL+PgUp / PgDn to flick through a couple of seconds at a time. Anyway, since I'm not going to have the option to work in CbB from some time in August, I've been testing out what the impact of the switch to Sonar will be. For most use cases I have, and certainly for music mixing, I'm fine with it. However, for the specific case above, Sonar is significantly more laggy than CbB. CbB is more or less instantaneous, where there is a tangible lag in Sonar. This is genuinely going to impact my efficiency and work rate. Anyone got any ideas as to why this difference exists? Is it something I can fix with a setting somewhere?