John T

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?

Another vote from me against this now time thing, though not entirely. I can completely see the logic of moving it; it made no sense where it was. However, I think this is an example of under-solving a problem. It sensibly belongs alongside the main now time, but there's not actually room to make it readable without redesigning that box more throughly. "Just make it tiny" is not a solution. A swing and a miss, IMO. To generalise this point a bit, I dabble with each Sonar version as it comes out, but I haven't yet got a membership. The subscription model isn't my favourite, but it's the generally worse readability than CbB that's actually holding me back. The main interface is quite good, but things like this and the pro channel EQ UI are frustratingly inferior to the previous versions.

Having to warn people about ASIO4ALL in the year 2025 is like having to warn them to stay out of fairy circles and always keep garlic above the door or something. I'm surprised there are even still websites mouldy enough that you can download the thing.

This seems a likely candidate. I've just discovered that it's not happening on *all* projects. Will do some investigations.

This seems a likely candidate. I've just discovered that it's not happening on *all* projects. Will do some investigations.

Neither of those things. Export starts a few mins into the timeline in this case. And exporting as wav.

Using last version of CbB. Am just doing some experiments with masters for an album where one track flows seamlessly into the next. I have a solution for the time being, and will assemble it in HOFA instead of Cakewalk, but I have discovered something odd. Seemingly no matter what I do, I end up with 0.033 seconds of silence added to the start of the file. Am exporting by selecting only a clip in Cakewalk, and the audio data in that clip starts right away. Anyone ever come across this?