murat k.

It seems you have a faulty keyboard binding registry. Just save your keyboard binding in a file and delete all lines in the file which contains: Kx00530B Then load that keyboard binding file. There is a keyboard binding bug in the Cakewalk for years, I hope developers will fix it in the final CbBversion.

It seems that some people still looking for an information. Autodesk Revit has a Public roadmap as an example if you looking for one. If you are looking for a DAW about more feature and user count look for Steinberg Cubase.

I guess the problem here are people are afraiding about losing their hopes on the features they want. And maybe the company is afraiding to lose their users when they share a not promising roadmap. If there is nothing hopeful, it is logical that they should not share it. There is no other reasonable explanation. But given what the company has done over the past few years, it looks promising. And sharing the roadmap will be to their advantage.

I understand you. You're worried that we will lose hope. I recommend you not to think like that. Yes I agree with you about the Staff View's development situation but did you see that post? Glenn gave us an idea about implementing the Musescore to the Cakewalk. Implementing a fully functional Music Notation software is easier than making it. So maybe developers consider our thought and contact with them then make a collaboration.

Nope. I will not answer the question that I am accused of the things that I didn't say, it's inappropriate like the intentionally deleted post contains before. If you are still interested in the answers, they're just simple information that is not open to any discussion and can easily be found by research on the internet.

This is not a place for personal arguments. Lets keep the talk in the concept. If anyone needs personal talk can send a PM anytime. This is the right thing to do for the forums peace.

It seems that the message sent to the right place ?

And I appreciate every interaction, we just don't have to think the same way, another way it wouldn't be a discussion.

Nope. The sharing of the roadmap will increase the BandLab's reliability. People will see the product is how going forward. I guess we all like it. Just we want it to be better and don't lag behind of the others. I never accused or insulted anyone even if I get one from other people. In the past the threads I talked are locked because of other peoples inappropriate behaviors.

It doesn't have to be DAW-specific, there are softwares that already have a Public Roadmap and it doesn't make any trouble. The crazy thing it that you as a user against the idea that will be good for us, and please do not talk on behalf of the Cakewalk Staff if there is a reasonable explanation they can share it here as I stated earlier. It has nothing to do with the competition. Even if it's related with it, sorry but Cakewalk is way behind it both feature and user count based. Roadmap will allow us to see when it will come at their level at least about the features. And if you're having fun with lovely surprizes, you just don't lovely look at the list.

No. They'll still work in peace, they already have a roadmap only we just don't see it.

Or if there is a reasonable explanation for the roadmap is not publicly shared that also can be explained in here by Cakewalk Staff.

The roadmap can be shared and updated in a subsection like Early Access in the Cakewalk by Bandlab Section in the forum. It can be open or closed to any discussion. After then we will become able to make our discussions with a clear sight.

At now the same things are requesting over and over again in a state of uncertainty. If Cakewalk had a Public Roadmap we'd see what's come next, and what features are on the list or not.

Just Note Names: Note Names.ins

I decided to conclude the conversation which is started in this thread: It wasn't a bad request actually, only the owner of the topic doesn't know about there is an existing function which already can do that. Also it can be seen in the title the request was containing only opening of the closed panes. Existing function allows opening and also closing the panes. Maybe it could be better when it was requested like double clicking on the same area where the closed pane bar is, even with the opened state, to expand and collapse them. With this way we will be able to sneak up the pane without changing the mouse position, for now we are not able to do that by clicking in the same area without clicking the expand/collapse button. Also reminding the developers that there is an issue with the existing function, it is not working when the pane is not resizable.

Of course, you can start by doing things that you don't need to ask such questions.

Definitely, we are looking for solutions, not workarounds.

Yeah, you're right about that. Separator Bar is only active in the Mixer mode. The cursor icon is not changing to resize mode because it becomes unresizable with the other modes. So this means that double click function is only active when there is a resizable dock.

No. In the OP you were not aware of the functionality of the Separator Bar's double click action. And after my comment you said: So you can't make a demand about a thing which you're not aware of. Only after my comment, you became able to do a feature request about expanding the functionality. After all these behaviours of yours, apology seems not acceptable but I accept it this time. We should be mindful of our behavior from the start and not have to apologize. Even if you use a slang your approach is not appropriate for a comment which points you a solution of your needs.

Also you can't make a demand about a thing which you are not aware of: And I told you the way: And please use an appropriate languge when you're talking to other people in the forum:

No. You can expand and collapse any of them also including the Inspector instead of either click on a rather tiny button or a keystroke.

Double click to "Separator Bar" instead.

Yeah, Cakewalk is astonishing in every way. I hope the astonishment changes to a good way after the implementation.