John T

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.

That's a good point, and I'll see if I can edit it. But if someone wants to say "you're not reading closely enough", well, perhaps they should be reading further than the title themselves.

Hey dude, read my answers again. Or, if you've nothing to contribute - which you don't - go and be rude and brusque elsewhere.

Yes. The dots are meant to show how far a given track extends, as I understand it. So if there's a zoom level where the clip is sub-pixel sized*, then ok, the clip disappears, but surely the dots should still be there? If they're not, then they're not serving their purpose. * arguably, it would be good for clips to always display at least a pixel width line at any zoom level. But either / both solutions work.

No, I know what the dots are, and I do want them to be displayed. This is about dots disappearing when they shouldn't.

I mustn't have explained very clearly. The dots are a good and useful feature, I agree,. The issue is that in the second picture, they stop too early, even though there are clips to the right of them. This seems to be caused by the zoom level. Once you're zoomed out enough for the last clip to become invisible, the dots leading up to that clip also disappear.

Here's a thing that's been a niggle for a long time, but I've never got around to documenting. So, among the things I do in Cakewalk is post production for audiobooks. And when dropping in pickups, I end up dealing with a lot of really tiny slivers of audio. Anyway, here's a view of the dots showing up to the last sliver in the third track (just to the left of the Now Time Marker) Now here's a slight zoom out from there. Notice how the sliver becomes invisible at a certain level of zoom. But more importantly, the dots now don't extend that far, and instead stop at a prior still-visible sliver. I realise this is a fairly fringe case, but would be really handy for me if it got fixed.

I've not upgraded to Windows 11 yet, but as I understand it, nothing about the driver model has changed. So the same process to get it working under Windows 10 should work fine.

Ah, re-reading your post, I see you're not currently using CBB. I suppose I'd say - it's free, so costs nothing to give it a go! Apart from time of course, which I realise is often a limited resource. But to answer your main question, fundamentally, all the big key features work. I use it all day every day to make a living, so that's one person's experience. There are quirks and annoyances, but aren't there always. I can't speak to the video editing experience, if you're talking about the integration with other hardware and all that. Outside of my area. But like I say, it's free to try. And I'd guess at that stuff being fairly standard Roland / Edirol integration anyway. Decent odds that Cakewalk's implementation of stuff makes little difference to that.

There are some bugs, to be sure. I find you can crash the program going back and forth between "EQ" and "Send" on the channel strip control panel, for example. I've just stopped using the send function. And there are oddities here and there. However - and I say this as someone who's been a vocal critic of how quickly support for the vs700 was dropped - it's pretty damn close to "full functionality". Certainly, the two things you mention, surround panner and the T-bar, both work perfectly well. Can you describe what problems you're having more specifically? There are a few of us vs700 users that refuse to quit on these forums, and I'm sure we can help you out.

Honestly can't see anything to worry about myself. Cakewalk staff are replying on the feedback thread for the last version and talking about bug fixes they're working on right now. I'm generally happy for them to take their time. The problem with the monthly pay model towards the end of the Gibson era - I thought anyway - was that it kind of tied them to hustling out a monthly release ready or not, worthwhile or not. Not being tied to that has led to the most consistently stable Cakewalk / Sonar there's ever been, I think. And the new features tend to be more genuinely useful than headline-grabbing, eg: the export overhaul. That's a massive daily improvement to my work process. I'm really glad when they take the time to make sure things are thought through and properly beta tested and all that.

I'm pretty sure automation is part of "events" not "properties". So you need to tick the "events" box in the dialog.

I do have virtual memory set to 16gb. I've just never noticed this before. Is it a recent change, or have I somehow missed it all this time?

My performance module is currently showing as seen in the attached image. Thing is, I only have 16GB of RAM installed. Is this a bug, or related to virtual memory in some way?

This is well worth a look, for anyone who has to deal with this frequently. $49, will check a batch of files and make sure it doesn't convert anything that looks mono but isn't, as Bitflipper refers to above. https://www.soundizers.com/

How dare you. I am 49. ?

If memory serves, Noel said something recently about Bandlab Assistant being in line for retirement soon-ish, so I expect all of this stuff is being looked at.

I think all the functionality is there; in that sense, it's not limited. But you're right that it could be made more friendly and intuitive. And I know Cakewalk of late are very keen to improve user-friendliness.

Yeah, I totally get what you're saying. If you read it a certain way, it sort of sets you up to think "should I open the folder? Is that a thing that I need to do?" UI and workflow design is full of these kinds of things. Perhaps "update now / update later" is what this box should be asking. Or maybe it should just automatically update after downloading.

My first DAW:

I suppose the assumption is that you'll either open the folder to install from there OR install from in the program. So the pop-up is a fork in the path, not a hub, as it were. "Take a look and then install from in the program" has never occurred to me, but I see what you mean.

New format for this in the latest update is great for me, thanks so much. Really clear and readable, and LSR indication clearly separate from the name is a great addition.

Sort of, sort of not. The thing we've been talking about is the prefix numbers which the new update has added. None of those screen shots feature anything like that.

^ I don't understand this post at all.