John T

Yeah, that's a substantial improvement.

It's a minor point, but I was a bit surprised to see that the Console Emulator and Concrete Limiter ProChannel modules don't have the new UI style.

Here's an example in dark mode. You know, the mode for tough men who carry a dagger between their teeth while they produce music.

And pushing a mouse around used to be such a robustly masculine pursuit. We live in a benighted age.

That's interesting. My overall impression is that the new version is the sharper one. I'm on dual monitors, both HP, both 1920x1200, which is native resolution. Windows display scaling is 100%.

I think the two existing attempts to replicate Tungsten and Mercury are a bit... unfinished, perhaps is the generous description. I think the default "dark" is actually a better take on Tungsten, if you give it a chance. Takes a bit of time to adjust of course.

It's definitely odd, and a negative, that lots of text fields have smaller fonts and yet don't fit as much text in. Right now, that's the big obvious clanger for me. I assume that's some kind of font spacing rule that's not too hard for the developers to iterate on.

Tell you something I really like, that I don't think anyone's mentioned: This is great. You just drag an effect from the browser into the sends area of a track, and it creates a bus with that effect in and a send routed to it. Such a small thing that removes a ton of clicks. Really nicely implemented.

Ah, indeed it does. Thought it wasn't before, but I just didn't have the EQ turned on on the master bus. That does give me a thought for a feature request: the ability to have the analysers on on channels where the EQ is inactive.

Really like this! Is it going to be added to buses too?

Just downloaded this and had a poke around. Seems promising. Overall, I like the flatness, though of course, it's still a bit raw in its present version.

What the manual calls "Quick Groups" is how this is done, but unfortunately it's not universally applied, and I don't think it works in plug-ins. But basically, you select multiple tracks by CTRL+clciking them. And then you hold down CTRL while you move a control. Where this has been implemented, that control will move on all selected tracks. This works well on the console and track view, and on many (most?) controls in ProChannel modules. But I've just checked, and it definitely doesn't work in the Sonitus compressor. I think it probably doesn't work in any VSTs.

There's a bunch of stuff to consider here. As CSistine says, there are uses of the term "bit depth" that are unrelated. First thing to get clear is that audio bit depth has *nothing* at all to do with the system processor. Disregard that completely. Also, Cakewalk will happily have files of different bit depths in your project. You may well record at 24 bit, as per your audio interface setting. But you may have dragged in a 32 bit file from elsewhere. Or - more likely - you've ended up changing a file to 32 bit by doing a bounce or freeze. Cakewalk's default setting for that kind of in-project rendering is 32 bit. If memory serves, this file stats box in the browser shows the highest bit depth of all the files in the project. So it's unrelated to either the project bit depth, or the audio interface bit depth. For the most part, you don't really need to think or care about this, these days. Always record at 24 bit, and mostly the software will take care of the rest for you.

If it happens again, we should call in the rockers too.

Have noticed a behaviour change with the new update. Previously, I had auto crossfade on all the time, which is useful for my workflow, but I could use S (or ALT+click) to split a clip without it doing a crossfade, which is also useful for me. Now having auto crossfade on also crossfades S-splits. Is there a way to get the old behaviour back? Switching auto crossfade on and off is slowing me down quite a bit.

AMEN

By the sound of it, it's currently just a global scaling level for the whole application. But independent zoom levels for some views would be a great feature for the future. EDIT: Mainly I'm thinking that I like my main / track view as it is, but would like to scale up my console view a bit. That kind of thing.

Reading through a chunk of this thread and just idly wondering if there's still a block function in this version of the forum. Can't seem to find it. Asking for a friend.

I miss the Munch Button.

Is anybody excited about scalable UI? Cause I think that's kind of exciting. For one thing, it'll make touch screen use much more viable than it's ever been in Sonar, despite it having had a decent fundamental implementation for years. I've tried it a bunch of times, and only really been defeated by the smallness of many of the controls. I can see a lot of potential in that.

It does! You hold down ALT (on the console, not your keyboard) and press the "SEL" button for the track you want to branch. Repeat to get back to regular mode.

+1 to this. I'm a big fan of Spitfire, and a user of BBCSO, and it's great. But it is kind of twitchy, and they're not great on bug fixing. If you want a hacky workaround to explore, I've found that it sometimes behaves better in non-ASIO driver modes. But a lot is dependent on what interface and what drivers you have; I've not found a consistent pattern across different setups.

Whatever son.

Yeah that's it. The clip rectangle will shrink as you zoom out until it's only a pixel wide. Then if you zoom out more than that, it disappears entirely. I think two things would improve this; have the clip rectangles never vanish, and always be at least a pixel wide. And also, always have the dots extend to the last clip. Of the two, I think the dots thing is more valuable.

Project 5 was really cool, yeah. But Abelton Live ended up owning that section of the market, so I can see why they gave up on it. But a really important and under recognised part of the development of computer-based music production, IMO.